I cant get wm6 on my wizard - 8125, K-JAM, P4300, MDA Vario Software Upgrading

I have an O2 XDA Mini S - G4 model
i have sat and read how to flash this model. I have installed HardSPL, shown on boot screen as shown by the olip in the version number, i then proceeded to use MUN RUU utility and my chosen rom which was the AMP rom.
I dropped the file into my updater folder and ran the flash tool
It runs through, goes from 1 to 100%, hangs for a short time at 100% then closes and reboots the wizard. All good so far, yes?
No, the ppc reboots and starts up WM5 again and then adds all the o2 customisation.
I have tried using the TNT rom too, same problem. I have also removed HardSPL and tried using SoftSPL. Same damn thing there too, once the flash is complete it reboots and starts wm5 again.
Anyone know whats wrong?
I seem to now have the TNT boot screen, but still have WM5. lol
Heres my device info
ROM Version - 2.21.4.1 WWE
ROM Date - 3/9/06
Radio Version - 02.07.10
Protocol Version 413.1.03
ExtROM Version - 2.21.4.101
Please help me out someone. Its currently standard apart from a tnt boot screen, HardSPL is still removed.
Please Note - I dont have any errors during flashing, it all runs through like its working fine. :s

its all good, i managed to get it sorted using mUn's ShellTool
Sweet application, followed the steps and it worked fine using TNT rom

Related

Problems with WiFi (QTEK 9100)

Hi,
Ever since upgrading to 2.17 (official QTEK version) I can no longer get a stable WiFi connection - I get poor signal displayed even though I am next to the AP and it can take anything from 5 to 20 attempts to get connected.
The 9100 came with 1.6.7 installed which not perfect more or less connected first time, but I hoped the later ROMs would fix some other stability problems.
I have tried AKU 2.3 and I still get the same issues (plus I miss the battery indicator in the top bar).
Also, I cannot get back to 1.6.7 (I managed to get the OS back to it but the other 2 were stuck at 2.4) as every time I try I get vendor ID is wrong.
Any ideas?
Cheers,
Taomyn
I have the same problem, but even worse. I see the network after connecting it says it is connected but I cannot browse or do anything on the "socalled Internet" DHCP says that it found an adress in my case at home 192.168.1.33.
I am not sure if an upgrade would help.
My wifi version is 01.04.10
I am looking for any idea too.
Just an update, though the problem remains.
I have downgraded the OS to 2.17 as it seems better than the later ones posted and is at least a QTEK one.
Still hit and miss with the WiFi
Does anyone know if there are any later QTEK ROMS available?
search this forum to find a solution to downgrade the rom version to 1.x then do CID unlock using aWizard.
or you should try upgrade to cingular 2.25WWE rom to see if there is any improvement.
huangyz said:
search this forum to find a solution to downgrade the rom version to 1.x then do CID unlock using aWizard.
or you should try upgrade to cingular 2.25WWE rom to see if there is any improvement.
Click to expand...
Click to collapse
I did try various of the downgrade tips but none seemed to work even though I've got a G3, so hopefully the LokiWiz will be updated soon to work on v2 ROMS.
The Cingular 2.25 ROM didn't work very well either and I hated the extra rubbish it comes with. The radio ROM I happen to be using was from that same one.
I suppose I could go for the 2.25 OS but not the Extension - would that leave behind the Cingular crap?
Taomyn said:
I did try various of the downgrade tips but none seemed to work even though I've got a G3, so hopefully the LokiWiz will be updated soon to work on v2 ROMS.
The Cingular 2.25 ROM didn't work very well either and I hated the extra rubbish it comes with. The radio ROM I happen to be using was from that same one.
I suppose I could go for the 2.25 OS but not the Extension - would that leave behind the Cingular crap?
Click to expand...
Click to collapse
I now run 2.25rom without its original Extrom. It works perfect for me.
huangyz said:
I now run 2.25rom without its original Extrom. It works perfect for me.
Click to expand...
Click to collapse
Thanks. I have now loaded the following but with the QTEK 2.17 Extension ROM:
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS: 2.25.11.1
I will have to wait until tonight to try the wireless at home.
One thing I've noticed is that I don't have a battery indicator at all now, neither in the Today window or the bar at the top. I'll dig around more to see why this has happened.
Taomyn said:
huangyz said:
I now run 2.25rom without its original Extrom. It works perfect for me.
Click to expand...
Click to collapse
Thanks. I have now loaded the following but with the QTEK 2.17 Extension ROM:
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS: 2.25.11.1
I will have to wait until tonight to try the wireless at home.
One thing I've noticed is that I don't have a battery indicator at all now, neither in the Today window or the bar at the top. I'll dig around more to see why this has happened.
Click to expand...
Click to collapse
it looks a little strange that you have a 2.25OS with 2.24IPL/SPL. :?
you could put a bat. icon on task bar by running Windows\Init_Tray.exe
Ok so I still can't get WiFi working :-( but at least I've sorted the the battery indicator out (thanks to a reg tweak for AKU2.2)
Which leads me to this AKU stuff. I keep reading about 2.3 but I'm not sure if this is an official release or something that someone has put together. I'm willing to give it a try but not if it's just 2.2 with some tweaks or something like that.
Can anyone shed some light on the AKU releases? Mine definitely says 2.2 at the moment.
Oh and can I simply create an upgrade file with just the 2.3 OS file in it?
TIA
Ok, my WiFi is still borked, it sees AP's all over the place but the ones I know it should connect to the phone just will not lock on to - it tries for a few seconds then simply says "Unavailable".
Currently I have on the phone a combination of:
IPL: 2.24
SPL: 2.24
GSM: 02.25.11
OS:2.24.10.1 WWE
Protocol: 4.1.13.12
ExtROM: 2.17.7.102
WM5 5.1.95 (14955.2.3.0)
I've actually tried what should have been a later OS, 2.25, but the AKU was 2.2 and the copyright message shows 2005 where as this one is AKU 2.3 with 2006 displayed.
I'm thinking now that perhaps the Extended ROM which is from the latest QTEK build I could find. Can anyone suggest a good replacement for it that doesn't have a load of baggage and only useful customisations?
As a last resort I'd like to try downgrading back to full 1.x ROM (QTEK 1.6.7 I think) but as I understand it this may not be possible. If it can be done, can anyone point me in the right direction i.e. which downgrade ROM to try? Yes, I have gone through this forum but it's almost "information overload" and very confusing,
TIA
if you update to shipped Cingular 2.25WWE rom, you can bypass all the extrom and see if wifi works normal (before you install other apps.)
Mine is ok.
the AKU2.3 one is a custom test rom which may cause slightly unstable.
while this still doesn't work, i think there's no means except sending your device back for checkup and repair.
Thanks, but how do I "bypass all the extrom"? Is there a clean extrom I can use with it?
Ok, I'm making progress.
I followed the instructions for downgrading, which although says it won't work for 2.21 or above, sort of does.
I downgraded to the custom 1.5.4 which succeeded but left SPL still at 2.24 but everything else had changed. I then ran the LokiWiz v0.2b and that seemed to succeed too at least there were no errors.
I then tested WiFi and it locked and connected first time - yay!!
Next I have taken the 1.6.7 QTEK ROM (which the phone originally had) and when that finished both IPL/SPL were downgraded to v1.x - WiFi still working.
At least now I know that WiFi is not borked but it's some strange ROM issue.
I'm going to try QTEK's 2.17 ROM and see what happens - at least I know I can get back to 1.x if it still doesn't work.
This is fun - not!!
Taomyn said:
Thanks, but how do I "bypass all the extrom"? Is there a clean extrom I can use with it?
Click to expand...
Click to collapse
after the RUU completed and restart automatically, after those init setting you must follow(eg. align screen, select time zone, etc.), at the moment when u see "customize within 3 seconds", poke the reset hole as quick as you can. Then you Bypass the extrom installation.
Thanks - you are being a great help, it's much appreciated.
I went back to 1.6.7 then added the Cingular 2.25 OS ROM but with the QTEK 2.17 extended ROM. What a mixture that is! WiFi would not work. I then hard reset and used your bypass technique - WiFi now works.
It seems that an extended ROM application is screwing up WiFi so I need to get everything up to the latest and greatest, bypass the extended ROM then one by one run them to see which is the culprit.
The plot thickens......
Well it looks like *any* v2 ROM screws up the WiFi on my phone and I have no idea why :x I have tried various combinations of ROM parts (proving the phone is most definitely CID unlocked :wink: ) and I either have no WiFi or some which progressively gets worse as time goes on to the point it stops connecting again.
I'm back to the original 1.6.7 QTEK WWE shipped ROM and WiFi works flawlessly but I'm now missing all the nice tweaks of v2 and I'm sure my BT headset doesn't work as well as before.
Maybe the next release will be better :?
Just to conclude this thread. The 2.26 ROM recently released seems to have cured my WiFi woes and it has made my phone run so much better than before.
I recommend it to anyone
Taomyn said:
Just to conclude this thread. The 2.26 ROM recently released seems to have cured my WiFi woes and it has made my phone run so much better than before.
I recommend it to anyone
Click to expand...
Click to collapse
Cheers!
wifi probs with 2.26
i just upgraded my MDA USA to this ROM. My wifi now doesnt connect. It was working fine with ROM 1.08. Any suggestions? I havent tried bypassing the ext ROM, will this work? thanks
Same problem here as above
I got same wifi problem when upgrading from 2.25 to 2.26 .
i am going to revert back to 2.25 which is from the imate website. and hope it sorts it.
will get back to you when done.

HELP needed changing ROM after installing Molski (2.26.10.2) AKU2.3 ROM

Hi there,
After I installed Molski's 2.26.10.2 AKU2.3 ROM I can't seem to upgrade/downgrade to another ROM. After starting the update utility my screen went black, the update tool stalled at 0% with error [260] UPDATE ERROR and the only way to reset was to remove the battery.
My specs right now are:
T-Mobile Vario G3 (G3 yes!) Wizard
IPL 2.26
SPL 2.26
GSM 02.47.11
OS 2.26.10.2
I tried getting into the bootloader by pressing and holding either one or both of the righthand buttons and a soft reset, but then the screen goes blank (black) as well with the removal of the battery as only option.
I also tried to install button's 1/05 ROM without succes (same 260 error).
I also reinstalled Windows XP + MS ActiveSync 4.1 just to rule that part out, but even then no luck!!
I flashed my PDA on several occassions using different ROMS each time, but this is the first time it doesn't work . Perhaps something to do with the bootloader?
Any help would really be appreciated!
Best regards,
Dennis
the Netherlands
You shouldn't go back to the 1.05 unless you need to downgrade your IPL/SPL for some reason or another...
I'd try the T-Mobile 2.26. (That's what I do when changing ROM's, because when I see the T-Mobile splash I KNOW that all parts of the previous ROM are gone.)
Always works for me, YMMV though ...

Upgraded to WM5 ROM, 1.15.00 radio doesn't work?

Hi,
I upgraded a Cingular SX66 unit using maupgradeut_noid and the latest AKU 3.5.2 WM5 ROM. Afterward, I had no radio ROM so I updated to the 1.15.00 release. However, my phone is still unable to make/receive calls or data (with multiple good SIMs.) It appears the radio ROM is having issues with this WM5 package because sometimes on hard restarts the boot screen lists R: and G: as NONE, but after a soft reboot they usually show the correct versions.
I searched and can't find any postings about this type of behavior. Nothing useful to report from the phone other than it says "phone is not ready" and "no service" with a good SIM.
I have several of these PDAs that I want to distribute to my internal staff with WM5 so they don't have to learn WM2003 (all of our other devices are WM5 or WM6.) Any recommendations on a procedure to test the radio ROM or a different combination of OS and radio ROMs?
Thanks for the help.
PS. running getdevicedata.exe yields the following:
PH20B1 WWE A %CID? 5.35.05. 1.15.00 % 4
downgrade to wm2003 and try to flash again radio 1.15 and post the results
sandimashsfootballrules said:
Hi,
I upgraded a Cingular SX66 unit using maupgradeut_noid and the latest AKU 3.5.2 WM5 ROM. Afterward, I had no radio ROM so I updated to the 1.15.00 release. However, my phone is still unable to make/receive calls or data (with multiple good SIMs.) It appears the radio ROM is having issues with this WM5 package because sometimes on hard restarts the boot screen lists R: and G: as NONE, but after a soft reboot they usually show the correct versions.
I searched and can't find any postings about this type of behavior. Nothing useful to report from the phone other than it says "phone is not ready" and "no service" with a good SIM.
I have several of these PDAs that I want to distribute to my internal staff with WM5 so they don't have to learn WM2003 (all of our other devices are WM5 or WM6.) Any recommendations on a procedure to test the radio ROM or a different combination of OS and radio ROMs?
Thanks for the help.
PS. running getdevicedata.exe yields the following:
PH20B1 WWE A %CID? 5.35.05. 1.15.00 % 4
Click to expand...
Click to collapse
Take it easy
all BA HAVE THE SAME PROBLEM AS YOU DESRIBLE
IF YOU USE WM2003 THE PROBLEM WILL DISAPPEAR~ SO,JUST SOFT RESET
YOUR PHONE EVERY TIME YOU CHANGE YOUR BETTERY!!
just one softreset, and when you need to charge, charge it when it reaches the 40%, etc, just don't take out the battery, or you will have to softreset it again for the radio work.
it is just the same with mine sx66, and i don't care at all.
Thanks for the notes...I kind of learned the soft reset 'fix' on my own, a little disappointing but I guess we're stuck with it. Why would I want to downgrade my phone to 2003? The whole point was to move to WM5 so my users and support team all work with the same interface.
Of course...my next project is to find out why SMSplus works on 8525 phones and not 8125 (standard Cingular OS load.) Might have to upgrade the 8125s to WM6 (sigh)

Dead Charmer... maybe

Hi all,
I tried to upgrade my MDA compact II (HTC Charmer) to WM6, but during the first step, downgrading to the "no vendor" version I made a mistake. A used a wrong version, it was for Prophet. After the final reboot, the device froze in the splashscreen "T-Mobile". After that I tried to do exactly the same with a "Charmer" version, but it didn't help me, the situation was the same.
However, now I'm able to flash successfully only the last vendor provided ROM update "RUU_Compact_ll_2060227_20602110_021921_T-MobileUK_Ship.exe", but it doesn't help me anyway, my Charmer is still freezing in the splashscreen. I tried to downgrade it , but the application gives the following error: "UPGRADE ONLY". When I try to make a hard-reset, and after that to confirm the factory settings by pressing "Yes" (green) button, the result is "Format FAT partition" and then "format is failed".
Only the bootloader is working now as well as the battery charging. Please, help me to turn back to the life my Charmer!
And one additional question: can I perform a CID unlocking just by ROM-flashing or the device must be fully operable?
Flash this:
http://rapidshare.com/files/41754719/RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe.html
After that, you should be able to make hard reset. If you succeed, flash "RUU_Compact_ll_2060227_20602110_021921_T-MobileUK_Ship.exe" - that.
Hello there,
I am a new use an recently got an MDA PM200. I am in exactly the same situation as petrun. I have tried the flash suggested by vlodeck but it doesn't work, saying incorrect vendor ID (I guess that's because it's for a Prophet?).
What should I do next...?
Thanks.
OK, I succeed with a little progress. Many thanks to vlodeck, I will try to explain what happend...
I successfully flashed my Charmer with this Prophet ROM:
RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe
Full link:
http://rapidshare.com/files/41754719/RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe.html
But it was possible only by using this "No ID" update application, not original one, maybe because my device is still locked:
Full link:
http://www.windowsceportal.hu/tartalom/programok/htc_charmer_upgradeut_noid.zip
After that I succeed to format the FAT partition (finally ). But I cannot after all to flash the latest official MDA compact II firmware. There is two possible events, which I experienced:
1. When I try to use the original flashing application, I get the following response: "UPGRADE ONLY".
2. When I try to flash the official MDA compact II ROM, but through the "No ID" application, I get "INVALID COMMAND".
Just for explication, now my device cannot boot, it freezes in the splashscreen (it is Qtek now, not T_Mobile...) and the following versions could be read:
IPL 2.06
SPL 2.20.0000
GSM 02.47.21
OS 2.20.7.34
So, how I can do that? What should I do further? I would like to unlock my Charmer, but should I firstly make it operable?
Thanks in advance for your help, guys!
By the way, all described above I tried sevetal times with the same result.
The other thing is that... all links about the CID unlocking downloads, which I found here are no longer active. Any alternatives?
Rise from the dead!
Incredibly, but it's a fact! After successfull FAT formating I probably didn't wait long enough. Today I turned on my Charmer and several seconds after the splashscreen "QTEK" it successffully booted in WM5, performed all settings and finally started to work!
It's GSM module works, the Bluetooth works, I am able to start different applications. Just the camera does not work. And the most strange thing for me is that this ROM was for Prophet, not for Charmer
So, after all, how to proceed to upgrade to WM6? Now the bootloader is above ver.2.
Should I firstly flash it with proper ROM (for Charmer) or it's not necessary?
Should I unlock it as is now (Prophet ROM)?
Vlodeck, I rely mostly on you, since the WM6 with Touch FLO is your creation.
Thanks!
You dont have to CID unlock. Just flash that WWE T-mobile WM5 AKU2 for Charmer. Good luck.
Maybe I am boring, but steel need an advice: I cannot flash "WWE T-mobile WM5 AKU2".
1. The original RUU gives me "UPGRADE ONLY", maybe because my SPL after flashing the Prophet ROM is 2.20
2. This "NO ID RUU":
http://www.windowsceportal.hu/tartalom/programok/htc_charmer_upgradeut_noid.zip
reaches 2% and gives "INVALID COMMAND", after that - only bootloader screen.
3. This "NO ID RUU":
http://forum.xda-developers.com/attachment.php?attachmentid=42657&d=1183226200
cannot open the nk.nbf image (but works with other images), I don't know why.
What is the solution? Any ideas? Maybe some tool to downgrade the SPL to ver.1? I tried (it perhaps was bad idea)"RUU_Charmer_1120223_11202110_11220_T-MobileUK_Ship" and IPL became 1.12, but SPL remained 2.20... and Charmer didn't boot after that. After flashing the Prophet ROM it works again and IPL is 1.12, SPL is 2.20
In brief... how to flash successfully the last Charmer ROM?
If you cant flash the AKU 2 charmer rom, then go for AKU3.3 rom (can be german, that doesnt matter). Once done that, flash wm6.
Success
Yeah! Thanks to vlodeck now everitging is all right! I flashed the original German AKU3.3 ROM by using this RUU:
http://forum.xda-developers.com/attachment.php?attachmentid=42657&d=1183226200
(The original one gives "INVALID VENDER ID", of course, in German ) After that - successfully upgrade to WM6 TouchFLO.
Briefly:
1. First try to flashing WM6 - crash! The reason: old bootloader version (IPL/SPL = 1.12).
2. Flashing the Prophet ROM - success for FAT formatting. The Charmer turned back to life.
3. Flashing the German AKU3.3 ROM from T-Mobile, but through the No ID RUU.
4. Upgrade to WM6 TouchFLO by vlodeck. At the begining I reached the same problem, as described here:
http://forum.xda-developers.com/showthread.php?t=331717
but after istalling cert_spcs.cab and enablerapi.cab in my device I succeed to finish the process.
Thanks vlodeck, good job! This ROM is really amazing!
petrun said:
Yeah! Thanks to vlodeck now everitging is all right! I flashed the original German AKU3.3 ROM by using this RUU:
http://forum.xda-developers.com/attachment.php?attachmentid=42657&d=1183226200
(The original one gives "INVALID VENDER ID", of course, in German ) After that - successfully upgrade to WM6 TouchFLO.
Briefly:
1. First try to flashing WM6 - crash! The reason: old bootloader version (IPL/SPL = 1.12).
2. Flashing the Prophet ROM - success for FAT formatting. The Charmer turned back to life.
3. Flashing the German AKU3.3 ROM from T-Mobile, but through the No ID RUU.
4. Upgrade to WM6 TouchFLO by vlodeck. At the begining I reached the same problem, as described here:
http://forum.xda-developers.com/showthread.php?t=331717
but after istalling cert_spcs.cab and enablerapi.cab in my device I succeed to finish the process.
Thanks vlodeck, good job! This ROM is really amazing!
Click to expand...
Click to collapse
WHERE I CAN GET BOUTH FILES cert_spcs.cab and enablerapi.cab
AND WHAT VIRSION OF PROPHET ROM SEND ME WORKING LINK THX DEAR
Charmer Stuck At Splash Screen
CHARMER STUCK AT SPLASH SCREEN
--------------------------------------------------------------------------------
I HAVE A MDA COMPACTII ''MADE IN TIWAN'' I WITCH WM5 I WANT TO UPGRADE IN TO WM6 SO I UPGRADE THIS WM6 TouchFLO Charmer WM6 ver. 2.1 FINAL by vlodeck AT THIS HOME PAGE http://forum.xda-developers.com/show...harmer+cert_sp... AFTER THIS I HARD RESET MY MDA C2 ITA ON BUT THE LANGUAGE IS NOT ENGLISH I CANNOT UNDERSTAND ....
SO I CAN REFLASH IT WITH THIS ROM Charmer_Touch_GER_Beta_2.7 .. AFTER FLASHING COMPLETE I SOFT RESET MY MOBILE.
SO MY MOBILE STUCK ON SPLASH SCREEEN ONLY T-MOBILE IS SHOW
MY MOBILE DETAIL IS AS UNDER
IPL 2.06 .0001
SPL 2.06 .0001
GSM 02.19.21
OS 4.0.0.0
PLZ DEAR SIR WHAT IS SOLUTION OF MY MDA C2
MDA2 CANNOT CONNECT WITH ACTIVE SYNC
Of course it cannot connect with ActiveSync, the device doesn't boot. One certain solution for bricked Charmer is Prophet ROM:
RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe
Use this link:
http://rapidshare.com/files/41754719/RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe.html
In order to flash this, you should enter the bootloader, without using the ActiveSync. After that try to perform a hard reset, you probably will succeed to format the FAT partition.
if you cannot connect the pda to pc HOW CAN U PUT THE ABOVE PROPHET RUU ON CUREENT?
I have a charmer and I was trying to update to wm6. I can´t because the ipl is 1.12. I updated rom to german aku 3.3. But I can´t hard reset. format error. I´m trying to put prophet rom to format it, but when I send the prophet rom, it always give me an error at 95%. error 326 - this nbf file cannot be used fo your pda phone. please check your nbf file. the aku3.3 rom flashes ok. any idea?? I try tu send a radio rom. after that is the same. 95%error. please help. I can´t bring my charmerback to life.
Hello together,
I have the same problem like _mestre_.
I updated from T-Mobile AKU 3.3 GER to WM6 and flashed back to WM5 without problems, but when flashing again to WM6 from vlodeck my charmer didn't boot anymore and had that "Format is failed"-problem when making a hard reset. I could not recover my device until now with the method explained in this thread cause of the problems "error 326 - This nbf file cannot be used for your pda phone". So the Prophet Rom does not seem to work with boot loader 3.x. Has anyone any idea? Please help! Thank you very much in advance!
Yallah said:
Hello together,
I have the same problem like _mestre_.
I updated from T-Mobile AKU 3.3 GER to WM6 and flashed back to WM5 without problems, but when flashing again to WM6 from vlodeck my charmer didn't boot anymore and had that "Format is failed"-problem when making a hard reset. I could not recover my device until now with the method explained in this thread cause of the problems "error 326 - This nbf file cannot be used for your pda phone". So the Prophet Rom does not seem to work with boot loader 3.x. Has anyone any idea? Please help! Thank you very much in advance!
Click to expand...
Click to collapse
same problem here... any suggestions or is my charmer bricked?

How to fix a bad radio flash ? "no gsm" on boot

Hi, i've bough a p3600 on ebay.
The seller tell me the phone is out because he flash a bad radio version on the phone.
I try to upgrade some file. ( Rom OS, Radio, SPL,etc ...)
I try the splexploit...
BUT ... The phone already stay on startup. i can see HTC startup screen,the windows startup screen ...but never the today screen.
I try hard reset, htc official rom, cookeed rom,...but when i flash a rom with "gsm", the update freeze at 13%
I try with usb and with sdcard..same thing, already stay at 13% !
But if i flash hard spl, 100%, if i flash OS, 100%, just the radio freeze at 13%
Any idea please ?
update
after the boot, i've got a "no gsm" message near the radio version
other people got the same problem like me ...
God oli, help me please
I more or less had the same thing and solved it with the sc card flash page.
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing
A rom that works for me to flash it back to the working original
http://www.allaboutphones.nl/forum/request-originele-spv-m700-rom-p3600-rom-t727.html
To download you have to register with them.
GL
Hi, updating the radio to 1.56 crashed, now I have the No gsm message and doesn't boot, running mtty from bootloader with info2 command it says supercid but I can't update any official rom SPA, WWE, ITA... the error is "vender id invalid". I've tried the sd method but returns to bootloader .
Any help will be appreciated.
You should try SSPL : http://forum.xda-developers.com/showthread.php?t=293632
And if it doesn't work the Des' Crash-Proof SPL :
http://trinityguides.info/index.php?option=com_content&task=view&id=39&Itemid=66
and try to flash a radio rom again !
doesn't work
try again and again ...the phone block at 13% ( when the radio upgrade begin) ...
pfffff
I've the same problem and after several attempts without result I sent the phone to the workshop and they told me the problem is with the main board! (this cost almost the price of phone itself). Moreover, I've seen some where here that the problem could be caused by radio chip but I couldnt get the detail.
If you find a solution give me a tip.
i've test lot of thing.
I progress with mtty. but i've got a problem ..i can't downgrade the phone under SPL 1.05.
SPL 1.04 can "reset" the radio, or enter directly to the radio bootloader. With that, i can save my phone.
Try mmty (see the wiki => bootloader info) and with the mfg spl, you can try the method.
Guys,
I've got the same problem...
I've sim and cid unlocked my spv m700 some time ago, using wonderful software from pof. Everything went smooth.
Today I've decided to update radio rom to 1.38.00.11 to enable gps.
I've launched RUU, everything was ok till 44%, when I've got message "Communication error".
After that program tried to recover rom without success, I've got another message "Image corrupted"...
I've tried to reboot my spv (both SR and HR), after rebooting I see:
M 05
B 05 D 1.23
then those symbols disappear and I see only Orange logo.
That's it... The end...
Should I reload radio rom or both rom and radio rom to my DEAD spv? If yes - how?
Please help as I'm very disappointed, frustrated and so on!
Thank you!
Update: A-A-A!!! I did it! I revived my spv! Let me explain how (I'm kinda new to all this rom and and ssl things, so forgive me for mistakes, if there are any):
1 I ran unbrick software. Yesterday it did not work (said, that could not find smth), but today it worked fine.
2 I ran RUU and BINGO! That's it!
BTW, I have vista, but it still worked (I think, thanks to Windows Mobile Device Center, which I have installed).
Also, I killed wmd process in Task manager in the beginning (have read this recommendation somewhere).
Thanks to everybody for their help!
nyco,
could you please explain briefly what you did exactly and which radio and rom you used
thanks and regards
Flash HSPL, then issue task 2A command from mtty. Flash full ROM.
Thanks stepw...
when I hit task 2A nothing happens.
Original ROM doesnt respond. I flash with cooked ones. Result 100% successful. I restart the phone- hang at boot screen.
stepw said:
Flash HSPL, then issue task 2A command from mtty. Flash full ROM.
Click to expand...
Click to collapse
Hi,
I'm already under the hard SPL. and "task 2A" not working.
Macars, try only with radio ripped or full original rom (from htc or cooked with radio) because some cooked rom have only OS.
Can you tell me what SPL you have?
Hard SPL?
Have you try splxploit ?
Can you tell me what rom you try oviplokos1 ?
thanks,
it shows SPL 9.99 and with this I cannot flash anything so what I do is to update with splxploit and then the phone changes to SPL 1.2 olipro. With 1.2 I can only flash coocked ROM and will go until the end 100% successful- (original ROM the phone does not respond), but when restarts with newly loaded cooked ROM the phone hangs at window login screen and when put it in bootloader the SPL 9.99 returns again.... the story goes on like this.
I'm becoming mad....
hi,
you can only flash cooked rom because the rom you flash contains only OS. When you flash HTC rom, the rom contains os+radio+spl+....other thing ...
Try this method to downgrade your SPL (9.99) to oli 3.20 :
1°) run splxploit
2°)when the phone reboot on the spl 1.20 oli, run HardSPL 3.20 olipro. (search on the wiki or the trinity forum
3°)upgrade to 3.20 oli ...
Now, when you go to the bootloader, you can see SPL 3.20 oli.
Try reflashing a radio only (see the upgrading topic, you will see radio 1.56.xxxx)
Tell me if this method work.
When i'm on spl 3.20 oli, i can load radio rom to 0%
when I downgrade my phone to spl 1.05, and i can run the upgrading to 7% (best score )
To downgrade to SPL 1.05:
edit the "unbrick.bat" on the splxploit folder.
Replace TRIN_HardSPL.nb to TRIN_SPL105.nb
try to find SPL 1.04. I'm sure if i got the spl 1.04 i can revive the phone
Did exactly as you said final result:
When i'm on spl 3.20 oli, i can load radio rom to 0% (and stays there )
hi,
ok, try to load spl 1.05 with splxploit, and when it is load, run radio upgrade (1.56.xxxx)
Try to find spl 1.04 and mtty it can be reset the radio bootloader
if you find 1.04, give me it
hi nyco,
I tried with SPL 1.05 the result is the same as your reaches 7% and restarts. I'm still trying to find SPL 1.04 I found one for Hermes I tried but didnt work failed.
macars said:
hi nyco,
I tried with SPL 1.05 the result is the same as your reaches 7% and restarts. I'm still trying to find SPL 1.04 I found one for Hermes I tried but didnt work failed.
Click to expand...
Click to collapse
arf :/
You got exactly the same problem i have.
did you check if you have bad block (with mtty)
try format the phone with mtty.
i contact pof, but he doesn't answer me

Categories

Resources