Update just radio in Vista - 8525, TyTN, MDA Vario II, JasJam ROM Development

I have a TyTN with official Russian WM6 onto it, which includes 1.16 radio version. I want a newer one, because this seems unstable, so i decided to update just radio (i don't want any cooked ROM or whatever for now).
Each new version of radio I found here failed earlier or later on a Vista x64 computer with error 260. What I have tried is 1.54.07.00 and 1.54.00.10 and 1.50.
To my surprise, packaging is different, but the effect is the same: after "Verifying the image on your device" (i can hear USB disconnecting and connecting back as the device enters bootloader) they time out with 260.
Right now I'm trying to revert what have I done to Vista as it won't allow me to turn off driver signing, as advised.
Ah, this doesn't work either (same error 260).
What am I doing wrong? My bootloader is, as said on that screen:
Code:
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
Yes, I have installed some...er...thing before, maybe it was called "HardSPL", but it didn't come handy and wasn't any use to me as I decided against cooking a ROM.
Update: What I like the most is, despite all my attempts the device still works! Other than the radio troubles, that is.

I've updated from an SD card.

Try this my friend... http://www.mrvanx.org

Thank you, I did.
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Click to expand...
Click to collapse
This is what I'm unable to do, but I suppose is beyond this forum.

Hi
I have had the same problem with my x64 vista pc and the 260 error msg. It took me hours but what seemed to finally fix it for me was to:
1. completely remove WMDC from the pc, reboot the pc,
2. reinstall WMDC plus upgrade,
3. uncheck the allow USB connections option on your 8525, exit out of the window, then do a soft reset
4. now make a USB connection w the PC
Let us know how it works

Sorry, you'll have to wait till my next upgrade Everything is working so far - so until I need something that can't be achieved using SD flashing I'll stick to this technique. Thanks for the advice anyway.

Related

Updating JASJAR

Hi all,
I have been trying to check out the forum here, to try and solve my problem, I literally bought my JASJAR today, and it was giving some wierd behaviour. In an attempt to reload the software (I prefere to reload the entire ROM), something went wrong, now all thats on my screen is "USB" and a lil lower down "v1.01".
ActiveSync obviously not connecting now bcos the OS is not on the JASJAR no more, in my device manager is a "Microsoft USB Sync" under my mobile devices.
I downloaded what I am guessing is WM6, 'JASJAR_WWE_20106_20301_11300_wwe_ship' from another thread in this forum, tried to load that but cant communicate with device cos no activesync.
I have tried the different reset options, like the 2 function keys and the reset on the back, I push 0 to clear, and then it jus goes back to the USB v1.01 thing.
I am running windows vista home basic, with the Windows Mobile Device Center, it synced perfectly with this software, communicated properly with the update tool, until my device reset and activsync lost connection, then i was stuffed.
Any help will be appreciated.
Thanks in advance.
Sounds like it is your first time with the upgrade. What you are seeing on the screen is the bootloader, which is what we use for flashing new ROMs.
ActiveSync or Windows Mobile Device Center (how come you have both on Vista?) will therefore not respond. This is fine, because we use a different program to load the new ROMs.
If you look at the folder you downloaded, chances are that there should be a program called "ROMUpgradeUt" or something similar. Provided that you have not changed anything in the folder, you should be able to flash the new ROM by simply following the instructions in the program.
You can also read this link for more information: http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
Here is an instruction guide on ROM upgrading: http://forum.xda-developers.com/showthread.php?t=269118
how come you have both on Vista?
Sorry, I don't mean to sound like I have both, I recently moved to Vista, and am used to calling it activesync and not WMDC.
Thanks, will have a look
Ok, well I have got it up and running again, only problem now is activsync keeps freezing when I try and sync the device...any ideas?
I landed up using my work computer, which has XP on it, and then used MTTY and that connected fine, on Vista it simply didnt wanna work.
I ran the utility for those 'stuck on serial/usb', and that fixed it. Now I would like to load up WM6, but it keeps getting communication failures.
Thanks for the help guys....I got it working...running on WM6 now...whoo!!

FLASH disaster

I was becoming an expert in flashing...but the cable became undone during a flash :-(
Now it restarts to a blank screen with R1.50.08.11 / G32.83.7020 etc. but goes no further.
Computer no longer sees device.
Used hard keys to go into bootlocker. (IPL 0.50 / SPL- 1.07.000)
My VISTA :-( computer sees device.
Then try RUU, but this gives a 270 error.
Tried moving to XP, but the computer does not install the software for the USB port, so now the RUU gives 200 error. Arrgh.
Question: How to update from a very corrupted ROM? Or where can I find the drivers for the USB port, for XP. and if I do can I do the update from the hard bootlocker?
Any help really appreciated!
MS
Update
Found USB drivers for Windows XP
But getting identical problem as with Vista :-(
Device not seen unless in bootlocker mode.
RUU starts and after 1% quits with 270 error - image file corrupt.
Tried RUU a hard SPL (olipro) but same 270 error occured.
Help still needed...
MS
I think you have to flash original HTC rom prio to try other roms
i got a similar problem here, my vista can find trinity only when it is in bootloader mode.
my experience is that connect tinity to vista when it is in bootlader mode, then i can flash a new rom.
after that tinity can sync with vista only via bluetooth.
for your case, maybe you really need restore your trinity to official rom first.
sailer1983 said:
i got a similar problem here, my vista can find trinity only when it is in bootloader mode.
my experience is that connect tinity to vista when it is in bootlader mode, then i can flash a new rom.
after that tinity can sync with vista only via bluetooth.
for your case, maybe you really need restore your trinity to official rom first.
Click to expand...
Click to collapse
Maybe helps:
http://trinityguides.info/index.php?option=com_content&task=view&id=20&Itemid=66
The trinity upgrade guide does not help here.
I can connect to device I have sorted out all the VISTA and XP issues.
The problem is at 1% status the 270 error occurs.
The telephone is actuall a Swisscom 1510. Original ROM was lost in first flashing, have searched but not found official update.
Is there a mini-ROM or a windows WM5 lite ROM which may overwrite what happens while still using the hard bootloader?
MS
Use SD card method.
See wiki page.
Bye
Hi,
...or .... MTTY Procedure....
BYE, Bobo
Tried SD card method - nothing happens. Just sits in Bootloader :-(
Try this procedure
In windows Vista use the attached driver in order to recognize your Device.
If your device is already recognized from windows vista replace the drivers with the drivers in the zip drive.
You have to use the drivers in the attached file not the windows default drivers VERY IMPORTANT!!!
After your Windows vista recognized your device try to flash it
Cheers
Thanks for all the help....but still I am having no success.
The HTC trinity is recognised in both Vista and XP when I use bootloader. (ie HTC USB SYNCH in device manager. Without boot loader the device is more or less dead.
I tried the SD crard trick - nothing happens.
Tried mtty.exe - just get cannot open USB port (on both VISTA and XP).
Nevertheless, the bootloader sees the USB port and the RUU goes to 1% then stops so some communication is happening.
Any other ideas?
MS
The final and, j' m sure, the definitive solution:
Try this one http://forum.xda-developers.com/showthread.php?t=308691&highlight=stack+in+bootloader
Just before I try splxploit, as a note I got this out of mtty
Cmd>info 8
Block 0x0(0) is Reversed block
...
Block 0xC(12) is Reversed block
Block 0x335(821) is BAD block !!!
Seems my problem must be here. Is there another fix besides splxploit?
MS
Install Olipro hardspl 1.20.
Bye
Dear, carefully look that thread again. Stack overflow for Trinity.
It's all my advise. I think you don't do right "Stack method" to get out your problem.
Best regard.(rest calm and do it again).
Uhm, try to download some rom again? and try Rom NVID (no vendor ID) for example. ???
Quick update...
Tried SD card - get 00068002 loading .... then goes to IPL0.5 SPL 1.07
mtty info 8 shows bad blocks
task 2a doesn't clear bad blocks because of CID lock
Tried various hard-SPL OLIPRO 1.2 1.3 etc, to unlock CID - to no avail.
Can the CID not be unlocked through mtty?
MS
ManStan said:
Quick update...
Tried SD card - get 00068002 loading .... then goes to IPL0.5 SPL 1.07
mtty info 8 shows bad blocks
task 2a doesn't clear bad blocks because of CID lock
Tried various hard-SPL OLIPRO 1.2 1.3 etc, to unlock CID - to no avail.
Can the CID not be unlocked through mtty?
MS
Click to expand...
Click to collapse
So you haven't yet tried splxploit?
END of STORY
YESSS!
POF you are a genius - Splxpoilt worked a dream.
Had to run unbrick.bat once. Hit soft reset, and run again as explained in the readme.
This got a good SPL on the machine - then a standard RUU worked a dream.
At the same time I got the SD card update working too...
OK, OK, so I should have tried splxpoit earlier. But I think I had to do the rest first to understand what was going on.
Strange thing is if I look at my machine again under mtty, there is still the Bad block (821). Who cares, I am unbricked!!!
By the way, this board is just completely amazing.
THANKS TO ALL....
i have the same problem
could you help me . how did you repair your spv?

Can't exit bootloader screen

Hi,
I tried to upgrade my XDA using Ranju's latest updater, the whole process failed and now I'm stuck at the BL screen "USB" at the top (when connected, otherwise it says "serial") and "v1.00" at the bottom.
My PC, SyncCentre and Windows Mobile Device Centre (I'm using Vista) all show the device as being disconnected (up until trying to upgrade everything had been fine).
As it's not showing up on my PC all of the software options for recovering it dont fail, all end with a plethora of USB not connected errors etc
I've tried the how-to on the wiki: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial to no avail.
Does anybody have any ideas? Greatly appreciated,
Thanks,
Lee
with jasjar-bl1.01-ruu-v1.2 I always restart my JJ Leave your uni in bl and start the application Good luck......
I think the Vista is not the problem this upgrade don't use AS or "in italian centro gestione dispositivi WM"
Bye
M.C.
Well, I flashed my Qtek a while ago, it failed to flash (using Vista) and doing a hard reset after it whas hanging at the startupscreen(the one with all the rom/radio numbers). No matter what I tried, following the instructions on Vista windows mobile center all failed... The good news is that your computer and your PDA still see when it is connected, ie USB/Serial, like in my case!
I then tried it on my desktop/XP, it flashed without a problem...
The funny bit is that I flashed my herald (WM6) 2 times using Vista without any problem...
I cannot explain but if U have the possibility, try and see if it works on XP...!
Good luck!
are you trying to flash it WITH your SIM card and / or SD card inside? If so, try taking them both out! It worked for me a few times!
I would start by getting rid of vista !
i had the same xprience
the different was i downgrade from wm6 to wm5 (i need the vcall)
failed in vista, succeed in xp
-> my advice : try in xp !! don't forget to remove the sd card
Manual for how to flash a rom in Vista
Read this post, you have the solution to the problem here:
http://forum.xda-developers.com/showthread.php?t=313001
You need to update the driver manually, if not, will not be able to install the driver.
You need to do this without sd/sdhc and without the sim.
If you follow these instructions, you can flash with success.
Greetings.
Kali.

[Question] 260 error when updating ROM

Okay, I've searched alot to get this thing solved. When I try to update my rom, the update starts normally, but then my telephone screen turns black, my gets disconnected, windows tells me it has found new hardware. The update failes and returns error 260 (connection lost). When I soft-reset the telephone afterwards, it returns to it's old shape.
Info about my telephone.
Rom: 1.93.404.1 NLD
Radio: 1.0025.05
PC: Windows XP SP 3, Active Sync 4.5
I tried to update with this rom: RUU_Diamond_HTC_NLD_2.03.404.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I also tried to update to Hard-SPL but that gave me the same error.
PLease guys does anyone of you know how to fix this? (personally I think it's windows xp which is screwing up).
Thanks in advance, I appreciate all help.
Yours, Martijn.
Even the tiniest tip may help (A)
I had the same trouble with that rom, I tried from internal memory and it worked. Search the wiki I am sure the info is there.
"ERROR [260] : UPDATE ERROR
This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again."
This is what the WIKI tells me. But I have tried that. How did you manage to perform the update on the internal storage? Because I tried that with hard-spl but it wouldn't work.
Besides I only have .exe files for the Hard-Spl and the official rom from HTC.
Thanks for your reply though.
EDIT PART, just read this on another thread in the wiki:
ERROR 260 (Update Error):
"Your phone is not connected to ActiveSync. Check your connection or restart the phone. Also make sure in ActiveSync that "Allow USB connections" is checked (under File->Connection Settings). If this still doesn't help, then remove the memory card and SIM card before flashing."
I'm going to try this now, if it worked, I'll let you know
Just found out I have a CDMA version or something, I'll try google for the problem now.
Get the rom image from your temp directory and look here, found in the wiki
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
dickenz said:
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
Click to expand...
Click to collapse
It looks alot like your problem yes. But last time the hardware installed correctly, then the patch I found for CDMA models on ppcgeeks failed, and my telephone got bricked. So I'll need to get that fixed first. After that I'll sure think twice before I try another rom update :/
Thanks for all the help though, and I have to advice everyone to not use the hard-spl for cmda users from ppcgeeks unless you're 100% sure it fits your model!

flashing problem

Hello,
I have a spv M2000 orange. I tried to update to windows mobile 6 I found here.
everything went fine at the beggining, but then activesync did the usual beep when disconnection occurs between pc and the smartphone. there was still the message saying "checking the information on your device... please don't disconnect... "I waited for a long time. but nothing happened then. still a black screen on my smartphone with "USB V2.07" written on it.
can anyone help me to find out a solution ?
thanks !
there is nothing lost or broken at this point, just try again using the instructions given here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
there is probably something you forgot.
thanks Chef_Tony, you give me back some hope !
I tried to flash back to wm2003, and it works fine.
I will follow very closely all the steps of the procedure described on the page you pointed at, and tell you afterwards.
thx again.
ok it works fine.
I forgot to remove the memory card when flashing the first time.
thanks again for the help
Hi. I'm a new member. I need your help. I try to flash my PDA2K with HTC_BlueAngel_WM6.1_WWE_Final_by_Ham3r using WMDC on my Pc with Vista... but without put my device into Bootloader mode. The software is started, my PDA2K was blocked with "USB" on top of the screen and "V2.07" on the right bottom. After nothing more. I tried SR, HR, like the instruction on http://wiki.xda-developers.com/index...ade1_WM2003SE0, but nothing. My PDA2K is dead. On screen, nothing. What can i do? I can resurrect my PDA2K? Thank you
ok, first of all, that link does not work. secondly, yes! your Ba is not dead, it is in a state called "stuck in bootloader" which is due to your attempt to flash under windows vista, which does not work the same way as under win xp. because, during the upgrading process windows vista, being smarter than xp, discovers the device changes and downloads new drivers and installs them, which disconnects the device, and in the beginning of the upgrade process the upgrade utility tells you, never to disconnect the device, unless the process is finished, but since vista is doing it on its oqn, you can't do anything about it.
normally i would advise beginners to use a windows xp pc, i even heard of people managing to upgrade from vista, using a windows xp virtual machine, but in your case, with the device already stuck, you should have a deep look over -=this=- and -=this=- before even attempting to flash again. then you should think, whether you deleted wm2003's extrom before you started upgrading, probably not!
so to upgrade, you should flash wm2003 again, first.
the entire process of upgrading is described pretty good -=here=-.
you say, you want to upgrade to wm6 from wm2003 and you use vista, then you get to all the steps needed for the first upgrade, please don't skip anything, please read carefully, if there is anything, you don't understand, please post back here, BEFORE destroying the device
with best regards
Chef_Tony
Thank you for your help. I'm following step by step the instructions of your links, but my PDA2K don't work. It's appeared again "Serial" at the top and "V2.07" at the bottom, but the Perform Reset don't appeared (point 3 of Link: http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5). Also WMDC don't see the devices either before or after the instruction on this link http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic ( i have never seen the boot option because my device don't make a perform reset). Help me....Thank you for you patience.
P.S.: I have also tried with my other pc with XP, but even ActiveSync see my PDA2K. However, in both my Pc, device manager show mobile device (microsoft usb sync).
I followed this procedure in this link http://forum.xda-developers.com/showthread.php?t=304408 with mtty.exe and my device is raised. Now is as good as new. Try with caution now. Thank you for everything.

Categories

Resources