Related
I have never flashed this phone with any kind of alternate firmware, yet when I go to run the official one from HTC, I get this at 8-% exactly, on 2 diffrent phones:
_______________________________________________________________
ERROR [326]: INVALLID COMMAND
This NBF file cannot be used with for your PDA Phone. Please check you NBF file.
_______________________________________________________________
Then the phone turns into a brick. All it does is show the Tri-Color test looking screen untill try to flash again...
Any suggestions?
What phone do you have?
Whoops....
Sorry... I posted this in the wiz forum and didnt even think to put my phone model....
Cingular 8125
Thank you!
Re: Official Cingular 8125 2.25 Update ---Problem---
pittaman said:
I have never flashed this phone with any kind of alternate firmware, yet when I go to run the official one from HTC, I get this at 8-% exactly, on 2 diffrent phones:
_______________________________________________________________
ERROR [326]: INVALLID COMMAND
This NBF file cannot be used with for your PDA Phone. Please check you NBF file.
_______________________________________________________________
Then the phone turns into a brick. All it does is show the Tri-Color test looking screen untill try to flash again...
Any suggestions?
Click to expand...
Click to collapse
If you are attempting to flash the official ROM on an 8125 and getting this error, there's some bad juju goin on.
Just to be sure, you got the following ROM, correct?
http://www.htcamerica.net/support/software_downloads_8125.htm
I’ve downloaded that so many times my browser is upset at me. There must be a lot of bad JuJu... because It has tanked 2 different phones.....
I’ve taken your 2.3 update, and ran it... It went though... got to 98 and turned red on the phone... finally went to 100% and rebooted... but it was still at 1.8... but at least the phone works again... I really need the push e-mail though... and would prefer to use the official update... or a close derivative..
You should CID unlock first before you apply any ROM found in this forum.
If your phone is virgin, i.e. never been updated to a non official ROM, you will be fine going from 1.8 to this ROM and you would not need to CID unlock. I have gotten an nbf error before, but it was from an attempted downgrade to the stock 1.8 ROM from Summiter's 2.17 release.
Check your OS version and report back.
I know it says you have never upgraded before... If you're still having problems, just take it back to the store, we bricked a phone stuck on the 2.17 ROM and returned it with no problems. Apparently the 8125 does not like animated themes (not my idea, but it did have entertainment value).
Could there be something up with my PC if it bricked 2 seperate phones? WOuld it be possible to fix em with a diffrent PC? and do you think a Cingular store would update the firmware on the phone if it wasnt broken already?
pittaman said:
Could there be something up with my PC if it bricked 2 seperate phones? WOuld it be possible to fix em with a diffrent PC? and do you think a Cingular store would update the firmware on the phone if it wasnt broken already?
Click to expand...
Click to collapse
There's always the possibility of a virus causing issues, but it's exceedingly remote.
If the phone is working you should be able to bring it into any Cingular store and have them do the update for you.
pittaman said:
Could there be something up with my PC if it bricked 2 seperate phones? WOuld it be possible to fix em with a diffrent PC? and do you think a Cingular store would update the firmware on the phone if it wasnt broken already?
Click to expand...
Click to collapse
I concur with gamescan that it might be a virus, or some crappy spyware. I don't think however that you've "bricked" your phones as you WERE able to install sumitter's 2.23 OK. Of course since you didn't SID unlock you didn't get the full upgrade. I disagree with those who insist that you don't need to unlock. Mayhaps you don't need to but I know that sumitter and the other ROM gawds here have always suggested so. If I was you I'd downgrade to the 1.05, unlock, then upgrade. I'd also scan your PC with Spybot, maybe AdAware. Also I'd delete my temp files, in the c:\documents and settings\%username%\local settings\Temp. Also empty your temporary internet files. I've seen large temp folders on PC's create all kinds of grief. Just a suggestion.
Steven
chow
Well... I appriciate all your help thus far.
I called Cingular Yesterday ant they sent out 2 replacement phones for free, and I got them today... With the update already in place, so I dont think I'll be playing with unlocking again LOL... But this information is very helpful, as my Uncle has the same phone and needs the push email more than I do. If his phone gets toasted, Ill be here with the results...
Thank you all very much... this is my new favorite place!!!
Not A virus .... its the phone
Apparantly the newer phones have a new flash chipset G4 which is not compatable with the current crop of cooked roms on this site. I think summiter has one that will work but it didn't work for me. I returned my phone for a replacement hoping to get the g3 chipset but to no avail all the new ones are G4 and are unable to be flashed to the custom roms. also you should be able to sim unlock with no issues but to cid unlock you may need to look elsewhere
Re: Not A virus .... its the phone
alynch75 said:
Apparantly the newer phones have a new flash chipset G4 which is not compatable with the current crop of cooked roms on this site. I think summiter has one that will work but it didn't work for me. I returned my phone for a replacement hoping to get the g3 chipset but to no avail all the new ones are G4 and are unable to be flashed to the custom roms. also you should be able to sim unlock with no issues but to cid unlock you may need to look elsewhere
Click to expand...
Click to collapse
First, the OP was using the OFFICIAL CINGULAR UPDATE not a custom Rom.
Second, He was upgrading from 1.8 which is a 1.x Rom, this means his phone is indeed a G3 variant as the 1.x Roms only have G3 IPL/SPL.
I had this same experience from a virgin HTC 8125....
I had stop all apps running and recharge my battery. Then disable my sleep and screensaver then it worked.
Hey All-
I'd appreciate any help anyone can offer. I am having problems updating to any of the WM6 ROMs out there (up here). One of a few things is happening:
1) Either RUU crashes just after it successfully sends my PDA in to bootloader mode, or
2) RUU is able to stay up, but for some reason, does not like the update file:
I either get an error: "This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.", or
it suggests the nbf file is "corrupted", I think indicating the RUU util I am running is out of synch with what the PDA is expecting.
I'm using a T-Mobile MDA (Vario?) and Vista.
I've tried all of the solutions I have been able to find:
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
* various flavors of the update utility to get around the crash, which do not let me upgrade to the ROM of choice!
* hard reset of the device
* I even tried pulling down one of the ROM upgrades from the T-Mobile dowloads site and dropping that in with a WM6 ROM nbf file. That was a huge flop.
I know people have done this! I've seen it over and over again. So what in the world stupid thing am I doing to not make this work?
Thanks.
Joel Niemeyer
Seattle
RUU doesnt work on Vista. Use shelltool.
Thanks for the advice. I'm sure it was good advice, but I am three hours in to it running now, and I don't have a good feeling about it. I think it says it would take at least 15 minutes. Not 180! Ugh, now I wonder what I should do?
Joel
jniemeyer said:
Hey All-
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
Click to expand...
Click to collapse
How do you do that? Thank you because when i try to downgrade my ROM or w/e so that i can unlock it when i gots to bootloader the fred green blue thingy it doesnt reconnect to active sync and maybe thats my probelm...=[
chaos, just look around for the RUU with Vista instructions- they are everywhere!
hey mate,
just follow this instructions http://www.modaco.com/index.php?showtopic=252977 to falsh every official ROM under MS Vista. Surely, when it comes to WM6 you gotta use the Shelltool.
regards
irm
Answer for Vista
My question is why don't people just dual boot vista with xp or 2000/etc...that would solve a lot of issues about the problems with vista.. just boot to xp..
I figure if you have the $Funds$ to spend on a $250+ phone you could shell out $50 for a 150gb 16mb cache HDD for your pc and dual/tri/quad/etc... sheeet son i've been doing this for years with linux/m$/mac.
Gotta face it, some software just runs better on one OS over another. peace out.
can someone confirm shell tool work
ANTC said:
can someone confirm shell tool work
Click to expand...
Click to collapse
I tried it, took like 6 minutes then it was completed, knowingly it wasnt flashed right, but did the hard reset on the phone and was stuck at the SPL screen, so just loaded up VMWare to reflash.
It worked for me...
I flashed one of the WM6 ROMs using my Vista Ultimate computer. One of the main parts in making the thing work is remembering to put your computer in bootloader before doing it. On post #7 in the MoDaCo thread, it says this.
Once more, here is the link: http://www.modaco.com/RUU-on-Vista-It-can-be-done-the-ultimate-guide-t252977.html
so your saying witht hat tut you flash a custom rom??
Yes
Yes I was able to. I don't remember which, but I think i was Core 2.0
Yeah, I was able to use shelltool to make this happen. Thanks for the feedback, folks. Only hang up was that it had appeared to have seized up (was seemingly stuck before the "End" portion). I waited for like 3 hours before I finally threw up my hands and hard reset the unit. Low and behold my wizard booted up in to the new ROM and I have been good to do since!
Hi Guys,
i consider myself relatively experienced at flashing HTC devices having been using and upgrading for a few years but i've run into an issue on my CID locked G4. i upgraded to WM6 without issue and i tried to revert back to my O2 rom, the flash failed and i'm now stuck at the splash screen. I've tried to flash the original ROM from boot loader but i get a 101 error unable to connect(can see it in device manager). as i'm using vista i did a search and found some instructions and driver files but i get the same result. the only thing i can think of now is to CID unlock but i'm not sure it will help (unless it allows me to do the SD card restore). any ideas guys?
IPL:2.21.001
SPL:2.21.001
GSM:02.25.11
OS:10.1.0.811
OK., what you need to do is use a PC with XP, because i have read that vista PC's can get you into a lot of trouble. When you are at an XP PC, follow the instructions in my previous post
( http://forum.xda-developers.com/showthread.php?t=313354 ).
When you flashed the original ROM, and you succeeded in doing so, think real hard if you still want to upgrade to a new ROM.
If you still want to do that, stick to a PC with XP installed (no vista!).
If you did reflash a good ROM into your HTC you'll be one step closer to upgrading your ROM.
Read this post thourougly :
http://forum.xda-developers.com/showthread.php?t=298613
as this will help you in case you didn't CID unlock your device.
(thanks vippie; this is the clearest walktrough i could find!)
If you are really sure you CID unlocked your device, you can flash your device to any ROM you think is useful to you.
If your device is really CID unlocked, you should be able to flash any ROM that is posted on this forum.
I know that it is that easy, because i have tried every WM6 ROM that is posted on this forum
good luck, and i hope in the end you will have the ROM that you want....
thanks. my device IS CID LOCKED and i've tried to flash it from 2 XP machines so it is looking like its a brick thanks anyway.
for sale wizard with pretty 3 colour screen - sold as seen!!!
One thing you can try is use another USB to mini USB cable, i have had one cable that didn't connect really well.
Sometimes it worked but if i moved my phone the connection went down.
I just thought of that because it was a while ago that this happened - I threw away the faulty cable and had no problems after that.
tried 3 different cables too
knownuser said:
tried 3 different cables too
Click to expand...
Click to collapse
How much do you want for it? I need a new screen and body shell!
jabreu203 said:
How much do you want for it? I need a new screen and body shell!
Click to expand...
Click to collapse
was actually kidding i'd like to fix it but i'm open to offers PM me.
ok .....HELP
i've paid for the CID unlock which went well i then tried to flash the O2 default rom failed error 101 (connection) i then tried wizard love failed error (300) in italian.
so stage 2 was to use the sd card recovery i ran the utility and then followed the instructions r2sd all etc..all seemed fine i restored the image to the wizard and rebooted it still won't go past the splash screen i've tried re-flashing and hard reset still no go....please guys any help???
If you have a memory card take it out. Right click on ActiveSync and go to connection settings. Uncheck allow usb connections then try to flash. With windows XP...
tried to flash on a win2K machine (4 pc's thats the only one thats not vista) still get error 101 on the original O2 rom and 300 on the wizard love rom.
still no joy anyone have any ideas???
http://www.t-mobile.hr/mdasw/RUU_Pro...R_WWE_Ship.zip fixed i'm on a tmobile rom i'll try downgrading again.
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 tried flashing the Hard-SPL so I could flash the Evo 6 ROM but no matter what I do, manual flash auto flash different USB ports different cables different cab files nothing works. I have a stock ATT ROM on my Tilt 2. I was able to flash my Tilt 1 to 6.5 but for some reason every time I try to flash this one it just hangs and I have reset the phone.
Any advice? I'm kinda stuck here. anyway to flash off the phone without having to go through the PC and USB cable? As of now the phones stock with no mods.
Need more info
Are you getting stuck flashing Hard SPL or the when flashing the ROM?
You should probably try posting on either the Hard SPL thread or the "Flashing your first ROM" thread, depending on the answer. They will be more specific to your issue.
ar91207 said:
I tried flashing the Hard-SPL so I could flash the Evo 6 ROM but no matter what I do, manual flash auto flash different USB ports different cables different cab files nothing works. I have a stock ATT ROM on my Tilt 2. I was able to flash my Tilt 1 to 6.5 but for some reason every time I try to flash this one it just hangs and I have reset the phone.
Any advice? I'm kinda stuck here. anyway to flash off the phone without having to go through the PC and USB cable? As of now the phones stock with no mods.
Click to expand...
Click to collapse
Basically what happens is at the progress screen it never passes 0% and it acts as if its not connected to active sync. Even though it is, I initially tried to flash the ROM first but then tired the Hard-SPL and got the same results.
You should definitely post this in the Hard SPL thread by Olinex. You'll find great help there.
Good luck.
ar91207 said:
Basically what happens is at the progress screen it never passes 0% and it acts as if its not connected to active sync. Even though it is, I initially tried to flash the ROM first but then tired the Hard-SPL and got the same results.
Click to expand...
Click to collapse
don't know if you fixed this yet but I would check to make sure that you unzipped the files, both the hspl and the rom files before attempting to run them.
ar91207 said:
I tried flashing the Hard-SPL so I could flash the Evo 6 ROM but no matter what I do, manual flash auto flash different USB ports different cables different cab files nothing works. I have a stock ATT ROM on my Tilt 2. I was able to flash my Tilt 1 to 6.5 but for some reason every time I try to flash this one it just hangs and I have reset the phone.
Any advice? I'm kinda stuck here. anyway to flash off the phone without having to go through the PC and USB cable? As of now the phones stock with no mods.
Click to expand...
Click to collapse
Install this to your device and softreset...then try to run the hardspl again...
I just went through the very same thing. The CAB jhernand1102 posted above fixed my HardSPL problem. Using the latest HardSPL app (v2.00R3), it would fail to detect that my Tilt 2 was connected when selecting the Automatic process. On the final window of the HardSPL app, it gives a URL where to download the CAB file. I installed it on my phone, then was finally able to run the HardSPL app in Automatic mode.
What version of windows are you running? Have you tried downloading mobility center 6.1 and the matching drivers? I had this problem as well. Once I downloaded the update for windows mobility center I have had no problems at all.
You need to post your questions(s) in the HardSPL thread