Hello! First time poster here.
I have a Cingular 8125 (HTC Wizard G3) that was stuck at the bootloader screen (red green and blue bars).
I was able to get the Button ROM (IPL & SPL 1.05) loaded onto device and it was working. I was able to place calls, send messages, etc.
Well, I was following the guides here on this site for unlocking and ran through the unlocking procedure, at which point I attempted to load the T-Mobile ROM (2.60 is what hte IPL and SPL shows).
However, while loading the ROM it failed at 85% giving an Error 302. The device started to reboot over and over again, never getting past the bootloader screen.
I am able to get it to a stable bootloader screen by powering the device off and then connecting it to a wall charger for awhile (i have varied the times, usually I let it sit for more than 10 minutes). I will then connect it back to the PC and try to flash the rom back to the button rom, but it has started doing it on the button rom as well!
Does anyone have any ideas? I have been scouring the forums and haven't found anything yet. I do have the Multi-port/USB TTY program, but I can't seem to find any commands to help me out.
Any help would be greatly appreciated. Thanks!
Update:
I was able to access the device from the TTY (while it was at the bootloader).
I entered in the password (BsaD5SeoA) then entered in the command: ruurun 0 followed by ResetDevice.
The device rebooted at the Button Rom came up! However, it is currently stuck on a customization program....installing Signed_DiscoButton8.sa.CAB
Ok, at this point I'd try the following things. First, hard reset. On reboot, go thru the whole screen alignment. Don't worry about setting date/time, you won't need it. When the screen gets to where it says Customization In 3 Seconds IMMEDIATLY SOFT RESET. You don't want it to customise. Now, it should work normally. Try to flash tmo rom. It will hang at 85% for a while. If that doesn't work, flash from the bootloader screen. Just go into bootlader, (hold camera, stylus into reset hole), after plugging up usb make sure you theres a usb at bottm of screen, and flash your rom.
Thanks for the reply witch.
I tried what you suggested, and I'm still having problems. Whenever the device attempts to flash, the screen will go blank and start endlessly cycling through the bootloader.
I was able to repeat what i did earlier, and got it back to working w/ the button rom. At least I am assuming its button rom. The numbers aren't really matching what button rom was originally. Button was 1.05 IPL and SPL, but the device still shows 2.26.
I checked the version screen to get some numbers, just in case.
ROM Version: 2.26.10.2 WWE
ROM Date: 6/7/06
Radio Version: 02.25.11
Protocol Version: 4.1.13.12
Any thoughts on why it won't let me flash? I'm a little leary about attempting any ROM upgrades now that I have it a (hopefully) working state. I am going to let the battery charge overnight (was dead after trying everything) and try making some phone calls w/ it tomorrow and test other functionalities.
Related
The problem appeared today morning, while listening music using tcmp. the sound stopped suddenly, and standard animated cursor appeared over tcmp screen. i closed tcmp, and the rest of the system seemed fine, i was able to mute the phone and entered my work place. After a while i noticed the screen is off and i can not turn it on using pwr button, although green led kept blinking so the phone was operating. after a soft reset it would not go over splash screen showing IPL, SPL (which are: IPL: 1.06, SPL 1.06, GSM: 01.12.10, OS 1.6.2.4).
I've tried multiple times and still the same, only difference is that sometimes I can see the cursor and sometimes not. I can get to rgb screen and "press send to restore" as well, but that's it. I can't remember whether previously pressing a key illuminated a screen and keys, but now it doesn't. I used to have problems with screen not going black on idle since few days, but that's it. What could have happened? And if the only solution is hard reset, please tell me, could I somehow backup my contacts now? I don't have activesync here so I have to wait till I finish my work to find out..
please help anyone...
rom version : 1.6.2.4 WWE,
date : 11/15/05
radio : 01.12.10
protocol : 4.0.13.23
extrom : 1.6.2.105
That's spooky. My MDA has the same versions of IPL, SPL, GSM and OS, and this morning started misbehaving.
What's this rgb screen you can get to with the "press send to restore" option?
How do I do a hard reset (I have a backup on SD) without being able to get to the Start>Settings>System>Clear storage control panel option?
Rgb screen is a bootloader which i enter by holding cam+voicedial+commmanager butons while softreseting wizard. the other screen i mentioned i enter holding cam and voice buttons, and then pres reset. that screen says 'pres send to restore factory defaults any other key to quit' and it does hard reset if you press green button here...
my problem seems to be over for now, i managed to turn the phone on while i plugged it into a wall charger (believe me, the battery was not a problem - i don't know for how long it's ok now, but at least i made contacts backup now so that i'm ok with a hard reste if i have to...
You both have old roms and could do with upgrading them to aku2 roms. (your device will be more stable) i.e. the first number of the rom will be 2. Please dont ask me to go through how to flash a rom because there are hundreds of posts on the same topic and read the wiki - shortcut top left of the screen. You need to identify whether your device is g3 or g4 but i suspect you both have g3 chips.
Now read & read esp the wizard upgrading forum and wiki and then when you feel confident - flash your device.
mu chipset is g3 based on my ipl/spl info... i wouldn't dare to ask anyone to explain the process of flashing, i'm not that crazy. only thing i'd dare, would be to advice me what rom should i use... or a way to determine this, since i know it can't be just any rom...
banannq said:
mu chipset is g3 based on my ipl/spl info... i wouldn't dare to ask anyone to explain the process of flashing, i'm not that crazy. only thing i'd dare, would be to advice me what rom should i use... or a way to determine this, since i know it can't be just any rom...
Click to expand...
Click to collapse
Looking at your rom numbers i gather you have a t-mobile vario - is it uk or usa rom or polish - i see you live in poland.
there latest uk rom is here ftp://[email protected]/Wi...Prodigy_2210206_109_21911_TMO_UK_WWE_Ship.exe
us rom ftp://[email protected]/Wizard/Roms/Tmobile/RUU_Prodigy_2170702_217_20710_TMO_US.exe
user name xda password xda
Its prob best you sim unlock and cid unlock before you flash in case you change to a non-tmobile rom inc one of the cooked roms.
see here http://forum.xda-developers.com/showthread.php?t=249474
and read dr puttingham's tutorial http://forum.xda-developers.com/showthread.php?t=285435
and now i have given you more than enough hints
p.s. by the way remember to write down your gprs settings and mms settings to use with your new rom.
thats right, its tmobile vario, uk one. it is sim unlocked, i'm not sure about cid but it should not be a problem. thanks for the hints, it really seems more then enough;] i'll probably have to use theese, as soon i have a spare evening...
you don't have to explain me the importance of gprs settings - forcing my wiz to work in uk's o2, then in polish plusgsm, then loosing settings and doing it again finally got me into a habbit of backing every settings up ;]
and last but not least, guys, yesterday i did my first HR ;] ...
I tried to install the faria wm6 update with the shelltool. everything was going as per the directions, about 3 or 5 mins in the install process(which says takes 15 mins) it stopped and it gave me an error on the phone saying something about the reprog.exe or someting... anyways, the computer said done and to reboot... so I did and now it goes as far as the white TMOBILE screen with the following 4 lines of code
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
and it freezes there... it wont turn off either.
Tries removing the battery and reinserting it. Well the same thing happens upon powering on the device. Tried hitting the little hard reset button on the side with the stylus... the screen flashes off and then it attempts to reboot again and the phone freezes at the same spot. Please help. I did everything according to the directions. PLEASE TELL ME I DIDNT BRICK MY PHONE. :'(
This was answered over in the WM6 forum.
But read this:
http://forum.xda-developers.com/showthread.php?t=298613
thanks.. the reboot with the camera button worked.. then I flashed the original rom back... now time to try again. thanks
I don't know if the phone is bricked or what. Was in the store tonight, tried to text message my wife who I couldn't find and the phone was all locked up.
Soft reset, and only the date/time loaded, nothing would run. Soft reset again, and the phone didn't load past the bright splash screen. Tried soft reseting a bunch more times, nada. Did a hard reset, first one didn't work. I think it was the 3rd hard reset that took. Phone seemed like it was back to basic WM5, would be okay. Went home, put it on the charger.
Went to take it off the charger to reload data, and it won't turn on. Soft reset, freezes at bright splash screen. Hard reset, same thing.
Is my phone bricked? Anything that I can do to revive it? Or am I SOL?
Cingy/ATT 8525 w/WM5
(By "bright splash screen" I mean when the splash screen flashes brightly. It increases brightness, but just stays that way.)
Any help greatly appreciated.
I managed to load the official WM6 ROM (spl 2.03) via the built-in bootloader. I have radio, ROM, and GSM. It boots through the ATT animation, then freezes. It leaves a black screen with a blue and green static bar running horizontally across the screen about 1/4" thick.
I don't know how to get Hard-SPL loaded on the device because the only way I can see the device is when it's in the built-in bootloader mode.
will attempt PB/KITL I guess, though I can't at this point get the phone to display the KITL info.
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
viatorx said:
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
Click to expand...
Click to collapse
Not sure I fully grasp what's happening here, but if you want to stop the customisation then hard reset and when it goes to the loading cusimisation stage shove the stylus in the hole to do a soft reset and it will stop it loading.
Mike
Alright, thanks, will give that a try.
I managed to run the official ATT WM6 ROM and flash it without a hiccup (twice), and task 28 in bootloader says no bad blocks. So I am confused how I can flash an "official" ROM successfully and the device still won't work. Am starting to suspect hardware failure apart from memory.
Thanks a million mate, that worked. Phone boots now, already have SSPL installed. Need to update .net and activesync for Hard-SPL 7 to run I guess. Then I have more options.
Woot! I unbricked my phone
Once I was able to hard reset and cancel the "customization" I ran SSPL, then Hard-SPL 7, then I Super-CIDed the device.
I haven't tweaked the data settings yet, but I can send/receive phone calls. Which is a coup, because this is my main line.
It runs sluggishly. I don't know if that is the ROM or the device. It won't boot if it's plugged into USB, and after flashing Hard-SPL it isn't a recognized device by windows, won't connect to activesync.
I am treating the phone gingerly right now, will try and unload the ATT wap settings cab and restore my pim.
At least now I have the option to install another ROM if it bricks on me again.
I really should have flashed Hard-SPL the DAY, the MINUTE after the warranty was up. Lesson learned.
Or not.
ATT ROM locked up on me, decided to try Schaps 4.40. Won't load past WinMo "tap screen to setup" screen. Guess I'll try something else.
For a stable WM6 rom try TNT SE. It is REALLY stable but does come with some 3rd party apps. Thought you might like to get it working though first then try the other roms and in my experiance I haven't found many other roms that were THIS stable...
Hope you get it working...
For a disassembly guide try this site - http://michael-channon.spaces.live.com/PersonalSpace.aspx?_c02_owner=1
Its a bloody good place to go for all things to do with hardware and Mike is a true guru with hardware problems...
Cheers...
Hey there, just want to say before I tell you my problems that this forum is cool. I recieved a lot of useful information and tools for my phone here. Thanks.
Onto the problems!
Okay so first of all, I was given an HTC Vogue on the Telus network from a buddy because my previous phone fell in the pool. I was having a blast with this phone, 'twas the best thing that ever happend to me.
Now before I get into specifics, I'd like to mention that I've never been able to connect to activesynce because the computer would not recognize the USB cable. I've never been able to fix that problem.
Recently I've been having problems with my phone. Sometimes it would take a little spill onto the floor from my lap because I'd forget it's there or whatever. The back casing would come off and the battery would come out. No worries, I would just pop it back in and off I go. But this time it would boot up to the Telus screen with the buncha red writing.
Code:
M 03
B 01
P DCAAXOM-4350H
R 3.41.00
D 3.07
After that text disappears, the phone would freeze at the Telus screen and either: a) No LEDs would flash b) a yellow LED would come on c) THe phone would be left on that screen and just shut off after a while.
So i did some research and found that I could preform a hard reset. Voila! It worked like a charm and I was off using my phone again, but it had barely been 24 hours before the phone froze and I had to reset. And the phone would revertback to the previous problem. Hard reset would NOT work. It would reset the phone but still freeze. Sometimes it wouldn't even stay on the hard reset, the phone would shut off as soon as I release the SEND button after holding all fo the hard reset buttons. So i went back here and on Google to look for the fix.
I've done a bit of research on possible fixes to my phone like disassembley of the phone and the placement of plastic sheet over a processor of some sort and flashing the ROM.
So what I did was look up some custom roms and what not. From what I understand you need a CID Unlocker before custom roms can be used. I looked around and found that I need the USB connector to work for the phone to become unlocked. But this conflicts with my current situation and whenever I try to flash with a custom rom from the microSD, it takes me to the Loading... screen and stays there without any mention of flashing a ROM. This is also the case when I try to put the CID Unlocking .nbh on my microSD card.
So I ask what I can do for my phone to revive it. I've done extensive searches on any fix to my phone with little or no result. I need some fixes fast because I have a tonne of important calls coming in that I need to answer. I will not accept that my phone is dead.
Please guide me in the direction on how to unlock the CID with a microSD card. Or just anything that'll enable me to use my phone again. I con't afford ot buy another one.
BTW
The info on my boot loader screen reads.
VOGU100
SPL-2.01.0000
CPLD-11
BTW
The info on my boot loader screen reads.
VOGU100
SPL-2.01.0000
CPLD-11[/QUOTE]
I gather that you can get to the boot loader screen by the above info. While on that screen try pluging you cable into a direct USB port on the computer and then into the phone. If your phone is recognized it will change from serial to USB at the bottom of the multi color screen. If that doesn't work let me know.
Also here is a link for the unlocker for the CDMA Touch on PPC Geeks
http://forum.ppcgeeks.com/showthread.php?t=20370
whitey10tc said:
BTW
The info on my boot loader screen reads.
VOGU100
SPL-2.01.0000
CPLD-11
Click to expand...
Click to collapse
I gather that you can get to the boot loader screen by the above info. While on that screen try pluging you cable into a direct USB port on the computer and then into the phone. If your phone is recognized it will change from serial to USB at the bottom of the multi color screen. If that doesn't work let me know.[/QUOTE]
I've tried that. The phone reads USB but the computer can't recognize the phone. Activesync won't work either.
EDIT
I've tried flashing with a stock rom. Everything runs fine in that screen. I soft resetted the phone and it went to the windows mobile 6.1 screen with an orange LED and just sat there, I wanted to wait but impatience got the best of me and I soft resetted and now it gets stuck on the telus screen again. Sometimes the green LED flashes as if the phone was running normally and the screen dims. I don't know whats going on.
I think I've tried that ppcgeeks thing but I can't be sure. It doesn't work because I can't connect my hpone with the USB cable.
My boot loader screen has changed after flashing the stock rom. It now reads:
Code:
VOGU100
SPL-2.01.0000
CPLD-3
same problem after flashing, just different writing on the boot loader screen.
patience
patience is the key.
patience is the key.
If you go to bootload screen connect cable and it changes to USB you should be connected.
Also here is a link to a tutorial
http://forum.xda-developers.com/showthread.php?p=3680838#post3680838
To be sure that your computer is not connecting to the phone plug usb in go to deivce manager and double check the USB if it is not connected correctly it will have a warning sign by that port. Try reinstalling updating your drivers for the usb.
patience is the key.
patience is the key.
beanage said:
My boot loader screen has changed after flashing the stock rom. It now reads:
Code:
VOGU100
SPL-2.01.0000
CPLD-3
same problem after flashing, just different writing on the boot loader screen.
Click to expand...
Click to collapse
You need to flash the SPL 2.31 bootloader
It appears as if it's fixed for the most part. Some minor problems but that doesn't stop the fucntionality of the phone. But I'm still pretty pissed that no matter what i do, my phone will not be recognized by the computer with the USB cable. i've tried everything and looked everywhere. Does someone want to send me the usb drivers for the Vogue? Please don't tell me that i don't need drivers because activesync won't connect. I've seriously looked all ove rthe internet for fixes and none of them work. Any pointers ro anyone want to send me official HTC drivers? I want to start using cooked ROMS.
here you go HTC windows driver will work for the vogoue
http://www.4shared.com/file/94429326/ffb09a5f/WindowsHTCdrivers.html
But unfortunately won't solve active sync problem. I would uninstall activesync and reinstall on your windows XP computer.
Quote from HTC website
Q.
Activesync is not recognizing my device, what should I do?
Be sure that you have not connected your device to your PC before you installed Activesync. If you did plug in your device before installing, uninstall Activesync and start the process over ensuring that you do not plug your device in until after Activesync has been installed.
Verify that your device is recognized by your PC in the Device Manager; if it is not, resolve that issue first.
Unplug your device from the PC for a few seconds and then plug it back in.
Perform a Soft reset on the device while it is plugged into the PC.
On the device, go to Start>Settings>Connections>USB to PC and check the "Enable advanced network functionality.
crap, my phone just ****ed off again. Same deal as before. Hate being broke.
help with vogue frozen loading screen
i unlocked my vogue and flashed NFSFAN 6.5 ROM and now phone freezes at loading screen and will go no further. i can still pull up bootloader thats all. any help or tips would be appreciated. thank you
what is your bootloader version
htc boot up screen and bootloader
m03
b01
acaaam-4070
r 2.26.00
s 3nfs
vogu100
spl-0.41.coke
cpld-3
are you using a GPS ROM if so you have the wrong bootloader and need the 2.31 from this post http://forum.ppcgeeks.com/showthread.php?t=20370.. Install the 2.31 and give it a try.
tried using 2.31 unlocker, when i run the RUU and says it will take 10 min it accually takes 10 sec and installs fast then after my phone restarts bootloader still says .41
You need that SPL 2.31 for that ROM
http://forum.xda-developers.com/showthread.php?p=3680838#post3680838
This is a quote from the facts thread for your ROM
First go here http://forum.ppcgeeks.com/showthread.php?t=20370 and
READ the hell outta it until you have it step by step.
(BTW use the 2.31 unlocker regardless about the GPS thing)
OK, now that you've read that (happy dance time)
Download the 2.31 Unlocker and NFSFANs WinMO 6.5 ROM.
Here is a good link for the boot loader. unlocker.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker_MFG_2.31.exe
yeah still can't get 2.31 to load on my phone. i tried to flash the stock alltell and sprint roms but at 29% it freezes or has recovery issues and will not go past 29%. flashed dcd 0.2.0 and got it to load! bootloader still shows .41 but now when i boot up phone it says in red at bottom of HCT boot screen.
m 03
b01
No radio
d1.17
Who is the original carrier You will need to get that OEM ROM and flash it. Then run the 2.31 unlocker follow the directions you can use the bootloader on the factory rom I have done it with sprint and alltel Vogues. The OEM ROM will reinstall your radio then you canuse the unlocker. The .41 unlocker is for non GPS radio and ROM combinations.
Hello mates,
My i-mate Jasjar doesn't start any longer. Here's how I got here. I tried to flash my jasjar with Crossbow ROM using ROMUpgradeUt.exe but it didn't do anything. So I went into the Country_ID_Error folder on the computer and executed MaUpgradeUt_noID.exe. My jasjar froze after this and everytime I restarted it just hung on the bootscreen that says i-mate.
So I tried using mamaich method using mtty and now I can't even get to the i-mate bootscreen. So nothing just happens when I try to power up the phone (I'm sure the battery isn't dead).
All I can do is just enter the bootloader mode. That is the only thing that I can do that I know.
Please suggest something. I'm lifeless without the i-mate.
Thanks and regards,
Aditya More.
i had this same issue, i task28?'d my device, whatever command that resets the flash structure, then booted into bootloader, and flashed this file:
http://rs507.rapidshare.com/files/184081773/JASJAR_WWE_11353_137_10301.zip
that should fix you up real good, hopefully.
Well thanks a lot. But it doesn't help. It gives me a connection error when everything is fine. USB is connected, ActiveSync USB connection is disallowed.
I forgot to mention, that when I task 28'd my device, nothing showed on the device. It just showed USB at the top and v2.01 at the bottom for ever, which means the task 28 wasn't probably successful or I ain't sure what.
Yeah, I had to ask you how if the above given file will work if the phone is in bootloader mode.
To fill you on more details, my phone somehow strangely starts. I'll explain how.
When the phone is switched off, and when I press the reset button, nothing actually happens, no activities can be observed.
When the phone is switched off and I connect it to the computer via USB, it shows the charging light. Now when I press the reset button with the phone connected to the USB, the charging light goes off and the USB detection sound sounds on the computer and the computer shows "USB Device not recognized". This means the phone started.
But strangely in both the above cases, none of the two lights on the phone indicate anything and display of the phone shows absolutely nothing.
The only thing I can do with the phone now is enter bootloader.
Also, since I compromised so much, is it possible that I can still flash it with WM6? Because going back to WM5 will make me feel miserable.
Thanks.
@cheapusenet:
I tried flashing with that file. It flashed successfully, but the screen is all smudged. I soft reseted the phone too (using reset+two soft keys) but it keeps displaying that same smudged screen.
Good news is it did something.
Bad new is that it didn't make the mate work.
Please help. I'm dying without the phone.
Thanks and best regards,
Aditya More.
is it possible you can get a picture of what screen its showing? I THINK it happened on mine as well, did you let it sit for 10 or so minutes? if i recall the bootscreen was all corrupted but it started into WM5 just fine.
and regarding wm6, i'd attempt to get the device working before you try and get fancy. is the device cid unlocked? mine was and thats what was causing the issues.
Originally Posted by mamaich
if you can enter bootloader - use "task 28 55aa", this would restore DOC to its original layout.
If you cannot - contact service center.
if you didnt run that exact command, it's probably a good idea.
and you could try reflashing that stock imate rom?
This is all that happens.. I have waited for 5 minutes. I'll wait for 20 minutes now.
i waited for 30 minutes.. no go..
yap it did that EXACT same thing to mine.
reflash it, i think that fixed mine.
if that doesnt work, attempt flashing some custom roms.
is it CID unlocked?
i flashed it twice.. no go..
what's CID unlocked?
CID
Read the Wiki on my sig link
cid unlock allows flashing of roms that don't match your device branding.
i don't remember what brought me back from that, i may have flashed a custom rom with the imate cid settings in it? i don't remember.
i'll post a rom that i think may have helped in a few hours, I have slow upload speed. until then, just keep tinkering.
also, you should only be flashing nk.nbf. not the ms, or radio nbfs.
http://milfweed.info/UNI_AKU3_2_WWE_IVAN_beta_4_extrom_public.rar
try that rom.
hey man.. Flashed the rom with Ranju's ROM of WM6.1.. it worked.. But I can get the phone to be turned on. i mean device turns on but I can't make or receive calls or text. Let me check the thread of that rom. Thanks a ton for your support. Really appreciate it.