Related
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
do you have a G3 or G4?
What are your IPL/SPL?
Which other ROMs have you had installed on this wizard?
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
My answer to you is the same one I posted to you before --
READ THE STICKY ABOUT UNLOCKING AND FOLLOW IT STEP BY STEP!!
Then -- and ONLY then -- will you be able to flash to a custom ROM.
newbie2 said:
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
Click to expand...
Click to collapse
Yep, I've replied to ecomajor's various posts in various threads and have basically given up. Very little info each time and having a problem that nobody else that has followed the steps has had.
Sorry ecomajor, don't know what else to tell you that hasn't already been said numerous times.
One Last Try -- Then, I Give UP!!
Read the following post on how to flash ANY Wizard (yes, that includes the 8125) --
http://forum.xda-developers.com/showpost.php?p=1177659&postcount=1
Now, follow the directions in that post WORD FOR WORD and STEP BY STEP. The only reason it wouldn't work is that you're NOT READING and/or NOT FOLLOWING THE INSTRUCTIONS STEP BY STEP.
If you CAN'T read and follow directions, then don't be trying to flash different ROMs to your phone. If you're not willing to do what's necessary to help yourself, then noone else is willing to help you, either. . . especially when your problem has already been replied to with the same information over and over in 2 DIFFERENT THREADS now.
Let me detail you the exact steps I have taken. I have read through those posts, many times so I am certain I took those steps
1)device starts normally goto step 3.6 since unsure if unlocked.
2) read farias thread
3) download buttons rom
4)attempt to downgrade rom - failed
4a)tried 1.08 rom instead of button - failed
4b)tried wizard love- failed
5)download lokiwiz
6)followed all directions -failed - since was not able to downgrade rom.
Obviously these directions are not 100% foolproof - I know that the first time I tried installing WM6, I did not read through all the threads and after much effort I discovered that if I installed the official cingular 225 rom then I could get my ppc back working but since then I have had no luck getting flashing to work. Please tell me what I am doing wrong because noone has had my exact situation. there is no need to act all holier than thou and accuse me of not reading because since I screwed up the first time I have read through all these threads numerous times.
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
And I've attached the ROM Update Utility Readme.doc that describes the error messages and how to fix them.
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
mfrazzz said:
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
Click to expand...
Click to collapse
ecomajor said:
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
Click to expand...
Click to collapse
I've never tried it in safemode so I don't know if that will work or not, it was just an idea as we are grasping at straws here. But if you boot to safemode, and with the phone at the bootloader screen (hold down the camera button while you turn it on to get to the "rainbow" bootloader screen), if it shows USB above the left softkey then the computer and phone are communicating and Activesync does not matter. BTW:You can try the safemode way there at work as you will have no network connectivity in safemode so you don't have to worry about violating security policies.
You still have not answered my one question directly... Have you tried flashing the button rom to your phone on multiple computers? Or have you always done it from the same PC? And are the PC(s) that you are using running Windows XP?
What DOC chip does your device have? G3 or G4?
If you have a G4 then i guess you ruined your bootloader since G4 devices don't have and don't accept 1.xx IPL versions!!
I have tried button from multiple pcs. This time it gets up to 98% on button and then dies and it gives error 302 - update error for the button. This is a problem that I was having before.
Did you read the document I posted?? If you're getting Update Error 302, you're not going to be able to recover with anything other than the stock Cingular ROM.
Chances are that you did indeed ruin the bootloader when you tried using the ShellTool to flash a G3 phone. And I doubt seriously that you'll be able to do a warranty exchange if you can run the stock ROM successfully, so I'm afraid you're stuck now with the stock-shipped ROM.
So you are saying there is no way to fix the bootloader (like flashing it or soething) I was figuring I had screwed something up. I actually had read the document before but thanks for your help. Why is it that you can fix many other issues with the 8125 but not the bootloader?
I'm not saying it CAN'T be done. What I AM saying is that in the year I've been registered and active here, I've not seen any posts/threads about recovering from a bad bootloader. But that doesn't mean that there ISN'T a way to do it.
You might want to do a search of the Wizard section for bootloader error or recovering bootloader to see what might come up.
Good Luck!!
I am new to completely flashing a custom ROM. I've been trying to flash a new ROM on my tilt, with the latest AT&T updates(ROM 1.62.502.0 Radio 1.27.14.09). Each time I try to flash a custom ROM I get Error 262 Update Error. The progress bar never gets past 0%. I've tried multiple PCs and tried reinstalling ActiveSync. Am I missing something, or do I have to do something first before being able to flash the new ROM?
Any help is greatly appreciated!
Steve
i suggest u read all the wiki's and stickies regarding flashing a custom rom before taking any action...u obviously havent read it or havent got a good understanding of it which is why ur getting this error...and btw..i also suggest u search for solutions rather than just posting a thread like this which can be answered through a brief search of the forums.
I am about 100% sure you searched, didn't you?
Here, baby boy, let me spoon feed you and you can ask your mommy if she can whipe your drool:
http://www.digwin.com/view/schaps-wm6-pro-roms-update-error-262
bapssystupr3m3 said:
i suggest u read all the wiki's and stickies regarding flashing a custom rom before taking any action...u obviously havent read it or havent got a good understanding of it which is why ur getting this error...and btw..i also suggest u search for solutions rather than just posting a thread like this which can be answered through a brief search of the forums.
Click to expand...
Click to collapse
I have searched the forums over the past week or so. The solutions suggested such as soft reset, hard reset, reinstall activesync, switch USB ports, etc have not done anything. I also came across this thread:
http://forum.xda-developers.com/showthread.php?t=370205
which would suggest that I there is an incompatibility. I was hoping someone could point me in the direction of which radio version etc I would need to update to in order to update to a WM 6.1 ROM.
edit:yes I have run CID unlock.
Steve
AT&T 1.62.502.0 w/ 1.27.14.09 radio should flash fine on any Tilt even without CID unlock, since it's signed by AT&T. While I'm glad to hear your phone is CID unlocked, it's still strongly suggested that you flash HardSPL & Security Unlock your device.
Regarding your current issue, have you:
* Tried another computer to flash from?
* Entered tri-color bootloader mode on your phone prior to flashing? You can find out how to on the wiki.
Hope this helps!
_Alex_ said:
AT&T 1.62.502.0 w/ 1.27.14.09 radio should flash fine on any Tilt even without CID unlock, since it's signed by AT&T. While I'm glad to hear your phone is CID unlocked, it's still strongly suggested that you flash HardSPL & Security Unlock your device.
Regarding your current issue, have you:
* Tried another computer to flash from?
* Entered tri-color bootloader mode on your phone prior to flashing? You can find out how to on the wiki.
Hope this helps!
Click to expand...
Click to collapse
Thanks Alex! Tri-Color mode worked!
Steve
My error 262 fixed
I don't know if this is the best place to put this, but I didn't want to open a new thread.
I too had been getting repeated error 262. And I spent a couple of hours searching for answers, and while there have been many questions raised on this subject, there have been few clear solutions (and certainly none that worked for me).
I have the HTC branded Kaiser installing from Vista. (By the way I am new to this, but as I had such a hard time working this out, I thought I should at least post what worked for me.) I unlocked the CID with pof's Hard-spl v1 tool. Then (as I want to stay with Mobile 6.1) I upgraded the hard spl to v3.28 by JockyW. I then downloaded a number of Roms I wanted to try. That is where the trouble started.
Each ROM I tried would get past the tri-color screen with no problem. Then it would hang at the 0% until finally showing the error 262. A soft reset would reload my previous rom unchanged. I tried many things: removing all USB's, firewall, virus protection, hard reset, reboot windows, every suggestion I could find (and understand).
While the hard spl I had should have worked, I thought I should try version 3.29. When trying to upgrade to that I had a similar problem with error 260 this time. Looking over spl update instructions I realized I had forgotten to uncheck "disable usb connections" in "Activesync" at the proper stage. Once that was unchecked, the new spl loaded. After that I was able to load the cooked roms with no problem.
It appears there was something wrong with the HardSPL v3.28 I was using or in how I installed it. The tricolor screen was showing 3.28. In any case, after I reinstalled a new hard spl (this time 3.29), I had no more error 262.
A bit long-winded, but hopefully this might help someone else.
Hi there, I've been reading your forums since I got my diamond. You have done a great job here.
Until now, I have been able to learn almost everything I now from here. (I'm new to ppc). Nevertheless, I have come up with something I cannot resolve.
I had installed hard spl signed from olinex (1.30). And also upgraded my rom to 1.93 without any problem. But when I tried to do the same with the radio (I want to go from .05 to .08) I get 260 errors over and over.
I use Windows Vista x64 which seems to be problematic but for me worked at first. Anyway I also tried to run it on Xp and go 262 errors instead so no luck with that.
I have tried several things I've already read. Switching USB port, starting the flashing on bootloader, disabling advanced network functionalities from Usb to Pc, ...
The issue seems to be with my PC not dealing with the device when the tricolor screen appears. USB is written in the white band, and Vista seems to recognize an HTC usb device. But when I try to run the CustomRUU when already in the bootloader mode, the app doesn't even recognize the diamond.
Otherwise it recognises it, but when it changes to tricolor screen and the progress bar appears it gets stuck at 0% until the 260 appears.
I think I have run out of ideas right now. Could any of you lend a hand, please?
im pretty sure you need unsigned spl for flashing radios. i dont think radios are signed. i could be wrong, so maybe wait for some more replys before flashing. btw welcome
Thanks. I suppose I'll wait as you said but you are probably right about that. Anyway I suspect that sadly that's not the main problem. I have tried to reflash my rom, just for testing if it worked and ... 260 . Trying to reflash HardSpl or trying to install an unsigned version didn't work either. I've downloaded from different sources to make sure that the file being corrupted was not the problem. I don't know if I'm doing something wrong or I was just extremely lucky the first time it worked
Hey everyone. I'm tearing my hair out trying to get this sorted but I just don't know what to do!
So, when I got my X1 as everyone on here should do, was flash my X1 with the HardSPL and some custom roms, this was a few months back. Then, shock! Horror! My case went and broke, (cracked near the volume button build W44) so I sent it back to SE for repair. I sent it back reset back to defaults but left the hardspl on there.
SE sent me a brand new phone (I think... This one says under the battery build w50, but the battery says w32..) I received it today. I thought it would be my old one repaired but SE had other ideas. Booted up and have Image Version: 1.03.931.10 and HardSPL 72.000 I think I said that correctly...
Now since sending it for repair and receiving it back, their seems to be quite a few wm6.5 roms floating about, and obviously I can't use the stock software as that wouldn't be right!
Now I have tried flashing the hardspl to the phone through my Vista PC and all it keeps giving me is connection errors. I thought maybe it was already flashed so I tried flashing just a rom, and that just made the phone get stuck on loading (flash by memory card). I thought it might be Vista, so I tried doing it on my other PC (XP) and I get the same issue. This bloody thing won't flash!
I have had "Connection Problems" - "Update Errors" with different numbers. The current one being Error [260] CONNECTION.
Now I have been searching around through the hardspl thread and other places trying to find out what I need to do or how I can fix it, but everything I try doesn't make a difference. I did read some other people with recently repaired phones having the same problem and perhaps SE have put a new spl thingy-ma-jiggy on there. (Please forgive the technical jargon, I have no idea what im on about.) I have also tried the ticking/unticking advanced network functionality, but that hasn't made a difference either.
So by the end of typing this, I have little hair left. Let's hope you can all help, before I have none left!
I would appreciate ANY help! Really.
Just wanted to add, I was at first getting the phone to a loading bar when flashing, but it would stay at 0% then flag up an error on the PC. Now after the tri-colour bars, the phone just sticks on Loading...
Well just to update. I have been trying to sort this since posting. I flashed the rom to an old UK generic one, as I read in another topic people had to do that before HardSPL. Done that, and tried flashing the hardspl. Same thing, just getting connection errors.
I tried going into bootloader and running the hardspl from there. It works and the phone gets to 10% and then gives an UPDATE ERROR. The phone is now bricked, and I have to reflash the original wm rom to get it back.
Though the Tricolour screen now shows 0.52.Olinex
Any ideas?
Shameless bump for help.
very stupid situation.
i have the same situation in puncto of flashing.
i get my phone three month ago.
after hardspl i .... sorry, no hardspl ... the phone says at 0% bla bla bla
i solve the problem by consulting one night absolutly stressing again and again and again .... google ... xda ... google
than 3 thinks at one time was the solution:
0. need activesync - connect !!!!
1. SDA_ApplicationUnlock.exe for desktop pc
2. enterbootloader.exe for pocketpc (please, the right version, it exist for eten too, but we need the xpediaversion ..)
3. changing registry-entries
how to:
activesync-connect, than copy "enterbootloader.exe" to pocketpc. it must be root, not sd-card. use a pocketpc-registry-program to change these values :
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies\0000101b = 1
if not exist than add the key.
now, start desktop-program, follow instruction EXCEPT reboot.
start "enterbootloader.exe" on pocketpc. now, you can install hardspl and the device is flashable for ever.
thats works on me, hope it could help you too.
Thanks for the reply. Not had time to try it till this morning. Ok so, after spending about an hour trying to find the correct enterbootloader.exe I finally realized, that the hardspl package includes it. *Duh!* So that was time wasted.
I changes the registry values as you said with Resco registry editor, and follower the unlock then enterbootloader.exe Start HardSPL package. Starts to install. Gets to 10% then I get
ERROR [262] : UPDATE ERROR
The rom update utility has encountered communication errors during the update process.
So im open to suggestions if anyone has any. I just can't understand why it's not working. It's not a problem with my computer or cables. I flashed the phone before I sent it for repair and I have tried doing it on two computers one with XP 32bit and one with Vista 64bit.
hmm. would u like to install a custom rom, or a stock rom?
msg me, and i hope, i can halp u.
I want to have the hardspl on there so I can flash custom roms.
If it's a case of the software/firmware/hardspl whatever you call it, has been updated by SE. How would one go about getting it flashed? Would we have to wait for an update HardSPL to be released?
U read this thread?
My first hardspl was from this thread. New X1 will come tomorrow back from SE (vibration was defect +++ some more problems with case), and i will try it again with this thread.
hope, this will help u mate.
Yeah, I have been through that thread with a fine toothcombe trying everything suggested to see if I can make it work.
When you get yours back, if you have to do anything out of the ordinary to get it to flash or can't do it. Please come and let me know in this thread. If they have updated yours like mine, and yours won't flash, at least I won't be the only one!
k, i will msg u tomorrow around 2pm.
Cheers.
In the meantime. Does anyone have any other suggestions I could try?
Bump, for some help.
now i know, what is exatcly your problem.... <--- SAME Problem
i hope, i will find a solution and msg u then. if u´ll got a solution for this prob, msg me too plz.
Solution found in this Thread!
Download this and unzip it to your device. ++ run it. It will start your X1 in Bootloader menu and say "0.52.OliNex".
Then start hardspl while X1 is in Bootloadermenu....
FINISH =)
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
vwrmic said:
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
Click to expand...
Click to collapse
hmmm... it works fine on my new x1. are u sure, that u start the ssplmanual on your x1 and not on your computer?
Yea, im not sure what the problem was with it. Thankfully I have it done and dusted today! Because I flashed it earlier to an older official version, and you said you got it working. I presumed you had - had yours flashed to the newest version due to it being off for repair. So I reflashed the official update and fully updated it. Then tried hardspl which didn't work. Tried with the advanced USB thing off, tried again with how you said you did it above, and Viola!
Hip hip hoorah! Thanks for the help. Can finally use me bleedin phone now!
no problem mate hf with your x1
hello,
i see smilies and yea's ...
for me to understanding (for next time or other users):
1. complete official update (if exists)
2. flashing (hardspl) without "advanced usb"
thats all?
cool.
I've done many flashes before. Maybe 1 too many (if possible???). I just flashed it and it seems to be stuck at the "update in progress..." screen, but it's at 99 -100% and it hasn't moved. I reflashed it 3 times and it's still stuck at this stage. I already HardSPLed it and i'm using energy rom. Do you guys have any idea what could be wrong? could it be because i flashed my phone too many times? i think i flashed it a total of 25+ times because after a certain point the phone starts to glitch up so i need a new flash... and i also like to keep updated..
please help! thank you in advance!
btw, I'm flashing via sdcard
Try RUU
Dear friend,
I had the same situation with my old Tytn II.
This is my recommendation:
If you have already done the HARD Spl,which is great,now do the following:
Go to the OFFICIAL HTC site and grab the latest stock 2.07 ROM.
Download it and you will get the RUU with it. RUU ( Rom Update Utility). Updating with RUU usually solves many problems when phones stuck at boot or whatever.
Follow the instructions in RUU and flash stock ROM.
But BEFORE you do anything,REMOVE that SD card with Energy ROM on it.
Please let me know if I was helpful.
Good luck,
Alexander.