hi everyone. im new to the site. i'm amazed how much i never knew about my xda2i before i found this site. there are sooo many cool tools and stuff i'd never heard about. indeed, i wish i had found this site before i made a huge mistake!
i found an update for windows mobile 2005 and tried to use it to update my xda2i (which i now know is really called alpine). of course it didnt work out how i hoped. it ran through the whole process correctly. it erased the curent rom and - so it said - it wrote the new rtom to my device.
unfortunately my xda2i no longer works. the screen is blank and nothing seems to help. soft and hard reset dont work. i tried taking out the battery, and putting it in the cradle. the red light on the top right corner flashes when i do this. but still no joy. i tried re-loading the 2003 se rom but active sync wont detect my xda2i!!!
i cant get any other tools to work because they all seem to use active sync...
i was hoping there was a way to manually put my device into bootloader mode but i cant find anything on how to do this. if anyone can help it would be much appreciated!!!!
all sorted
well it looks like i was a bit premature in posting my problem. i've just been told how to manually put my alpine into bootloader mode. it worked a treat and i have no problems anymore. many thanks and once again im grateful to the have such a great resource as this site! i'll definitly donate next time i have some money in my paypal!
for anyone else having similar problems i'll just say how to put your device into bootloader mode as i had the hardest time finding it out. too many people assume this to be common sense and dont explain for all of us newbies! lol
simply hold down the power button, the select button (thats the directional pad pressed down centrally) and the reset button for a couple of seconds. this puts the alpine into bootloader mode.
athomas81 said:
hi everyone. im new to the site. i'm amazed how much i never knew about my xda2i before i found this site. there are sooo many cool tools and stuff i'd never heard about. indeed, i wish i had found this site before i made a huge mistake!
i found an update for windows mobile 2005 and tried to use it to update my xda2i (which i now know is really called alpine). of course it didnt work out how i hoped. it ran through the whole process correctly. it erased the curent rom and - so it said - it wrote the new rtom to my device.
unfortunately my xda2i no longer works. the screen is blank and nothing seems to help. soft and hard reset dont work. i tried taking out the battery, and putting it in the cradle. the red light on the top right corner flashes when i do this. but still no joy. i tried re-loading the 2003 se rom but active sync wont detect my xda2i!!!
i cant get any other tools to work because they all seem to use active sync...
i was hoping there was a way to manually put my device into bootloader mode but i cant find anything on how to do this. if anyone can help it would be much appreciated!!!!
Click to expand...
Click to collapse
there is no window2005 rom for 02i at the moment. note that before upgrade ROM you have to find out the suitable rom for you PPC. 02i rom is always Alpile ROM. the newest is 1.11.171 radio is 1.04
First things first, device info. Cingular 8125, summiters latest ROM.
My messaging is not working. As in when i click the hardware button, it just illuminates the device. If I click "Messaging" from the start menu or from the windows directory I get the same. This is the second time this has happened to me. The last time I completely blew up the device and upgraded the ROM (was using summiter's 2.3, so it's not a ROM issue). The phone was working fine. I put it down for a couple hours and when I got back to it messaging wouldn't open. I did a soft reset and even the today plugin was gone.
The 2 times now this has happened, the common denominator has been configuring Wisbar Advance Desktop. I've searched their forums and posted but found no information. I'm making a backup of my device in case I need to blow it up again but I'd really prefer not to. If someone could share some insight or maybe tell me how to reinstall messaing it would be greatly appreciated. I'm assuming that the EXT-Rom's are just configurations not the actual software right?
HUGE Thanks in advance to any kind soul who can help me out.
I decided to just go ahead and blow up the phone again. I put Summiter's new ROM back on. BTW - huge thanks to him and others for making our devices so much more enjoyable. So i'm setting up just my core test software. ROM, Omapclock240, Wisbar Advance2, and Wisbar Advance Desktop. NO BETA SOFTWARE at all this time around. I have my mail configured and my custom WAD theme installed. I will leave it like this for at least a day before installing more software. If it doesn't tweak out, then I'll feel confident installing the rest of my apps. If it does the same crap again, then I will be convinced there's an issue with WAD and either the device in general, or my specific device. I really want this to work with WAD because it eliminates the need for at least 3 other peices of software.
So for anyone that's interested I'll update this thread with my findings. Also, I have noticed SIGNIFICANT improvement in signal strength since updating the ROM. Previously when leaving my phone on my desk at work I'd have to touch my right pinky to the ear piece, stand on one leg, wave my underwear over my head and yell "Git spook git!" to get 1 bar of signal. Now i'm sitting comfortably and my phone has typically 3 bars.
well that didn't take too long. Roughly an hour later, my phone had been on standby and POOF!! my messaging has gone the way of the Dodo. I have sent an email to lakeridge software support (though I think it's just one guy) to see what they have to say. I don't like paying for software that makes me have to reinstall my OS 3 times.
If anyone has any ideas, anything at all, please feel free to chime in. For the rest of the day, i'll try anything.
It gets weirder. (This is becoming more of a blog than a thread but I hope I'm enlightening or entertaining someone)
Out of boredom, I disabled wisbar advance and tried messaging. still nothing. reset, still nothing. no messaging. Then for some unknown reason I decided to try switching my today theme (while wisbar desktop was running) and presto! my messaging came back. I have no idea why. So for now, I have messaging. Let's see how long it lasts.
Hello, I am new to this site and the whole BA experience. I got my sx66 about a week ago and decided to upgrade the ROM to 1.33.51. Yes, from what I've gathered from reading it is also a little out of date, but I was trying to start out small. Well, at some point things went terribly wrong, everything seemed to be well, when all of a sudden my screen went blank and I was left with a screen that just says serial at the top and v 2.07 at the bottom. I have left the battery off for about 20 hours now, waitting on the backup battery to die(from what I understand my phone may be stuck in bootloader mode and this should fix it) Well, I just got home from work and the phone still says the same thing if I put the battery on. Any help or suggestion would be appreciated or even just a "Hey, your phones gone" would be as well, just curious to know what to do. Thanks!
Yes, you're in bootloader mode. It's now ready for upgrade.
If you put it in cradle, it will change from 'Serial' to 'USB', run the upgrade and do the (Record,Camera) reset with 'no,yes,yes' and press 'Mail' button.
Most of these are in the Wiki.
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?
Well, after hours of research and searching and reading, I finally decided to flash my T-Mobile Wing. Yay! First, I did Hard-SPL from HERE and followed the instructions to the point. The CanonYang splash screens came up and my Wing loaded into Windows Mobile just fine. From there, I installed ASerg's policies again and ran Itje's Touch-IT Lite for the Wing "1__UPGRADE_ROM.bat" and followed the instructions it prompted me with. An error screen came up on my phone saying "Unknown Status" but I just left it alone. After about 10 minutes, Itje's RUU completed and I hard reset my phone.
Now, only the first CanonYang splash screen comes up and my phone locks up there. Did I just brick my phone? What do I do to fix this?
Any help is greatly appreciated.
*EDIT* In my haste and fear of the "brick", I chose to post a thread rather than do the obvious that many will most likely state. If it helps my situation, please note that it's nearly 5am in Chicago, I have not slept yet, and I'm pretty much terrified I just made a $300 paper weight. I'm certain many of you would do the same.
Yes, I did fix my problem... and yes, I found my answer by searching the forums... and yes, I will buy you all cookies! Itje gets a candy bar though
lol soz
press the camera button and at the same time use the stylus to push the reset ..... a colourful screen will come up ...... connect it to your computer and run a official rom..... you can either look from some or get windows mobile 6 from htc.com if you sign up to the eclub and just find it from there.
hope this helps