Database Users

8525 cingular freezes in att logo

I unlocked the phone using the v3 pof method and it worked and the phone calls were working.. glad i spent the time to do so and went to bed.. this morning i turn it on and it freezes in the att logo and doesn't go anywhere else.. despite soft reset hard reset and doing the two button stylus method...
so is my phone bricked or fried? it sucks cause it was working and not it won't pass the att logo... i can go to the tricolor by pressing ok and power button... any suggestions/

Try flashing rom, SPL?

ok, so do you mean go somewhere like here
http://www.htcamerica.net/support/8525/software-downloads.html
to update the rom spl? i think my rom spl is 1.40 im thinking this is the latest or not? anyway i think latest might be 1.40.3 or something while mine is 1.40.01
is this what you mean by upgrading my spl rom?
since i'm able to only go to my boot screen with att logo only i can't go to the device section in win6 and see my rom version ... so i did the ok button and on button to get to the tricolor area.... and spl showed 1.40.. so is this the rom spl that i have?
im hoping this will help clear the att logo screen freeze... if not i have no other options..

i can't even upgrade the rom since it'sat that screen always... does this mean i'm stuck for good?

Try flashing HardSPL

monkeyisland90 said:
i can't even upgrade the rom since it'sat that screen always... does this mean i'm stuck for good?
Click to expand...
Click to collapse
you can still flash from that bootloader screen. see if the following link helps
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick

I forgot to mention i do have hard spl 1.40 ollipro
do i need to upgrade to the 2.10xx ollipro?
also looking at the unbrick from the wiki i need to
"flash only nbh containing os"
now i'm not sure where i can get this "nbh" file containing os and how i can flash it without being able to sync via usb cable since it doesn't get passed att logo splash screen...
BUT
I can go to the tricolor bootloader...
so if anyone can direct me on how i can get the "nbh" file containing os only
(not the nbh file containging radio only)
and how i can do so via the tricolor bootloader, i will give you a pat on the back! i have warm hands so you'll get healing from it also..

monkeyisland90 said:
so if anyone can direct me on how i can get the "nbh" file containing os only (not the nbh file containging radio only)
Click to expand...
Click to collapse
Pick a ROM (make sure it's OS only, most are), uncompress it, look for a file (usually. I've never seen a cooked ROM that didn't have this filename as the OS image, but one never knows) named "RUU_signed.nbh".
That that file and read the wiki on flashing the phone using an SD card.

Get stuck in Bootloader

Hi !
My P4350 got stuck in the bootloader when I stied to flash a new ROM
Active sync doesn't recognize the P4350 anymore....
IPL 5.04.0002
SPL 4.10.0000
What should I do now ????

search for bootloader... there are so much threads with the same question

Did it fail during the flashing process? Do you see an error message on the bootloader screen? ActiveSync won't recognize the device unless it is booted up in Windows Mobile. If you can still get into the bootloader reflash the ROM from there. You don't have to flash ROM's connected via ActiveSync; you can do it from the bootloader as well.

It did fail during an flash !!
The only thing on the tri colour screen: is: IPL 5.04.0002 and SPL 4.10.0000
When I try to flash a new rom it gives errors, it starts for 2 seconds and than it stops with an error. (on several occasions different errors ==> one error at the time).

Post some of the error codes you get. Have you tried flashing a different ROM? You may need need to use MTTY if you get a ROM upgrade code message in the bootloader itself.

Ehhhhhhh what is: MTTY if you get a ROM upgrade code message in the bootloader itself.
I have NO idea what you mean.
I had before an TyTN and that was no problem ever (until it died..)

Miep Miep Zoeffff said:
Ehhhhhhh what is: MTTY if you get a ROM upgrade code message in the bootloader itself.
I have NO idea what you mean.
I had before an TyTN and that was no problem ever (until it died..)
Click to expand...
Click to collapse
Is ur device CID unlocked(HardSPLed)?

Miep Miep Zoeffff said:
It did fail during an flash !!
The only thing on the tri colour screen: is: IPL 5.04.0002 and SPL 4.10.0000
...
Click to expand...
Click to collapse
I'm a retard. You don't have HSPL flashed to your device. This is why it keeps failing when you try to flash a ROM. The HTC SPL on your device is blocking you from flashing unsigned (custom) or CID-mismatching ROM's to your device. All you should need to do is flash HSPL and then your custom ROM. Read the Wiki for this device if you need more information.

My phone was provided by Vodafone.
I have now Telfort.
I flashed Vodafone to Canonyang.
Then I tried to put the Dutch back on it and then it got stuck in the Bootloader.
Wasn't it hard SPL than??

Digital Outcast said:
I'm a retard. You don't have HSPL flashed to your device. This is why it keeps failing when you try to flash a ROM. The HTC SPL on your device is blocking you from flashing unsigned (custom) or CID-mismatching ROM's to your device. All you should need to do is flash HSPL and then your custom ROM. Read the Wiki for this device if you need more information.
Click to expand...
Click to collapse
I've tried 2 different HSPL now.
It goes well, even says 100 % on phone AND computer but than it gives error 270 'update error'
What now...

Have you followed this? I know it works for me...

I've seen it, but where do I have to intall the 3 cab files?
Do I have to install them on the microSD card?
Do I have to put them like this .cab or do I need them to unpack them??
please help!

Copy them to your phone, install all three on your phone's memory.

ehhhhhhhhhhhhhhhhh How should I do that ??

Oh right. I'm retarded. You're stuck in the bootloader... Sorry just reading too many threads and getting confused. Have you tried searching for "bootloader" or "Goldcard" in the ROM development forums? There are tons of explanations on how to recover from being stuck in the bootloader.

Unable to downgrade my SPL from 3.13 to 2.20

Hi there,
Hope you can help me...
Since i bought my Cruise, I flashed it to the newest ROM version of HTC and it automatically installed SPL 3.13 with.
The problem is that if I want to install the WM 6.5 rom, I have to "Downgrade" My SPL version from 3.13.0000 to 2.20.
I followed the steps explained by "Olipro", but when the upgrade starts, RUU kills activesync (seems to be normal) and when the phone normally reboots in bootloader mode (like when you flash a new rom), nothing happens. The phone didn't shutdown and tries to establish a new USB connection !
I tried to turn manually the phone in bootloader mode on to force the SPL update, but the % bar stays at 0 and RUU returns a communication error (262).
I tried also to install the wm 6.5 rom without install SPL 2.2, but it crashes (stays @ 0% too)
I don't know how to install this stinky version of HARD SPL.
Heeeellllpppp !!
NOTE : I tried with or without µSd, does the same thing.
Thx

hmm try disabling firewall and antivirus one of them may be blocking the connection. Thats my only thought about it.

Thank you for the answer but it don't work...

Nobody can help me ?

Try to extract the files from the newest htc rom to a new folder, and then copy the "RUU_Signed.nbh" from the SPL V2 folder to the extracted files (to the new folder) and run the "ROMUpdateUtility.exe" from the extracted files (from the new folder).

nope ...

Please, consider my asks...
I know there is necessarily a solution but I have not yet found.
I don't know where/why it is crashing.
What does the HTC need to downgrade the hardspl ?
Is there a protection that can't be bypassed with the 3.13 ?
The only thing that I can do atm, is flashing the official HTC rom (useless ^^).
The actual version of my rom is :
_HTC Touch Cruise_RUU_Polaris_HTC_FRA_3.13.406.0_radio_sign_25.85.30.07_1.59.42.15_Ship
Thanking you in advance...

Pixel69 said:
Please, consider my asks...
I know there is necessarily a solution but I have not yet found.
I don't know where/why it is crashing.
What does the HTC need to downgrade the hardspl ?
Is there a protection that can't be bypassed with the 3.13 ?
The only thing that I can do atm, is flashing the official HTC rom (useless ^^).
The actual version of my rom is :
_HTC Touch Cruise_RUU_Polaris_HTC_FRA_3.13.406.0_radio_sign_25.85.30.07_1.59.42.15_Ship
Thanking you in advance...
Click to expand...
Click to collapse
HSPL 3.13? In this ROM is ver. 3.13 drivers, not HSPL... If you have original ROM and you dont install Olipros HPSL, you have original HTC SPL...

When I enter bootloader mode, the HSPL version is : 3.13.0000
Of course it's the original htc HSPL.
The problem is that I can't downgrade it to the olipro's version : 2.20.

Did you try it on other PC?

2 PCs, 2 USB cables..
The official rom upgrade works fine, I dont think that the problem comes from the computer.

definite guide:
1. establish a connection with activesync via usb (orbit2 to pc)
2. start the romupdateutility provided in hardspl folder.
3. before it starts flashing, you need to also follow on-screen instructions on orbit2!!! execute jump-spl and stuff: click yes on orbit2!!
4. when the orbit2 states: Replug USB. you need to plug the usb-cable once off and then put it back to connect to your pc.
5. it starts flashing and restarts after its done.

Hi Manaaa,
I don't know what is jumpslp ??
I found it on the web (xda..), copied it in my "my documents" folder, ran it but it asks me a jump address (default is 0x00000000) and an spl (*nb) file..
What is jump spl ? What is the address to jump to? and where can I find the *nb file ?
In the olipro's hspl folder is only a *nbh file.
Thank you

I wouldn't recommend using a jump spl for our phones if there isn't one in the Hardspl Pack then one is not needed to be run.
Personally im still really confused by this so if i get it straight.
You are synced with activesync.
Run the file for Hardspl Run RomUpdateUtility.exe
Then go though. It switches off activesync.
Then what?? Exactly Does it ask you to replug the cable? Do you get the rom flash screen (with %) at all??
Also i dont think that spl flashes can be run from the booloader as it has to be a modded bootloader (jumpspl if you will), loaded by the program to be able to flash the new hardspl.
Also i know very little on this, this is as much as i understand it to be.

chris10230 said:
You are synced with activesync. OK
Run the file for Hardspl Run RomUpdateUtility.exe OK
Then go though. It switches off activesync. OK
Then what?? Exactly Does it ask you to replug the cable? NO
Do you get the rom flash screen (with %) at all?? NO
Click to expand...
Click to collapse
Normally, after killing activesync, the phone turns into bootloader mode. Mine stays in winCE and tries to establish new usb connection...
I also decided to force manually bootloader mode and killing activesync by myself.
I ran RUU again, it first checked the phone state (such as battery >50%, connectivity...)
CHECK : OK
Next step, by clicking "NEXT" on the RUU interface, the phone turns in "% mode" and the update starts but stays at 0%.
After a while, RUU returns an update error (such as 262).
Noway to flash hardSPL :'-( , v3.13 seems to be "write protected".

ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. If this happens, you can just soft reset the device and run RUU again. The update process will then continue. At this stage the rom on the device is incomplete and it will not boot back up into Windows. You will need to place it into the bootloader to continue.
Click to expand...
Click to collapse
That is what error 262 is but really dont see why this happens either. And since you can boot into windows its not much help.
So it just wont go to flash it when you click it through, hmm
Your last resort would be to PM cmonex as she will have helped make this with oilpro. Ask and see if she can shed some light on this one. Maybe something has gone wrong somewhere (quite likely) that we don't know how to fix.
Stupid question but have you tried downloading, unzipping it again? May have been a bad dl... or unzip

Have tested it with about 10# DLs...
I PM'd Olipro, waiting for a response now

Flash back to HardSPL and don't Re-Plug
Hi Pixel,
Herewith are guide for you
1) Flash back to HardSPL and don't re-plug until end of session (5 minutes)
2) Flash back to original SPL 3.13 on this post . This original SPL for HTC Touch Cruise only
3) After you do this you cannot flash with other Cooked ROM or Shipped ROM
with different ID, unless you flash back to HardSPL
Good Luck my friend

I have exactely in the same configuration as Pixel69 with the same result.
I've tried to an other PC without any change.
Has somebody any idea?

Just had an idea what OS are you running to do it?
If its not 7 may not be fully compatible... Shot in the dark really

Ok, yeah..i bricked it..

So....i had read the thread and installed HSPL on my phone before i attempted to used a cooked rom, having tried to install my first one i find now i have the 'white triangle of death with upside down exclamation mark'.
I am on T-Mobile in the UK and i do not want to brick this beyond all repair..what is the procedure i should do now to get it working..i beleive i need to format a SD card to fat32 but which rom do i put on it and then what is the button press sequence..i have no connection via active sync anymore.

phone off - hold "volume down" - tap power whilst still holding volume down - phone will boot to bootloader (three stripes)
what does it say next to spl?
if
1.42.0000 then hspl isn't installed. what rom did you flash and how?
if says 1.42.HSPL then hspl is installed, plug in usb, wait for "serial" to become "usb" and flash your rom again from usb.

Thanks...
1.42.HSPL is what it says, it also says lower down 'upgrade ROM code error please try again' which i did do several times through the .exe on the rom i tried to upgrade to which i believe was TOUCH_X_TREME_21895_1_2_36_47, im not to sure whether the rom is compatible for me or even what i done wrong, i was relying on the fact that i had installed HSPL prior to trying to flash the new rom, i can confirm that the phone changes to 'usb' when i plug it in on the tri colour screen...so when you say try to flash the rom again what exact method do i use..when i tried the first time i just run the .exe file in the rom folder and followed the prompts
EDIT: having just followed what you said...i run the rom .exe file and followed through recovery and it says error 'error 302 update error'...what if the rom i am flashing is NOT compatible.

Why don't you first try to flash back a stock rom that you can download from http://www.4shared.com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html ?
Choose preferably a 1.48 rom.
Anyway, you'd better read the "flashing for noobs" thread in ROM dev forum before you go and do something even worse. You're probably trying to flash a corrupt file or something alike.

get the T-Mobile ROM from HTCs website, boot into the bootloader and connect and flash the stock ROM...that should at least get you working again

yea as above.sounds like a bad download or something. try a different rom or re download.
be aware the rom you are flashing needs a certain radio, so when it does flash it still won't boot till you flash the correct radio.(it's all in thefirst posts of the rom thread)
you have hspl installed so as long as you only flash by usb you are safe. just boot to bootloader, run the instal from the pc, phone will flash

EddyOS said:
get the T-Mobile ROM from HTCs website, boot into the bootloader and connect and flash the stock ROM...that should at least get you working again
Click to expand...
Click to collapse
Have done this..still not flashing, keeps giving update error, as i said..i have no active sync connection and it states that is needed ?...so how do i flash the rom ? also when you asked me to go to the tri colour screen and read off the HSPL part, on the green section it says 'upgrade ROM code error please try again'..is this normal in this state

Why am i getting this error when i try to flash it via usb...comuter still recognises phone but active sync does not connect to it so i am assuming this is causing the error ?

So when you go into the bootloader and plug in the USB does it say USB on the phone screen? If so, you also need to run the updater as an administrator. If this doesn't work, try another PC. If that doesn't work then you may very well have bricked it.
Also, are you using ActiveSync or WMDC?

EddyOS said:
So when you go into the bootloader and plug in the USB does it say USB on the phone screen? If so, you also need to run the updater as an administrator. If this doesn't work, try another PC. If that doesn't work then you may very well have bricked it.
Also, are you using ActiveSync or WMDC?
Click to expand...
Click to collapse
Yes it changes to USB when i plug it in, i am using WMDC but when i plug the phone in it does not connect anymore, i have tried running as admin but it makes no difference, i keep getting error 302.
Correct me if i am wrong, i thought the idea of installing HSPL would keep me safe from bricking the phone, i think all i initially done was flash an incorrect rom, ill try it on my laptop but that has not been in contact with the phone yet

What OS is on your laptop? if it's Windows 7 just plug in your phone and it will automatically WMDC so you don't need to install it first

Laptop done the trick !..seems to be doing the job now...dont know what the hell thats all about...
Would be helpful if knew what radio i had on it...and do i install rom first, then install radio ?

ActiveSync or WDMC wont recognise the device as the phone has not fully booted up.
With the phone in boot-loader mode and connected by USB, then run the ROM installation program. Ignore the fact that it says you must be ActiveSynced. Just tick the box and go into the next page.
As been said already, make sure you install the correct RADIO rom for the customised ROM. Once that is done, then you can install the ROM.
The best ROMs to download are ZIP'd or RAR'd ones, as they have a check that they have not been corrupted when uploaded or downloaded.

Well this is highly weird !!...i restored the Tmo dump from htc website but i now have the rom on there that i was trying to install previously before i bricked it...Touch X treme

What radio are you trying to flash? Read this and use this to flash the phone with the radio needed for your ROM choice:
http://forum.xda-developers.com/showthread.php?t=644781
Once done, try flashing the phone again (I'd make sure HSPL is on the phone too)

fred_up said:
ActiveSync or WDMC wont recognise the device as the phone has not fully booted up.
With the phone in boot-loader mode and connected by USB, then run the ROM installation program. Ignore the fact that it says you must be ActiveSynced. Just tick the box and go into the next page.
As been said already, make sure you install the correct RADIO rom for the customised ROM. Once that is done, then you can install the ROM.
The best ROMs to download are ZIP'd or RAR'd ones, as they have a check that they have not been corrupted when uploaded or downloaded.
Click to expand...
Click to collapse
So find out what radio i need before flashing, what if the radio i need to flash is not for the currant rom i am using...and am i right to say that some of these roms i cant use as they are not for the UK ?

All radios can be used, you can get them on their own and use with that link I posted before. going by the Touch X thread it says you need a 2.07 or 2.08 radio so get one of them and flash that first before flashing the ROM

I understand that better now...still not sure what went wrong there, from the laptop i thought and still do that i was flashing the stock rom for tmo from the htc website to restore the phone...but when it started up i was shocked to see the splash screen for the Xtreme rom..maybe i flashed that ?? if so why did it work this time..bad flash before ? and i have certainly not installed a radio myself...well thaks for your help anyway..the phone is up and running again and i will make sure HSPL is still there before i try my next rom

Likely bad flash - glad you're sortred now though. I always do the task29 with the radio nI want to use before flashing a ROM now to make sure the memory is clear...

Brick HTC Touch Viva

This is what I have done and transformed my htc touch viva into a brick :
I wanted to install WM 6.1 WWE 1.35.720.2 Stock ROM. I used Opal-SSPL-Manual.exe on my device. After that I installed version rom 1.35. After reset, I had ONBL 1.57.0000 and SPL 1.57.0000. Then I get the error "Your OS isn't customized for your hardware." Now I cannot revert to spl 2.00.cmon, I get error 270. Also I cannot install any other rom.
I really apreciate if anyone think that there is a chance to save my htc touch viva.

If you haven't tried to install any other rom using bootloader method then try:
1. Open your device's back cover.
2. Press the soft reset button (the red one) with ur stylus.
3. Just after pressing soft reset button immediately press volume down button and keep holding it until you see bootloader screen.
4. Then connect your mob with pc via usb cable.
5. Run rom update utility of a working rom.
That's it now it should work.

Thank you for your answer, but unfortunately when I try to flash a new rom I get error 294 : INVALID VENDER ID. Tried several roms, same error . I also tried to put SPL 1.26.0000 and SPL 2.00.cmon from my storage card (after renaming them as opalimg.nbh) with no succes.

Actually the biggest mistake you did is flashing another spl, why u did that just to install a rom from unknowns source and from a stranger (yes me talking about the user ddl.team).
Well, no more ideas left but try to flash the stock rom which came with ur device.

I am thinking to use htcRIE application to extract the SPL from there and modify it to allow me to flash any other rom, but I don't know what application to use to modify it.

Usually custom roms dont have any SPL so nothing to be extracted although you can try to remove spl and other things from stock rom and post.

Well, I tried, no success. The only thing that remained to try is to flash the stock rom which came with my device. Guess I will have to address to HTC service.

Lol you haven't tried to flash your stock rom?
I already suggested you, i think u just overlooked it. You should have read it properly. Anyways, try to flash if it didn't work then remove everything from stock rom except OS part with the rom editing tool.
Good luck.

that's why im afraid to flash cooked rom in my touch viva. mate,