Database Users

opps

Alright well i was trying to update my MDA to WM6 and it errored at 96% and now all i got is the three color thing.
My question is, how do i go about fixing it and reinstalling an OS?

You need to specify what your IPL/SPL is so we can tell if this is a G3 or G4 phone and what state its currently in, but... Since you have the rainbow boot loader screen, with the USB attatched, you should be able to run your carrier's official rom to reinstall it.
A lot of the ROMs will pause for 5 mins or more around the 95% mark (it varies, I've seen some pause like this at 80%, some 90%, some 95% or 96%), so you just have to wait for it to finish (or you get an error on your PC).
If you are wanting to load a custom rom (or one not from your carrier) then you need to go into the Wizard Upgrading forum and read the stickies at the top. If you have a G3 device, the Faria and Dr P stickies are the ones you want. If you ahve a G4, then read the sticky for upgrading a CID Locked device...
Good luck (and be careful. make sure you read and read and read )

Alright, thanks for all the help, i just need to find my T-Mobile disk now. lol. which might be hard seeing as im kicked out of my home and don't have all my stuff just yet.

Folic said:
Alright, thanks for all the help, i just need to find my T-Mobile disk now. lol. which might be hard seeing as im kicked out of my home and don't have all my stuff just yet.
Click to expand...
Click to collapse
?if you mean the cd that came with the phone from t-mob and the official rom. it almost certainly won't be on the disc as the phones are sold with the rom already flashed, and they don't want you to be able to flash another rom so they would not provide it to flash back to. you'll have to search for it. if you are usa t-mob http://www.t-mobileapps.com/downloadcenter/Software_List.cfm?selDevice=24
otherwise, google.

Error 270

I really hate to make a bad first impression but...
No matter what I do I get this error. I was trying to HARDSPL the phone, I put it into boot loader mode, I installed all the .cab's . It starts the progress bar up gets to about 3% and the phone screen goes black and restarts and then ERROR 270 shows up in the RUU. I searched around but found nothing for the Herald about it. Just asking for any help as to what I can do.
Thank you in advance.

diacronic said:
I really hate to make a bad first impression but...
No matter what I do I get this error. I was trying to HARDSPL the phone, I put it into boot loader mode, I installed all the .cab's . It starts the progress bar up gets to about 3% and the phone screen goes black and restarts and then ERROR 270 shows up in the RUU. I searched around but found nothing for the Herald about it. Just asking for any help as to what I can do.
Thank you in advance.
Click to expand...
Click to collapse
Have you tried going to start/system/usb to pc and enable advanced network functionality? What rom are you running?

dougstoner said:
Have you tried going to start/system/usb to pc and enable advanced network functionality? What rom are you running?
Click to expand...
Click to collapse
ok that was disabled. I enabled it, same problem.
Seems to be running Open Touch 5.0.
Just bought it off ebay.

Ok think I got it. Seems to be very hard to find a newbie guide for first timers of this sort of thing.
Found some files by ivanmmj and sifted through them. Found a USPL program that SID unlocked the phone, after that I was able to run HARD SPL, and everything was fine. Now my next step is to try to flash a ROM on it , wish me luck.
Think after all this work I'm going to try to write a guide for first timers like me to explain this stuff a little better.

If it had OpenTouch 5.0, it might have already been HardSPLed. Either way, I'm glad you found the answer yourself. It shows that you actually did your research.

diacronic said:
Ok think I got it. Seems to be very hard to find a newbie guide for first timers of this sort of thing.
Found some files by ivanmmj and sifted through them. Found a USPL program that SID unlocked the phone, after that I was able to run HARD SPL, and everything was fine. Now my next step is to try to flash a ROM on it , wish me luck.
Think after all this work I'm going to try to write a guide for first timers like me to explain this stuff a little better.
Click to expand...
Click to collapse
That's really not a bad idea. I know I was EXTREMELY confused the first time I flashed my rom. It took me a lot of reading to finally understand RUU stood for rom update utility. You do know for some roms, it's not necessary to hard spl. I went from stock rom to open touch 3.0. What rom are you thinking about flashing to?

There's a walkthrough by me somewhere in the forums.

dougstoner said:
.... I went from stock rom to open touch 3.0. What rom are you thinking about flashing to?
Click to expand...
Click to collapse
Just downloaded ivan's kitchen , but I'm having problems getting it to run. Going to use that to probably make my own and get used to the programs that are out there.

Newb Wing Help!

I've read tons of posts on here about flashing the Wing and I've still be unable to flash it correctly, during the flash it will get some type of ITWRITE error then my phone will have a box on the screen that says error unknown status, I let it sit then my pdocwrite pops up that error and then it will lose the USB connection to the computer and be locked up then I have to RUU it to make it work again, SPL is 4.28.0001, I'm just trying to put some new firmware on it to make it run better than the stock t-mobile firmware, all these posts are here are confusing me on what to do because some are outdated or I'll read one thing then something else I'll read contradicts itself, can someone point me in the right direction, I know that you have guides and things but half of them are outdated and I'm not even sure what the latest firmware is for things like OpenTouch and what not, I wish someone would clean up all the old posts so we don't have quite as much to dig through. Any help would be appreciative.

you're trying to flash using aserg's method, which is painfully outdated and you've got an SPL of more than 4, so you should just go ahead and HardSPL.
in the windows mobile world, NEVER read the outdated stuff, especially on xda-devs. somebody always asks some question that requires one of us to go back into the deep recesses of our memory, and that kind of question usually happens pretty often. Most answers are either really specialized or there is already thread on the topic on the first or second page of the forum.
now to answer your question. Do not touch the cable while flashing. When it says to unplug it, do so and then hard reset. Make sure you install the cabs before you start pdocwrite.
welcome to xda-devs. feel free to pm me any questions.

If I've already done the hardspl using Aserg-Hard-Spl.4.70.yan, and I'm trying to put Open Touch v6.1 Lite on my Wing, do I use the Herald-USPL-Beta3 method, I've got Open Touch v3.0 on my phone now but want to see if I like Open Touch v6.1 any better..

Nevermind I figured it out, followed the updated flashing guide.

Please help - bricked XDA Orbit II

Hi, first post on the forum so please be gentle with me....
I have an XDA Orbit 2 which was until last Thursday working fine with the last official upgrade from O2 (Win 6.1, no idea about all the other stuff).
Whilst using the phone last week it suddenly died in the middle of a conversation. It wouldn't power on at all. I took out the battery, waited a couple of minutes, put the battery back in and switched it on. All that happened was the phone displayed the 4 colour screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white. I repeated the battery removal exercise a few times, waiting for increasing lengths of time but nothing changed.
I had a fairly long search through the forum and have tried for a few hours now going through the various fixes suggested but I am getting nowhere.
It won't hard reset, all that happens is the message "No Image Found" appears for a very short time and I then get stuck on the 4 coloured screen with the message above.
The same thing happens if I try just putting the thing in bootloader mode.
I can't use any of the official O2 rom upgrades as the phone because all the PCs I've tried connecting to it won't recognise it over a USB link.
I've tried connecting to it using mtty, again on several PCs, but I just get a message "USB port can not open". Just in case I've uninstalled Activesync on one PC and got the same answer.
The "how to flash you polaris using the microSD card" originally looked useful but I have some problems with it.
The first is that I need HardSPL installing on the device, which I can't do because I can't get to it.
The second will be down to me not knowing where to look, but I can't find a ROM to download and copy to the microSD card as POLAIMG.nbh. I did manage to find a Win6.5 one (the HTC Polaris - PDaviet rom wm6.5 manilla 2d (core 23004) by tranminhman one) which I thought I'd try. I guess the idea was that if I could just get something working I could always reflash it again with a different ROM or maybe apply the o2 upgrade. Unfortunately the image was password protected and I couldn't find the password in the thread.
I'm kind of at a loss now so any help would be appreciated.
Cheers

Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan

Did you do soft reset

alanazar said:
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Click to expand...
Click to collapse
Bit in bold er... cant quite understand why in iolite section as the xda orbit 2 is the rebrand htc touch cruise => htc touch find. Its in the right place.
On the side of what to do i the ony thing i can think of would be mtty and if that didnt work then try to reflash the official o2 6.1 release and see what happens when you try to do it.
You cant try to install any 3rd party roms they jsut wont flash as you dont have hard spl installed and cant do that until you have it running again.
Try the above and see what happens...

Hi Nik
I have tried just about every kind of reset, nothing has worked.

Hi Alan
If I can't get it sorted any other way I'll probably send it off somewhere but I'd like to have a go at fixing it myself. It will at least be a bit of fun!
I take then that I've posted this in the wrong forum. Oops, apologies.
Jon

You have not posted in the wrong forum look at my signature!

Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
1a) Extract shipped ROM by WinRAR , take RUU Signed.nbh
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]

Nik Ahmad said:
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Click to expand...
Click to collapse
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon

jonfsharp said:
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
Click to expand...
Click to collapse
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend

have u tried this?...
turn off, pull out the battery, then put it back, charge ur phone till the battery indicators shows green (which mean it's already fully charged) then... power on ur device.
it looks like a dumb suggestion , but... i have had a same situation
(HTC KAISER, not Polaris).
if it doesn't work, then try to upgrade with a POLAIMG.nbh (take it from official HTC ROM)
in a 2G FAT32 microSD root directory.

Nik Ahmad said:
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
Click to expand...
Click to collapse
Thanks Nik
Much appreciated.
Downloaded the ROM as suggested, unzipped to the SD card, renamed the image to POLAIMG.nbh, stuck it in the phone and things got slightly more interesting.
In bootloader mode I now get a bit further. I get a grey screen which says "Loading ..." then "Checking...." then "00028002 Not allow". It then goes back to the four coloured screen as before.
However, does the fact that it is trying to read something mean that I have just got the wrong file?
I'll try a few more and see what happens.
Thanks once again, your help is greatly appreciated.
Jon

Hi oza
Yep tried all the battery pulling out stuff but got nowhere.
The ROM thing on the SD card gets further. I extracted the ROM from the official O2 upgrade, stuck it on the card and renamed it POLAIMG.nbh.
If I put the phone in Bootloader mode I now get even further than before. I get a grey screen with:-
POLAIMG.nbh -
RADIO_V2 -
BOOTLOADER -
SPLASH1 -
OS -
Press power button to start update image
Press action button to cancel update image
If I press the power button
I get an "Update In Progress" message and a progress bar.
After about 4 minutes I get a full progress bar and :-
POLAIMG.nbh - OK
RADIO_V2 - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
Update complete
UPDATE SUCCESS
And that's as far as I've got so far.
If I take the SD card out and try a hard reset I just get stuck on the 4 coloured screen I got before, but with no No Image Found message.
I get the same thing with bootloader mode and when I just remove the battery.
If I put the SD card back in I can go through the update process but I can't do anything
else.
So, have I actually made any progress? I'm not actually sure what I have updated and what state the phone is in at the moment. Is the fact that this didn't work an indication of a hardware failure and I should send it off somewhere.
Any advice on next steps would be good.
Jon

what is ur bootloader screen says now?
IPL...
SPL...

Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?

Try this one M-AMINES if the radio you had was a 1.59.xx radio as it has the radio included.
if it was a 1.65.xx radio then try the VLIT naked rom.

oza_crazy said:
what is ur bootloader screen says now?
IPL...
SPL...
Click to expand...
Click to collapse
Hi Oza
Exactly the same as it did when it first broke. I get the 4 coloured screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white.
No idea what the IPL is or was I'm afraid.
Jon

bally3 said:
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Click to expand...
Click to collapse
I've not been a big modifier in the past so it was just using the bog standard O2 software from the O2 website. The name of the file is "RUU_Polaris_O2_UK_3.13.206.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe" so I presume that there can be information gleaned about things like the SPL, ROM and radio versions?
Not a complete nunce, no, but so very far away from being comfortable with all this. This post was a result of a good few hours trawling through the forums looking for help. Anything I have done has been the result of a post on this site and I am very grateful that there are people willing to share their knowledge.
Anyway, as for hard spl, nope it isn't installed. I'd never needed anything like it before the phone died and now that it has died I can't get onto it to install anything.
Yes, this happened right in the middle of a conversation after a good year or so of normal day to day use. As I said, I haven't needed to make any changes to the phone so the only thing I've ever done is upgraded it with software from the O2 site.
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon

jonfsharp said:
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
Click to expand...
Click to collapse
Well whatever you do dont bin it, we can always use it on the Android project if you decide to go that way.
Ok.. so lets see.. the phone is not picked up at all in windows?
If that is the case, if even a serial connection cant be made then theres issues. At this point, I would disregard all the other advice as it only applies to a hard spl device unfortunately. SD card flashing and all other radio rom flashing will only work with hard spl as far as I know - definitely safer for certain and you dont want to wreck a repairable device.
I take it, its not under warranty, for your mention of costly repair.
The important thing at this stage is a serial or usb connection from a Windows PC. I think I have heard of forcing this connection by opening the device but this would really be in the realms of profficient repairer or enthusiast.
I'll have a look but also do some searching yourself for making a connection to a Windows PC and forcing an SPL onto a phone.
I dont know whether anyone's ever managed to HardSPL a phone using a memory card? Just a thought...

Who would have known.. have a read of this and see if you can follow it up regarding the spl through sd card ..
http://forum.xda-developers.com/showpost.php?p=3273438&postcount=7

Does anyone know how to unbrick the CDMA Hero?

My phone shut off and has not been able to turn since. I tried flashing a ROM and didnt relive after that. Please help.

What do you mean it doesn't turn on? What happens when you hold the power button?

it doesn't boot ...it is as if it were dead

Check to make sure it is charged and the battery is installed properly. I have had the battery so dead that it didnt even vibrate to indicate booting.

Yeah. Let it sit on the charger for a few minutes, make sure battery is in right and everything is plugged.
Check for amber LED, let it charge a few minutes, then try again and do it like that every couple minutes. If nothing still, buy a new battery or exchange it.

nothing so far ...ive scheduled an appointment to repair ...i know they wont be able to do anything for this phone. I wanted to see if I can avoid not having to give up my HTC hero and deal with a replacement phone for a while.

ummmm, how did this happen?
you may not want to say for fear of bashing but I promise I won't, as far as I've seen it takes a very unique set of circumstances to actually brick these things
EDIT: my prediction: you tried to flash a GSM rom onto it

so when attempting to get the download file for the Eclair 2.1v1.5 rom it stated that the radio posted is recommended. Prior to flashing the radio i did a nandroid backup and then I flashed the radio. During the flash screen (open box to phone image) it blacked out after about 20 seconds.

kel_o91 said:
so when attempting to get the download file for the Eclair 2.1v1.5 rom it stated that the radio posted is recommended. Prior to flashing the radio i did a nandroid backup and then I flashed the radio. During the flash screen (open box to phone image) it blacked out after about 20 seconds.
Click to expand...
Click to collapse
sorry bout what happened. I know jack-diddley-squat about radios...so I might have been in your place if I tried it.

kel_o91 said:
so when attempting to get the download file for the Eclair 2.1v1.5 rom it stated that the radio posted is recommended. Prior to flashing the radio i did a nandroid backup and then I flashed the radio. During the flash screen (open box to phone image) it blacked out after about 20 seconds.
Click to expand...
Click to collapse
So my theory is that this nOOb flashed the GSM radio. Here is what he did.
He seen the post on the Eclair 2.1v1.5 rom on our forums and got click happy. Clicking on the link under that thread for the GSM ROM.
The current build is based on Lox and Behnaam's GSM 2.1 v1.5.
Click to expand...
Click to collapse
Which took him here:
http://htcpedia.com/forum/showthread.php?t=1448
Then he flashed the radio in this post.
(Suggested radio 63.18.55.06JU_6.35.09.26)
Click to expand...
Click to collapse
So yea he didn't read, just clicked, have fun with that.
And i suppose you didn't flash a recovery img after rooting? Well next time you will learn to read.

Have you tried booting into recovery and doing a nandroid restore?

i've never heard of a bricked CDMA hero... but i guess flashing a GSM radio would do the trick
ok i searched and this may be the FIRST EVER bricked CDMA htc hero!
correct me if i'm wrong but i couldn't find anything on google about this.
maybe we should sticky this, or delete that link to the gsm rom so this doesn't happen again?

yeah i guess i did flash a gsm rom which definitely pwnd my phone ...i did everything possible. hard reset buttons. basically couldnt do anything with adb as the phone was completely shut off so no way to connect. Well all in all i learned my lesson. The techs at the sprint store couldnt do anything to fix the original phone so they said what the heck and provided me with a brand new google branded hero.

We all have done it!
kel_o91 said:
yeah i guess i did flash a gsm rom which definitely pwnd my phone ...i did everything possible. hard reset buttons. basically couldnt do anything with adb as the phone was completely shut off so no way to connect. Well all in all i learned my lesson. The techs at the sprint store couldnt do anything to fix the original phone so they said what the heck and provided me with a brand new google branded hero.
Click to expand...
Click to collapse
Flash lesson 101, read-read-read!!!
Don't worry we 'ALL' have done it. And LEARNED from it.
Keep on going!!!

I'm glad to hear you got your phone replaced. I don't understand how you couldn't boot into any mode that would allow you to fix this. But I don't mess with radios whatsoever.

thedudejdog said:
maybe we should sticky this, or delete that link to the gsm rom so this doesn't happen again?
Click to expand...
Click to collapse
+1 Please sticky and/or remove link. We don't need people jumping the gun and flashing ROMs that will brick their phones.
Cheers.

WhiteWidows said:
So my theory is that this nOOb flashed the GSM radio. Here is what he did.
He seen the post on the Eclair 2.1v1.5 rom on our forums and got click happy. Clicking on the link under that thread for the GSM ROM.
Which took him here:
http://htcpedia.com/forum/showthread.php?t=1448
Then he flashed the radio in this post.
So yea he didn't read, just clicked, have fun with that.
And i suppose you didn't flash a recovery img after rooting? Well next time you will learn to read.
Click to expand...
Click to collapse
Wow, way to show class. Nothing like a little compassion around the holiday season, I see. You are a true class act, and I bet your friends and family are very proud of the way carry yourself. Unfortunately, not everyone can be as perfect as you are, so try to take it easy on the rest of us.

Let it go guys... on all sides of the argument.
he made a simple enough mistake. It's been remedied. Lets all move on.

obelisk79 said:
Let it go guys... on all sides of the argument.
he made a simple enough mistake. It's been remedied. Lets all move on.
Click to expand...
Click to collapse
+1 for this

How does a radio flash stop a phone from turning on?
Isn't the whole point of a recovery mode, to be able to "recover" if something goes wrong.
Shame on you whitewidows, for bashing him... The whole reason people get things working is because of trail and error.
If anything he helped us all by confirming that a wrong radio flash will completely ruin your recovery console, possibly bootloader, and (maybe even some actual hardware).
Hopefully this doesn't discourage users from trying to hack our radio.