I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.
help me, my xda wont display anything on it's screen even the wallaby wont appear though it's power is on.What might be the cause of the problem?
thanks in advance...
what happened with it? did you drop it? installed an app, went swimming, etc? have you done a hard reset already?
sunny side up...
fried xda
I just upgraded it to from xda special rom 1.2 to ppc2003, then the upgrade didn't complete because of some conflict on the process so I did a hard reset and presto the bootloader keep on appearing and doesn't boot on the OS, then after that I made a soft reset, after that the even the wallaby didn't appear anymore...is it already dead?or can I still reprogram the wallaby?plss helllp.
a million thanks....
cant you make it enter the bootloader ?
fried xda
I can't enter the bootloader
you may need to do a couple of hard resets. i don't think your unit is fried; just got stuck while going through the upgrade. a lot of chaps had to do a bunch of hard resets until the unit brings itself back to bootloader...this was for both xda1 and 2 i believe...just keep on hard reseting the unit. it should go back to bootloader eventually.
once that's done cradle back the unit and rerun the upgrade. oh btw; when you recradle don't expect activesync to show any indication that it's working or recognizes your device. just cradle it back and click on your upgrade file. with luck it should go through.
good luck
tnx a lot, but how can I know if my unit is already fried?
a zillion tnx
as long as the unit shows some signs of life it's still ok. when i upgraded to 2003se my unit got stuck w/the screen saying serial 1.something. only after like 2 hard resets did it go back to bootloader. in your case it should still be fine. if all else fails...well maybe it IS fried and it's an excuse to upgrade the unit itself
Robson said:
as long as the unit shows some signs of life it's still ok. when i upgraded to 2003se my unit got stuck w/the screen saying serial 1.something. only after like 2 hard resets did it go back to bootloader. in your case it should still be fine. if all else fails...well maybe it IS fried and it's an excuse to upgrade the unit itself
Click to expand...
Click to collapse
I forgot to tell that my son accidentally removed the Memory card while I'm flashing, would that fried the unit?
Thanks in advance if anyone can come up with something that helps... I can't imagine what that might be though!
This morning I had a stock Mogul... original ROM, no hacks, even had the Sprint S/W on it. It worked fine.
I downloaded the new Sprint ROM 3.35.651.2 and ran it. While running the Mogul rebooted, went to bootloader, then failed. It was then stuck in bootloader mode. I read up and found that a successful flash should bring it out gracefully so didn't troubleshoot much. I tried a couple of times more to no effect. It was still in bootloader mode.
I then downloaded the old 2.17.651.0 ROM from HTC and that wouldn't work either. Still in boot loader mode.
I read somewhere that a guy got the 3.16.651.0 leaked ROM to update even when the others would not. So, I downloaded and tried it. Everything looked good! It was loading the ROM, the bar went across the screen to 100% and then...
nothing. A black screen. Vista loaded some new drivers and seemed to know there was a USB device attached but I couldn't connect to it in any useful way through Explorer and it didn't show up in the Mobile Device Center.
I thought I'd try flashing it again but since the screen was black I was just guessing. I did a hard reset (both soft keys plus soft reset button) and I got nothing... not even the same connection I'd had after the 3.16 update.
Now, I plug in the device and get no USB connect sound or notification in Windows. I get a orange light on the right LED for maybe 15 seconds then it goes out. Other than that one brief LED the thing is a brick as far as I can tell.
Any ideas? I plan on taking it in to Sprint tomorrow and telling them they bricked my phone with their update if I can't figure anything out tonight.
Thanks!
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Geckotek said:
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Click to expand...
Click to collapse
Yes.
FYI... I just left the battery out for about 5 minutes (what the heck, worth a try right?) and put it back in. I get no lights, buttons do nothing, soft & hard reset do nothing, forced bootloader does nothing. The only way I can get the phone to do anything is to plug it in to a USB cable. The orange light comes on for about 15 seconds then goes out. The computer never recognized there is a new USB device attached.
I loaded many custom ROMs on my old 6700 and never had a problem. I leave my new 6800 alone and wait for the upgraded stock ROM and look what happens! Guess I shoulda used a custom ROM instead, eh?
lol sounds like a legitimate "brick" to me. Very strange, and congrats on your new mogul paperweight (i also have one that was a victim of water) haha, good for holding things down on the windy days.
Yup, bricked.
Sprint couldn't figure out how to unbrick it and just gave me a new phone. The new one upgraded nicely and now I have GPS!
Everyone enjoy the upgrade!
same problem
no need to retype what you said. i had the EXACT same problem. phone was completely bricked and continued to crash at 11%. I went to my local store (i work for sprint, and i know a smart tech there) and was told it was kaput. Hard reset, tried to reload other roms, the whole 9 yards. It's a goner, and now i have a new mogul in my hand. I'm afraid to try it again. I'm running vista, and im wondering if that's the problem.
Anyone with vista have the same bricking problem? Is it an issue to directly upgrade from factory rom to the 3.35? My old brick had the current 2.17 or whatever... HALP
Vista
The first time I tried the update I connected the Mogul to my Vista Business 64bit Thinkpad T61p.
The second time I tried it (on the new Mogul) was from my Vista Business 32bit desktop (white box).
I don't know if that helps or not. The second time went smoothly.
On another note... an entertaining one... while I was in the Sprint store today waiting for their tech to confirm that the phone was bricked another guy came in with a Mogul and complained of the same thing. I took the last Mogul they had in stock. Poor guy. I hope they get more soon... there are a lot of people who want GPS and are upgrading their phones. That means there are gonna be some more bricks I'd think.
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
OK, let me start by saying I am NOT getting the bootloader, I am NOT getting stuck on a startup screen, and I am NOT new to loading HTC ROMS (but I am new to the titan - former owner of Hermes). With that out of the way....
I bricked my Titan - It won't startup at all. Plugging it into the USB port generates a red LED and nothing on the screen. The only USB activitey seen on the computer is the HTC USB modem (no other communciation appears to be possible - no activesycn, no response to ROM updates etc.
This is the order of the bricking
1. Started with Default Verizon install (less than 4 days old)
2 unlocked with olipro 1.20
3 attempted install of Sprint 3.35 update to get radio (failed and rebooted device at 11%)
4. attempted intall of radio 3.27 (sucessful)
5. installed NexVision 3.35 cooked rom
6. ran into some stability with the rom (phone remained "Unactivated") and reverted back to ruu_signed_verizon stock ROM
7. Booted OK (phoen remained "unactivated"
8. reattempted install of sprint 3.35 (thinking rom instability was due to radio version) device rebooted itself at 11% and failed.
9. installed olipro 2.4 thinking it might circumvent the 11% reboot issue on Sprint ROM.(appeared sucessfull) phone never came back after that.
Now I'm dead in the water... Pulled the battery, Tried a hard reset (2 softkeys under screen/press soft reset) - no change in the device.
are there any secrets to unbricking a Titan?
Starting with the default Verizon ROM, updating to olipro 1.20
Hold off for a little bit, at the moment there is no unbrick, but ImCoKeMaN and jocky are working on this. Your phone now is booting into Qualcomm download mode and it is recoverable. It's just a matter of a patched loader to get a new spl on it...
thank (fingers crossed)... even tried the relocker by ImCoKeMan and it's not detecing the device either...
Time to be patient and wait for CoKeMan to come to the rescue.
just to make sure...
when you tried a hard reset... sometimes people dont know to hold the soft keys for a couple seconds (this is my experience anyway)
jsut for kicks try this again... press and hold the 2 soft keys, press reset button, keep soft keys held down, release reset button, wait a couple seconds then release the soft keys.
Hmmm I remember someone else with a similar problem not too long ago. He thought he had bricked the phone too and was getting the same red led when he plugged it in, but nothing else. His problem was that he had a defective battery. If you could get your hands on a spare battery I'd say try that...I'm not 100% sure it's the battery, and if it's not then I hope cokeman comes through for you...but if you can check that out, I definitely would.
gcincotta said:
Hmmm I remember someone else with a similar problem not too long ago. He thought he had bricked the phone too and was getting the same red led when he plugged it in, but nothing else. His problem was that he had a defective battery. If you could get your hands on a spare battery I'd say try that...I'm not 100% sure it's the battery, and if it's not then I hope cokeman comes through for you...but if you can check that out, I definitely would.
Click to expand...
Click to collapse
Was just about to post the same thing, red LED is definately an indicator of a battery issue, could be defective or just totally dead. If you unplug the battery and reinsert it and then plug in the usb charger without turning it on do you get a green LED? If so I would say battery is 100% discharged and wait for it to charge (I have had this happen). Otherwise if it is still red after that I would say replace the battery (I had this happen on my first titan, it was doa due to defective battery).
jjlwork said:
Was just about to post the same thing, red LED is definately an indicator of a battery issue, could be defective or just totally dead. If you unplug the battery and reinsert it and then plug in the usb charger without turning it on do you get a green LED? If so I would say battery is 100% discharged and wait for it to charge (I have had this happen). Otherwise if it is still red after that I would say replace the battery (I had this happen on my first titan, it was doa due to defective battery).
Click to expand...
Click to collapse
Exactly, all the roms downloaded from HTC recommend having at least a 50% charged battery.
Yup, battery was at 99% before the upgrades. with or without the battery in it reacts the same, with or without the USB in it reacts the same.
I left it plugged in all night, no change.
Solved (but not really)
Since the phone was brand new, Verizon techs took it back as a "faulty phone"... thankfully the Red LED to them means "bad battery" too and when they replaced the battery and it didn't fix itself they exchanged the phone.
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
wow, i didn't (i did-but not reallly) know that it was really really possible to brick your phone, i thought there would more or less always b e a way out. pretty scary!
Shadowmite said:
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
Click to expand...
Click to collapse
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
Click to expand...
Click to collapse
Ok well then I guess you could call me a naysayer then. And I assure you I am no dummy myself, in fact, I'm a Computer Engineer and work with embedded systems alllll day long. I don't doubt your knowledge about the bootloader and the SPL, but before you doubt MY knowledge explain this one to me. Stock battery, no bootloader, no nothing...just red LED. Replaced battery and all of a sudden phone boots...both normally and when forced into the bootloader.
I have the exact same problem. I don't remember exactly how it happened, but was similar scenario to previous posts. I believe I was trying to get the 3.35 radio installed for use with dcd's 3.0.1 kitchen, although I can't be positive.
QPST shows that it is seeing a Qualcomm device in download mode. Here is the exact model# it displays:
Q/QCP-XXX (Download)
Hope this info is useful to those that don't have a titan stuck in this mode.
Yep, that is a brick currently, but a method to fix it is being attempted.
Basically the phone has a dual core cpu with 1 core running the spl, and wince; and the other runs the oemsbl, qcsbl, and amss (the radio). Your spl is missing so the operating system core is doing nothing. However the phone side is still up and running. (this is mostly theory)
So we need to have a patched bootstrap to send in download mode (notice qpst software download actually sends over a bootstrap 7500.hex file found in your qpst bin directory) which will load the spl back into the correct areas of memory. I don't believe we can jump to it because we are on the wrong core.
Do you know which address range the SPL sits in memory?
JTAG ?????
Shadowmite said:
Yep, that is a brick currently, but a method to fix it is being attempted.
Basically the phone has a dual core cpu with 1 core running the spl, and wince; and the other runs the oemsbl, qcsbl, and amss (the radio). Your spl is missing so the operating system core is doing nothing. However the phone side is still up and running. (this is mostly theory)
So we need to have a patched bootstrap to send in download mode (notice qpst software download actually sends over a bootstrap 7500.hex file found in your qpst bin directory) which will load the spl back into the correct areas of memory. I don't believe we can jump to it because we are on the wrong core.
Click to expand...
Click to collapse
Hey Shadow, I think you are correct, and also possibly do you think that JTAGing it would work ? Grad the image from a good one and load it into a dead one. I do not yet have one to take apart yet to try, but if i get a bad one to take apart I might just get it.
It would be great to see this issue resolved as this same problem happened to me last nite and the "friendly" folks at Bell Mobility took one look at the phone and told me it was water damage. I've had the 6800 for about 20 days and it has not been close to water. Anyways, that's besides the point. I look forward to seeing some kind of resolution to the matter....thanks!
Do you see same in QPST ?
Escobar600 said:
It would be great to see this issue resolved as this same problem happened to me last nite and the "friendly" folks at Bell Mobility took one look at the phone and told me it was water damage. I've had the 6800 for about 20 days and it has not been close to water. Anyways, that's besides the point. I look forward to seeing some kind of resolution to the matter....thanks!
Click to expand...
Click to collapse
Do you see this same thing they report with the QPST also ??? Man I would not break mine to fix the problem, but would love to have one to poke at too.
Yes I am having the same problem phone basically dead....
Shadow may fix it, but,,,,
Escobar600 said:
Yes I am having the same problem phone basically dead....
Click to expand...
Click to collapse
I am not going to take mine apart to look for it, but i am sure there is a JTAG port inside these as there is every other I have seen.
Hi all. Had to soft reset my phone this morning after the screen froze and now I am unable to get it to boot passed the windows screen. After about 3 mins it gives me a screen saying something like, "Press Volume Up to hard reset the phone. This will erase all data, blah blah...." Whilst I don't mind having to do a hard reset if necessary, is there any way I could try to salvage some of my data first, particularly texts. It has been some while since I used My Phone to back up the phone sadly.
Well I have got home and put in in the sync cradle and unfortunately it will not open Active Sync. Can anyone see any way I can salvage my data before a hard reset? All ideas welcome.
-BA- said:
Well I have got home and put in in the sync cradle and unfortunately it will not open Active Sync. Can anyone see any way I can salvage my data before a hard reset? All ideas welcome.
Click to expand...
Click to collapse
Have you tried to remove the battery and leave it for a while?
Sometime it helps
If after that you cant boot your phone, there might be something wrong with the OS itself or hardware related problems
Good luck
silverwind said:
Have you tried to remove the battery and leave it for a while?
Sometime it helps
If after that you cant boot your phone, there might be something wrong with the OS itself or hardware related problems
Good luck
Click to expand...
Click to collapse
Hi silverwind, thanks for replying. Sadly yes I have tried taking the battery out and leaving it for well over an hour before trying again.
I am also going to try the 3 mins in the freezer tonight but I am starting to think I have no way of salvaging my sms.
You wont be able to save any of the data unless you can get it to boot into WM.
What were you doing when it froze?
Might be worth checking that you volume button hasnt somehow become stuck in a "pressed" position.... probably not but worth a try I guess...
Thanks for that suggestion, will try when I get home. I had the camera running and the it stopped working properly so I decided to soft reset it and that is when it wouldn't boot back into windows. Hadn't added new software in some time which is what worries me that there may be a hardware fault.
Pretty resigned to losing my data now but c'est la vie