I found this thread. I want to try this with my Dream. I just want to discuss to fix our bricked Dream.
http://forum.xda-developers.com/showthread.php?t=417930
Click to expand...
Click to collapse
After read the topic above, you can see this:
1) Windows XP with SP3
2) ActiveSync 4.5
3) ActivePerl 5.8.8.822
4) Crypt-DES and XdaDevelopers-NbfUtils PERL packages
5) typhoonnbfdecode.pl PERL program
6) itsutils tools
7) working mobile device with any Windows mobile OS (2003, 5.0, 6.0)
8) any .nbh ROM file from the official Herald's RUU
9) heradiag.nbh file
10) micro SD card (tested on 512MB and 1GB)
Click to expand...
Click to collapse
We need dreadiag.nbh . Someone please get it for us (who has a bricked phone)
funbacon said:
I found this thread. I want to try this with my Dream. I just want to discuss to fix our bricked Dream.
After read the topic above, you can see this:
We need dreadiag.nbh . Someone please get it for us (who has a bricked phone)
Click to expand...
Click to collapse
I've mentioned this in the brick think tank, but people have reported that it wouldn't work. I'm not sure if it has been tried, though.
And how do I get the dreadiag.nbh?
@funbacon
I downloaded the DREADIAG.nbh file some time ago from the XDA forums. I have attached it to this post in the hopes that it can help you.
You'll need to rename the file to DREADIAG.nbh .
I'm led to believe that you can't boot off the sdcard with the Dream but I really hope that I am wrong.
I've also discovered that when you run logcat when you boot up the phone that the SD card serial number is shown.
Best of luck!
ivanmmj2 said:
I've mentioned this in the brick think tank, but people have reported that it wouldn't work. I'm not sure if it has been tried, though.
Click to expand...
Click to collapse
The HTC Elf in that thread is bricked after updating Hard_SPL. Our Dream is bricked after updating SPL 2005. Our phone still boot to android screen (ADP) or Tmobile screen (Tmobile phone) -> there is one SPL or IPL alive. I'm look for dreadiag.nbh. Who have it? Please share us.
funbacon said:
The HTC Elf in that thread is bricked after updating Hard_SPL. Our Dream is bricked after updating SPL 2005. Our phone still boot to android screen (ADP) or Tmobile screen (Tmobile phone) -> there is one SPL or IPL alive. I'm look for dreadiag.nbh. Who have it? Please share us.
Click to expand...
Click to collapse
Didn't the guy above you just post it?
mer6 said:
Didn't the guy above you just post it?
Click to expand...
Click to collapse
A have a slow internet connection. Sorry . Bricked G1 ower. Let's test
Wouldn't you need an SPL to load dreadiag.nbh?
I used dreadiag.nbh before, but you would have to have the ability to access the bootloader.
My dream is not bricked,but when I tried the DREADIAG.NBH in spl .2005 It gets stuck on the part after "updating" I don't remember what it said exactly...Ill get a pic when I'm home.
I bricked my Dream (non-ADP) by updating to SPL 2005 before the radio. It was careless on my part. Anyway, I got another one so I no longer have my bricked one.
However, I maintain full interest in a solution to "Un-Brick" a G1. Nandroid offers a pretty big safety-net but there is currently nothing to save us from a bad SPL/Radio flash. If a method became available then I anticipate far less fear on developing on that level. If there was a failsafe on that level, imagine the stuff that we could "Dream" up.
to use the dreadiag (Dream Diagnostic) image you turn your card into a gold card, and the SPL boots from it.
sadly, if your phone is bricked, it doesn't touch the SPL.
the dream boots up like this: radio -> spl -> [recovery/dalvik/whatever]
when you brick your device, the radio fails to boot the SPL.
haykuro said:
to use the dreadiag (Dream Diagnostic) image you turn your card into a gold card, and the SPL boots from it.
sadly, if your phone is bricked, it doesn't touch the SPL.
the dream boots up like this: radio -> spl -> [recovery/dalvik/whatever]
when you brick your device, the radio fails to boot the SPL.
Click to expand...
Click to collapse
Does Dream have a second bootloader ?
haykuro said:
to use the dreadiag (Dream Diagnostic) image you turn your card into a gold card, and the SPL boots from it.
sadly, if your phone is bricked, it doesn't touch the SPL.
the dream boots up like this: radio -> spl -> [recovery/dalvik/whatever]
when you brick your device, the radio fails to boot the SPL.
Click to expand...
Click to collapse
Can use dreadiag.nbh without HTC gold card. Need other way to fix.
Some links to read:
http://forum.xda-developers.com/showthread.php?p=3736434#post3736434
http://forum.xda-developers.com/showthread.php?t=487945
http://forum.xda-developers.com/showthread.php?t=417930&page=13
After read these, I understand that Dream have 2 bootloader, 1 is bootloader in SPL, 1 is bootloader in radio, because dream run: radio -> bootloader -> ... then after update radio error, we can't pass step 1 (radio boot). Do I understand correctly ?
I guess it's like bricking the IPL on any other phone, it effectively kills the phone.
Question: What causes the brick in the first place? Does the Radio attempt to call the SPL at a different memory address or something? Maybe we can modify the SPL to stop the bricks in the first place...
Another of my long posts..
Watch out, this guy right here can type!
Let's see if I can add any additional ideas here. Watch out, I'm going to be rather raw (no, I don't mean swearing.) Anger isn't going to get us much further than where we already are.
It is accepted that the boot order *chain* is Radio>SPL>whatever.
It is accepted that the chain is broken because the Radio can not call/initialize the SPL
My Explanation/Opinion: My experience would be that the chain between Radio and SPL was broken. My understanding of this is that the Radio is supposed to call on the SPL but can not because the SPL is in a different place (memory address or perhaps just initialized/called differently.) This is the break. Both the Radio and the SPL exist but the Radio can not call upon the SPL.
Important question: HOW DOES THE RADIO CALL THE SPL?
Accepted: The newest radio works with the default SPL, the Engineering SPL and the hacked HardSPL.
Accepted: The newest radio ALSO works with the 1.33.2005 SPL.
Hypothesis: The new radio works with both the old and the new SPL while the older radios only work with the older SPLs because the new Radio supports both types of call/initializations for the SPLs.
Assumption: The new radio can employ the call/initialization methods that call the older SPLs and the new SPLs. (I am assuming that there are at least 2 different call methods.)
If this is indeed true then it could also be accepted that the SPL was changed (HTC?) and HTC (it's HTC making the radio images right?) started including compatibility for this change in the SPL call/initialization section of their newest radio images.
So, the SPL was changed and the radio's latest versions needed to be modified to support the change.
The older radios must have no programming for this change and thus hang on that SPLASH1 screen because there is no further (known?) logic in the Radio image to handle such a situation.
So, at this point any solution that involves invoking the SPL (if called from the radio anyway) is useless.
So, we can accept this then: We are therefore stuck at the Radio image part of the chain.
Question: What accesses are actually available from the radio image?
What systems of the Dream has it *woken up* at this point?
Does the Radio image touch the USB plug *at all?*
Does the Radio image touch the radios at all?
I WANT TO POKE THAT RADIO IMAGE WITH A STICK! I want to make that Radio image do SOMETHING. What is it doing with the SD Card, what is it doing with the USB port, BLUETOOTH, the actual GSM/3G radio in that thing? Is it *listening* for commands from the *mother ship?* I WANT TO BE THAT MOTHERSHIP!
We all know from our knowledge/experience with hacking that anything that *listens* can be *spoken too* and manipulated into giving us access to whatever *it* has access to. What does the Radio have access to at this point?
And I have yet to read anywhere about what that "Blue LED Mode" screen is that you get when you hold Power and the Trackball in. I think I did read about it having a bluetooth feature.
Bottom line: Let's find out what the Radio can offer us (in terms of ANYTHING,) Let's find out what that "Blue LED Mode" is and let's pull out all the stops and reverse engineer that Radio until we can more fully document what it actually is that is going on.
... my regret is that I can only speak in theory about this and not actually play a more hands-on role in this.
nicksen782 said:
Watch out, this guy right here can type!
Let's see if I can add any additional ideas here. Watch out, I'm going to be rather raw (no, I don't mean swearing.) Anger isn't going to get us much further than where we already are.
It is accepted that the boot order *chain* is Radio>SPL>whatever.
It is accepted that the chain is broken because the Radio can not call/initialize the SPL
My Explanation/Opinion: My experience would be that the chain between Radio and SPL was broken. My understanding of this is that the Radio is supposed to call on the SPL but can not because the SPL is in a different place (memory address or perhaps just initialized/called differently.) This is the break. Both the Radio and the SPL exist but the Radio can not call upon the SPL.
Important question: HOW DOES THE RADIO CALL THE SPL?
Accepted: The newest radio works with the default SPL, the Engineering SPL and the hacked HardSPL.
Accepted: The newest radio ALSO works with the 1.33.2005 SPL.
Hypothesis: The new radio works with both the old and the new SPL while the older radios only work with the older SPLs because the new Radio supports both types of call/initializations for the SPLs.
Assumption: The new radio can employ the call/initialization methods that call the older SPLs and the new SPLs. (I am assuming that there are at least 2 different call methods.)
If this is indeed true then it could also be accepted that the SPL was changed (HTC?) and HTC (it's HTC making the radio images right?) started including compatibility for this change in the SPL call/initialization section of their newest radio images.
So, the SPL was changed and the radio's latest versions needed to be modified to support the change.
The older radios must have no programming for this change and thus hang on that SPLASH1 screen because there is no further (known?) logic in the Radio image to handle such a situation.
So, at this point any solution that involves invoking the SPL (if called from the radio anyway) is useless.
So, we can accept this then: We are therefore stuck at the Radio image part of the chain.
Question: What accesses are actually available from the radio image?
What systems of the Dream has it *woken up* at this point?
Does the Radio image touch the USB plug *at all?*
Does the Radio image touch the radios at all?
I WANT TO POKE THAT RADIO IMAGE WITH A STICK! I want to make that Radio image do SOMETHING. What is it doing with the SD Card, what is it doing with the USB port, BLUETOOTH, the actual GSM/3G radio in that thing? Is it *listening* for commands from the *mother ship?* I WANT TO BE THAT MOTHERSHIP!
We all know from our knowledge/experience with hacking that anything that *listens* can be *spoken too* and manipulated into giving us access to whatever *it* has access to. What does the Radio have access to at this point?
And I have yet to read anywhere about what that "Blue LED Mode" screen is that you get when you hold Power and the Trackball in. I think I did read about it having a bluetooth feature.
Bottom line: Let's find out what the Radio can offer us (in terms of ANYTHING,) Let's find out what that "Blue LED Mode" is and let's pull out all the stops and reverse engineer that Radio until we can more fully document what it actually is that is going on.
... my regret is that I can only speak in theory about this and not actually play a more hands-on role in this.
Click to expand...
Click to collapse
*off-topic within reason*
Are you a public speaker? Geeze that was motivating! lol
@memorylasts : No, I'm not a public speaker. I am enthusiastic for this topic which all public speakers (the good ones anyway) are. So, maybe I'm in a way a public speaker.
<Somewhat Off Topic>
Actually, I have experience with ROM and Save State hacking with emulated NES roms. (Hex editing, pattern discovery.) I can change characters and shapes and actually write my own Game Genie codes because I've read up and learned how the Game Genie just patches bytes. Easiest ones are to extend a value such as from 1 lives to 10. Logic where you don't lose a life is also possible with some base understanding of the 6502 chip (I read other people's guide on that one though.) Lots 'o fun! *A bit off topic, yes.*
</Somewhat Off Topic>
My point is, well, maybe I can in fact help. Perhaps I/we can't bring the Radio image back down to base code but I think that we can reverse engineer it and at least identify the areas of the code where processes happen, such as it's call to the SPL. ... Trying to figure out what we even have to work with, ya know? Think of SecuRom hacking for game CDs. The main .exe is encrypted and calls to the CD for a decryption key which requires the user to have the CD. This sort of CD is more difficult to copy which is important to this type of security. So, Mr and Ms hacker got together and watched where the .exe called to the CD and grabbed the key that the .exe uses to decrypt itself. I would love to see what the Radio image is calling and listening for.
... or, as I said before, "poke that radio image with a stick."
Can we post here what we KNOW so far about the Radio? I'd really like to know more about that "Blue LED Mode" too.
Blue LED Mode :
1. No buttons combinations that work on a unbrick phone are active. (If their is different ones for this mode we dont know what they are)
2. USB Mode does not work (Or at least the normal usb, my computer in both windows and linux does not recognize that anything is plugged in. Special drivers might thearetically allow it to connect.)
3. Bluetooth is NOT broadcasting anything
4. The screen does not turn on
5. (Maybe) The keyboard is not active (Light does not turn on so what would indicate it is even on)
6. You cannot exit out of the "Blue LED Mode" without taking the battery out
7. The power light is blue
---------------------------------------------------------
I have an idea that this may be a mode where with the correct cables and drivers you can connect to the phone without the radio or spl. The mode works regardless of if it is bricked or not. If the radio cannot connect to the spl then how would this mode even be able to work unless it never connected to the radio? It must be independent and it must serve a purpose.
Thats all I got, Run with it.
It seems ridiculous that with all the brilliant people here at xda, no one really has a clue what this blue LED mode is even for...I mean, it has to be something!
So maybe a new thread, "Uncovering the mystery behind that blue LED" is needed to raise new awareness and interest on this topic.
Just a thought
Related
1st things first complete noob i apologize for any stupidity in the following post. Right i have faria wm6 ROM on my phone it is unlocked and i did all the steps to installing as to the instructions on this forum. Now heres wots happening my device will not load past the boot screen where it says windows mobile unless i take the battery out, now i thought it might be because of the new american dst so i ran the microsoft cab to patch it up. Well no luck there i sync my time it lags so much so i take the battery out it resets to feb 2006 and it's fine. Also active sync is a pain when you click sync the bar comes up at the bottom and thats it no roatating arrows the softkey does not change to stop. Also when i configure my exchange it says message format and i can change to plain txt or html well wen i first used it i could change it to html but now its stuck on plain txt but i dont know whether thats a setting my exchange provider has to change on there sever - i dunno. But it all seems to revolve around active sync and the devices time. Please help or point me in the right direction because i would hate to go back to t-mobiles rom which is boring!
Any help much appreciated
P.S sorry if this has been posted many a time maybe looked in wrong place but plz post link.
Cheers Guys
dnlohara said:
1st things first complete noob i apologize for any stupidity in the following post. Right i have faria wm6 ROM on my phone it is unlocked and i did all the steps to installing as to the instructions on this forum. Now heres wots happening my device will not load past the boot screen where it says windows mobile unless i take the battery out, now i thought it might be because of the new american dst so i ran the microsoft cab to patch it up. Well no luck there i sync my time it lags so much so i take the battery out it resets to feb 2006 and it's fine. Also active sync is a pain when you click sync the bar comes up at the bottom and thats it no roatating arrows the softkey does not change to stop. Also when i configure my exchange it says message format and i can change to plain txt or html well wen i first used it i could change it to html but now its stuck on plain txt but i dont know whether thats a setting my exchange provider has to change on there sever - i dunno. But it all seems to revolve around active sync and the devices time. Please help or point me in the right direction because i would hate to go back to t-mobiles rom which is boring!
Any help much appreciated
P.S sorry if this has been posted many a time maybe looked in wrong place but plz post link.
Cheers Guys
Click to expand...
Click to collapse
This post makes no sense to me. First you say you can't boot past the 3rd splash screen (Windows MObile 6). Then you start talking about doing cab files and other stuff (which indicates you are past this screen and working on your device).
Please take a breath and give us more information and full details of exactly where you are at. You also have to tell us your current IPL, SPL, and OS versions that show when you boot the phone (we need exact numbers to be able to help). Is your phone a G3 or G4? What is the last / current ROM you have on your phone? Are you now able to get into your phone (ie: did you flash back)? Is your phone CID Unlocked?
Sorry for my confusing post. I am able to get past the boot screen if i take my battery out and put it back in but turning on normally It wont get past if you get what i mean. further explained below...
Heres my numbers: ipl is 2.21, spl 2.21 os 2.18 gsm 02.19.11 , it is CID unlocked, it was flashed to farias rom from t-mobiles latest rom. Ive flashed farias rom twice now going back to t-mobiles first in both instances.
The main problem i seem to get is with the devices time - i'll try to explain this as well as i can - if the devices time is set to now then it is really slow and active sync does not work and the today screen will only show the time and nothing else like messaging, live, tasks, calender etc. and if you reset the device it does not get past the boot screen. Taking the battery out therefore reseting the devices time it works great but changing the time back to now and it lags again. Hope you understand this
P.S. I have installed microsofts dst patch
dnlohara said:
Sorry for my confusing post. I am able to get past the boot screen if i take my battery out and put it back in but turning on normally It wont get past if you get what i mean. further explained below...
Heres my numbers: ipl is 2.21, spl 2.21 os 2.18 gsm 02.19.11 , it is CID unlocked, it was flashed to farias rom from t-mobiles latest rom. Ive flashed farias rom twice now going back to t-mobiles first in both instances.
Click to expand...
Click to collapse
I honestly don't know if this will help, but you might try flashing the latest TMobile US ROM to get you to 2.26 instead of 2.21
http://www.t-mobileapps.com/downloadcenter/Software_List.cfm?selDevice=24
Then flash Faria's over that. Note that the 2.26 ROM will put the 2.25 Radio on your phone. You may want to then get the 2.19 UK radio from the ftp site here and go back to that one (I find the 2.19 works better than the higher versions on WM6 for me).
Also (and maybe before doing what I just suggested) try either turning off BatteryStatus, or upgrading it to 1.04.201 Beta 3. There have been fixes and I had a lockup problem (I couldn't reboot my phone if the USB cord was plugged in and BatteryStatus 1.04.200 Beta 2 was running). I'll attach the cab to this post.
The main problem i seem to get is with the devices time - i'll try to explain this as well as i can - if the devices time is set to now then it is really slow and active sync does not work and the today screen will only show the time and nothing else like messaging, live, tasks, calender etc. and if you reset the device it does not get past the boot screen. Taking the battery out therefore reseting the devices time it works great but changing the time back to now and it lags again. Hope you understand this
Click to expand...
Click to collapse
Are you overclocking or anything? Have you installed other apps, or does it work this way right after installing Faria's WM6 rom?
Faria's WM6 ROM is very good and I've never seen stuff like this reported so it seems its something with your setup. You could try flashing the fixed mUn's ROM ( http://forum.xda-developers.com/showpost.php?p=1172977&postcount=361 ) and see if it behaves the same way. If it does then you have an issue with your phone it would seem. If it doesn't then its an interaction with software on the device.
P.S. I have installed microsofts dst patch
Click to expand...
Click to collapse
You don't have to install this on WM6.
I have an at&t Tilt. I am having a problem with the device automatically powering off during the Windows screen while loading.
To get to where I am at:
1. I followed the instruction to install the HardSPL from HERE. On my bootloader screen, I see:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
2. Then I did the Sim Unlocker procedures found HERE. After completing step 5, the device rebooted, the AT&T icon displayed, then the screen goes blank and stayed that way.
3. I found the fix for the black screen problem HERE. It was a radio problem, and I needed to update the radio to a compatable radio.
4. My phone worked fine for a day. The next day, my phone just died and when I rebooted, it said critically low battery. After I tried to charge it overnight (with AC adapter charger), it was still critical low battery. Then I tried USB charger for the day, still critical low battery. I figured it was a SPL-Radio conflict.
5. Then it stops getting into Windows altogether. It will power off at the Windows loading screen. I let it charge all day. I suppose that the battery is not dead because it is able to stay on the Tri-Color screen without being plugged in, and it always turns off at the same exact point while loading Windows.
6. I still can get to the tricolor screen. I can see USB when plugged and serial when unplugged.
7. I can flash ROMS, and I will even see the different Windows loading screens (Dutty's screens are different than the AT&T green Windows screens.) I have tried original AT&T and cooked WM6.0 Roms/Radios, WM6.1 Roms/Radios. It still keeps rebooting at the Windows loading screen. I tried the original and cooked roms from HERE.
8. I tried accessing the phone via MTTY and use the "boot" command. I still don't fully understand the boot command and what exactly it does, but from my understanding, it resets the boot loader chip.
9. I would like to update the SPL -- instructions HERE. But since I can't fully boot the phone, I can't actually run the Soft SPL (JumpSPL).
Please... any advice will be greatly appreciated.
Similar Problems/Threads:
1. http://http://forum.xda-developers.com/showthread.php?t=406163
2. http://forum.xda-developers.com/showthread.php?t=409272
Try to charge through the usb port on your computer... I have had a similar issue, but that was full stock and still have the issue. HTC chargers wont work for me but select moto ones will. Does the orange light come on when you connect by USB to your computer?
I have tried charging through the USB port on my computer (as well as AC Adapter). It does show the amber light on top (for both methods), but no matter how long I charge it, it will never get to the fully charged green light.
I haven't tried a different (non HTC) charger, but I will try that next.
Are you sure the SIM card door is locked? My phone reboots on its own during start-up if the SIM door is nor properly locked into place...
I just tested the sim card cover. It will reboot at the same point even if the cover is on of off. However, I do believe the cover is sitting correctly, because if I'm at the white AT&T boot screen and remove the cover, the phone will power off.
have you tried hard-resetting your tilt before and after flashing? I had the same problem before. Try to do a hard reset, flash a stock ROM for your tilt, then hard reset afterwards. If same thing happens again, we'll try another method
Put phone in tricolor mode and connect with MTTY.
Type "info 8" and post output here. I suspect problem is caused by bad sectors in the OS area.
There a few different forums on this same subject, and I had the exact same experience on a brand new kaiser last week and thought it was dead. Yea, your gonna have to do a hard reset holding down the power and camera buttons then clicking the soft reset button to get to tri color bootloader mode before it dies, then plug into pc and reflash the official htc rom. It seems like a one time phenomenom as my Kaiser is running just fine now as I was three seconds away from flushing it down the toilet
jockyw2001 said:
Put phone in tricolor mode and connect with MTTY.
Type "info 8" and post output here. I suspect problem is caused by bad sectors in the OS area.
Click to expand...
Click to collapse
Here is the output after using MTTY:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x94C0
Partition[3], type=0x4, start=0xA200, total=0x110C0
CE Total Length(with sector info) = 0x5151000
CE CheckSum Length(without sector info) = 0x5100000
Cmd>
kaalgoosy said:
There a few different forums on this same subject, and I had the exact same experience on a brand new kaiser last week and thought it was dead. Yea, your gonna have to do a hard reset holding down the power and camera buttons then clicking the soft reset button to get to tri color bootloader mode before it dies, then plug into pc and reflash the official htc rom. It seems like a one time phenomenom as my Kaiser is running just fine now as I was three seconds away from flushing it down the toilet
Click to expand...
Click to collapse
I have tried a hard reset before and after flashing the ROM. The method I used was pressing down the two buttons on the front of the phone then soft reset (one above internet button and one above mail button)... then I am prompted with a white screen saying, "This operation will delete all your personal data, and reset all settings to manufacturers default. Press Send to restore manufacturer default, or press other keys to cancel." Please let me know if this method is wrong.
I actually haven't tried the official HTC rom because my phone is originally an AT&T phone. I have tried the official AT&T rom, including the WM6.0 and WM6.1, but I will try the HTC rom now. It won't hurt to try!
UPDATE: After hard reset --> Load official HTC Rom 1.56.405.5 (radio 1.27.12.11) --> hard reset again. Still does the same thing... still rebooting during Windows load. The only difference, no more AT&T screen during bootup... now it's a "smart mobility" message.
jommo said:
I have tried a hard reset before and after flashing the ROM. The method I used was pressing down the two buttons on the front of the phone then soft reset (one above internet button and one above mail button)... then I am prompted with a white screen saying, "This operation will delete all your personal data, and reset all settings to manufacturers default. Press Send to restore manufacturer default, or press other keys to cancel." Please let me know if this method is wrong.
I actually haven't tried the official HTC rom because my phone is originally an AT&T phone. I have tried the official AT&T rom, including the WM6.0 and WM6.1, but I will try the HTC rom now. It won't hurt to try!
UPDATE: After hard reset --> Load official HTC Rom 1.56.405.5 (radio 1.27.12.11) --> hard reset again. Still does the same thing... still rebooting during Windows load. The only difference, no more AT&T screen during bootup... now it's a "smart mobility" message.
Click to expand...
Click to collapse
my OS is writing in bad blocks before that's why it's rebooting over and over again. What I did was use jocky's frankenkaiser (http://forum.xda-developers.com/showthread.php?t=393337). This WIPES OUT ALL DATA IN YOUR KAISER and you need to restore it back again. FOR THIS YOU NEED TO FLASH THE RADIO FROM HELL (get it from here http://forum.xda-developers.com/showthread.php?t=393182) AND AN OLD SPL which you have right now. Read the directions carefully-- it's not that hard but also not for the faint-hearted. Goodluck!
pfcsabre said:
my OS is writing in bad blocks before that's why it's rebooting over and over again. What I did was use jocky's frankenkaiser (http://forum.xda-developers.com/showthread.php?t=393337). This WIPES OUT ALL DATA IN YOUR KAISER and you need to restore it back again. FOR THIS YOU NEED TO FLASH THE RADIO FROM HELL (get it from here http://forum.xda-developers.com/showthread.php?t=393182) AND AN OLD SPL which you have right now. Read the directions carefully-- it's not that hard but also not for the faint-hearted. Goodluck!
Click to expand...
Click to collapse
I know you specifically said to get the radio from hell, but after reading jockey's guide, I got the other radio that GSLEON3 successfully got working with FrankenKaiser. Now I'm stuck because it didn't work out for me. I used radio 1.64.08.21 rather than the actual radio from hell 1.65.17.10. Hopefully GSLEON3 and Jockey will be able to help me with this one.
Can't recall I published FrankenKaiser for radio 1.64.08.21
Here is is:
http://rapidshare.com/files/130939717/FrankenKaiser-V1.9408.zip.html
(follow the readme inside the zip file)
jommo said:
I know you specifically said to get the radio from hell, but after reading jockey's guide, I got the other radio that GSLEON3 successfully got working with FrankenKaiser. Now I'm stuck because it didn't work out for me. I used radio 1.64.08.21 rather than the actual radio from hell 1.65.17.10. Hopefully GSLEON3 and Jockey will be able to help me with this one.
Click to expand...
Click to collapse
ooops... replied to your pm it seems jocky sent you the correct one already. Good luck mate
Losing hope....
Well, I successfully completed the FrankenKaiser process, updated my SPL to reflect:
Security Unlocked
KAIS1*0 MFG
SPL-1.1.JockyW
CPLD-8
I am still getting the power off while Windows loading.
I even tried to load back the original radio from hell (1.65.17.10) and completely ran through the FrankenKaiser process hoping somehow it would fix the problem... but unfortunately, it did not work.
1. Maybe I'll try a few more rom/radio combinations
2. At least I can re-use FrankenKaiser to get back to factory SPL when I attempt to go through the warranty process.
Any other suggestions??? Please let me know.
***Thanks for the help so far Jockey and pfcsabre***
I also have the at&t tilt kaiser version and used the North American Rom update from the HTC website to get it back up. Have you tried getting into tri color bootloader mode by holding the power and camera buttons then clicking the soft reset button then connecting to pc and flash the the official rom? That's what worked for me
also, are you getting any kind of notifications before it shuts down?
kaalgoosy said:
I also have the at&t tilt kaiser version and used the North American Rom update from the HTC website to get it back up. Have you tried getting into tri color bootloader mode by holding the power and camera buttons then clicking the soft reset button then connecting to pc and flash the the official rom? That's what worked for me
Click to expand...
Click to collapse
I have NOT been flashing this way. I have been flashing anytime I get to the tri-color screen, rather than this exact procedure you noted. (Tricolor bootloader--> then soft reset and back to tricolor bootloader) I don't know if this makes a difference or not, but I just tried your method with the rom from the HTC website AT&T Official Rom Download from HTC Website. Still no luck. It still turns off at the Windows screen.
Also, I do not get any kind of notification at all. It always resets before or at the Windows Mobile 6.X screen. I do get a distinctive chime the majority of the time right as it shuts down.
I was having random power down issues as well. This may or may not be the same as your problem, but mine ended up being a hardware issue with the camera itself. My device would suddenly say the camera (actual camera hardware not software) was not recognized and then soon after I would get the chime and then shut down. My only solution was to warranty it. Let's hope I have better luck with a replacement device then a lot of the other storries I have read around here.
Goin' for the warranty...
I want to try the warranty route now. I feel it's hardware at this point because I've already done FrankenKaiser.
Now, my problem lies with returning back to the factory SPL and Rom. I can use FrankenKaiser to UNDO "Security Unlocked" and then use JumpSPL via FrankenKaiser to get back to the factory SPL, but from that point, how do I get back to the original ROM?
Note that I still can't boot into Windows at all, and I will want to flash OEM Rom while I have the OEM SPL. Will the OEM SPL allow flashing back to the OEM Rom, WITHOUT JUMP SPL???
Thanks for your input..
Hi,
My girlfriend recently bought an XDA Orbit 2 which has WM 6.5 install on it.
Everything else on the phone works perfectly and without issue but she is unable to make phone calls correctly;
The phone will be able to dial out and establish a connection but no sound can be heard by either party even though both phones say the connection is there.
This can be resolved by a hard reset, however this only last for about 10-20 minutes before we lose all sound once again.
Can anyone shed some light onto this for me?
One thing that always screws up phone calls is the radio on the phone it should be a 1.59.xx.xx to check it go to start => setting => system => Phone Information => Software Information. Will find it there also while you are there what 6.5 rom is she running on it as if its not a stable one it may be worth updating it...
Should the .xx.xx be anything in particular or just stay as .xx.xx?
anything in particular i use the stock one (with the default rom) which is .42.15 any should do the job though...
Ok the radio on it is 1.58.25.14 which im asuming is wrong. How do I change it?
This a custom flash thingy ma bob wont hard reset the phone when you flash it => http://forum.xda-developers.com/showthread.php?t=376119
http://forum.xda-developers.com/showthread.php?t=426203
Is the radio i am using and imo the best for signal/ battery life.
How to do it.
1.Download both
2. Put the nbh file in the same directory as the custom ruu
3. Put the phone into bootloader (Start + OK + Reset whole on bottom, hold the buttons until it show a red green white blue screen)
4. plug it in to computer (let the drivers fully install)
5. Start up the Polaris_Custom_ruu.exe
6. Follow the instructions, shouldnt take too long to go through and flash
7. it will reset and you will have a nice shiny new radio and hopefully no more call problems.
All i will say now is what an idiot for selling the phone in that state... (may actually be the reason it was sold lol)
Im going to sound ike a total idiot now but I have no idea what ruu is or nbh or where to put it or what a bootloader is.
Could you possibly put it in moron speech Chris?
LOL well honestly i thought that i had already done that....
Have a look at the files that you download and then it will be explained.
The RUU is the thing that will do the flashing to the device
The nbh files contains the information of you download the stuff and follow the instructions you will have the result that you want honestly i cant think of a simpler way of doing it
Ive also put 2 screenshots to try to help you (one has a different radio but you get the idea...)
Also give this a read but i feel it may confuse you more..
http://forum.xda-developers.com/showthread.php?t=381600
Its a noobs guide to flashing and has all of the info that you need to have.
It does give one point that it has to have SPL-2.20.Olinex on the screen but i would guess this is there as you already have 6.5 on the phone.
Awesome, thanks chris I will get it done tonight after work and let you know how it goes, if it fails I have no doubt I will be back complaining about my lack of phone savvy.
Hey Chris, just to let you know that it worked perfectly, thank you for your help it was much appricated.
No worries glad that it worked as if it didnt then i would be out of ideas...
Hello this is my first post I'm writing because I'm having trouble putting Hard SPL
on my ATT Fuze. I have XP and I connect the phone to the computer and sync it
then open the SPL program go through the prompts then my screen on the phone turns off, the phone I believe also turns off and I get the error 260 a screen pops up on the computer saying it found new hardware. Any help with what I'm doing wrong would be greatly appreciated.Im kind of freaked every time I get up the nerve to do it and think I bricked my phone.
Did you install Microsoft .NET Framework 3.5 first?
Here is the link to follow steps incase you didnt see it.
http://forum.xda-developers.com/showthread.php?t=448008
Hey thanks for your help after further reading I know I should have posted this in the right section and yes I have framework 3.5 installed I guess one question would be that I installed 3.5 to the computer do I install it to the phone? Also I have been reading the hardspl post I think one of the ideas is to first install the SSPL manual
to the phone is that correct? Then do the hard spl? If this is corect what do they mean by install it? run it? active sync? sorry just want to get this right
This is from memory - so if i miss something, sorry!
You shouldn't get any error messages when you connect your phone to the pc, regardless of what boot state the phone is in.
The manual jump SPL is to be used if your phone doesnt enter the correct state automatically from the RRU.
If you want to use the manual jump SPL, do this:
1) Connect your phone to the PC (ensure it can sync correctly - no connection errors)
2) Copy the SSPL_manual to the phone
3) (on the phone) run the SSPL_manual file
3b) Phone should now go to a blank black screen
4) Run the RaphaelHardSPL-Unsigned_190_1_3.exe on the PC
4b) Follow the PC on-screen instructions
**However**
you say that the phone turns black / screen off when you run the exe normally - this is supposed to happen. You shouldnt get an error here. (this screen off part is what the manual SSPL is going to do anyway).
**
If you still get problems, ensure you are connected to the computers USB port - not via a USB hub, take the SD card & sim out the phone. Maybe try a different PC, different USB lead - always make sure you are following the instructions very carefully - and if you still have problems, let us know & we'll try harder! - remember to tell us everything, if you try 2 leads - tell us! If you get something different, tell us what! You can never give too much technical info when asking for technical help - and the more you have tried, the more interested others become (we all like figuring out a problem!)
Beeble
Thank you so much for your help just to give you an update either way I do it
Manual SSPL or just run the Hard SPL by itself the screen goes black and I know
thats what it is supposed to do. Just to clarify at first I did not know the screen was supposed to go black so thanks for that. Again either way it disconnects and a screen comes up saying it found new hardware from that point at first I was scared to do anything else but but eventually I just clicked YES install the hardware hoping that after I did that it would not disconnect but even saying yes to the Found new harware it would say it could not install any hardware and I'm stuck
from there still getting the error
Again I cannot say enough how helpful people have been even if I have not been able to get hard spl on the phone yet
Good day.......
I am mailing out of real frustration.
I don't know if this is allowed.
I collected a cingular 8125 from a friend in the UK.
I noticed on starting up that there was Tmobile screen first before the windows mobile screen starts. I had no problem with the fone until i realised that i couldnt connect to my local networks GPRS service (who uses a phone that can't browse)
After scanning thru the site, i decided to flash the phone with Crasing's WM6.5 ROM after doing a HardSPL and i could browse and it was the perfect phone apart from the fact that it was real slow and hangs attimes.
It got worse so i got fed up and decided to revert it back to the original ROM and sort the browsing stuff with a network fix that someone on this site had told me.
I reverted the hardSPL and on installing the Tmobile ROM, it brought out an error message, tried with the Cingular ROM same thing.
So i tired reflashing by using a software called Flash Center and it started and stopped at the 1%.
Restarting my phone just shows me the bootloader screen and i have been battling it constantly for 3 weeks but to no avail
I have read almost all forums here, done almost all they ask to do, but nothing.
The only ROM that worked on it is the WIZARD love ROM but it using exactly 21mins to start up. Thot of downloading Faria/Molski WM5 ROM (cos i sorta prefer going back to WM5) but the links for their downloads are dead.
Please help/direct me to where i can see help cos i really need the phone like 2 weeks ago. I am most definitely depressed now.
Thanks.
Check here for all HTC Wizard WM5 OEM shipped ROMS. The one for Cingular is listed in there.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Wizard_Windows_Mobile_5.0_Shipped_ROMs
You say the phone is a Cingular (G4 DOC version). Does it look like this one (click link ... http://www.brighthand.com/assets/4811.jpg ) with the Cingular logo on top left, etc?
Did you require the HardSPL to be able to flash to new ROM, or did you just use the SIM / CID unlocker using the Wizard Service Tool (note the Wizard Service Tool will only work for G3 DOC type device, not the G4 DOC devices)
You said you also removed the HardSPL. If you removed the HardSPL, then you can only flach the OEM ROMS (i.e., if yours is Cingular, then you can only flash the Cingular Stock ROM ... check link above and use Cingular 2.25 (click here ...
... http://www.4shared.com/file/BJUEhCC9/RUU_Wizard_Cingular_8125_WIZCN.html )
First do a battery pull, replace battery, then start device in bootloader mode (i.e., press and hold Camera button on side, then using the stylus press and release Reset button on same side. Do NOT power up the unit by trying to turn on using the Power button on top). Take note of IPL and SPL version that shows up on Bootloader (3 colour) screen. Then plug in USB and try re-flashing with Cingular OEM ROM.
After successful OEM ROM you can then try HardSPL again and re-flash to other ROMS. There are plenty of cooked WM5 and WM6.1 ROMS out there. The WM6.5 is too much (I think) for these devices. A neat clean simple WM5 or WM6.1 with overclocking works very good.
Regarding your settings for ISO, GPRS, WAP etc. you can look for a Netwrok Wizard cab file, and install ( heres the newest I could find ...
http://forum.xda-developers.com/attachment.php?attachmentid=121023&d=1223800573). This will install 6 files into the root Windows directory of the phone. Reboot the phone and you will notice the Network Wizard icon show up in the Settings/Connection control panel.
One of the files it installs is called provision.zip. You will want to update this by copying the following to the windows directory overwriting the old one. This contains all the settings for your phone. Once you copy this over, click on the wizard in the Connection Settings control panel, and it should give you options for Country and Cell Phone carrier/provider. Click away and it shoould automatically set up the correct info for WAP, GPRS, ISP, MMS, etc.
Good Luck. Let me know what happens.
WOW
Thanks for the response
I used the HardSPL to flash the new ROM.
I removed the HardSPL and the Olip in my IPL was changed back to the 2.26.0001
I tried the cingular 2.25 ROM but it says it wasn't meant for the device and most times the RUU doesn't recognise the phone. Tried the Tmobile 2.26 same thing.
Also used crossbow WM5 AKU2.3 and AKU3.3 ROMs they worked but fails at 96%
The only ROMs that worked is Wizard Love ROM but it spends about 20mins to get to the part where it asks you to align screen and it doesn't move from there
Thanks for the info on the WM5/WM6 also the network wizard cab file. Really hope that phone works
I'm a pretty desperate guy right now cos i use the phone to trade and money is moving, she(money) is a *****
WOW
Thanks for the response
About the pix you reffered to? Yes thats exactly how my phone looks like
I had used the HardSPL to flash the new ROM.
I removed the HardSPL and the Olip in my IPL was changed back to the 2.26.0001, SPL 2.26.0001
I tried the cingular 2.25 ROM but it says it wasn't meant for the device and most times the RUU doesn't recognise the phone. Tried the Tmobile 2.26 same thing.
Also used crossbow WM5 AKU2.3 and AKU3.3 ROMs they worked but fails at 96%
The only ROMs that worked is Wizard Love ROM but it spends about 20mins to get to the part where it asks you to align screen and it doesn't move from there
Thanks for the info on the WM5/WM6 also the network wizard cab file. Really hope that phone works
I'm a pretty desperate guy right now cos i use the phone to trade and money is moving, she(money) is a *****
PS: My IPL/SPL is 2.26.0001
OK. Good info.
Not sure how you did it but somehow you managed to get the T-Mobile IPL/SPL on it, and yet it still recognizes it is Cingular. For one reason or another one aspect does not let the other load and vice versa. ????? Hhhmmmnnn ????
Here is what I would try.
1) I have attached a zip file called SoftSPL. Inside I have made an image file nk.nbf, which contains ONLY the 2.25.0001 IPL and SPL for the Cingular 8125.
Unzip this folder to your Desktop and then try to run only the "newromupdateutility_wizard_noid.exe". Remember, start the phone up in bootloader mode, connect via USB then run the "newrom...exe" file. If you get an error right away saying this is not the right update utility for the phone or something like that, then start over ... i.e., disconnect phone, pull battery, start phone in bootloader mode,reconnect via USB, but this second time try using the one called "2.exe". I found sometimes when I flashed ROMS the first one did not work and the second one (2.exe) did for me.
IF this works, once you get the 2.25.0001 IPL and SPL showing on the bootloader screen then start again (pull battery etc. same as above) but then re-flash back to the original Cingular OEM 2.25 ROM that you tried earlier (the original RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe). Try this and let me know how it goes.
If and when you get it back to the original Cingular ROM, if you get to this point, you can then start back like it was when phone was "new". It will still be SIM unlocked so you can use any carriers SIM card but you cannot flash other ROMs.
If you are going to try other ROMs, re-apply the HardSPL, but make sure you only use ROMs that have been cooked, say they are safe for G4 devices and do not have IPL/SPL in them. This means when you have it HardSPL'd you cannot, or should not use other carriers OEM ROM's such as T-Mobile 2.26 or 3.08.
Lastly, if you do like some of the "extra's" offered with WM6 or higher and do not like a slow phone and want to keep it fast like a WM5 ROM, then stick to either WM6.0 or WM6.1, clean (or what they call Vanilla) ROMs.
Good Luck. Give feedback of how it works out for you and pay attention to errors and messages and IPL/SPL etc. for reporting back and I can help you a little more.
Another thanks again.
I really owe you if and when my phone is finally done cos i think i am getting there.
But i successfully changed the IPL/SPL but on flashing the cingular ROM it says the RUU cannot see my phone and once it sees that it says the update utility cannot be used for my phone.
So what next?
Maybe the ROM is not the right one but i ensure it was meant for g4 tho"
Tried MUN-RUU but to no avail
Eagerly waiting your reply.
Thanks again
OK. YES. You are getting there.
You say the phone is now IPL/SPL 2.25.0001. It shows this on the 3 colour bootloader screen?
What did you run in order to flash; did you run the "newromupdateutility_wizard.exe", or "2.exe", or did you need to run the "START-sSPL.exe" to flash th nk.nbf file I made? (I don't think the "START-sSPL.exe" works from the bootloader screen...phone has to be booted to working status).
Here's what is next. I made a new nk.nbf which is the Cingular 2.25 OS, splash screens and 2.25 radio only. I removed the IPL/SPL and the Extended_ROM, and cooked this back to nk.nbf.
Download it from here .....
http://www.fileswap.com/dl/7WhstX82/nk.nbf.html
..... and copy this to the folder you made of the SoftSPL earlier (overwriting the other nk.nbf - you may want to save that as a back up)
Now try flashing this new nk.nbf again as you did for the IPL/SPL.
If it works, then let the phone boot up completely. Check it out. And then you can run the RUU for the original Cingular OEM once the phone is booted to get it back to Cingular OEM state (full IPL/SPL, OS, GSM, Extended_ROM, etc.)
From here (if you make it) then any further flashing of ROMs, you will want to flash G4 safe ROM's, and you can do this using the SoftSPL folder. Copy the nk.nbf from the custom ROM you want to flash into the SoftSPL folder and run the "START-sSPL.exe" with your phone connected (not in bootloader mode, has to be completely started up and recognized by ActiveSync, but you do not need to establish partnership ... just skip/cancel that part and phone will connect to ActiveSync as a "Guest").
Good Luck. Let me know how you make out with this.
Just to answer your questions.
I ran the "newromupdateutility_wizard.exe"
Would follow thy new instruction sire and get back to thee.....lol
Thanks again.
I am not here to say "Yipee, its done'
But rather to say that the universe, cingular and the god of communication might have just conspired against me.
Just when i think i would finally get my phone working after 3 weeks, a 2 yr old kid took my batteries and only God know where that batteries is now.
Tried to buy a new one but all i get is "Wow! that a pretty old uncommon phone here"
I intend to use an ac to dc converter and when i am done i would give you the feedback
Thanks
PS: Just wanted to give you the heads-up
So i found the battery early this a.m.
Flashed the phone with the ROM you uploaded and it was succesful but on starting it i get a green screen and its damn slow and doesn't even pass the spot where you are asked to align screen (i really do think that nothing happen and its still the Wizard Love ROM that its still booting into)
So I am still stuck?
Hmmm....
OK i guess there might be a psych diagnosis for what i am doing (posting excessive replies without any respond)
It just a worried person.
So i kept re-trying to flash the ROM on my phone about 2ce.
Then i noticed on the 2nd time at about 86% the phone seemed to restart itself into bootloader mode about 2-3X, so i thot the battery was running out. Decided to take it out and get it charged.
On plugging the battery back to the phone all i got was a white screen and starting it on bootloader mode OR hard-resetting still gives me that white screen. On removing the battery the phone flashes like once or twice.
Is this the end? The phone has brought an apocalypse on?
Been doing a lot of browsing for clues but nothing tangible yet.
God smiled on me and the phone started
Got the ROM you gave me flashed and its really refreshing to see the Windows Mobile logo again
But i am stuck at the align screen tho'
I tap and nothing happens unless i drag the target and it just moves around and get back to the original spot.
Thats the latest pal.
OOPS. I did not read all .... your posts ... I just answered your post at the end of the last page. Did not see these last 2.
This is a good sign that you get past the initial boot splash screens and make it to the Align Screen ... soft reset the phone again and look at the IPL SPL that shows on the screen. Is it 2.25.0001 or 2.26.0001?
If 2.25.0001 then let the phone boot up to the Align Screen (and if you cannot get past this then just leave it at this point). Plug back into computer and now try to flash Cingular OEM ROM 2.25 that you tried earlier using the stock file.
If this doesn't let you flash for the same reasons as before (i.e., Invalid RUU tool or Not correct operator) then extract the nk.nbf from the Stock Cingular ROM (right click on the Cingular RUU OEM exe and select "Extract here ...".) then copy the nk.nbf over to the Soft SPL folder and use the START-sSPL.exe and flash this way. (you can delete the rest of the files from the Extract process.
Good Luck. Let me know the IPL SPL you get.
I know my posts are getting sickening but i am really desperate.
Got some info about how to bypass the align screen online but couldn't get my phone to boot anymore.
Soft reset/Hard reset/Bootloader mode: All of it just shows a white screen and nothin more.
Any ideas?
PS:The last time i could start the phone the IPL/SPL was 2.25.0001.
Just want to add this cos i just noticed it:
1. Sometimes tapping the Camera button alone puts the phone on (tho' it shows that annoying white screen)
2. On connecting the phone to a PC the PC recognises it even tho' its off and once i put it on and that annoying white screen comes on, the PC gives the same sound as when a USB is detached.
Hope these info would help.
I"m really getting depressed now. Hope's looking dimmer.
OK. I am now suspecting that you may also have a battery problem. How old is the battery. Could be the battery no longer has enough capacity. It may charge but only hold a charge for very short time and voltage may be too low. Maybe enough power to keep some of the electronics "awake" but not enough to drive the LCD.
It is now IPL/SPL 2.25.0001 so it should be able to flash the Cingular OEM ROM. You may want to try a different battery. Other than this, if not a problem with the battery then I think maybe phone itself is coming to an end.
I would try the battery route, making sure you have a good power source, and then try to flash the stock Cingular ROM.
You can still get these batteries on ebay and phone as well. If you are going to spend any money then maybe instead consider a newer model phone on ebay. (if you are patient you can find very good deal ... I got the T-Mo MDA Vario version of the Wizard (WIZA200) for $25 plus shipping, brand new with a carrying case. It was an estate item from a salesman who passed away and phone was not used before he passed on. One man's misfortune, another man's luck. I am now selling this on ebay plus memory card and earphone here ... http://bit.ly/hDHxrW. I have two more on sale at ebay here... http://bit.ly/eV0zZh ... and here ... http://bit.ly/gLIiKh. I am selling 3 and I have upgraded to Touch Pro 2. Go with AT&T version as this can beused world wide on 3G in North America and is quad band GSM for use in rest of world)
WOW
Thanks Bud
I would change the batteries and really don't mind buying another one but the only problem is i am not in USA nor Canada except i give an address in the US to send it to.
PS: Got to the links and it was a bidding process that was over by the time i got there. If anything opens up you can holla at me.
Would get back to you if there are any new developments
WOW
Thanks Bud
I would change the batteries and really don't mind buying another one but the only problem is i am not in USA nor Canada except i give an address in the US to send it to.
PS: Got to the links and it was a bidding process that was over by the time i got there. If anything opens up you can holla at me.
Would get back to you if there are any new developments
Cheap battery on ebay ..
http://cgi.ebay.ca/New-Li-ion-Batte...652056?pt=PDA_Accessories&hash=item5d2d297c58
http://cgi.ebay.ca/Battery-HTC-Wiza...163910?pt=PDA_Accessories&hash=item45f7ebb846
Phone
Wizards
http://cgi.ebay.ca/HTC-MDA-Mobile-S...0528835033?pt=Cell_Phones&hash=item4cf50dc5d9