Related
I recently used Faria's How to and unlocked my phone, loaded his crossbow rom etc. My phone works flawless.
Now i am attempting to do a friends 8125 (g3)as well. Ive followed the how to exactly and im having a small problem. The first time i tried to downgrade to the buttons 1.05 rom, it froze up. I rebooted, and tried again, its hanging up showing 99% on the PC and 98% on the 8125 and WILL NOT MOVE. I also of course can not get an activesync connection due to the fact that the only screen i get on the 8125 is the 3 color screen. Anyone have any ideas? Quick responses would be greatly appreciated!
When applying ROMs sometimes it appears to stop at 98 or 99% but it isn't. You have to wait for a while - up to 10 minutes I suppose (worst case).
The three color screen is fine. Plug in your USB and the letters "usb" should show in the lower left hand corner. Start your ROM upgrade when you see this.
Let us know...
Alright, so I've been lurking on this forum for quite some time now. I've flashed, reflashed roms. I thought I had a handle on everything but I guess I was wrong. I've been away from a Window's computer for quite some time now. And I recently saw the new 3.3 rom from the gods of xda. Well, I downgraded, to button's 1.01. and then here's where i screwed up. i forgot to go back up to a 2.xx rom. and went straight for the gold and went for the 3.3. yes i know i screwed up. well here's where I'm at now. still stuck with Button's 1.01 ipl/spl but i have the 3.3 OS. And now I'm not getting any active sync connection, my computer isn't recognizing my wizard. also. my 8125 is slow, i mean i tap the screen and i get nothing re-tap nothing eventually nothin happens, and it's stuck on the today screen. I should also mention it's G3, and yes, i unlocked it all the way. so now I'm basically stuck on the today screen with nothing to do. I foolishly finally tried to clear the storage and start from scratch, but now I'm stuck with no extended rom i believe, all the settings are wiped. am i screwed or what? Or does anyone know a way to at least get active sync back up and running, shouldi re-install it? alright so correction, I'm seeing that all the settings from the extended are showing up (i.e. the battery settings on the today screen, the one-touch voicemail/ 411 connect.) so any suggestions.??
edit--
also when booting up, it takes for ever. litteraly 2-4 minutes. And i tried soft rest via stylus, and then it went to button's boot screen shows ipl spl 1.01 and no radio rom but os was 3.3 and then it would reset showing the same damn beer mug, and then it would do it again. then the screen almost faded away and then it showed the same damn screen again. finally it will go to the crossbow splash screen. and no the battery meter at the bottom is showin -1%
you wizard is not dead yet
I did this...hurry...hurry, hurry but there's somethin' that you can do. Try flashing again button's rom by entering your ppc into bootloader, and then attach it to the pc. It will be recognized, and then you can start flashing.
Good luck. And from mistakes we all learn
hmmm
Well I took your advice, put the 8125 into bootloader. And then connected to the laptop. Still no active sync connection, however the 8125 does recognize it I suppose, when I plug into the laptop the USB appears at the bottom left of my 8125's screen.
also
sorry... i hit the edit button in place of quote.
faria
bootloader mode?
i haven't messed up any of my roms personally yet...but i've read in the past that there is a bootloader mode that you can try to enter and reflash your rom from there. maybe it'll work to try and reflash back to the 1.01 rom you started with?
gotta do a search on here to find it...i think it had something to do with holding the comm manager button and the voice dial button and hitting the small button on the right side of the phone between the voice dial and camera button...
waaait
It is how it's supposed to act. It shouldn't charge...it's in bootloader. Just after you hear the "device connected" sound start the button's rom upgrade. that's it. easy as pie
Or you can start with any 2.xx rom. i think it's going to work with that too.
Ok man, I'm such a spaz, alrigh, there's no active sync, but I am running the no id update utility. And it's running on the ppc, so hopefully, I'm making progress.
Exactly what I said
monkey_knight said:
i haven't messed up any of my roms personally yet...but i've read in the past that there is a bootloader mode that you can try to enter and reflash your rom from there. maybe it'll work to try and reflash back to the 1.01 rom you started with?
gotta do a search on here to find it...i think it had something to do with holding the comm manager button and the voice dial button and hitting the small button on the right side of the phone between the voice dial and camera button...
Click to expand...
Click to collapse
That's what I'm trying to tell him. I went thru that. It worked perfectly for me, so it should for him.
anichillus said:
That's what I'm trying to tell him. I went thru that. It worked perfectly for me, so it should for him.
Click to expand...
Click to collapse
It worked for me too.
Boo yah, well I'm back at button.s rom, time to try again. Thanks guys, you've been a world of help.
eightysixfilms said:
Boo yah, well I'm back at button.s rom, time to try again. Thanks guys, you've been a world of help.
Click to expand...
Click to collapse
Also, it's not showing that the 8125 is charging either. On usb, or regular wall outlet. What have I gotten myself into?simply put the device in booloader mode and flash the latest aku2 rom from your provider...this will bring it to live again. due to an hardware flaw wizards cannot be charged with out a proper working OS ....if your battery has drained you need to find an alternative way of charging it and then only you can flash the rom.
ps
activesync is not needed once in bootloader ....
with pleasure
As i said...some mistakes come in handy
@ Faria ... man, I think that if you don't have active sync installed, it won't work... It installs some drivers, the first time it goes into bootloader(for an upgrade 4 example), but it's true that you don't need "active sync" ....course, it's verry possible that I'm wrong...but I had a motorola Mpx200 and it wouldn't recognize it for flash until I've installed active sync
anichillus said:
As i said...some mistakes come in handy
@ Faria ... man, I think that if you don't have active sync installed, it won't work... It installs some drivers, the first time it goes into bootloader(for an upgrade 4 example), but it's true that you don't need "active sync" ....course, it's verry possible that I'm wrong...but I had a motorola Mpx200 and it wouldn't recognize it for flash until I've installed active sync
Click to expand...
Click to collapse
yes you correct you need the driver ..... what i meant to say is you dont need activesync in runing state.......but you do need activesyc in the pc in order to flash.....
thanks guys
Hey, got everything up and running, thanks to all those that helped out, ever in chicago let me know, we'll go out for some beers. But the newrom is up and running and everything seems to be going good. And hey I wasn't torn apart buy the elite on here. So thanks for making me not look stupid. haha
faria said:
yes you correct you need the driver ..... what i meant to say is you dont need activesync in runing state.......but you do need activesyc in the pc in order to flash.....
Click to expand...
Click to collapse
Yeah I didn't know that either, I started to freak once i saw activesync wasn't picking up the 8125. But it's good to know that you don't necesarilly need it up and running.
Yes,
Note: I have had HardSPL, Olipro, etc for ages, and have been flashing roms in the 81, 85 and now 89 series for years.
An odd issue: I had the RyanCPPR v4 Rom in my Tilt, and the multi-color bootloader screen popped up and froze in my Kaiser, Soft, Hard and Battery Resets ensued, but nothing worked......after multiple tries, it reloaded....
I figured a corrupted Rom and tried the new Friday13thV7Diamond....voila...same problem......try, try, try again, and finally it loads....
But, I don't know what is going on. I would guess a radio issue as it stayed from Rom to Rom, but, this not being my area of expertise, wanted to get some thoughts from the big boys.
Anyone?
Thanks, G
Some more info -
Come on people, throw me a friggin' bone here...I know there are a dozen reasons this could be happening, so I'm not abut to run MTTY and start throwing in commands , no matter how much searching I do without some guidance.
On the bootloader, we have:
KAIS1*0 MFG
SPL-1.0OliPof
CPLD-8
MultiColors and at the Bottom
Serial
PPS: Problem began when Opera 9. whatever froze the Device (IN THE LAST ROM) and I softreset-ed. But this could be coincidence
Thanks again,
G
PS: Mystery Continues: Removed Sim - Booted. Let's see how long this lasts.....yup, Looks like sim is affecting it, though it has booted with the sim before.
Thoughts?
Guys,
I'm in front of a peculiar problem in my HTC Touch diamond; it started around 2 weeks back when I powered on the device it got stuck up at the point where it displays "Touch Diamond" in white fonts in black background...normally, after this point the version details flash in red font at the bottom right corner... But in this case it's getting stuck up at this point not displaying the version details like R 1.09.25.23 …. etc.
assuming that the battery charge is low, I put the device on charging, then after flashing the centre (round) button white light twice or thrice, the device start reboot again and again got stuck up at the "Touch diamond" point, if I continue to charge the set, this cycle starts repeating endlessly.
Then, to check, I got the battery charged in an external charger for 24 hours, and also procured a thick battery (Model. DIAM171, Rating: 3.7 V DC & 1340 mAh) too, and kept the device open for 48 hours or so. The device started smoothly and was functioning well for next ten days.
Then this insect called "new ROM" started biting my brain (?), and at first I had flashed an unsigned hardSPL v1.40 Olinex. Then Radio 1.09.25.23 and then the Sone wwe 2.1. All the flashes were done individually, and successfully.
And by the way, I'm no monkey to this flashing thing too, of course, the courtesy and credit goes to the whiz kids of XDA-Developers for the learning imparted on me. Earlier I'd flashed i mate KJam, then HTC ARTEMIS successfully too.
But, alas, after running the new rom nicely for a few calls, and after one more soft reset, it has come back to square one. That is, "when I powered on the device it got stuck up at the point where it displays "Touch Diamond" in white fonts in black background...normally after this point the version details flash in red font at the bottom right corner... But in this case it's getting stuck up at this point not displaying the version ......"
Please help...friends.... plzzzzzzzzzzzz...help....
By the way, the device is going to the Bootloader smoothly on pressing the volume down button while soft reset.
I tried hard reset the device by pressing the round button and the volume down button while soft reset the device and did hard reset it successfully. Still the problem remains.. plz buddy, plz help...
Yep, found your post...after replaying to ur PM
But I'll post here my answer in case that anyone else could also been interested in it:
"Sorry to hear this issue, although I haven't seen this post in the forum...
Ok. based on your story I think that this issue has nothing to do with the cooked rom you've flashed.
It seems more like an SPL problem. I'd suggest to flash the latest HSPL, the 1.93 one.
Till now none complained about such kinda issue... They bricked the phone or they didn't...But such kind of intermediate behavior never heard...
An other suggestion, try to flash with a branded ROM (try downloading the latest official for ur device).
Waiting for ur feedback.
Good luck!"
at last my Diamond is working again...
Warm regards to Shaks1979 & SeatOne for ur kind and quick response... anyway, my diamond is working again......Yeterday... I had started flashing the Radio... earlier the Radio version was 1.00.25.03 (that came with my phone from the factory) which was upgraded to 1.09.25.23 as the ROM Cooker i.e. Seatone is too using this radio ( SONE v.2.1 WWE by SeatOne)
Yesterday, I flashed the Radio version 1.00.25.05 and the phone started working again.
Guys, as soon as the phone started working, I had flashed two more roms, just to understand what went wrong, & the ROMs are (v6.4FullHDTFl by christonge) and (XBMOD_V2 by xboxmod). The flashings went smoothly. At this moment my phone is on XBMOD_V2 Rom & Radio 1.00.25.05.
After seating back, I tried to understand what went wrong, why the phone was not going beyond "Touch Diamond" display point (in white font) and getting stuck up at that point before the R.... G..... etc version details appear on the screen with font colour red and background black.
The problem was with the Radio 1.09.25.23; but the mechanism of the problem went tangentially above my head, I'm in total darkness. Guys, can anyone of you genius can throw some light.
I shall wait for your inputs in the matter.
I have the same problem. After rebooting ok it goes to start up and gets stuck at the touch diamond screen with info about the radio and stuff in red. It won't turn on for me to re-flash it.
So you just fully charged it and left it a while without the battery in then tried again and it worked
Any help would be great... 8-s
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know
Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt
Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.
Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.
awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok
Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse
I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.
heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.
hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.