I know this topic has been covered previously but the problem I am having seems unique
I have updated my univeral rom in the normal way but the device will not come out of bootloader.
I have removed the sd card and run the rom update again but to no avail the bootloader screen remains.
I have updated a few times using various rom updates ie o2 Exec/ Imate / Qtek and never had a problem before.
The only thing different about this installation is I put the rom unlocker (ref Buzz) and I can only think this is causing the problem.
Can anyone help
Hi jonboy,
just had the same problem few days ago and my heart dropped ;-)
Then I tried to install simply the phone-rom version 1.04.02 (I forgot from which package) - waited, rebooted and hurray
HTH for you as well
ndee
i´ve tried to run an RON update tp my tytn.
at all without success!!!!
every time i will get "error [262]: update error"
trying on
- Windows XP SP2 with all update
- activesync 4.5
on different machines
my tytn ist
ipl 1.01
SPL 1.09
and Schaps ROM 3.54c WWE
any idea´s for a solution
thanx
mhecker66 said:
i´ve tried to run an RON update tp my tytn.
at all without success!!!!
every time i will get "error [262]: update error"
trying on
- Windows XP SP2 with all update
- activesync 4.5
on different machines
my tytn ist
ipl 1.01
SPL 1.09
and Schaps ROM 3.54c WWE
any idea´s for a solution
thanx
Click to expand...
Click to collapse
Sounds like you have not read the instructions on how to upgrade your rom. There are many sources for the documentation. The easiest to understand are the upgrade guide by mrvanix. Maybe read about the unlocker/hard spl and read the wiki and mrvanix upgrade guides.
i have done the upgrade for a couple of times
every time the same way.
It work perfectly until the last update to schaps 3.54c
Now i get this error message
any idea?
try CID unlock.....search the WIKI
Maybe this will help you out... I have posted the error codes HERE...
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
thanx for this information
my tytn run´s fine - but the upgrade fails!!!
on the screen you can see "0% image upgrade in progress"
no further messages
on PC i´ll get the error [262]
after softreset everything seems ok
regards
When you run the update....select autodetect....sounds like you are running the wrong RUU for your SPL version...
....actually...update to HArdSPL v2.10 first...then run it. Your SPL at the moment is very risky to use and could kill your device......update to hardspl first.
thanx mrvanx's
your advice works great...
now i can upgrade my device to the current version ;-)
regards
262 update error
I just recd. my KAIS130 with the following:
Hardspl 1.81.0000, CPLD 8,
RomV: 1.56.405.5
Rom Date: 8/28/07
Radio 1.27.12.11
I have used two different laptops, usb ports, WINXP pro. The active sync 4.5works fine and is connected.
Trying to load HARDSPL V7 or Alex v52.ATT.162 ROMs i get 262 Update error. With hardspl it makes the ding sound disconnects the activesync and comes with error 260. i tried to disable the USB on the PC as recommended then it does not even recognize the kaiser. Did a hard reset on the whole device, reinstalled activesync several times. Some reason it disconnects my activesync. I have been reading and reading different forums for the last several days but cannot make it work. Can someone help please
maybe try to disable windows firewall
Tried disabling firewall too - nothing doing.
Configured a new laptop with XPPRO with no virus protection, firewall just bare bone. Copied HardSPL v7 and ran it same thing - active sync goes away, shows on the screen verifying info. reboots the kaiser and on the laptop shows "ERROR 260:UPDATE ERROR". Anyone any idea. It seems like it just does not want to load anything on the kaiser.
15Apr - Issue resolved with the new laptop. I was able to do hardspl v1 meaning downgrading I think from hardspl 1.81 and everything seems to be ok. Now i am able to load ROM with no problem - Whew!!
ROM HTC Cruise
Tengo la ROM de BEPE 0.67 Premium. Alguien sabe si hay alguna ROM mas nueva o mejor para prbar?
saludos y gracias.
ERROR [262] : UPDATE ERROR
I am getting this same error, follow the recovery steps and restart teh update (to radio 1.54.30.10) and it just continues in a loop. soft resetting does not help
anyway to get this bad boy out of the updater so i can use the PDA aspect of the hermes anyway? i tried to update the radio because it has been going quirky on me and saying NO GSM at startup
262 error updater error
Im trying to update from WM6.1 Pro to WM 6.5 built 21159 Beta 5 ROM but Im getting 262 error updater error. How can I get it to update?
Help with error: 262
SORRY to bother yu guys, but i think i ****ed up my X1 like i put da stock spl without downloading the original rom i already had an uploaded cooked ROM on it and when i was flashing the stock spl i got error 262 no matter wat i do the problem isnot going away all i get in the boot screen is a message saying:
Continue to upgrade ROM
Please wait...
If anyone can help that would be greatly appreciated
htc touch pro2 t-mobile
I Have htc touch pro2 t-mobile run´s fine - but the upgrade fails!!!
on the screen you can see "0% image upgrade in progress"
no further messages
on PC i´ll get the error [262]
htc touch pro2 t-mobile
help meeeeeeeeeeeeeeee plz.
Hi Guys
I have read all the threads and support messages re: Error [246] Device not responding. And mine is different.
I first experienced this problem after I flashed Pays 1.45 Lite after previously installing Pays 1.45 Full. When i try to flash any ROM (not just Pays) I get an "Error [246] Device not responding" message.
Unlike other Error [246] Device not responding problems my bootloader tricolor screen does not come up on my Hermes. I have tried, reinstalling Active Synce, Hard and Soft Resetting, Restarting the bootloader SSPL and still no resolution of the problem.
Sorry bring this problem to bear but it is different to your typical "Error [246] Device not responding " problem and it is driving me batty. the ROM i currently have installed works (Pays 1.45 Lite) and my USB syncs with active sync fine.
Any ideas what the problems could be? I am tempted to drown the hermes in holy water atm to make sure it isn't demonic possession ;(
Any help would be appreciated ;p
Quick update:
I used Force using Safe SSPL for installing ROMS in the past with no problems. It is using this method that I get the 246 Error.
Other methods used gain different errors:
SPL1.04/1.10 - SPL1.09 Bootloader = Error 260 Update Error (check phone attached to usb cable and computer - which it is)
SPL1.11/1.13/1.20/1.35/1.40 Bootloader = 1% complete progress the error 270 Update Error (file image is corrupted) NO MATTER WHAT ROM I USE.
SPL2.02/2.10/2.30 New Bootloader = error 270 as above
Bootloader Screen Reads:
HERM100
IPL-1.01
HERM100
SPL-2.03
I have successfully flashed about 4-5 roms before without experiencing this problem. I have made no changes to my device or my PC. I don't know what could have caused this to happen all of a sudden and out of the blue.
Could a moderator please move this to Hermes Upgrading etc section please?
Have you tried installing the latest Olipro Hardspl v7.... it will read as v2.10 which is a later release than the v2.03 that you have... it will also fix any bad blocks on your device and you should be fine after that...
Debonairone
You. sir.... ROCK!
Works great. Tragedy averted. Thoughts about buying an iphone extingusihed.
;p
Hi gurus,
Im having the similar problem encountered the Error [246] Device not responding.
I have try installing the latest Olipro Hardspl v7 but unable to work. I am still encountered the same problem.
Im currently on Dopod 838 Pro (Hermes 100) with PAYS ROM, Rome Date : 08/09/07, Radio Version : 1.47.00.20, Protocol Version 32:80.7020.20H
Any advises and ideas ?
debonairone said:
Have you tried installing the latest Olipro Hardspl v7.... it will read as v2.10 which is a later release than the v2.03 that you have... it will also fix any bad blocks on your device and you should be fine after that...
Click to expand...
Click to collapse
can i use this olipro v7 for the herald/wing? i am unable to flash anything. i am hard spld and i have a working rom, i just dont like it. thanks
NO!!!! Using the Hard SPL for ANY Version of HTC device it wasn't intended is the fastest way to brick your phone...
ultramag69 said:
NO!!!! Using the Hard SPL for ANY Version of HTC device it wasn't intended is the fastest way to brick your phone...
Click to expand...
Click to collapse
cool, i didn't use it. but i can't flash anything. this stinks. i'm stuck with a rom i dont want.
Hello I have an at&t tilt and it is freshly resetted with nothing on it. When i try to upgrade it with any type of rom it always gives me error 262. i followed all instructions that were given and it still does not work
Hi All,
I think I owe all of you this post.
I have been stuck with the Windows Mobile Screen(NO GSM) for over 2 hours today. I was trying to restore my dopod 838 pro to WM5 (WWE shipped) coz i was having so may issues with the WM6.5 versions. Here's what I did:
1. Tried to run the official installer found in the HTC Site. Didn't work so...
2. Took the .nbh file and used RRUWrapper.exe to load it into the device.
It worked but got NO GSM everytime I tried to boot.
I scoured the threads for solution and this was the recap of the things I did...
1. Entered Bootloader, reran RRUWrapper.exe to reload the WM5 rom.. Didn't work
2. Entered Bootloader, reran RRUWrapper.exe to reload DarkVisions v5 rom. That was what i used before the issue. Didn't work.
3. Removed battery for 20 minuites. Restarted phone after 20 mins. Still the same issue (stuck on bootscreen - no gsm)
4. Entered Bootloader, reran RRUWrapper.exe to load the official WM6 WWE (for tytn) rom. This seem to resolve it.
I always flash the rom without sim and microsd. I have inserted the sim and card, rebooted 2x... everythings normal...
I think it goes without question that i'll be sticking to this rom... At least its the official rom...
Thanks to all your posts from before. They all helped...
it didn't work for me.. any further suggestion?