What are my options here? - 8125, K-JAM, P4300, MDA Vario General

Okay, yes I'm new to the Cingular 8125. I read here about updating the ROM but not about unlocking it first. Read that while it was updating the ROM. Now with the new ROM in place and, of course, the phone still locked it is well locked. All outside access seems to be denied. The phone and EDGE are disabled, I've tried Active Sync but my computer never sees the phone be plugged in, and I've even tried resetting up my Active Sync through Bluetooth. That's disabled. And finally I attempted to reconnect with my wireless router... WAN appears to be disabled as well. Phone runs slower with this new ROM in it as well, presuming because of the lock thing. So, now that I can't get back into it what's next?

1) Download the original ROM from Cingular.
2) Get thyself to the bootloader (search the forum for the key combo, as I can't recall it offhand).
3) When you're at the rainbow screen, check to see if it says USB in the bottom left. If it does, this is good.
4) Plug it into your computer.
5) Run the original ROM update installer.
6) Pray.
7) When you're back at the original ROM, unlock before updating.
8) If the original ROM won't reinstall, look for the special "downgrade" installer that was created by someone in the Wizard Upgrading forum. There is a thread on it.

gamescan said:
1) Download the original ROM from Cingular.
2) Get thyself to the bootloader (search the forum for the key combo, as I can't recall it offhand).
3) When you're at the rainbow screen, check to see if it says USB in the bottom left. If it does, this is good.
4) Plug it into your computer.
5) Run the original ROM update installer.
6) Pray.
7) When you're back at the original ROM, unlock before updating.
8) If the original ROM won't reinstall, look for the special "downgrade" installer that was created by someone in the Wizard Upgrading forum. There is a thread on it.
Click to expand...
Click to collapse
U get to the bootloader by with the device off - press and hold camera button and press power on button.
I like step 6 of above advice :wink:
Downgrade installer (post by faria) here http://forum.xda-developers.com/viewtopic.php?t=47848 - which rom have U upgraded too? - this only works on 2.21 rom or below

Update
gamescan said:
1) Download the original ROM from Cingular.
2) Get thyself to the bootloader (search the forum for the key combo, as I can't recall it offhand).
3) When you're at the rainbow screen, check to see if it says USB in the bottom left. If it does, this is good.
4) Plug it into your computer.
5) Run the original ROM update installer.
6) Pray.
7) When you're back at the original ROM, unlock before updating.
8) If the original ROM won't reinstall, look for the special "downgrade" installer that was created by someone in the Wizard Upgrading forum. There is a thread on it.
Click to expand...
Click to collapse
I don't know you but I'm pretty sure that I LOVE YOU!!! Update I started the install for the older ROM for unlocking and it's loading currently. All I needed was the info about get yourself to the bootloader. You're the best. I'll let you all know how this ends up. Thanks again!

1/2 way there now...
Okay after all of that it appears that the phones battery is below 50% so now I'm waiting a bit to load the new ROM. The unlock seems to have went successfully. All the stuff with Loki went as it read and I have a BIN file with the lock code on my Hard Drive. The phone is currently back in operation as well, with the old ROM ( one posted here by Button for purpose of unlocking ). Thanks again! I'll let you know when I'm done how this ends up. Waiting ( biting nails at this point )! Oh yeah and praying.

Make SURE you use Lokiwiz02b to both SIM and CID unlock.
A common error is to simply SIM unlock. This does NOT help you with ROM upgrading.
You must SIM unlock to use another carrier.
You must CID unlock to upgrade to a custom ROM.
Once performed, both unlocks should be permanent.

Okay... Well I'm following http://forum.xda-developers.com/viewtopic.php?t=47848&sid=af7ca6d1ea263047d0c1f69177976a16 instructions. I don't really need to unlock the carrier. I'm perfectly happy with Cingular. Just want to upgrade the ROM to hopefully be more stable and to include the stereo bluetooth support and such.

Doh!
Okay I ran that program again and I see what you mean. I had unlocked ( that's the choice I took ) so I unlocked the carrier but not the ROM. I was about to have the same problem all over again. Geesh! Alright then I love you and I owe you a child or something. Hehe... Thanks!

Final outcome...
Okay, I am now on the new ROM. Too early to post stability or compatibility's as I'm still adding my software and configuring for my tastes. All components that I've tried are working, however. Cingular connection is strong including the EDGE digital network. Active Sync works fine, even through Bluetooth. And it talks to my in-home network wonderfully through the built in Wi-Fi. So all-in-all I'm on the road and headed the right direction. Thanks for the great ROM upgrade and for your assistance this evening.
P.S.: What is the 'Clock200', 'Clock240', and 'Clock252' for exactly? They're not hurting anything but they really don't appear to do anything either. They are listed in the 'Program Files' and when clicked or even double clicked on they do... Well nothing. :roll:

Related

Dutch to english ROM

Hey guys,
Im another newbie, but who is actually scared of screwing up the phone. I have the Tmobile MDA compact III obviously, and the information page looks like this:
ROM version 1.13.114.1 NLD
ExtRom version 1.13.114.101
Model nr ARTE 110
CPU OMAP850
Im not so sure what this information tells you people who are knowledgable about this, however can I safely use the customised powermap file from this website's ftp (ftp://ftp.xda-developers.com/Artemis/Customized_ROMs/) to change the phone to english?
What are the procedures EXACTLY please, and what problems should I expect.
Another thing, what is CID lock, and how can I see if mine is or not?
I checked most of the threads, so I am knowledgable about this issue a bit, however because none of the topics were specifically about the Dutch version I wanted to make sure. Thank you a lot for your help...
1. you have to CID unlock your phone. only real solution is imei-check website, and that will cost you $40. this will prevent MANY of the problems with installing ROMs
2. don't do updating on Vista PC, use XP or older
3. follow on screen instructions of your chosen ROM update utility. don't panic if it takes too long and looks like the update process has "freezed". make yourself a coffee and let it finish installing.
4. enjoy!
PS... i strongly suggest you read as much as you can on this forum before doing any upgrading.... then you'll know what to expect.... and of course, don't forget that only YOU are responsible for anything that happens to your device, good or bad... good luck!
hey dim4x4,
thanks for the post, I appreciate it. However is the exe file I mentioned (customised power map) the right one? i know there are a few options to chose from, like the 3 options of the pdamobiz.com website. While im not too clear of the main differences, the general concensus on the forum is that the powermap is preferred, and has a lot of nice things. Is there a better one? perhaps on a different ftp. Maybe if you have one you can send it to me.
Another thing, if it dont work, or works and I dont like it, can I get back to my original ROM, the dutch one from the tmobile dutch file on the ftp site as well?
Thanks
1. Personally, I use PDAmobiz Lite version. Powermap version has a map of Thailand which I don't need. "A lot of nice things" for my purpose is a lot of unnecessary stuff. If I need something I can install it myself into RAM or storage card. You have to choose the version which suits you best.
2. Everything is on this server. You have to register to log in http://www.wm-gurus.com/registration/signup.php
3. I went back and forth with different ROMs (versions, languages, etc.) without any problem until I found more or less what I want. Please note, my device is CID unlocked by imei-chek.
Good luck!
Urgent Help
I tried the powermap version of the ftp. This is exactly what I did:
I connected the phone and established contact through activesync, then I started the exe file. The DOS windows opened, and then it started initialiying, and the process started. It said that it will take 15-30 mintues, and the process has started. So far im sure everypone is familiar with those. However, I waited about 35-40 minutes, and still nothing different on either screens. The DOS window said however that if nothing starts I should reset the process. I tried but didnt work. At that time I tried to reset the phone and now it is stuck in the startup screen. All I see on it is the IPL/OS data, and it is not moving further.
Please help, what do I do now?
So this is what I did so far....
1. Flashed with PDAMobiz_Dopod_P800W_AKU301_v1.1.2_PowerMap.exe (with device on Today screen)
2. The process started and stuck on "uploading file [don't remember] and as the instruction said I reseted the phone after 30 minutes.
3. All there is on is T-Mobile splash screen, version infos and that's it.
5. Tried to flash again in bootloader mode but the device was not visible by PC
How do I go from here? Maybe I need to flash the original rom version of the phone. I have the dutch tmobile mda compaxt III, but with the dutch ROM version on the ftp of this site is scary, because there are too many files and have no clue which one to flash.
Any suggestions?
There is no Dutch T-Mobile ROM available yet.
You could try the English T-Mobile ROM (art_tmouk_11311001_024990_wwe_ship.exe), which is available on this site: http://www.wm-gurus.com/registration/signup.php
There's a chance this ROM will work on your Dutch T-Mobile phone, if the signature is correct (I assume your phone is still CID locked).
Read this link http://wiki.xda-developers.com/index.php?pagename=Artemis_Resets on how to enter the bootloader of your phone.
mRmAGIC...
I Tried That Already; But I Got An Invalid Id: So I Dont Know What Else So Far: Do You Think I Have To Cid Lock The Phone To Be Able To Try The Other Versions?
tghobar said:
I Tried That Already; But I Got An Invalid Id: So I Dont Know What Else So Far: Do You Think I Have To Cid Lock The Phone To Be Able To Try The Other Versions?
Click to expand...
Click to collapse
CID unlocking isn't possible if your phone isn't working.
If you don't have your original rom, you have to contact your provider to repair it.
try from bootloader screen
Hi I also did as u did but with a hards reset in the beginning.And it worked fine.read somewhere that if u dnt do a hard reset you could get into problems.If u can try to go to bootloader screen and try to flash from ther.
flashing from the bootloader screen gives me an error, the file cannot recognize that a phone is connected to the PC. that is the biggest problem I think.
DO you know how to flash the Tmobile NL version on the ftp. there is one that I dont know how to use

wm6.1

I recently upgrade to the new rom.. was wondering if anybody has just a rom to upgrade to 6.1 and not have to go with the cooked rom.... i don't really want to deal with the unlocking and locking and what not on my phone am pretty happy with it just want to have windows 6.1....any suggestions?
What? You know WinMo6.1 is leaked, right?
You know that no provider is give out WinMo6.1
yet, right?
This mean, no way to get WinMo6.1 from provider.
So you must use a cooked ROM.
nobody can take it out of like the dcd rom and have it be like a cab?
buy a handset that has 6.1 from the provider, i think the att tilt might?
You can't CAB the OS!!
The OS is built as XIP - Execute in Place.... it runs from where it is permanently stored... If you want to install an OS it must be XIP for WinMo.....
So if you want to install OS you have to BUILD the ROM.
Why you so aversion to use whole ROM? It's just like OEM but better... there is no problem, just install it and see.
well is it just a install thing like the official rom or do you have to do the whole unlocking or locking..thing i dont wanna go through all that hastle..but if its just a one file one click thing i'd be more than happy to give the dcd a shot
Its not like other cell phone unlock. Unlock work is not scary word in PDA. It just mean... make it so your phone accept other update from non official source.
You just need SPL to do that.
It's rediculously easy. I had some issues, but it was because I was originally using the wrong file. Once a kind soul on this forum guided me to the right file, it worked like a charm!
1) Activesync your phone to your PC
2) Run titan_SPL_2.40-olipro.exe
a) Follow the promts and it should bring you to a multicoloured bootloader screen
b) Disconnect and re-connect your USB adapter just like it tells you
c) Once it's done, if you're not at the bootloader screen again - Press and hold Power + Camera + push reset. This should bring you to the bootloader again.
3) Run titan_radio_3.27.00.exe
a) Should be relatively the same as above.
4) Run dcd2.3.2-telus.exe (if you're with Telus, otherwise find the one for your provider)
a) Should be same as the last two steps
5) ???
6) Profit

Sorry to be such an idiot but...

I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
N1cholas said:
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
Click to expand...
Click to collapse
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
egzthunder1 said:
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
Click to expand...
Click to collapse
I'm running windows version 7. and no i didn't unlock the device. i just ran the installer application (i hadn't found a detailed install manual) i'm not entirely sure how i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
N1cholas said:
I'm running windows version 7. i'm not entirely sure i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
Click to expand...
Click to collapse
By bootloader, do you mean the three colored screen?
egzthunder1 said:
By bootloader, do you mean the three colored screen?
Click to expand...
Click to collapse
no, the screen that says serial/usb at top and 2.07 at bottom
I just wanted to make sure that we were on the same page
In my opinion (and this is just a theory), Windows 7 (since it is a beta) does not have the necessary drivers to recognize the "usb device". Hence, when you put it in the cradle, it just doesn't see it. Again, this is just a theory...
You may want to get a hold of a machine with XP (that is if you didn't make the one you are using a dual boot). You should be OK if you try to flash via XP.
If everything else fails, you can always use mtty and flash via SD card (the procedure can be found in the wiki).
I had the device synced up before the install. it's just having issues syncing while it's in the bootloader mode. The device actually appears in the usb devices, but doesn't sync. i was thinking that the device might have to be authenticated with local software(on the sx66) in order to sync. I'm using the windows vista drivers. I do have this machine dual boot, but it's not any other version of windows i'm using
Your device does not have to sync in order to up/downgrade. Think about it this way... the RUU will put the device in bootloader anyways.
Just run the installer of the stock rom (the upgrade from Cingular).
@N1cholas: Please correct me if I'm wrong. I'm just a little confused. Are you expecting MS Active Sync to show as it usually does when you are syncing your phone? If that is the case, it won't happen when on boot loader. Are you getting any error when trying to flash or you haven't tried to flash yet?
Advise:
1. Keep your hopes, don't get despert. Egzthunter is a master
2. Make sure you follow the guide... Step by Step to upgrade.
3. If it'll take you too long to complete the reading and flashing, reset your phone and put it to charge. You won't be able to flash with a dead backup battery. Main and Backup battery won't charge while on bootloader.
Edit: @Egzthunder: Sorry mate, while I was thinking, drinking coffee and writing you had already replied Like I said, your the help master. Once again, I encourage the MODS to propose you to be part of their teem. You're always there to help.
Mark
i'm going to head off to school, but it's not working. when i try to run any mods i get an error saying that it cannot communicate with device.
Yeah! Egz for MODS!!! Woohooo and Xplode too and someday..me! LOL (no i mean it!)
windows 7 uses the same drivers as vista
beakybal4 said:
windows 7 uses the same drivers as vista
Click to expand...
Click to collapse
Why do you think I don't trust it?
@N1cholas,
I apologize since I ended up going to bed yesterday night.
I think your best bet will be to find yourself a PC running XP and try the reflash in that since it seems to me that something is going on with the OS.
@red and mark
Thanks for the support, guys!!! But you guys are awesome as well!
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
N1cholas said:
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
Click to expand...
Click to collapse
You will not see the device in any type of sync software (call it ActiveSync, WMDC, etc). I hvae uploaded the SX66 stock installer from Cingular, so give that a shot
Here you go
SX66Update.exe
Like I said... XP computer. Also, for the SD flashing, you need to look for something called mtty and instructions on how to use it.
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
xplode said:
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
Click to expand...
Click to collapse
Hey xplode,
To be perfectly honest, I haven't flashed 2003 since 2006, so I would be lying if I told you. Feel free to add it to your database if you wish. FYI, this is the upgrade that Cingular Wireless used to offer when the SX66 was still available in the at&t website.
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
N1cholas said:
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
Click to expand...
Click to collapse
Did you try the update that I gave you?
i ran it, and it said it was trying to get the settings from the device, then it just disappeared lol. now when i run it, it extracts the install data to the temp folder on my pc, then just disappears

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

official at&t callerID update bricked my phone.. :(

after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!
......
noone?????
The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)
Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...
Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .
i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck
There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL
It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?
another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL
When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.
I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.
The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!
Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.
It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.
Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."
The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!
Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.

Categories

Resources