Hey there all trying to upgrade to the new Cingulat 2.06 ROM...
It errors out when it reboots the phone to the bootloader...
I am currently on:
ROM Version: 1.34.502.1
ROM Date: 09/21/06
Rasdio Version: 1.16.00.00
Protocol Version: 32.53.7018.01H
Bootloader 1.06
Whats going on...
I am SIM/CID Unlocked...
Gromet
describe "errors out" plz...
when I click the "update" button, The phone reboots, and goes to the bootloader. I hear the USB disconnect sound...
Than the upgraders screen changes and gives me a "ERROR [206]: Update Error" AND SAID IT CAN'T CONNECT TO THE PHONE.
Gromet
Try the "safe flashing" best practices:
hermes directly usb connected to rear usb port on pc. no usb hubs allowed.
computer running winxp pro
close open apps
turn off any pc powersave mode
disable screensaver
I'm running Vista...
known issues there. I'd do some forum searching on it to find out more.
So than it's not something to do with bootloader 1.06... I thought maybe that was the issue, you think it's a Vista issue...
If you are supercid, bootloader version shouldn't matter. They can all flash in nbh...
Gromet said:
So than it's not something to do with bootloader 1.06... I thought maybe that was the issue, you think it's a Vista issue...
Click to expand...
Click to collapse
Vista is definately the issue,
do a search as I remember reading a thread a while back on a method to flash via Vista.
http://forum.xda-developers.com/showthread.php?t=291723
..ive tested and it does work
Related
Hi,
I'm trying to make my Vodafone 1605 VPA SuperCID, but when I run HERM_Unlock_v2a.exe I get a Windows error ...not a valid Win32 application.
I'm guessing this is something to do with my laptop hardware because I've had a problem loading other software due to the Due chip (Dell Latitude D820 - Centrino Duo etc).
Any advice appreciated - but be gentle with me 'cos I'm new to upgrading Windows mobile.
You actually copy that file onto your phone and run it from there, not the computer.
That should do the trick!
Thanks for quick reply - it shows how much I've got to learn!!!
Ran the file from my phone and got the "SUCCESS" message but when I checked using mtty.exe the phone still reports locked to vodafone.
I'll have a play and see what I come up with - hopefully not frying the phone in the process
ach2 said:
Ran the file from my phone and got the "SUCCESS" message but when I checked using mtty.exe the phone still reports locked to vodafone.
Click to expand...
Click to collapse
You _must_ be running the unlocker's patched radio 1.16 on your phone when you run HERM_Unlock_v2a.exe, otherwise it will report "SUCCESS" but do nothing.
Thanks Pof, but I don't know what to do next...
my bootloader screen shows IPL-1.00 and SPL-1.04.
My device info shows:
ROM version: 1.20.161.6
ROM date: 08/02/06
Radio version: 1.03.06.00
Protocol version: 32.34.7010.01W
I've read most of the WIKI (and even understood most of it) and also as many posts to this forum as I could.
Also, the 'available ROMs' page shows that this is the only ROM that Vodafone UK have produced and, bacause another poster has done the same thing with the same hardware and ROM I guessed I shouldn't have too much problem.
I think that as a beginner I must be doing something wrong or misunderstanding some of the lingo but would appreciate any more help which will get me away from the Vodafone ROM - and who knows, as I learn I may even be able to help some others later
Cheers, and thanks for all the informative posts
ach2 said:
my bootloader screen shows IPL-1.00 and SPL-1.04.
Radio version: 1.03.06.00
Click to expand...
Click to collapse
Follow instructions here, after flashing patched rom your radio version should show 1.16, then run HERM_Unlock_v2a.exe on your phone and wait the "success" message. After that you should be SuperCID, if not, read the unlocking thread... it has all been answered before.
OK, finally worked it out - all I had to do was RTFW - ALL of it, not just the parts I think are relevant.
Cheers for the help, I'm sure I'll screw up later and need more lelp but I've learned loads already...
Now trying to work out which ROM to use (except Vodafone) and hoping not to brick the phone in the process )
Ok...I have been through all the posts about upgrading etc. I still have a problem and I'm sure that I'm overlooking something....but I can't figure it out on my own. Here is what is happening (it does the same thing with every RUU that I've used...the DST fix...upgrading to WM6....etc)
1. I run the RUU and let it go through its routine (extract files, verify info on pc, etc.)
2. I check the box that says I have read the readme and click next
3. The next screen appears and it has the following steps:
Connect to the USB cable (check)
Establish an ActiveSync Connection (check)
Disable standby and hibernation on PC (check)
Make sure batter is > 50% (check)
Then I check the box and click next
4. I pick the update and click on the update button
5. I verify that I want to upgrade my phone from ROM verion x.xx.xxx to x.xx.xxx and click next
6. The program tells me that I am finally ready to update...and if I am sure I want to proceed to click next...so I click next
7. As soon as I click next...the progress bar comes up on my pc and my phone goes into standby mode (no bootloader...just standby). The progress bar never moves.
8. After a minute or two the RUU give me the ERROR [260]: Connection
9. I reboot my device and repeat steps 1-8
10. I reboot my device and my computer and repeat steps 1 - 8.
Now if I leave my device connected to the usb and close out the RUU after it gives me the ERROR [260], and then run the RUU again...when it is first verifying the information on my pc (before it asks any questions and before it tells me to connect my device) it will throw the device into bootloader mode. If I try to keep running the RUU while the device is in bootloader mode it give me the error that my device is not connected. I have tried and tried...maybe one of ya'll can help me. Thanks in advance
Chris
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
gerald_s said:
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
Click to expand...
Click to collapse
XP
No firewall
I tried to flash the WM6 from AT&T I assume its beta
and no did not install the Olipros bootloader
Ok...I think I found out how to do this...Ya'll can tell me if I'm screwing something up.
I go through all the steps listed above until it gets to the progress screen. When it gets there I manually put the the device in bootloader mode (Power, side ok, and reset). Once I do this...the progress bar starts moving. I will let you know if this works...
Hmmmm
Its not the way it should work but if it works its ok
You should have installed Olipros HardSPL first and then try to flash an official rom. If its working then something with your download is wrong.
What ROM is on there now?
Has the phone been CID unlocked?
Oli's CustomRUU is better, you may want to unpack the ROM and put the NBH in a folder with Oli's RUU and then do the upgrade.
BTW, gerald_s is right, you should not have to do that... what you may want to do is put the phone in Bootloader mode manually (while not connected to the PC), then plug in the USB, then start the RUU. That helps some people with 260 error.
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
You may be trying to flash a rom that includes the radio rom. What is your device? Is it possible that your device is a new x01ht with radio 1.14 and radio bootloader 0182? If yes, then you will get this error when you try to flash a rom with this method because during the flash it will be disconnected by the radio bootloader because it is not overwriteable. If you flash using the NBH file on the microSD, it will skip past radio and radio boot and just flash the other parts of the file.
mikebraeuer said:
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
Click to expand...
Click to collapse
If you are running windows XP, just connect the card to the computer, open MY COMPUTER, right-click the removable disk that is your microSD and then click format. Default in windows xp is to format using FAT32 filesystem which is perfect.
The thing is... if you dont know how to format a drive in Windows, should you be flashing your device yourself?
Which Solution???
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Wantoknow said:
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Click to expand...
Click to collapse
Have you tried flashing with your microSD?
Kevbodian said:
Have you tried flashing with your microSD?
Click to expand...
Click to collapse
I forgot to tell that, I had flashed through extra memory card yet, and could be done!
But I wanna flash ROM against CustomRUU through MS Active Sync as I had used before. Can you help me
i have a problem very similar to Chris. when i check the box "yes activesync is syncronised", and then the progressbar shows up and the phone goes into standby.
i've turned standby of in powermanagement options.
my os is XP
i use active sync v4.5
and this is first time i try this.
i've read something about this bootloader, i can get there but then i cannot sync with active sync. so i kinda stuck.
have been searching the forums and this was the same problem as mine but i don't understand your solutions.
//KufrA
--Problem solved--
i did all things without activesync,
1. start phone in bootloader
2. do the install
3. wait 0% to 100%, and done.
is there a problem with active sync or why do i have to do anything with it at all?
Hello,
I am new to this site, and also to WM based phones. I have run several searches on the forums for this problem and spent at least 3 hours today trying to run through the results, but I haven't found an answer that fits my circumstances. If the answer is on the forums, please forgive me, but I probably missed it because most posts start with one topic and become something entirely different within 5-12 pages.
So I have a Cingular 8525 with these stats:
Rom Version: 1.34.502.1
ROM Date: 9/21/06
Radio Version: 1.16.0.0
Protocol Version: 32.53.7018.01H
Windows Mobile 5.0
I am working from a Windows XP Pro, SP2 box with ActiveSync 4.5 installed.
I downloaded 2 different update packages. The first was the latest shipped ROM, the second was the official Windows Mobile 6 upgrade. I have a USB cable attached to a USB 2.0 port. This is what happens when I try to upgrade with either program (I have done this both with the SIM card in and without it in):
Method 1:
I connect the 8525 to the USB cable and run ActiveSync. It connects and syncs, then I run the Upgrade program I downloaded. It starts up, then I lose the ActiveSync connection to the 8525. A second or so later, I get the rainbow color bands across the screen and it sits there. The program gets to the part about how you might brinck your phone, and I continue with the upgrade process. It gets to the part where it is supposed to check for the phone's current ROM, and it shows a blank instead of the ROM's version.
Method 2:
I start the upgrade program, then when it gets to the part about connecting your 8525, I connect it to the USB cable, then run ActiveSync. After it syncs, I continue with the process. This lets me avoid the problem with the rainbow screen and it identifies the current ROM on the phone. I continue the upgrade process, and it gets to the part where it is supposed to begin actually doing the upgrade. Then the program says that there is a USB connectivity problem, error 260. It gives me the option to reset the 8525 and see if it recovers correctly (which it always does), then try again, but I get the same effect.
I can't figure out what to do, and any help would be greatly appreciated!
An Update:
On the rainbow screen, it says:
HERM100
IPL-1.01
HERM100
SPL-1.11
USB
Ok, this time I downloaded the latest update from HTC and ran it again. I got the same result as method 1, but even though it didn't show the existing ROM version, I let it run and it actually did update!
I now how WM 5 (still) and:
ROM Version: 2.15.502.3
ROM Date: 04/09/07
Radio Version: 1.40.30.00
Protocol version: 32.73.7020.16H
So far so good, but man that startup tone is LOUD! I am guessing that there was either a problem with the first upgrade I downloaded, or I just chickened out and didn't let the upgrade continue when I didn't see what I expected...
Hope this helps someone else!
Hi Friends:
Today, I tried to run my HTC MOGUL PPC-6800 in Bootloader Mode (SPL-1.07.0000) and then I run ROMUpdateUtility (Hard-SPL-MFG) to update the SPL to 2.40-olipro and I got the following:
- only 0%
- and finally ERROR [262]: UPDATE ERROR
I needed to do the recovery procedure and tired again and got the same results.
Can you help me?
Thanks
TecMan
Sprint HTC MOGUL PPC-6800
Windows Mobile Device Center 6.1.6965
Windows Vista 64-bits
You must establish a Activesync connection first and not be in Bootloader mode then execute Hard-SPL-MFG.exe. Checkout the updated Wiki:
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
search is your frined
I recently did the update with 2.40 and DCD's ROM, I had the same issue. I don't know what I did to make it magically work agian. I tried three different times. Anywho, sorry I can't be more help.
Hi Friends:
I solved the Error [262]: Update Error, it was very simple...
1. I run the Microsoft ActiveSync 4.5 with Windows XP-SP2 and then run Hard-SPL-MFG.exe and my NEW SPRINT HTC MOGUL PPC-6800 got a Bootloader Mode with 2.4.Olipro
2. I run RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship.exe and I had the following:
Windows Mobile 6 Professional
CE OS 5.2.1629 (Build 18136.0.4.8)
ROM version: 3.35.651.2
ROM date: 02/22/08
Radio version: 3.35.04
3. in Bootloader Mode, I run DCD_3.0.1_Sprint and I had the following:
Windows Mobile 6.1 Professional
CE OS 5.2.19199 (Build 19199.1.0.0)
ROM version: dcd 3.0.1
ROM date: 02/22/08
Radio version: 3.35.04
Thank you for your support and now my NEW SPRINT HTC MOGUL PPC-6800 is working great!!!
TecMan
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
mrfantastic said:
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
Click to expand...
Click to collapse
Run this to exit the bootloader.
Sorry run what?
Sorry that was the problem i have that the titan_exitbl.exe
and it wont work and gives me the error msg i mentioned
mrfantastic said:
Sorry that was the problem i have that the titan_exitbl.exe
and it wont work and gives me the error msg i mentioned
Click to expand...
Click to collapse
Oops, sorry I misread that the first time.
If you did uncheck the allow usb connections, you may to try killing the device center process. I've had issues with that before (I use Vista as well).
Look for wmdc.exe in the Process list and try killing that. It should work if you then reconnect your phone. I've had success going that route on Vista anyway.
Tried that too didnt work
Weird because i kno my computer realizes something is connected but I try the titan_exitbl.exe and get that error
is it because im running on vista?
hi all,
i have recieved a hermes with boot loader screen (tri color) when i try to switch it on it goes directly to 2 color screen doesnt go further at all. I've read the sticky thread . As the phone which i have shows on screen the following
HERM100
IPL-1.04
HERM100
SPL-1.40. Olipro
thats it nothing else exept tri color screen so read the sticky threadabout how to unbrick hermes and did following options when i flashed tmobile uk rom it goes further but it stucks at 11% and doesnt go further and when i try to flash a rom which has 1.04 (528420-ruu_hermes_1[1].18.255.3_1.18.255.108_1.03.03.10_qtek_wwe_ship) but it doesnt do anything with phone, it cant even detect the phone and give error straight away can anyone please guide me what should i do further to alive this phone
UPDATE - To easily unbrick type 2b (on T-mobile UK) - please flash with wm6 test from t-mobile @ http://forum.xda-developers.com/showthread.php?t=322905
SPL HTC_BOOT Boot OS? No GSM? KITL Diagnostic Solution
1.04 Any No No --- Bricked while flashing OS, radio intact Flash any shipped ROM with bootloader 1.04 on it 2 times (1.04 bug)
hi no reply but 53 views any mod plz help
WHaT YOU MEAN?
by:
UPDATE - To easily unbrick type 2b (on T-mobile UK) - please flash with wm6 test from t-mobile @ http://forum.xda-developers.com/showthread.php?t=322905
SPL HTC_BOOT Boot OS? No GSM? KITL Diagnostic Solution
1.04 Any No No --- Bricked while flashing OS, radio intact Flash any shipped ROM with bootloader 1.04 on it 2 times (1.04 bug)
---I think your hermes is bricked if you cant upgrade even a stock rom is bricked dude...
For the last thing you could do about it... flash a stock rom like ATT stripped you can find it on the WM6 subforum here on hermes forums... all the chefs put in the main post the link to it... if it doesnt works so... you are screwed up...
be sure ahave this:
Battery at 100% at least 60%
XP pc not vista not wm7 ok?
A nice usb cable and nice USB ports too on the XP pc
Dont run anything till it finish and... dont flash with SIM card and microSD inserted.
Go ahead and post your results again.
hi thanks for your reply i have tried these 2 following roms
HTC_TyTN_WWE_3[1].54.255.3_6275_1.48.00.10_108 (stucks at 12%)
RUU_Hermes_CINGULAR_WWE_3[1].62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship (stucks at 11%)
with these its not really working anyother thing which u think i should do
br
Sounds like the radio rom is corrupted. Flash a Stripped Stock rom (no radio) . This should get you back up and running windows but it doesn't look good to get the phone running again...
mmmm
Sounds like your batt is almost dead... maybe it shows... 70% but drains to fast is lying to you... or your cable is broken somewhere...
you can DL the stock stripped here
http://www.4shared.com/file/61372397/e2bf76c0/official_ATT_WM6_striped.html
ultramag69 said:
Sounds like the radio rom is corrupted. Flash a Stripped Stock rom (no radio) . This should get you back up and running windows but it doesn't look good to get the phone running again...
Click to expand...
Click to collapse
yes u r right mate my phones radio rom was corrupted and thanks to + Que PPC for providing help and link of the official AT&T WM6 striped rom which turned my phone back to normal but the problem is when i went to device information it says like this
ROM version: 3.62.502.3
ROM date: 10/11/07
Radio version:
Protocol Version:
so radio and protocol versions are blank nothing is there so can u please tell me wt should i do to solve this or its not solvable at all thank you very much indeed to you guys. I really appreciate it
br Sherry
Not solvable... You might like to try running your SHIPPED STOCK Radio Rom, if you know what it is, but there isn't much hope of recovery once the radio goes... Look at it this way, couldn't hurt....