Database Develop

PLEASE HELP - I just BRICKED myG3 While Upgrading to AKU3.2

Hi Folks,
I followed the sticky and unlocked my G3. IPL and GPL were both 1.01. Then, I mistakenly upgraded to the AKU3.2 ROM (without radio) downloaded from the xda ftp site.
After the update, the device boots fine and every loads up. However, when I tried to connect to an USB ActiveSync to perform another rom update, nothing happens. Also, there's no battery information at all. It shows an unknown battery and the battery icon at the lower right hand corner is replaced by the charging icon, even though it's connected to any charger.
Is there a way to update ROM using the memory card (I have a 2 gig card) or I should throw this device out the window? I sincerely appreciate any guidance you may have.
Best,
NA

NeoAlpha1 said:
Hi Folks,
I followed the sticky and unlocked my G3. IPL and GPL were both 1.01. Then, I mistakenly upgraded to the AKU3.2 ROM (without radio) downloaded from the xda ftp site.
After the update, the device boots fine and every loads up. However, when I tried to connect to an USB ActiveSync to perform another rom update, nothing happens. Also, there's no battery information at all. It shows an unknown battery and the battery icon at the lower right hand corner is replaced by the charging icon, even though it's connected to any charger.
Is there a way to update ROM using the memory card (I have a 2 gig card) or I should throw this device out the window? I sincerely appreciate any guidance you may have.
\
Best,
NA
Click to expand...
Click to collapse
No matter what you say you didn't follow the instructions. You should have upgraded to a 2.x ROM image to get your IPL/SPL up to 2.x prior to doing anything. The best way is to use one from your carrier. This may help.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
http://forum.xda-developers.com/showthread.php?t=263116
http://forum.xda-developers.com/showthread.php?t=282498
http://forum.xda-developers.com/showthread.php?t=284292

I just liked the term "bricked" being used because it didn't work as expected. I suppose that term can be retired now, it doesn't really mean anything anymore.

I like how the term "Help" now means "do everything for me because I'm either too stupid or too lazy to read anything".
This whole site has depreciated in value to the point of depression.

rkwhyte2 said:
No matter what you say you didn't follow the instructions. You should have upgraded to a 2.x ROM image to get your IPL/SPL up to 2.x prior to doing anything. The best way is to use one from your carrier. This may help.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
http://forum.xda-developers.com/showthread.php?t=263116
http://forum.xda-developers.com/showthread.php?t=282498
http://forum.xda-developers.com/showthread.php?t=284292
Click to expand...
Click to collapse
Thanks for the info. I completely agree; mistakes were made in ROM update process.

In any case i think you can power up your phone in update mode (when you start the upgrade process it reboot automatically in this mode but you can force it) on the screen you see some coloured bars, if it start in this mode you can try to return to old rom

Activesync is not used at all in the upgrade process... you'll not need it... press the two buttons on the right side while resetting and try to flash an official rom that contains newer versions of the bootloader from the rainbowscreen. NOTE: make sure that it sais USB in the bottom left corner of the bootloader...
Good luck and remember that upgrading the rom CAN IN FACT BRICK YOUR DEVICE....

NeoAlpha1 said:
Hi Folks,
I followed the sticky and unlocked my G3. IPL and GPL were both 1.01. Then, I mistakenly upgraded to the AKU3.2 ROM (without radio) downloaded from the xda ftp site.
After the update, the device boots fine and every loads up. However, when I tried to connect to an USB ActiveSync to perform another rom update, nothing happens. Also, there's no battery information at all. It shows an unknown battery and the battery icon at the lower right hand corner is replaced by the charging icon, even though it's connected to any charger.
Is there a way to update ROM using the memory card (I have a 2 gig card) or I should throw this device out the window? I sincerely appreciate any guidance you may have.
Best,
NA
Click to expand...
Click to collapse
You found the sticky. You downgraded to the 1.05 (where the freak 1.01 came from I dunno..) You didn't upgrade to the T-Mobile per my suggestion. You haven't read my sticky all the way through because I relate my exact same issues of nearbricking..
Reboot your PC. Rerun the Button 1.05. If it still doesn't work use a friend's computer. This procedure works.
kyphur & mark - uh huh!

kyphur said:
I like how the term "Help" now means "do everything for me because I'm either too stupid or too lazy to read anything".
This whole site has depreciated in value to the point of depression.
Click to expand...
Click to collapse
Thank you for your help! Your words have inspired to find the solution.

markgamber said:
I just liked the term "bricked" being used because it didn't work as expected. I suppose that term can be retired now, it doesn't really mean anything anymore.
Click to expand...
Click to collapse
My sincere apology for referencing the term “brick.” I am new to this hobby and from what I have read in this forum, the term is fitting for my particular situation. I did not know that it was antiquated to the point of nausea.

You're asking for our help????
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!

Dr Puttingham said:
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Click to expand...
Click to collapse
My appologies, I think you have misunderstood. My question was not related to unlocking the device. Your instructions were extremely good, and I was successful in unlocking my device. In fact, I have revised your instructions in lieu of grammatical style. I am planning to perform several screen captures to make the guide more useful to others.
There's been alot of misunderstanding regarding my original post. I made a mistake and update the device with the wrong ROM. As a result, ActiveSync no longer works, so I came to this forum seeking additional assistance. I do not offer any dissenting opinions for your article. Your article is extremely useful and your efforts in preparing such article is commendable.

I Found The Solution! Thanks to All
The solution was to boot the device into Bootloader mode and then injecting with a new ROM. Unfortunately, the accepted method of entering Bootloader mode (holding the Communication and Voice buttons while reseting the device) did not work with my device. By doing so the device enters the hard-reset mode. A black screen with white letters offering the choice of restoring the device.
Inspired by Kyphur, Dromico, and _Nomad_, I began investigation alternative methods of entering Bootloader mode. I was playing with the device and by accident held down the "Voice Command" button and reseting. Ulreka! I entered the Bootloader mode and the "Rainbow Screen" appears, thus allowing me to inject a new ROM.

Thank You All!!!

Actually... the two buttons on the right side of the device is camera and voice command... keeping these buttons pressed while resetting gets you straight into bootloader mode... my post mentions nothing of pressing the communications button...

Dr Puttingham said:
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Click to expand...
Click to collapse
Hey Steve, maybe we should hit the coffeeshops and get bricked.

kyphur said:
I like how the term "Help" now means "do everything for me because I'm either too stupid or too lazy to read anything".
This whole site has depreciated in value to the point of depression.
Click to expand...
Click to collapse
Good thing you're so perfect @ everything and that you've never made a mistake.
I love it when people become proficient in something and forget that they were new at it once.
The new people coming on board might have some great things to add. Everyone is a n00b in the beginning.
If you weren't so high and mighty you might realise that offering a helping hand can foster some great community moments and pull some good ideas into the forum.

So new is the same as illiterate? This isn't rocket science, apparently reading is.

Dr Puttingham said:
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Click to expand...
Click to collapse
Plese show me where he was rude to you enough to warrant this type of exchange? I've read the replies to this thread 3 times and I don't see what warrants this type of rude and aggressive response from you.

ppl... pleeease...
take it easy

thought I wasn't a newb, guess I was wrong.

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.

PLEASE HELP!!! Wont Boot - Red/Green/Blue Screen

Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow

and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows

Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.

Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.

grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?

If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.

GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).

Actually, ill just message you tomorrow or something.
Ive been really busy this week.

well did you get it fixed? what did you do?

Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.

I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it

You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!

this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse

dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse

dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.

GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?

Ignito Hard SPL

Howdy, i have looked at all the guides, done loads of research into upgrading my Ignito.
I have tried to use the Olinex 1.40 and also the signed version....
But when i load it all up, go through the correct steps etc.. My phone screen looks like its just had some dodgy virus and looks like its about to die and then slowly turns off...
It then does a full reboot and its like i have a brand new phone again...
I am at a loss as to why it does this..
Anyone have any tips or tricks as to how to get around this problem ?
Any help at all will be very very welcome
Cheers
Sam

when you do the hard spl, you will only get a black screen and then it will reboot, just as you describe.
Hold the volume down key and then soft reset, if you see OLI anywhere, then it worked.

The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....

The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....
Click to expand...
Click to collapse
Maybe you could give more detailed information, what exactly are you doing, what does the PC end of the process say etc.
Can you take any screenshots, what SPL do you have now - the guide suggests that 1.93 could be better for you than 1.4?
Kim

It says complete after about 10seconds and then the phone reboots fully.
The current one i believe is 1.93.....
I have tried both of the Olinex versions to no avail at all.....

......

MuDvAyNeX said:
......
Click to expand...
Click to collapse
I guess no one is helping because you're not giving us enough information, procedure, XP or Vista, have you tried Hard-SPL 1.93, screenshots or better description of the problem.
Screen goes funny and then reboots just isn't enough
Kim

Well i have tried both of the Olinex versions both the 1.4 and the 1.93.
I am using windows vista and the mobile device center, its fully connected as i do a sync etc before hand.
I then load the Romloader that does the usual tick this, tick that etc.
Once that has happened i click the upgrade button, it then confirms i am going from the current SPL do the one i have chosen.
I click ok and then it goes to the progress section where it says it could take upto 10min, the screen on the phone then looks like it has got a virus and starts to look like its dying.
Meanwhile after about 10 seconds it tells me that upgrade is done, this is while the phone reboots and starts like its a brand new phone again with no changes that i can see...
In all honesty i can't see what i am doing wrong

Scrath what i just put, as i was typing that i was trying the upgrade via my mates XP laptop and it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol

MuDvAyNeX said:
it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol
Click to expand...
Click to collapse
Great, glad it's sorted, I was gonna say I don't have much experience with Vista (an' I don't want to )
I'm sure that I've read that there can be issues with the Vista device center(sic), A quick search of XDA-Dev will help.
If you want to eliminate the PC <-> Ignito pitfalls maybe try Suillers method of upgrading direct from the device Internal Storage.
Kim

Tilt Freezes at Radio Splash...Bad Blocks!

Hi guys,
Well, I've searched the forum and get close...but no cigar. So, I'll go ahead and ask.
I have an AT&T Tilt, Flashed the 6.1 from XDA MONTHS ago, and have been running Slither's Cube...not even all the time...as well as the HTC Home Customizer.
Yep, that's it.
Well, I have purchased another Tilt with a busted screen (otherwise absolutely fine) for $30 and am waiting to afford a new screen for it...at which time I'll have a backup and then the Cooking and Flashing will begin in earnest!
But I digress. Here is the sequence of events, and where I am at now:
1) Went to hang up from a phone call (BT headset active) by pressing the "Hang Up" Button...no response from the phone.
2) Pressed the Power Button...no response.
3) Slid open the Keyboard...no response.
4) Held the Power Button...no response.
5) Dumped the battery and rebooted...AT&T Splash then Radio Info...stays right there. Screen will dim after awhile, but never goes out. Rebrightens when removing external Power.
6) Soft Reset...same result.
7) Only way to Power Down is dump the battery.
8) Removed SD and SIM...attempted Bootloader Screen
9) Bootloader DOES show up:
KAIS1*0
SPL-1.93.0000
CPLD-8
Serial
10) I don't remember if there was anything with "Serial"...like a number or such...when I looked at it last (when flashing 6.1) so that may or may not be significant. There's nothing there now.
11) My Radios show up as:
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I am avoiding Hard Reset or Re-Flash until I can at least figure out what happened...if anyone has any ideas...or find out that this is common and that's the best or only way to solve it etc.
Since I haven't found anything quite like this in the Forum, I'm presuming that it may not be so common and I may...or may NOT...be able to find a way back before going that path. As well, I really don't want to send it off for repair...although I have insurance and coverage through Hawk (our AT&T Provider) that would be reasonable for repair ($35) but perhaps inordinate for rreplacement ($175). I'd like to be able to resolve this myself, but not knowing what may be wrong leaves me only with Hard Reset and/or Re-Flash alternatives...if those will even work...so out goes the question:
Has anybody run into this or have any idea of why it happened or the BEST recourse to resolve it?
Thanks in advance for any and all info, y'all are awesome and I truly appreciate your help...
RAF

These phones freeze all the time. Software conflicts, too much running at once, and it just feels like screwing you when you need it most. And of course all of a sudden, the hardware just crashes and never works again.
It looks like a hard reset will solve your problems, unfortunately, unless you do regular backups, you will lose all your info.

Thanks denco7!
Well, this is the first time it has locked up that early in the boot...all others have been easily resolved.
Hard Reset is not an issue with Data...I do keep my phone (data) backed up and have most of my volatiles on the SD.
And, honestly, I don't mind having to reflash or reinstall my apps...at least not yet, once I start cooking my own I feel I'll get a bit testy when I have to 'start over'.
I should probably find a good full backup app to snapshot the whole phone, then just put it back on when things 'happen'.
I do have a full backup from December using the 'supplied' app, so it will at least have most of the tweaks in it.
I'm gonna do the Hard Reset and see if that clears this, but I must say I'm not that hopeful.
Not really an expert...not a noob either...but this technology is just not rocket science, and I can actually do that along with quite a bit more.
Don't ask me to write a driver tho...I respect anyone that has that kind of patience!
Suffice to say, this just doesn't "feel" like a resetable issue...but I'm game. I'll update once attempted.
Thanks again, see you on the other side...
RAF
Okay...no joy on the Hard Reset. Behavior has stayed the same. Kinda expected that tho...
Next stop, Re-flash the ROM. I'm gonna check on latest releases of 'Official' HTC ROMs...but if anyone has any suggestions I'm open.
I'm still hoping that someone out there knows what happened here, it would be helpful to know the 'why'.
Thanks again...

not so much a suggestion but a correction. You don't have a wm6.1 rom but actually have a wm6 rom because the radio you have flashed i.e. R 1.27.14.09
is a wm6 radio not wm6.1 and that radio is only compatible with the following roms:
AT&T 1.60.502.3
AT&T 1.61.502.2
AT&T 1.62.502.0
Q-Mobile 1.2 AT&T Version
(source for above info: http://forum.xda-developers.com/showthread.php?t=393182)
so make sure that your rom matches the radio you have. I would recommend that if flashing is not something new to you than go ahead and upgrade your rom and radio to wm6.1 rom and see if the issue presists.
hope this helps

first post you stated you have a 6.1 rom but your spl is for a 6.0 rom, either your not on a 6.1 rom or your on the wrong SPL and should HARDspl if your flashing custom roms.

Thanks Guys...
I had it in my head that I went to 6.1 when I flashed it last...went out and looked at the file and sure enough it was 6.0.
This is what happens when u have 7 kids, 6 female and 4 of those in college...I'm too broke to pay attention.
No not new to flashing, and when I can get home before 10-11p some night...or this weekend...that's my plan.
Looking for the best choice 6.1 to flash and attempt to bring it back, but still curious as to the behavior in the first place.
Thanks for pointing out my ADD, and all comments are welcome...
Hoping for the un-bricking soon...
RAF

Now I'm REALLY Currious...and Frustrated! A Little Help Please...
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF

Rustafergi said:
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Click to expand...
Click to collapse
If you cannot flash a 6.1 rom or install the correct hard spl I would not even attempt using MTTY. Go to the rom section of this forum. Look for "spl rollup thread" it is a sticky from DaveShaw. Pick any 3.xx hard spl's for 6.1 rom and download. Now download jumpspl and place it somewhere on your device other than your memory card. Now run jumpspl and follow the rest of the directions in that thread. After you installed the correct SPL find a 6.1 rom and flash your device. If your sound doesn't work change your radio to a compatible radio, which would be listed in the "ultimate radio thread" by alltheway.
These are the basics. Hope it helps.

Rustafergi said:
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Click to expand...
Click to collapse
Wow! I think you missed the advice and wisdom given to you about NOT FLASHING a 6.1 ROM with the SPL for a 6.0 ROM...
Anyways, lets see if we can help... I don't think you are going to be able to flash a SPL, as you probably can't even get an active sync connection to copy over the files...
So, try getting into boot loader screen; you hold down the camera button and then press in the rest button and hold that until a tri-color screen appears...
Then tell us exactly what it says, just to make sure we know which SPL you have... Then I will post a link to the exact ROM you need to flash to hopefully bring her back to life.
If you are not able to get into boot loader, which wouldn't surprise me, someone else with more experience un-bricking will have to help.

Some Answers and Info...Still Confused
redbandana said:
If you cannot flash a 6.1 rom or install the correct hard spl I would not even attempt using MTTY. Go to the rom section of this forum. Look for "spl rollup thread" it is a sticky from DaveShaw. Pick any 3.xx hard spl's for 6.1 rom and download. Now download jumpspl and place it somewhere on your device other than your memory card. Now run jumpspl and follow the rest of the directions in that thread. After you installed the correct SPL find a 6.1 rom and flash your device. If your sound doesn't work change your radio to a compatible radio, which would be listed in the "ultimate radio thread" by alltheway.
These are the basics. Hope it helps.
Click to expand...
Click to collapse
pjcforpres said:
Wow! I think you missed the advice and wisdom given to you about NOT FLASHING a 6.1 ROM with the SPL for a 6.0 ROM...
Anyways, lets see if we can help... I don't think you are going to be able to flash a SPL, as you probably can't even get an active sync connection to copy over the files...
So, try getting into boot loader screen; you hold down the camera button and then press in the rest button and hold that until a tri-color screen appears...
Then tell us exactly what it says, just to make sure we know which SPL you have... Then I will post a link to the exact ROM you need to flash to hopefully bring her back to life.
If you are not able to get into boot loader, which wouldn't surprise me, someone else with more experience un-bricking will have to help.
Click to expand...
Click to collapse
Hi again,
Thanks to redbandana and pjcforpres for the responses...I thought I might not get anymore!
I'll start with pjcforpres,
First, my appologies if I have not been specific enough on my descriptions...I've been attempting to be more succinct (I'm not so good at that).
This was a Stock ROM Tilt, then I had flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe quite awhile back...shortly after it was available.
I added Slither's Cube and the HTC Home Screen and Customizer and have run it that way since then.
Somehow, I got it in my head that I had flashed 6.1 but I was flat out mistaken...hence the comment in the earlier part of the thread.
Then we get to the #1 post in this thread...add some confusion and voila.
The ref'd 6.1 flash was also Stock...RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe...and I thought I read everything, incl that it replaces the SPL.
Durring the flash, it pauses @ 13%, the USB disconnect 'bing' sounds and the Bootloader screen reappears showing SPL-3.02.000.
Then, the USB reconnect 'bing' sounds, goes back to the % screen and then completes the flash successfully.
My Bootloader screen is now:
KAIS1*0
SPL-3.56.000
CPLD-8
So...did I miss something and screw up? Or was I on the right track?
And redbandana,
It did successfully flash 6.1, but it still doesn't start...specifically, get passed the initial AT&T Splash.
Although I had already thought of going to JockyW's HardSPL 3.29, I cannot 'see' the phone in XP and therefore cannot get JumpSPL onto it...so, no HardSPL (unless I missed something else in the threads).
It DOES however give me the USB 'bing' sound when I go into the Bootloader...but clicking on the "Mobile Device" icon in Windows Exploder leaves a 'blank' right pane.
Before your post, I had read up on MTTY and noted the DON'Ts...like DON'T use task 2a!...and found several threads with commands.
None of the info commands seem to fuction, like info 2, info 7 or info 8 so I don't have much 'info' there.
One of the things I tried was 'task 28' to format the thing in case there was some corruption...this was the response:
Cmd>task 28
Format start
Storage start sector=0xC2C0, total sector=0xF000
Storage start block=800, total block=960
Total Bad Block in CE: 1
Erase physical block from 1091 to 2032
formatstorage Bad block found: 1397
formatstorage Bad block found: 1398
si backup: Erase physical block from 2032 to 2048
Format end
So I looked for 'bad blocks' on the Forum and there are suggestions to contact JockyW and GSLEON3 for more help.
I haven't as yet done this thinking I can work my way through this by searching the Forum and monitoring this Post.
My searches for MTTY Commands have shown me that there are different Commands for different SPLs, and the info is way scattered and confusing.
It is becoming clear(er) to me that I have an issue that is not that normal...or at least not with an intermediate level 'fix'.
That's why I asked for more help in the right direction, I feel like I've hit this pretty hard and done alot of footwork on my own.
I also feel like I'm running out of options and may resort to bugging JockyW and GSLEON3...unless there are any more suggestions
PLEASE let me know if there is more info that I can provide to narrow this down, or some procedure to attemt, or an MTTY comand that will give us more info, or another search in the Forum for something specific I've missed...or simply some PFM that can be performed...and I'll be HAPPY to comply!
Thanks again...and again...for the assistance, my grattitude and appreciation out!
RAF

I am going to be short and swet for the moment... my computer crashed so I am solely on my phone until I work again around 2 central time USA...
Good news is that there is a chance without MTTY to get you running, and if not, those with the knowledge are very hepful and patient.
I will do the searches tomorrow for the stock ROM you should try, and give a walk through on how to flash using a micro SD card.
I am out for now, and will get back to you as soon as I can tomorrow.

Patient and Prepared
Thanks pjc...if we can fix this I'll vote for you
I sincerely appreciate the assistace, and PLEASE let me know if there's any research I can do to facilitate.
If you're willing, let me know if I took a wrong turn somewhere or if I did something to make this worse...I like to learn from my mistakes (I AM pretty good at those...)
I just got the new screen for my backup Tilt and I'll be swapping that out tomorrow (uh...today) sometime, so I'll have a reference phone soon.
Askew but relevant, I'm on day 12 of a nasty cranial muscle spasm and 3 days into meds for it...so we'll see if I can stay focused
Thanks again and in advance...
RAF...Tilted

http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
Try downloading from here... it is the 100% official AT&T Tilt 6.1 ROM, plus upgrade tool.
This includes everything you need, and is probably what you flashed already, but it sounds like you had a bad flash or something...
Make sure your computer doesn't go into hibernate during this process, and that you don't have anything running other than the update program and activesync...
Also, make sure when you run the update program, you right click and select 'run as administrator' or 'run as' then in the menu that comes after that select administrator.
If you can't establish an activesync connection, or if you are using Vista, and thus no Windows Mobile Device Center connection can be established, let me know, and I will track down the ROM by itself and the Radio by itself and walk you through that.
This should be the easiest fix, though, so we will try this first.

Been There, Done That...I Think ?!?
pjcforpres said:
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
1] Try downloading from here... it is the 100% official AT&T Tilt 6.1 ROM, plus upgrade tool.
2] This includes everything you need, and is probably what you flashed already, but it sounds like you had a bad flash or something...
Make sure your computer doesn't go into hibernate during this process, and that you don't have anything running other than the update program and activesync...
3] Also, make sure when you run the update program, you right click and select 'run as administrator' or 'run as' then in the menu that comes after that select administrator.
If you can't establish an activesync connection, or if you are using Vista, and thus no Windows Mobile Device Center connection can be established, let me know, and I will track down the ROM by itself and the Radio by itself and walk you through that.
This should be the easiest fix, though, so we will try this first.
Click to expand...
Click to collapse
1] Yep, same one I have already flashed several times to determine if there was a pattern.
2] ActiveSync will not connect...remember from #1 in this post:
1) Went to hang up from a phone call (BT headset active) by pressing the "Hang Up" Button...no response from the phone.
2) Pressed the Power Button...no response.
3) Slid open the Keyboard...no response.
4) Held the Power Button...no response.
5) Dumped the battery and rebooted...AT&T Splash then Radio Info...stays right there. Screen will dim after awhile, but never goes out. Rebrightens when removing external Power.
6) Soft Reset...same result.
7) Only way to Power Down is dump the battery.
8) Removed SD and SIM...attempted Bootloader Screen
9) Bootloader DOES show up:
KAIS1*0
SPL-1.93.0000
CPLD-8
I've never gotten passed the initial AT&T Splash since then...no matter soft hard reset flash the 6.0 ROM that was already on it or this 6.1 version.
Only difference is when I flashed this 6.1 ROM, the Radio and Protocol Versions that normally pop up at the bottom in red no longer pop up.
It now stays at the initial AT&T Splash, no versions, and never dims the backlight.
The ONLY time my Laptop 'sees' the Phone is when I put in into the Bootloader I get the USB 'bu-bingk'.
MTTY can see it, and the ROM Upgrades see it and run successfully...but Exploder can't and neither does ActiveSync.
Just to clarify that I've been there more than once...
3] Well, that I have not attempted...but all my previous flashes have gone fine (I am the only user on my Alenware Aurora m7700...and effectively I AM the Administrator), so I'll attempt that...(see next).
I downloaded, overwrote and ran this 6.1 ROM again...I set this XP install with me as the only Administrator (only user other than Guest), and I want to point something out that may be significant:
The Screnshots below show that there's no info in the Current Image Version area, I click on 'Update' and get the 2nd one.
(okay, sorry I haven't attempted very hard to embrace multiquote or embed a screenshot yet )
But this has happened every attemp to reflash after the initial sequence of events. As well, the same events recurred during the flash as all attempts before:
Durring the flash, it pauses @ 13%, the USB disconnect 'bing' sounds and the Bootloader screen reappears showing SPL-3.02.000.
Then, the USB reconnect 'bing' sounds, goes back to the % screen and then completes the flash successfully.
So...did I screw up somewhere? I really thought I had a handle on the 'small steps' that I took..it was the 'next steps' that I was mildly trepidatious about.
My understanding and instincts point to the 'bad blocks' errors durring the MTTY 'task 28' format, but I can't find anything pertinent to 'do' about it in the Forums...other than contacting JockyW or GSLEON3.
I want to try SOMETHING on my own before I go bothering them with a PM...although I've read (and even learned) alot here recently on TOP of what I had already learned over the last 2½ years, I feel I've got to at least attempt something before begging for help that way.
Still, I haven't found a path to get this basal into the core of the phone to noodle (safely mind you) around and become more adept so that I can solve these issues on my own...and it may be time to capitulate.
Let me know if you've spotted an error on my part...something I did or didn't do...or if there's another path I should take or search in the Forum I should look up.
Thanks ton again...and my appologies to all for my un-succinct pontifications...
(S)tilted...RAF

I don't think you are really doing anything wrong on your part, it just doesn't want to flash right... I had you try the stock stuff again just to make sure it was a clean download, and a clean flash.
I am not sure if it is the SPL not matching the ROM, or the Radio... The MTTY commands do indicate a problem with something not flashing right to the phone. Especially since that download has been recommended and successful so many times for people with a similar situation. I have done a fair amount of looking into this myself, and I have found a couple solutions:
1. Some people found success by flashing the same stock AT&T ROM 2 -5 times, and then it finally caught and worked right.
2. Others found luck by flashing a HardSPL, then new Radio, then new ROM.
3. They PM one of the greats... right now in the Kaiser area, JockyW is amazing! But is mostly focused on newer devices. I would recommend contacting mskip or DaveShaw. They have much more experience than I do, and should have a better idea of exactly what those block errors mean, and the solution....
If I were you I would try one last time doing a hard rest, you may need to hold down the 2 soft keys and the rest button extra long to get it to register... I would also try flashing that same upgrade 1 last time, followed by 1 last shot at a hard rest. If you still have the same stuff going on, I would contact those 2 guys and see what their wisdom says... mskip moderates the "NOOB flashing guide" thread and DaveShaw is a moderator for the Kaiser section in general.

Thanks pjcforpres...Contacting DaveShaw...Any Other Ideas?
Okay, one more time...and, no joy. Held the Soft Keys for 2 mintes solid for the Hard Reset, Reflashed, then another 2min Hard Reset.
I've resorted to sending DaveShaw a PM per the suggestion and will patiently wait for a reply.
In the mean time, if there's ANY other suggestions or a list of MTTY commands that run on the 3.56.000 SPL that can get info from the phone to help determine what the actual problem is or to correct bad blocks I'd be SERIOUSLY appreciative and VERY grateful.
Thanks to all who have responded, and in advance to all who may help from here...
RAF
A Little Updated Info:
Replaced the screen on my 'backup' Tilt, and flashed the RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_s ign_25.88.40.05_1.65.21.18_Ship.exe ROM thaT I had flashed on the 'bricked' one.
It had the same behavior @ 13%, so I'm certain now that the flash went fine...I am even more convinced, with all of the events and symptoms to this point, that the issue lies in the 'bad blocks' reported durring the MTTY task 28 format.
I've left a PM for DaveShaw...and I AM patient...but if there is someone that may be more appropriate for this question I'd like to contact them as well. If anyone knows the right Guru, please let me know.
Thanks again to all...
RAF

Well I'm here at last sorry for the delay in getting back to you - I'm not sure how much I can help you though .
Can you post the output of "info 2" and "info 8" from an MTTY connection to your bootloader.
Also, can you please clarify: are you stuck at the bootloader (red/green/blue) or the splash screen (with R G D)?
Thanks
Dave

DaveShaw said:
Well I'm here at last sorry for the delay in getting back to you - I'm not sure how much I can help you though .
Can you post the output of "info 2" and "info 8" from an MTTY connection to your bootloader.
Also, can you please clarify: are you stuck at the bootloader (red/green/blue) or the splash screen (with R G D)?
Thanks
Dave
Click to expand...
Click to collapse
Wow man, THANKS for just bein here!
That's just it Dave, none of the info commands in MTTY seem to return anything (see #10). I've used MTTY: ver. 0.01 2001 and ver. 1.42 1997-2001 and both report literally nothing for info 2 info 7 or info 8...just another Cmd> prompt. However, (also in #10) I get to the 'bad blocks' ref running "task 28":
Cmd>task 28
Format start
Storage start sector=0xC2C0, total sector=0xF000
Storage start block=800, total block=960
Total Bad Block in CE: 1
Erase physical block from 1091 to 2032
formatstorage Bad block found: 1397
formatstorage Bad block found: 1398
si backup: Erase physical block from 2032 to 2048
Format end
Remember, the stuff in #1 of the thread happens and then I went through all this digging...took it to where I could and posted.
This wasn't a HardSPL fail or a bad Flash... I had BEEN running stock HTC 6.0 WWE with Slither's Cube, the HTC Home Screen and Home Customizer.
RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe (flashed 07/20/08)
This isn't a RUUNBH issue either, and I can get into Bootloader and I'm not 'stuck' there...currently:
KAIS1*0
SPL-3.56.000
CPLD-8
I can flash stock ROMs all day long w/no errors...flashed HTC 6.1 WWE on my backup Tilt to be sure the behaviors were the same, and they are exactly.
RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe runs FINE on the backup Tilt.
After flashing the HTC 6.1 WWE on the 'bricked' one however, there is no longer the R G D Radio Protocol info at the bottom of the AT&T Splash after the initial Splash...it was there before the 6.1 flash, and that's where it used to hang: Initial Splash, R G D, hang...backlight eventually dimed but never went out...battery dump only way off.
Now it hangs at the Initial Splash, NO R G D, NO backlight dim...still needs battery dump for off. It ACTS like it's lost it's damn mind...
I'm pretty sure I 'downgraded' back to the 6.0 mentioned above and went thru some similar steps to confirm, but I didn't write it all down and I'm way ADD so I can do that one again and record it all this time...unless that's a bad idea.
I very recently (like as I was searching I saw you had answered my plea...) found some other references to a MFG HardSPL that someone was thinking about working on to fix bad blocks, but I haven't read through it all yet. And, since Exploder and ActiveSync simply can't 'see' the phone, I'm not sure that I could get a HardSPL on the thing in the first place...'cause I can't get no JumpSPL on the phone itself...should've done that back when it was working I guess
I truly believe I'm at the 'needing guru help' level at this point, but if you see something I should do PLEASE point me that way and I'll dive right in. Also, like I've asked others, if you see something I did wrong or in the wrong order or whatever, please let me know that also...there's GOT to be something I can actually LEARN from this.
I warned you I tend to pontificate, but I hope that this clears up where I'm at. ANY help you can provide is fantastic and greatly appreciated, even if it's just to tell me to go somewhere else (I'm kinda used to that )
Thanks again, seriously...
RAF

In that case I have no idea. I think GSLEON3, jockyw2001 or cmonex are going to be the only one's who can help you.
Dave