Related
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.
HELP!!!!!! My HD2 turns itself off automatically after about 15-30 minutes of running Android OS. I have HD2Froyo_V2.1.7z. Also installed HSPL3_PKG from XDA and Kumar's TMOUS C5 Premium V2.6. I solved my robot voice and no sound problem. Only thing left is getting it to actually stay on while running in Android. Any help would be greatly appreciated!!!!!!!!!!!!
Hi I have a similar problem. It happens only when I have the phone in my pocket.
My theory is that I press the shutdown button when held in the pocket and thereby turns off the phone. The best thing would have been if the feature was removed when it is in the locked position ... Do you think we have the same problem?
I'm running Duttys rom (v8) and radio 2.10.50.28_2 (HSPL 1.66)
No clue....?????
I am very new to the whole "hacking my phone" scene, if you will... I was pleased with myself for actually getting it to boot and run for a decent amount of time. My phone will just cut off (when im running Android OS), when it's in my hand, when im playing a game, when im doing just about anything in Android. It works perfectly fine in Windows, no probs what-so-ever. I had an issue with connecting to T-Mobile's 3G network, but i think i resolved that. For the most part everything works great, only prob is that the phone just resets on its own. Still very confused as to why..... HELP!!!!!!
I'm no expert on this either. Your problem sounded exactly like mine, just had to ask if it could be so in your case also.
You know what they're asking for technical support? Is the power cable in? Hehe, sometimes it can be very simple things that are wrong.
One thing that struck me was that perhaps you should look over the radio version. There are a few threads on XDA about different radio versions work with android.
Consider what I wrote at the beginning, I'm no expert
Alright. do this and it will work.
1. format your card with your phone to fat32. you need to do this. (yes again)
2. HPSL3 your phone, it seems that once you do it you wont have to do it again but this are the exact steps I did before getting the hd2 android for more than 72 hrs using 99% of the phone. (remember it is always better to have stock android)
3. I am using Chucky ROM but is HORRIBLE ugly and nasty. ROM your phone to Chucky rom or Miri Rom.
4. get Matt C Froyo version of android.
Install it. reboot. tap on CLRAD and then HRET and it will work.
I have an auto loader now it seems they all work but some are nicer. oh by the way you will use your SD card as it was th phones memory with this build, meaning the Windows version of the HD2 is safe for when Windows 7 gets a release and you decide to send to hell android as I will.
I was wondering if anyone found a solution yet for disabling all buttons except the unlock button.. this is the reason why I have been calling ppl without actually noticing I pressed keys while my phone was in my pocket. also it has shutdown few times. sucks because I miss calls that way.
HectiQ said:
I was wondering if anyone found a solution yet for disabling all buttons except the unlock button.. this is the reason why I have been calling ppl without actually noticing I pressed keys while my phone was in my pocket. also it has shutdown few times. sucks because I miss calls that way.
Click to expand...
Click to collapse
I would really like to have a solution to this also. The problem is that you get an option to switch to airplane mode or turn off the phone when you long press endbutton. Even if it is locked. I want to see that when you are only in unlocked mode, the shutdown menu shows. I really hope someone fixes this.
thanks for your help, i tried doing this but that didnt help, i flashed my rom with the energy rom and the lastest mdeejay froyo 3.4. Is there a way i can fix the phone shutting down itself? to turn it back on, i have to take the batter out and turn it back on all the time.
any help pls?
Hi, i seem to have the same problem, android works perfectly when all of a sudden with no reason my phone reboots to winmo. And it has nothing to do with pressing buttons. I have it on a desk and it shuts down. I have noticed that it varies from build to build. Mmce v2.0 would cut down every few seconds. Mdeejay's builds were the most stable, but had no camera. The one I'm using right now "bangster's 1.5" with camera shuts down 1-2 times per day. I can live with that for now. PS: I would like however to thank all the developers for their hard work.
Sent from my HTC HD2 using XDA App
Have you tried running a non-undervolted kernel? Both Hastarin and Michyprima offer non-undervolted alternatives.
http://forum.xda-developers.com/showthread.php?t=787588
Release r7.1 Alternative - as above but without Overclocking, Undervolting, or AXI. NOTE: requires nand_boot=0 in your startup.txt cmdline, see README.txt for details.
http://www.multiupload.com/23ADQU06GU
Click to expand...
Click to collapse
Brgds... /Tubgirl
hd2 turns off I have a solution
first off this isnt a software issue at all. with much time devoted to figuring out the problem with my hd2, it randomly shuts off whenever it wants...well its simply a hardware issue. but nothing to has to do with overheating or anything like that. the battery pins are very flimsy and loose connection to the battery itself very easily. use a piece of paper and make sure its the length of the battery. and fold the paper to create a wedge in the top of the phone and the battery. place the paper wedge halfway in front of the battery as you are putting it in the phone and then gently force the battery into to place. this will create a secure connection between the battery and the pins. i promise it'll work...its just to keep the battery from bouncing and loosing connection.
its just a poorly designed battery casing not being snug enough to hold a connection with the battery. let me know if you are confused on how to do it or anything.
I'm having similar issues and I'm almost sure it's overheating.
Install Hastarin's 7.7alt version kernel which isn't overclocked on startup. This will make your phone a lot cooler after booting. Then install SetCPU and current Widget.
run SetCPU and set a profile to clock down the CPU (245-400mhz) when the Temp is above 98 degrees and to give you an Audible beep
run Current widget and pay attention to the temp. then run something like angry birds that will heat up your phone.
If it crashes at a certain heat, set SetCPU lower.
Another method to diagnose is to run Angry Birds like normal and see how long you can play before it crashes, then put some ice cubes in a double plastic bag and hold it against the lower back of the phone while you play again (after reboot of course). See if you can play longer.
I'm trying to figure out if the HD2 is still under warranty because this is a huge hassle.
EDIT: Just got off the phone with HTC TmoUS repair division and the phone is still under warranty and will be repaired at no cost except one way shipping. I'm going to stress test it in WinMo to make sure they will be able to replicate the problem and I'll ship it tomorrow. I just need to find something that's as CPU intensive as Android.
Does anybody have a solution to this? None of these answers work.
Automatically reboots
I have similar problems with my T-Mobile HD2; it was fine when I first got it (I lined up before the store opened on the day it came out) and am not running Android. It will periodically turn off and go back on again for no reason. I read somewhere that old SIM cards could be a problem and was wondering whether this was the issue as my SIM is more than 10 years old.
i recieved the ota update, but still gps is way off. i thought this was one of the main problems this ota would fix. if someone has answers or experiencing the same problem lets discuss it and find a solution.
grlddawkin said:
i recieved the ota update, but still gps is way off. i thought this was one of the main problems this ota would fix. if someone has answers or experiencing the same problem lets discuss it and find a solution.
Click to expand...
Click to collapse
I'm just curious if your Vibrant has the hardware lock issue as well? I am wondering if there is a common element between that and the GPS not working.
I purchased two vibrants same day. They had different date codes on boxes. One had near zero gps function and was hardware locked, the other had good gps and was not hardware locked.
My Vibrant isnt hardware locked either and I can't even get a GPS lock outside. Ill be looking into this more later.
TheExpertNoob said:
My Vibrant isnt hardware locked either and I can't even get a GPS lock outside. Ill be looking into this more later.
Click to expand...
Click to collapse
Good to know they don't seem to tied to each other then. Definitely let us know what you find out.
Its interesting you bring that up South, both my wife and I got our vibrants together, hers was two days "older" but was the one that was hardware locked though its gps was marginally better (getting a 40m lock in about 5 minutes vs. mine in 7-8 min). I wound up perma-bricking hers not realizing there were phones hardware locked like that. We exchanged it and got her one that's dated about a week after mine (so now mine is the "old"one ) yet no hardware lock on it. I know this is all circumstantial but it does indeed seem as if the hardware lock /gps issue is a flaw, not by design. Either way, running the stock JFD was **** on both, so I updated to JI2 and gps works great on them. I've since updated mine to Bionix 1.7 on mine and will be doing hers tomorrow.
Sent from my SGH-T959 using XDA App
After the JI6 update mine didn't work until I completely formatted everything and installed JFD with ODIN and checked repartition. Then installed JI6 over it with Odin without repartitioning.
Then I used lbstestmode and reset gps data. (I tried this before formatting and got nothing.)
After the format and gps reset I got lock after about 4 minutes outside. GPS is still weird sometimes but for the most part, turning the phone off and back on will result in a lock after 3-4 minutes.
hope that helps
Put your phone in flightmode and see how much better your GPS is
Came to conclusion that the cell signal is interfering with GPS signal
causing inaccurate positioning, accuracy , and losing GPS signal all together
http://forum.xda-developers.com/showthread.php?t=803939
My GPS works amazing after the update, I also did the hardware lock fix since I alsohad a hardware locked phone.
There is a fix for the hardware locked phones? Are you talking about un bricking them or actually making it so you can get into recovery and download modes without using adb? And here I was thinking I was keeping fairly up to date with SGS development lol.
Sent from my SGH-T959 using XDA App
flight mode doesn't work, not. sure if hardware is locked. but went outside and took a drive and gps is all over the place. destination on right, but navigation saids turn left. very dissapointed g1 had a great gps.
ShanDestromp said:
There is a fix for the hardware locked phones? Are you talking about un bricking them or actually making it so you can get into recovery and download modes without using adb? And here I was thinking I was keeping fairly up to date with SGS development lol.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Getting into download mode via hard keys on the phone.
ShanDestromp said:
There is a fix for the hardware locked phones? Are you talking about un bricking them or actually making it so you can get into recovery and download modes without using adb? And here I was thinking I was keeping fairly up to date with SGS development lol.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
[MOD] Fix for hardware locked phones / cant access recovery without adb.
HW unlock the phone so hardware buttons can get into recover and download modes.
As for un bricking them....if any one knows how to I am game to test
I have Ji6 and my gps does not work at all....no locks outside. I have 12 visible but it won't lock on any. the compass sort of works but it's erratic. I previously had the ji2 gps fix and gps/compass were working fine. I'm not sure what to do now. I already had a problem with the ota update bricking my phone because it conflicted with the ji2. I really would like to get my gps working again, but I'm getting really sick of messing with this stupid thing, I just want a phone that works :{
update didnt fix crap for me
Since OP says his GPS "is still way off" I suspect his GPS wasn't broken to start with. I believe the only thing they fixed was phones like mine for which the GPS did not work at all. And I mean that literally -- sometimes my GPS wouldn't even power on, and other times when it did, it would get a lock or even see more than one or two satellites. It was completely non-functional. Not just "way off".
Even after being "fixed" the GPS kind of sucks compared to a dedicated GPS or many other smart phones. Some have speculated this is because of the extremely thin form-factor and the type and placement of antennas. Maybe they used a cheap GPS chip, I don't really know.
But if it worked before (and one of our three phones did), from what I can tell there is no change with JI6.
j16 didn't fix gps (At&t sim)
I have a unlocked vibrant running on AT&T. Everything works but the GPS. CardioTrainer, Endomondo, and Google Maps aren't locking. Before the upgrade it did lock on to the gps, but extremely erratic. Tried the Labtest mod. and didn't get the phone to lock. Performed the upgrade and guess what? 0 gps locking. Not sure if the phone is hardware locked or if the fact that its not lockin in has something to do with the phone being on AT&T (which i doubt). After j16 update, I can't access Labtest mode either. any ideas?
Updated to J16 via stock Vibrant. Still no GPS fix, though I did that unofficial hack (#*#*1472365*#*#) before the update. Can't get back into the hack to reformat the settings after the OTA update.
Alright, guys; I need some help. I previously had the classic all to well known problem with my digitizer, where I was missing about a half inch of touch input on my screen. I had gotten used to just rotating it to type, cause I was out of warranty, and I'm upgrading soon.However, more recently, I have developed a much bigger problem. My touch screen no longer works, AT ALL.
The issue first started when I attempted to install "Someone's ROM" with "That libs". I got screen fade-out that some other users reported, so I pulled the battery and flashed back to my EPinter's CM10 backup. After it had booted, I went to unlock the screen, and NOTHIN'. Not registering any presses or swipes what so ever. I then went into recovery and cleared everything, still nothing. Hooked it up to my PC, ran a FULL wipe (OS included), and flashed a fuitcake. After booting; still no touch screen. A helpful member of this forum suggested I try the PDS fix, so I did. Still left with the same result.
So, my question is... Is there any way that someone MUCH smarter than I can look at some type of statistic I can pull from my phone to see if there's a software problem causing this issue? And if so, is there any way I can retrieve said info with out being able to use the phone it's self? I really don't want to go the next 2 weeks with a flip phone. heh.
EDIT: If anyone can figure this out and get it fixed, I would be more than happy to donate.
Mast likely your digitizer is just broken!
Happens quite a lot on that phone.
They are not that expensive! (see for example http://www.amazon.com/Motorola-Screen-Digitizer-Replace-broken/dp/B004Z0UO8O)
If you can't change it yourself see if you find someone to do it.
Yup. Sounds more like a hardware issue since you already did all recommended procedures.
Sent from that Atrix.
Yeah, I figured as much. Just hard to accept that it's finally completely gone out on me. Especially since it happened at the exact second I tried flashing experimental, untested firmware. I am aware of how simple a digitizer replacement would be, but I don't want to spend $40 on a new one, when I'm about to dump another $300 into a new phone in two weeks, ya know?
Hi everybody i am asking for advice on trying to repair a phone for a family member the phone is a galaxy alpha F variant UK stock rom, factory unlocked and unrooted the problem started after finishing a call the handset was left un attended and when it was later picked up the screen was black but does not appear broken aywhere and does not appear to respond to touch
i have tried un successfully to get it into recovery or download modes the handset turns on and the blue lights come on and you can hear the start up tone but see nothing on screen, it also charges and i have tried a new battery, odin does recognise a device but as i cant get it into download i cant flash a stock rom which i have already downloaded.
So my question is, is there any software that i can download to diagnose whether or not the screen is dead or whether it is a f/w issue or is there a way around this where i can use a different tool to get into the handset and flash a new stock rom in case the current f/w is corrupted
Thanks in advance for any useful help and advice
Please understand that i am a newb to this so if i have made some mistakes or my questions have been answered elsewhere previously i do apologise
I think it seems pretty obvious that the problem is the display itself
Hi BigHands,
I faced a problem having the exact same symptoms as yours twice in the last few month: screen was staying black but phone reacted to some "external" actions (ON/OFF), blue light.
Not sure what happened exactly, but removing the battery and trying to restart the phone finally brought the device back to life after trying more than than 10 times!!!
So in my case, the display was probably not the (only) root cause.
Really weird however that I needed to reboot the phone >10times to make it work: usually when software is screwed either one single power cycle will bring the device back to life or it will never power up again!
Anyways, a FW issue is still a possibility considering the number of bug this phone has (for the price it was sold, that phone is definitely the worse gadget I ever owned!)... But it seems there is a bunch of FW updates on going on this model accross the world, so there is still a little hope things might improve... Samsumg may have woken up; who knows...
JF