Related
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,
I've had a good search and can't find any info and have been pointed in this direction for advise.
I've got a spv m3100 and wanted to upgrade to black 3.0.1. I've followed the details given by MrVanx and installed hardSpl 2.10.Olipro first. I checked that this has installed using the ok, start and reset combo. (the installation did seem to be quick thoughm took about 2 secs from the screen on the phone changing to install being complete).
Then wanted to install the latest radio version and this is where the problems started, I ran the .exe making sure the other file was located in the correct directory and that the phone was sync'ed. I got a message saying that could'nt contact the phone and then the following message
Error, unknown version! you should pick sspl
This also happened when trying to install black 3.0.1.
If anyone could help I would really appreciate it. I bought the handset from Ebay and have unlocked it and installed hardspl 2.10 and thats it.
I also want to change the flash load screen to get rid of the orange display as I will be using O2 sim.
Once again, I thnak you in advance for any help.
James
You need to choose force using sspl, you will be ok as you have hardspl 2.10 installed so you should not brick it as you have some protection, it is just that autodetect is not recognising the rom version already installed. Try the rom upgrade first. You need to refer to mrvanx guide as this explains how to change your splash screen to a custom version, post back if all was ok
EDIT:- Black 3.5 is now available!
jamesx10 said:
Hi,
I've had a good search and can't find any info and have been pointed in this direction for advise.
I've got a spv m3100 and wanted to upgrade to black 3.0.1. I've followed the details given by MrVanx and installed hardSpl 2.10.Olipro first. I checked that this has installed using the ok, start and reset combo. (the installation did seem to be quick thoughm took about 2 secs from the screen on the phone changing to install being complete).
Then wanted to install the latest radio version and this is where the problems started, I ran the .exe making sure the other file was located in the correct directory and that the phone was sync'ed. I got a message saying that could'nt contact the phone and then the following message
Error, unknown version! you should pick sspl
This also happened when trying to install black 3.0.1.
If anyone could help I would really appreciate it. I bought the handset from Ebay and have unlocked it and installed hardspl 2.10 and thats it.
I also want to change the flash load screen to get rid of the orange display as I will be using O2 sim.
Once again, I thnak you in advance for any help.
James
Click to expand...
Click to collapse
Thanks BOZ.
I appreciate your response, So I should attempt the black ROM upgrade before the Radio using force SPLL?
I won't now be able to try this until at least next week so I'll have to wait before I can report if all works. Thanks again for your advise. Its all new to me and I'm learning from helpful people like yourself. I've been really lucky that I've found a couple of forums with very helpful members that are happy to advise and assist.
Thanks Again.
jamesx10 said:
Thanks BOZ.
I appreciate your response, So I should attempt the black ROM upgrade before the Radio using force SPLL?
I won't now be able to try this until at least next week so I'll have to wait before I can report if all works. Thanks again for your advise. Its all new to me and I'm learning from helpful people like yourself. I've been really lucky that I've found a couple of forums with very helpful members that are happy to advise and assist.
Thanks Again.
Click to expand...
Click to collapse
You've got it, cheers boz.
If its any help - I had the exact same problem with "unknown version" error. Before I upgraded, I did a hard reset on the M3100 - not necessary I know but I felt happier.
As I had already installed the HardSPL 2.10 Olipro - I simply chose the option:
SPL-2.02/2.10 New Bootloader (rather than 'AutoDetect')
on the RUUWrapper - Hermes ROM Upgrade opening screen and upgraded as per mrvanx instructions (as this offered good protection from bricking my phone)
Upgrade went fine and its fast and so far stable.
Incidentally, I didn't change the radio version, as by all accounts 1.38 is a better version.
Hi!
long time viewer first time poster.
I have G4 CID LOCKED Cingular 8125 with mfrazzz's Crossbow Reloaded 1.7.1 I have wizard love Rom as Base.
I really tried hard to update (I guess it is really a downgrade) my original Radio from 02.25.11 to 2.19.11 but no matter what I do, it failed.
I tried with every romupdateutility_wizard_noid.exe i could find but I get the same result everytime.
ON PC: I get 260 Error (tried in two machines same error message)
and
On my Wizard: stuck in this 3 colored screen. I see 3 color screen with "RUU" in right upper corner and "USB" on left bottom with IPL/SPL version showing in red If i press reset button, it will boot back to mobile windows fine.
Can anybody help me?
My rest device info:
ROM Version: 2.18.0.0 WWE
ROM date:2/14/06
IPL/SPL: 2.25.0001
GSM:02.25.11
Protocol version? 4.1.13.12
ExtROM version: faria V5.0
My Downgrade
All I did was use the rom upgrade utility from the "wizard love rom" (the one that is in Italian) and the T-mobile radio rom listed in the Wiki.
Worked like a charm!
thanks for the reply..
but of course i tried that already.
i think error 260 is communication related issue. PC communicate perfectly with ActiveSync.. but when it reboot for the flashing to occur,it just get stucked as if pc is not communicating with the wizard.
is downgrade to 2.19.11 really worthy?
nic2mit said:
thanks for the reply..
but of course i tried that already.
i think error 260 is communication related issue. PC communicate perfectly with ActiveSync.. but when it reboot for the flashing to occur,it just get stucked as if pc is not communicating with the wizard.
is downgrade to 2.19.11 really worthy?
Click to expand...
Click to collapse
Is your device actually booting up? If so, just download one of the radio ONLY roms. It won't matter whether you have a CID locked phone or not and the radio ONLY rom will not touch the IPL/SPL.
Having said that, is there a reason why you want to downgrade to 2.19? Are you having missed calls issues?
Hi titus666,
I am having the same ROM and missed call issues too.Even when i am on a full coverage area my wizard signals seems to dropping,coming back,dropping ....
What could be the probalem .Any recommended Radio ROMS's.
Probably you read this already
xdawiz said:
Hi titus666,
I am having the same ROM and missed call issues too.Even when i am on a full coverage area my wizard signals seems to dropping,coming back,dropping ....
What could be the probalem .Any recommended Radio ROMS's.
Click to expand...
Click to collapse
A little bit off regarding your initial post but here´s good feedback on how both radios behave.
http://forum.xda-developers.com/showthread.php?t=312834
I've had some problems as well.
I used the tool that came in the download to downgrade to 2.19 (I am having missed calls problem) and it won't.
I'm using a Windows Vista and already did the whole thing to update drivers with the one given on the forum over here, yet, everytime I run the thing it crashes and then I have to go through it all over again.
Its like the driver just doesn't work anymore, even though I have tried "re-updating" it to the one that I downloaded here, unlike the real Roms this one just won't go throguh and wait for the 3 colored screen to come up, just freezes before.
Hello all,
I Eb'd an HTC wizard (cingular 8125) running Wizard Love/NBD WM 6.
On the load screen I get:
AKU 2.3;
IPL and SPL:2.25.0001;
radio:2.25.11;
rom: 6.0.0.0.
My carrier is Tmobile.
Question 1: If my phone has this newer ROM and it takes calls on the Tmobile network it has been CID unlocked and SIM unlocked...right?
I wanna update my rom and think that I am competent enough to do so but there is alot to learn and this is not my full time gig...right.
Question 2: So, if I am correct in Q1 I should be able to flash roms right?
However when I attempt to do so the RUU gives me [error 224]. Active sync and or WMDC says its connected. (I installed the AS drivers in WMDC)
Question 3: Where do I go from here?
Question 4: The wi-fi is currently not working will a new rom potentially clear this up?
Thanks in advance for the time and advice..
grazie
hmmmm,
Well,did you updated to NBD wm6 yourself ? and how did you updated ? which method you adopted ? SoftSPL or HardSPL ?
You say its SIM unlocked as it takes calls on the Tmobile network .Did you SIM unlocked with lokiwiz03a ?
yes ! a G4 can be SIM unlocked but it can not be CID unlocked,however,it can be upgraded to wm6 rom,but with method either 'SoftSPL' or 'HardSPL'.With your present ipl/spl 2.25.0001 and you say its NBD wm6 running,then it must have been upgraded through 'SoftSPL' method,as it uses patched ipl/spl and Cid unlocks the phone temporarily,but it never permanently CID unlocks the phone.But with 'HardSPL' ,it changes the ipl/spl to a patched ipl 2.21.0001 and spl 2.21 olip.So everytime you want to upgrade,you'll have to upgrade using 'SoftSPL' method.
could you elaborate a little more about this.
Cheers!
Hey thanks for the correspondence zabardast_1, I have been getting frustrated and I have many times contemplated going for the brick or bust approach here.
So, I have done none of the updating on this rig. I rec'd it and I wanted it primarily for wifi however I can't get the wifi card/ (sdiowlan I believe) to even recognize an AP (... I posted in the networking forum but no response.) Thus my own reasoning leads me to believe I should start from scratch with a new rom unless you know of something else.
So, I am not the most savvy and thought that all of the info I had led to SIM and CID unlocked. I just read otherwise last night and in your reply. The info I have provided is accurate the IPL, SPL, radio, although I don't know which NBD release it is; just says 6.0.0.0 and release date: 2/2/07.
I am trying to get the new rom on the my device however and I would've probably already bricked it if I could get an RUU to communicate with my wiz. I always get [Error 224] when I run it and my phone is connected through active sync. I am running vista but have installed the AS drivers for WMDC. I also tried it at work the other day with XP same situ. I then tried flashing from the bootloader screen with an NBD, Wizard Love ( w/ Italian installer?), and T-mob (226102_22610105_022511). The only one that says it will update is the Tmob ROM, however I got cold feet at the update button and canceled.
Other funny stuff I have observed that may or may not be related to the problems I am having are:
Can't install cab files ie (enable rapi or Cert SPCS) and Wiz Sys Tools couldn't read my CID block and hard_SPL G4 gives me REXX error ( SPL_Version has no value).
So, any wizdom you or anybody can drop is much appreciated and needed at this point.
Whew...
Listen carefully. G4 Wizard cannot be CID-unlocked without paying money. (And yes, you are using a G4).
What you need now is to Flash your original stock carrier ROM (Or wizard love) to get your OS back. Then either use SoftSPL or install HardSPL and flash WM6 ROM.
Thanks Starkwong,
I will try installing wizard love tomorrow at work and if that don't work I will attempt a Cing ROM (will all of these work or do I need to mind my G3's and G4's for these???)
Grazie
So, It worked using Wizard Love at work and out of the bootloader window. Now I need to:
1.) Get wifi working.
2.) Get a newer ROM
I put a post up in the networking thread, I am a tool so far as these devices are concerned so be easy on me.
http://forum.xda-developers.com/showthread.php?t=372811
So do I get the wifi issue resolved before I reflash???
Thx again
I don't know what you mean by "wifi not working".
Maybe it is the wifi AP doesn't allow 11Mbps (802.11b) connections?
However, going to any of the WM6 ROMs should already set the registry to allow Wizard connects to G-Only APs. Just use HardSPL/SoftSPL and flash a WM6 and you will see.
OK so "wifi not working" may indeed be a general statement...
What I mean to say is that I am not able to connect to any wireless networks for internet not home (Linksys WRT 54G v5 with ddwrt firmware) or school (university wide) or my city's wifi network. It won't even detect them at least none that Ive seen since I've rec'd this phone. So, that is what I meant by the ambiguous statement.
So, being as your last post was a success I will try as you say and post the results tomorrow. Thanks again starkwong!!!
1 quick thing however, to be sure, I can now try the hard spl or soft spl method of tricking my phone to run an upgrade to WM6?
Still not able to get wifi APs????
OK although I have been successful at reinstalling the Mfg ROM and then Hard SPL'ing my wizard thanks to ya'll I still am unable to connect to a wireless network (see one even). I have the Olip on my SPL and I installed a TNT version of WM6 and I am still at work (drunk but still here). Anyway I can't see my wireless AP and I am beginning to think its a hardware issue if thats possible, i dunno the dynamics of this system maybe thats why it was for sale. In any event as usual I am willing to try what ever you guys throw at me as you're my only hope obi wan. Alright Im gonna go home for the night and try getting on to my home network.
Thanks again for all the help guys.
Is your device a original one from phone operator? I suspect your device is a China Dopod 838 with replaced casing, because the China version has the wifi hardware removed, so wifi can't be started even if an English ROM is used.
Looks to be authentic 8125
Starkwong, the Cingular logo and the 8125 model # are on the phone case where they have been when I've seen them before in pics. Therfore, I dunno I guess it looks like every other 8125 I've seen. Can I check the SN, IME or anything to be sure?
Thanks Again!!!
Starkwong,
I am getting all the options for wifi on my phone the LHS LED flashes green when I enable it and alternates blue green when BT is enabled. So, could it still be that its a dupod? I dunno but I am going home for the night... Thanks for your help. I will try connecting to my home network when I get there.
Hello, I am in serious trouble! I got a brand new HTC Athena with Windows Mobile 5.0. I succesfully upgrade it to Windows Mobile 6.0.
All was OK.
Than I was interested to move into Windows Mobile 6.1 and possibly 6.5. At first I did the Athena unlock (3 step process) and all went OK: Antenna 1.5.0, SPL 1.2 OLI....
THAN I DID MY ERROR! I try to upgrade my 6.0 ROM with the Micky 6.1 cooked file with SPL 3.5. After a 92 percent upgrade, the ROM crashed and now I always get a nasty black screen with few lines (No 3 color bands!). When I try to upgrade again the same ROM or ROM for SPL 1.2 I get an error (ID mismatching). I guess the only solution is a hard and full reset of the Windows. But doing only a hard reset with the PDA will NOT change my error message and I will keep see this nasty black screen and I cannot load the Windows ActiveSync application-
I am totally lost. Help please. Any tool for a true full restore/recover??? (I did NOT make any backup!).
This thread might hold a solution to your problem.
Hi
If you follow the instructions exactly in post 33, it will solve your problems. just click HERE
Jay
Hello, those links are basically for corrupted wifi antenna files.-
In my case my HTC Athena crashed the Windows 6 ROM while I was attempting to upgrade, after unlocking the phone, the Athena from version 6.0 to version 6.1
Are you sure I can use the post #33 also for my specific trouble?
Thank you in advance!
this is also to repair your bootloader-infos
if you look at your bootloaderscreen, you will see ATHE100, IPL, ATHE100, SPL. if not, you have to repair it
make sure you flashed the right rom, spl 1 or 3.5
How can the bootloader get repaired?
yes use that link, post #33. fixes both wifi and modelid problems and bootloader problems when you got stuck at 92% of the flashing process.
Cannot re flash ROM
Please help! I tried the unlocker and it failed at 92% and since then I have no WM6. Then I tried to flash the Michy WM6.5 and that failed. I was getting model id errors so I did the mtty and mac1 fix which was succesful. However all I can get now is a grey screen on boot-up. I can get to the bootloader screen and it displays ATHE100, IPL-v2.02, ATHE100, SPL-v1.20. Olipro. From what I have read on the forum at this stage I should run a RUU to flash a WM6 ROM but all that I try can't connect because no OS running to connect with Activesync? Is there a way to flash from the bootloader? The other option seems to be putting an image and flasher on a miniSD but I can't find clear instructions for this or which files?
Please ignore - my battery wasn't charged enough. Replaced battery and recovered device.
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
I have follow the link (thread 33)...., however, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
first, how can I get the mac address of my device? It is NOT written anywhere in the Athena parts (checked in the battery bay and so on.....), and so when I run mtty i am in trouble! I have used a mac address got from my company's manager, but not sure it is ok to use it with the Athena!
Anyway,......I have follow the post link (thread 33)...., and followed the various steps.- However, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Solved!
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
puffo said:
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
Click to expand...
Click to collapse
Can you tell what you've actually done after you've changed ROM with Mtty?
I done the thing with Mtty but just as you described when I reset it now I still get the grey screen. And if I try to update ROM it fails again on 92%
where did you find the upgrade from wm5 to wm6?
the link I found on rapidshare seems not be availabel anymore