I've got a Cingular 8125 (HTC Wizard) that is stuck on the first splash screen - the one with the Cingular image on the background displaying the IPL/SPL/GSM/OS information (image here)
I've flashed with the "button rom", the "wizard love rom", and tried the method to flash with a different rom to a CID locked device. The "button rom" and "wizard love rom" flashed fine, but it still hangs on that splash screen after the flash. I've reverted back to the "official" HTC rom, and it still does this.
The device is NOT CID/SIM unlocked.
This device is NOT under warranty. (A few months out actually, but it was purchased at full retail price without renewing a contract and Cingular seems unwilling to move on any sort of warranty replacement/repair -- big shock huh?)
Is there any hope?
Take out any sdcard/ mini sdcard in the phone and do a Hard Reset.
Button's and wizard are patched Roms,they can be safely flashed to a CID locked phone just like official rom,but no other custom Rom like wm6 will work or flash to a CID locked phone.
Secondly,when you flash,take out the sdcard,it sometimes creates problem in flashing if it needs formatting,and also close/disable any anti virus or firewall and don't surf the net or run any other program,rather try to close down any programs running at the background.
There is no SD Card in the phone, and the SIM card was out when it was flashed.
There have been so many hard resets done to it that it's not even funny.
All unneeded tasks were killed before performing the flash.
I'll try it again tonight (I left the phone at work to give me something to piddle with) just to make sure there wasn't some sort of fluke.
Does anyone think it would be a good idea to just buy an 8125 that has a broken screen or something and replace the innards of my frozen one with the innards of the one with the broken screen?
It isn't crucial that this phone be fixed - it's more of just something for me to fool around with to see if I can get it working. It was actually given to me for that purpose, but if I can get a cheap PDA phone on the cheap, then I'm all for it (even though I'd have to switch carriers - cause I'm pretty sure it won't work with Verizon.)
[EDIT]
I'm gonna try replacing the motherboard battery (I've successfully taken it apart and put it all back together without breaking more than it already is) and I'll report back once I get that replaced. Perhaps this is the problem?
Related
Not quite sure what the issue is with this one. Back in the beginning of the year my XDA II fell from waist height when the carry case snap popped open (notebook bag brush across the front catching on the flap). The only noticeable problem after that was that the power button no longer works, so I have to power it on by pressing the phone or address book buttons etc.
About a month and a half after that incident the phone suddenly just stopped getting signal. I was using the standard shipping firmware with a few apps. Soft reset, hard reset both failed to fix the issue, the phone simply will not pick up the network. Interestingly enough if I play with the phone settings and go through the process of manually selecting a network the phone WILL pick up available networks in the area (this kills my idea that the GSM radio failed altogether). For now I've had to switch back to a junk phone as I've been unable to figure this one out. Anyone have any ideas on this one? I'm using T-Mobile for a service provider and I'm based out of California.
Also, does anyone know of a place that can do diagnostic/repairs here in the U.S.? So far my searches have come up empty.
Thanks in advance.
Give this a try:
Reflash the phone with any version of ROM and it should start working fine again. I think the problem is that you're radio firmware somehow got corrupt.
Ok, guess I'll have to give it a try. I've been avoiding trying the slightly riskier stuff as I got this thing via an independant third party, so warranty/support are iffy.
Is there a general release ROM that I should be looking for (using T-Mo in U.S.)? Or should I look to cooking my own (which I'd rather not)?
You can try upgrading the ROM with the same branded one. That shouldn't void the warranty.
I.e. If you've got an O2 device, get the new O2 ROM
Reflashing
I have had a simular problem with hard locking. Finally my phone quit working all together. I went into boot loader mode and flashed it. It's like having a new phone again. So yeah.. I think the ROM's can get corrupt.
Brandon
NeoCole: Looks like you are using T-Mo in the U.S. Mind if I asked what you flashed yours with? Did you use a specific ROM, Radio Stack version etc.?
I'm running an unlocked i-mate (contradictory to my subj title, I know).
Flash it with the T-mobile 1.72 ROM
ROM Version
Well.. I flashed it with the IMATE 1.72 ROM and used most of it's extended ROM. I used the battery Meeter from the Qtek extended rom. I built most of my extended ROM Myself.
I look at T-Mobile's Beta 1.72 ROM like I look at Windows ME. Both should have never happend. I can't count how many times I had a hard reset with the T-Mobile ROM. I'm not sure if it was a combination of the programs I was useing or not. I saw a post that said SBP was possibly causing the problem. So I quit using SBP products. Later I still had to HARD RESET from time to time. Now that I'm running differently, My device has never been so smooth.
Let me know if this helps,
Brandon
Looks like I'm pretty much screwed. Without a working power button I can't do a hard reset into bootloader mode. When I try using a utility app that allows me to do a hard reset I can't hold down the jog dial at the same time. Good times.
*edit: yeah, that would be 'can't' hold down the jog dial.
You don't need to boot into the bootload to perform an upgrade... the upgrade software takes care of everything for you (except the hard reset at the end)
All you need to do is sync through Activesync and then run the upgrade program.
I would (and have!) flash the imate 1.72 ROM. It is very stable for me and HAS improved the battery life of my imate.
As stated above, just start the flash process and it will put the device into bootloader mode and perform the flash. It will need a HR at the end, but since your power button is not working, maybe you could remove the battery, slide the red slide/switch back into place for a few seconds as if the battery were there, then slide it back, put in the battery, slide it back into place and press one of the puttons to turn it on.
Hey . . . it might just work!
imate 1.72 ROM did the trick. After I actually READ all the posts regarding the ROM I realized it came with an installer and got that done. So far so good. Now if I could only find my missing tomtom 3 cd key that went MIA during my last move
Hey, that's fabulous! Welcome back to the world of convergence.
After working with a couple of reflashes I decided to go back to the released 2.16 ROM. After RUU completed, the device auto-rebooted as usual but when it came up the display was toasted, looked like a TV that lost horizontal hold. Attempts to go back into the bootloader usually result in a scrambled display as well but occasionally I get a clear screen. In any case, the phone appears to function normally sans display - any other resets I'm unaware of or is the unit just toast?
Cheers,
Mike
Well the first wizard that can receive tv i am jealous.
On a serious note try one of the other roms then you can tell if it is a software or hardware problem.
Did you use super cid on the unlocker - thats what i used when i went back to old rom - good luck
Sadlt it appears truly toasted. The device was previously SIM unlocked and SuperCID'd. I've found that the DeviceCID (info 2) is no longer recognized as HTC SuperCID - it's now HTCS ´í•6HTCE. Likewise my bootloader is now locked - g_cKeyCardSecurityLevel = FF - and, when I do get a screen on the rare occassion, I get data crashes with my SIM. Methinks that something went horribly wrong during the flash and trampled some sections it shouldn't have...
try this
Bootloader then reflash with latest firmware. se if it resurects your device...
Spoke to someone technical about the problem with screen alignment going wacky 3-5 times a day. He said the system files are probably corrupt and to do a Hard Reset. Told him I had upgraded ROM and wondered if that could have affected my 8125. Nope. His solution was to ship back to HTC or go to Cingular where they would reinstall Cingular ROM, as this is a low level problem and flashing ROM wouldn't fix the problem since the files are Cingulars. Sort of like reflashing BIOS on a PC, really low level.
Is this info correct? Phone is SIM/CID unlocked. Can the basic ROM be changed? I have already applied a ROM update to IPL/SPL and radio. I am using Suncom (not Cingular) and would love to get rid of Cingular splash screen and stuff.
Anyways, Hard Reset and reinstalled everything. 5 days now and 8125 has not gone out of alignment.
Thanks all.
i cant make calls or send any texts, basically no communication what so ever, when i call my number from another phone while the phone is inside the mda compact II it just doesnt go through...
anyone know why it may be? i got a feeling its 'blocked' (not locked, so doesnt need unlocking for other sims)...
looking forward to hear from you...
tia
Do you get any form of 'reception' (bars on your phone)?
I have the same problem too. In your case, you just need to reflash the RADIO ROM on your phone.
Just as Nokia said, check the reception signal. Your antenna may be busted. Also, does the phone as you for the PIN code when you reboot it? Your sim card may not be properly connected to the mainboard.
I've checked the connection on my antennae, to find that it was indeed connected. I can access the contents of my SIM card with ease. Any suggestions?
do a hard rest n c wt happns...
You haven't answered me about the PIN code after soft reset. Does it go through when you type the PIN or maybe it doesn't even ask for it?
What happens to me now, appears to be fimware related. My phone will work after a hard reset, but then the radio quits working when I the extended ROM customisation kicks in, and reboots the unit. I've tried many ROMs with no success.
You can cancel the customization process by simply pressing the soft reset the second after it starts customizing.
or you have a phone that was
A: STOLEN
B:Switched off by the carrier, So therefore blocked
C:You have a device that Is waving a sign saying sell me abroad ,sell me abroad,sell me abroad
Vlodeck, I've cancelled the customization using a soft-reset (with no success).
I've definately purchased the phone myself about 2 years ago (its also past the warranty period). I contacted my cellular provider, they claim that the imei number I have isn't on the 'blocked' list either.
Go to Prophet forums and find yourself a radio rom. Flash it to your charmer and see if it worked. As far as I recall the one working best with charmer was 2.69.
Vlodeck. I've tried this.
What now seems to work for me, is flashing my unit, using Taxist's "Big Storage" ROM. The problem now, is the radio stops working again, when I install any application that makes registry changes (then does a reboot).
What Taxist's "Big Storage" ROM? Which device do you have anyways? You sure it's not Qtek S110?
Its found on this page: http://forum.xda-developers.com/showthread.php?t=297080&page=3
I have both a Charmer, and Magicain P10A. They both seem to be having slightly similar problems (Note: I'm not confusing the ROM images when I'm flashing though).
The concept behind the "Big Storage" is eliminating the extended ROM from the flashing process (therefore you get more storage space) (that would be wasted with useless customization data) (giving you a ~20MB increase in storage space).
Nokia 3650 said:
The concept behind the "Big Storage" is eliminating the extended ROM from the flashing process (therefore you get more storage space) (that would be wasted with useless customization data) (giving you a ~20MB increase in storage space).
Click to expand...
Click to collapse
I know what Big Storage ROMs are I was just amazed due to the fact the there never was a Big Storage ROM for charmer. That's why.
I tried creating my own (for the Charmer), but the file never seems to be written on the SD card. Why is this?
NB: The write protect tab isn't on, and the card is properly formatted.
I'm using VZW's official 6.1 rom.
This problem started two days ago when i changed the text message settings from threaded to classic. Did a soft reset, and got stuck at tri-color bootloader screen.
I am using the titan exit bootloader program to get myself out of it, but I get stuck again on every soft reset.
I was able to successfully re-flash the official rom, so I thought my problem would be fixed... but it turns out soft resets STILL put me in bootloader.
I'm not sure what the problem is. I have no third party programs installed...
Help?
I had something similar happen on my Verizon X6800, I installed Delorme mapping software and it worked and then after the first run it started going to the bootloader (gradient color screen) with only TITA100 showing. The only way I could rebooot was to remove the battery for several hours and then start it up again and it would work for a short period of time but then eventually go back to the bootloader screen with nothing functioning. I managed to get all my personal info off the phone but that was about it. My phone was within warranty and I was able to exchange it through Verizon, but they gave me a load of crap and repeatedly kept saying you cannot load third party software on the phone or it voids the warranty (I said, you're kidding me, that's why you buy this phone is to make it do tricks other phones can't). I had to take it into a Verizon store and have a "tech" look at it before they would process the exchange. The guy kept saying you can't install 3rd party software, eventually he explained it looked like I cooked the ROM trying to modify the ROM. I had no intention of doing that. I think the ROM was faulty not to mention it zapped my 4 gig SD card.