Helmis upgrading problems - MDA III, XDA III, PDA2k, 9090 Software Upgrading

Hi All,
I tried to upgrade my PDA2K from Helmis 1.3 to 1.41 using the instructions on this site but it failed and now my device says 'Serial' at the top of the screen and 'v2.07' at the bottom. It changes to USB when I plug it back into the cradle. but nothing else after this step i'm getting an 101 error messsage listing that my device even is not connected or powe is off or swiched of or whatever , questions are:
1- is their any specific steps i should use any unlocker or operater before using this upgrade?
2- i'm using wvista does it effects this operation
3- my machine returend back to helmis 1.3 version but start regecting any installed applications and become so slow any help

Related

I Can't Upgrade my device

Heloo every one ... i'm tired from this pda p3600 ... since 4 day's i wanna to upgrade my rom from wm5 to 6 & the upgrade process didn't work ... i try everything .... but non is work ...
first i was trying to make upgrade through windows vista home premium but didn't go well & this is the photo for my problem :
http://www.freewebtown.com/Haitham/CIMG0511.JPG
http://www.freewebtown.com/Haitham/CIMG0512.JPG
http://www.freewebtown.com/Haitham/CIMG0513.JPG
http://www.freewebtown.com/Haitham/CIMG0514.JPG
http://www.freewebtown.com/Haitham/CIMG0516.JPG
then i try to upgrade through my freind windows xp ... and also didn't work good .. the error message say that the phone is unable to upgrade do u rom flash or something like that ... so i try to instal the unlock & also same message ....
i'm in **** mood ...
any one can help me please
Until the new version of WMDC is released with fixes, I suggest you use XP computer to do upgrade.
New WMDC v.6.1 coming soon: http://windowsvistablog.com/blogs/w...ows-mobile-device-center-6-1-coming-soon.aspx
The XP computer needs to have Active Sync 4.5 installed. Reboot xp computer before starting, to clear any existing syncs. Delete current sync profile on Trin. Connect to pc via usb as usual, let ASync run, but cancel when it tries any profile, you are left as: Guest sync
You should be connected now. Upgrade rom file should be extracted in explorer, e.g., so you can see all files. Run RUU wrapper or ROMUpgrade exe, depending on rom you're using.
If you go through process, & get error message. Don't disconnect Trinity. Close that page & start again. It should work the 2nd time. When it's working, you will see the boot screen, color bars & at bottom usb notation. (If it says serial, you'll have to, unhook usb connection, reboot computer, re-sync to guest status, & start again.) Then the update screen on Trin will show % bar, if process is working correctly.
If you still get error message, then check Trinity Wiki info as rom upgrade problem FAQ is there. I'll assume your Trin is unlocked. Check boot screen on Trin to see boot loader info. Wiki explains how.
Also: Use SSPL software Bootloader solution from "Des" - this loader ignores the CID and the upgrade will work also with wrong CID. See also http://forum.xda-developers.com/showthread.php?t=293632
If you still have problem, come back here & give info:
1. What rom is currently on Trin? What radio?
2. Did you buy an unlocked Trin? Exactly, what device do you have?
3. What wm6 rom do you want to upgrade to?

Upgrading help needed.

Hi Gurus,
Tried upgrading using different methods to O2 XDA IIs Asia Eng rom, however all methods seem to fail. Have already read the readme file.
a) Using Activesync and MaUpgradeUt__NoId.exe with the new rom.
http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5
Activesync 4.5 somehow connects at first, detects the rom versions, and closes without warning, leaving the xda2s disconnected giving connection errors.
b) Using manual method,
Using editfix.exe & getdevicedata.exe
Somehow gets warning errors about invalid passwords and wrong header file.
Is it a type 2 rom ?
c) Done hardreset and Going direct into bootloader (V.2.08) and using usb cable without activesync. The word serial does not change to usb, hence there is no connection through usb to the xda in bootloader mode.
Any ideas ? SD Card interface is not working. My guess is that the drivers for usb and sdio is not working. Any input ? I know that the usb cable and interface is working as i can browse the windows folder using activesync.
Updates
Managed to solve the issue with the bootloader mode detecting usb.
I'm trying to download from WM2005 to WM2003 (O2 Official WWE 1.42 release - Asian version.)
Followed the steps exactly in this link :
http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5
Copied the official nk.nbf rom to the downgrade folder as instructed. When i ran MaUpgradeut_noid.exe, the screen stuck at the checking of info of device. does not seem to be able to flash in bootloader.
I'm using v2.08 of the bootloader (and usb is being displayed.)
Am i doing anything wrong ? Is there an alternate method ? This doesn't seem to work for me.
please help
i've got a ppc660kit and i did the processing and when it was done and i reset it show some colored screen and at the bottom it says no gsm and d 5. somthing.
please help
thanks
just a guess
mtnbikefreak said:
Managed to solve the issue with the bootloader mode detecting usb.
I'm trying to download from WM2005 to WM2003 (O2 Official WWE 1.42 release - Asian version.)
Followed the steps exactly in this link :
http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5
Copied the official nk.nbf rom to the downgrade folder as instructed. When i ran MaUpgradeut_noid.exe, the screen stuck at the checking of info of device. does not seem to be able to flash in bootloader.
I'm using v2.08 of the bootloader (and usb is being displayed.)
Am i doing anything wrong ? Is there an alternate method ? This doesn't seem to work for me.
Click to expand...
Click to collapse
just a guess, are you trying to flash your device from a widows vista pc, because connection errors especially happen there, because windows downloads new drivers while flashing, disconnecting your device, normally the manuals here are detailed step by step and seem to work for every compatible device, so there is probably the vista thing, a broken cradle or cable which is rather unlikely, or a general software issue with your pc
i forgot to ask, why are you using a Maupgrade, isn't he general upgrade file for blueangel compatible devices the Baupgrade?
nevermind
no i got it. i uploaded the 2.0.3 on my phone it fix the phone. but still shows the 4 color screen, that doesn't matter it still works
thanks anyways guys

My turn to brick it...

Hi All
Owning a Vario III and using Hardspl I upgraded to the latest incarnation of HTC's ROM (WM6.1). Having been caughtout with the freezing issue and after reading some posts about removing Hardspl I began to do so.
After reading the Idiots guide which stated :
'2. Flash the OEM ROM to your device (this will restore your OS but not the bootloader, we'll get to that below)'
I couldnt locate a proper T-mobile Wm6.0 ROM so thought as I'm just getting rid of the Hardspl I'd use the standard HTC ROM WM6.0 which went on fine.
This allowed to rid my phone of the HARDSPL.
I was then getting the Vender ID error when trying to load the new WM6.1 HTC ROM (which of course I would get as HARDSPL had been removed).
I then thought sod it and Ran SSPL-KAIS.exe and then began to run the latest HTC ROM. It started fine but bombed out at 15% and then I was left with a Tri-color screen and the message below :
In the Upper right hand corner it says RUUNBH
On the left side a little lower it says
KAIS1*0
SPL-1.56.0000
CPLD-8
At the bottom of the screen if I have USB plugged in it says USB, if nothing is plugged in it says Serial.
I cant seem to run MTTY 1.16 or 1.42 as I'm using Vista and the processes are slightly different (though I stopped what I thought were the relating ones to no affect)
Anyone on this awesome forum got any bright ideas as to how I can resurrect this one ?
btw : if I/we do manage to fix this one, do you think it will be possible to a) have a copy of the OEM T-mobile ROM ?? b) still upgrade to latest Wm6.1 ROM without the need for Hardspl ??
Cheers all
Steve
RUUNBH errors are from incomplete flag clearing after a flash. All that is needed is MTTY, 1.42 is best, & a few commands.
The first command is:
cmd>set 16 0
The second based on what SPL you now have (1.56) is:
cmd>boot
For use with Vista, you'll need to follow the dirsections used to flash via vista, & roll back the USB drivers. Do a search for Flashing with mtty and vista in google.
FANTASTIC !!!
Many many thanks for your prompt help !. Magic.
Im back up and running thanks to you brilliant help .
Do you think its worth trying again to Flash the phone using SSPL-KAIS and the latest HTC ROM ? or do u think I should quit whilst I'm back up and running ?
Alternatively, is there a way for me to sidestep the T-mobile lock without using HardSPL ?
Apologies for the questions, but after reading the many many posts on this, my brain is deffo boggled !!
Big thanks
Steve

D810 w/WM6 upgrading fail, error 260

I've spent whole day reading through the froum and the trinityguides.info site but can't find any proposed solution to work for my situation.
Device info:
ROM version: 3.00.707.17 (WM6)
ROM Date: 6/29/07
Radio version: 1.46.00.11
I've tried using all 3 versions of hard-spl but they all end up with the same result. With active sync linked and ready, ran the "romupdateutility.exe" at the end the PDA prompts if I want to run the "enterbootloader.exe", the moment I press yes the active sync connection would drop and eventually the program timed out with error "260" while PDA stuck in the tri color screen displaying the following:
TRIN100
SPL-1.07.ds
I've found some similar problems in the forum but those users are using vista however I am running XP sp3 in this case. I've tried all other solutions in the FAQ areas but none of them works.
My unit came with the WM6 already but I just want to upgrade the radio and get some cooked ROM to get faster performance. What am I missing here?
Any help is appreciated.
Once it drops to the tri-colour screen and is in bootloader, run the RUU again. Should be all that you need.
I've tried running it over and over but on the bottom it just kept on saying "serial" when it suppose to say USB.
Anyways, problem solved and it turned out to be the cable. For some reason the cable is good for anything, except keeping the phone connected/recognized while in bootloader mode.
I think this should be listed as one of the FAQ in the trinityguide. This might be a rare problem but it surely took me a lot time to figure out.
on Vista
Hi,
I have similar problem but I'm using Vista (Business). Is there any workaround ?
Regards,
Daneal
Hi
I have the same problem
spl 1.20 Olipro display serial instead of usb
I tryed several usb cables and still the same
when trying to update the rom it refuse to connect the ppc and end displayng the 260 error no connection
My system is vista and the first time I upgrade everything was fine, I followed all tutorials and no problem at all.
Do you think that could be this new 6.1 Mobile device center I recent install the cause?
best regards
Inabox
The problem isn't the WMC as such more the fact its Vista. Find an XP PC and do it from there.
Hi there, I had the same problem just now and cured it(in Vista). Just upgrade the htc driver in device manager again with "wceusbsh.inf" previous file, then should be ok. It seem to be Vista replaced the driver during it switched to Tri color menu.....

PC restarted while upgrading P3600 Radio. Please help.

Ok so I was upgrading my radio on my P3600 to 1.41.00.11 to enable GPS and when it started upgrading, the status bar started on the PDA (as per trinityguides.info's instrucions) but it didn't on my computer. My computer then switched itself off, was dead for about 3 seconds, then restarted itself. I pulled the USB cable from the PDA and now it is stuck in a bootloader style screen, but sais,
TRIN100
IPL-0.50
TRIN100 MFG
SPL-1.30.Olipro
A soft reset does nothing, neither a 'Battery pull-out'
I think that I am stuck in Hard SPL (according to Trinity Guides). Can anyone help me get the PDA back to normal so I can re-flash with the new Radio please? Thanks Alot.
P.s If it is of any relevance, My PDA was not synced with Activesync, But before the flash, I downloaded Activesync 4.5 to fix the 'Generic RNID device' problem on XP. It was identified on my pc as 'Mobile device' in my computer, as far as I can remember.
Sorry if this thread is not new to the site but as a noob (lol) im not really 'broken in' to the site yet. Thanks again for your help.
Hi everyone,
After further research, I reckon I should do the following:
1. In hard SPL, Connect it to another XP computer (my laptop)
2. Untick box called 'Enable USB connections' or whatever in Activesync 4.5
3. Open the ROM of my choice and Double click 'upgrade' or whatever
ROM][WWE][30.10.2008]Karmba_a Diamond Blue For Trinity
4. Wait for the ROM to install
5. Let the trinity soft-reset
6. Done!
7. Upgrade to radio '1.41.00.11' off trinityguides
8. Wait for the radio to install
9. Done!
Please tell me if im wrong so I know if there are any other steps to take. Thanks alot.
Ok guys, I guess, with time I solved my own problem. I did in the end connect my PDA to my XP laptop and used 'splxploit' (thanks to whoever made/programmed this!) which unbricked my device. Now when I tried to upgrade my radio again to a different version, because I have Olipro 1.30 installed instead of 1.20, I was unsuccessful. This shall be what I do next so I guess this thread is not needed anymore.
I'd appreciate it if one of the mod's would close this thread to try and save precious server memory, or can I do it myself (soz im new(ish) to the site!)?
Cheers Guys.

Categories

Resources