Phone is borked? - Touch Pro2 CDMA

Hi guys,
My girlfriend somehow has borked her phone.
From what she's explained, she used Task 29 to wipe her phone, or something to that degree, and then tried to flash a GSM ROM to it. However she in on Sprint, so I assume it's a CDMA phone.
As of right now, the phone appears off. If you hold the power down, nothing. If you take the battery out, put it back in, and hold Vol Down it'll boot into the bootloader (I believe that's what it is, the colorful background thing) however the bootloader soon goes away and back to the black screen.
Sometimes the phone will randomly boot up to the HTC logo, and then back to blackness.
Does anyone have any idea what she's supposed to do at this point? Or what I should do to get a ROM on there? I have 0 experience with Windows Mobile roms, so I don't know what happened or what to do next. Guidance of what happened and what to do next would be appreciated so I can solve this issue and understand the situation past 'is it borked'
Thanks everyone
EDIT UPDATE: I figured it out. Her battery was dead lol however USB charging wouldn't work. I happen to have an external charger hah so I saved the day. I was now able to boot into the bootloader, have it stay there, and put a ROM on there. Easy Peasy.

Related

G1 is bricked!!!

after i attemped to upgrade my jf 1.41 rc 30 to jf 1.41 rc 33 my phone freeze and then i took out the battery, try to turn it on and it wont turn back on is there any way or any buttons i need to push to get this back on again? i'm desperate and dont want to wait for a g1 replacement which is coming next week please give me some advice on how to make my phone work again.
both CAMERA/POWER and HOME/POWER are not working?
yup both i tried nothing works
ariex said:
my phone freeze and then i took out the battery, try to turn it on and it wont turn back on.
Click to expand...
Click to collapse
Did you put the battery back in?
what do you think?
I upgraded from JF 1.41 RC30 with no problem, Radio and all, good luck!
ariex said:
what do you think?
Click to expand...
Click to collapse
So far you are the only person with this problem so we are running through the basics.
Did you get any errors or messages during the update? Did the phone run out of battery mid update? Did anything odd or unusual happen?
quick question in while in the topic, had he done a FULL nandroid backup and was able to atleast get to boot screen would he be able to restore his phone? just a quick questions because to this day i have no idea how the nandroid thing works i cant do it on my x64 vista either and dont see how it comes in handy lol. Sorry just trying to fig it out.
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
@zgjbeta Yes. If you can get to the blinkin android screen, your not really bricked. Nandroid would fix it right up.
If it wont even turn on, like your case. I dono what to tell you.
For starters, try to connect it to a wall outlet to make sure its not the battery.
Also tell us exactly what happened during the update process.
EDIT: I read your most recent post. That's strange because everyone gets the chip thing, you shouldve tried home + back or menu + green + red.
One of those wouldve most likely worked.
Good luck.
Also maybe try to take it out again and put it back in.
I had the chip and arrow after the radio update, I didn't take the battery out, started pressing random keys, lol... and then it went away and booted back to a JF recovery style screen. Pressed home + back and it rebooted to a stuck flashing android. Then did call+menu+end to reboot and it has worked fine ever since.
There is definitely something whacky going on...
yes i tried to do the home key plus end and camera plus end options while in that chip state but didnt do anything so i resolve to take out the battery and it wont turn on again. i also tried all the button reset combo nothing happens
If it wont even turn then there is really nothing that can be done. Another thing I would try is if you know someone else with a G1 try their battery.
ariex said:
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
Click to expand...
Click to collapse
Also try cleaning the battery contacts in the phone and on the battery. This happened to one of my dumbphones once - cleaned out the battery contacts and it worked again. Bizzare situation, simple solutions first.
You might've turned it off while it was writing a vital file. Thus your phone might be bricked.
Here's an idea - sent it back to T-Mobile/HTC - and I don't think they will notice you violated your warranty until it's too late (they have to fix your phone to find out) so you could just refuse to pay and have them send it back to you.
I too saw the chip with the arrow thing, so that makes 3 people in this thread. It happened when I did the radio update. Anyway, in my case, I held down the recovery mode keys for a while and it went to the menu. Then I just rebooted and everything was great. Glad I didn't take out the battery (I considered it).
I had the chip and just waited and it took care of itself. Just be patient people.
plug in the wall charger, wait 10 seconds, then hold the red power button for 3-5 seconds then release, it should turn on
i tried that didnt work anymore advice?
also is there any way to run diagnostics of this phone to pc to make it work?
If the phone won't turn on, go back to the T-Mobile store and ***** em out. Not much else to say if we can't even get power to it.

[Q] Liquid Thunderbolt Problem

Hello. First and foremost i am noob, but i fee like i've given this site a fair scrub for my situation and i haven't found anyone in a similar situation. I have an htc thunderbolt, I am not sure about any of the software versions, but i am on verizons network. I recently rooted my phone. The rooting process went fine. I then went on to install the latest version of liquid thunderbolt using rom manager. The install seemed to go fine. IT go to the point where a graphic loaded on the screen. I think its the liquid thunderbolt loading graphic. It's like this vortex-like thing with a bunch of lightening in the middle and then a water drop surrounded by lightening. Either way it's been stuck on this screen for the past 4 hours. What should i do? Is my phone what htey call bricked? If so can i recover from it? Should i just yank out the batter?! PLEASE HELP!
What you are describing is happening to me right now as well. Have you found out any new information. btw My tb has been rooted for 4 months with no troubles. last night i put clockwork mod/rom manager on it went through the process step by step then selected a new rom I think it was from liquid thunder. Now no mater what i do the phone boots up to the htc screen and then to rotating screens just like you described. that's it nothing else. it will not power off without to pulling the battery. i have pulled the sd card. it will not boot into hboot. press down vol. then the power.
thanks,
Jarrad
Hi, this is Jarrad's wife and I have fixed his phone. I was asleep last night when he did this to his phone and he has been up all night working on it. He even went as far as to make me breakfast in bed in order to soften the blow I guess with regard to the information he was about to tell me about his brand new very expensive phone, since he knew it would piss me off. So anyway he had the phone off for about an hour and a half on the charger and stopped messing with it. After he told me his story of what he did to the phone I decided to take a look at it. He told me that when you go into recovery you push and hold the power button and the volume down button at the same time but, this is not true or at least its not what I did to get him to the recovery screen. I was going to turn it on but, forgot he said it had a problem, so after holding down the power button ALONE for about 5 seconds I then pushed the volume down button and held them both together and boom the recovery screen came up. Now it was not a fluke because he then used the wrong recovery option and locked it up again. So, again a pressed the power button ALONE for about 5 seconds and then added the pressing of the volume down control button and boom back to the recovery screen. I hope this works for you the way it worked for me. Good Luck.
Jarrad's Wife Liz

Constant boot loop - can't even get download mode

I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
That almost sounds like some sort of power issue. Have you left it sit turned off until the battery was full?
Yes, I left it overnight and it just keeps flashing the battery screen and then resets. I also have an external charger and used it to charge the battery, so it's not an issue with the battery actually being empty.
Have you been able to get the phone into download mode previously?
Have you have dealt with a boot loop and performed an Odin recovery previously? If not, remember it can take a few tries to get download mode to pop up.
If you can't get Odin to go, you might try flashing with Kies.
I am wondering if your phone met with some kind of disaster when you weren't around (trauma or liquid).
anyone747 said:
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
Click to expand...
Click to collapse
This sounds almost exactly like the problem I had with my Sidekick. In my case, it turned out to be a bad battery and a loose ribbon cable on the motherboard. I'd check those two things.
This happened to me as well, and the three-button method to get into download mode wasn't working. For some odd reason, for me to get into download mode all I have to do is hold down the power button + track pad, and it goes right into download mode... Maybe slightly different model?
Try that - power button + trackpad
Bootloops.
Not a guaranteed fix by any means but for troubleshooting purposes you may want to consider making a USB JIG. It will most definitely help you figure out just how serious the problem is and if it IS software related with a way to get it working again you will need the JIG anyway so its worth a shot. If nothing else you learn a new skill and you're the proud owner of an incredibly useful tool that you can say you made yourself. good luck!
I know this post is kind of old, but it just happened to me last week (same circumstance, a rooted phone, but stock). I ended up just pulling the battery out and pressing the power button a couple times to hopefully drian it and letting it sit for 15 minutes, and then I put the battery back in and it worked again. I now have another rom flashed on it, I hate stock.
I know this forum is ancient, but I'm working on an E-Bay phone with this exact issue. I found the following thread the most useful and informative on the problem:
http://forum.xda-developers.com/showthread.php?t=1996709
Hopefully this helps other.
what i did was hold the power volume and button between the menu n back with the left hand YES HOLD IT UNTILL THE PIT IS UPLOADED. then u can let go then slide in the vattery with the right.while checking off the flash bootloarders on the heimdall with it fixing my phone XD
I had this happen, I dissassembled the phone, and used an alcohol pad to clean the power button area, and manipulated the button a lot, let it dry, reassembled...it still bootlooped.
BELOW IS RISKY BUT WORKED FOR ME
So while the back cover was off (exposing the cicuit board but everything still connected) I inserted the battery and watched it boot loop...during this, I used a flathead screw driver to "short" the power button pins...this let it boot fully, and it has been fine since.
i smacked the phones power button a few times and it worked

phone wont even turn on... WTF

how do all.... nexus s I9023
i have just purchased a some what lovely google nexus s I9023
working fine for an hour or so...
i had a little pop up asking me to update...
i thought OK... sure why not...
having done so phone worked fine for an additional 20 mins...
then phone froze... i took the battery out and started it up again...
it froze on GOOGLE screen...
iv trawled every forum possible since this has happened...
now the PHONE WILL NOT EVEN TURN ON...
the phone is completely stock no mods or addon's to it!
im at the end of my tether.. SOME ONE PLEASE HELP!!!!!!!!
Hold volume up + power after reinserting the battery and putting it on charge. Do you enter bootloader mode? And what happens if you click recovery?
done the hold volume up and press power...
still no joy unresponsive!!
when it does work after 50 attempts of taking the battery out and putting it back in and doing volume and power
it turns on.. scroll to recovery.. it turns off google screen pops on...
then a Green android lying on his back appears with its stomach open showing white blocks and a explanation mark above it!
IM PUZZLED!!!!!
it then resets it self going back to being unresponsive!!
HELP!!!!
Give this a shot.
Also, could it be a power button issue? And that android screen is the splash for stock recovery. You have to press vol. up + power again to get past it, beyond this you can do a factory reset and similar magic. However you likely don't want this, and on the screen where you chose to enter recovery, you'll likely want to use fastboot to unlock the phone (which will wipe all personal data) and then flash a stock ROM again. At this point i would advise lots and lots of reading.
If it's less than a year old, i would be calling samsung though. If it is a new phone i would definitely do this first. Do not unlock unless you have no chance of going through warranty. Will need to know the exact status of the phone for best advice here.

[Q] Bricked phone (in a weird way)

So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.
The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself
If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.

Categories

Resources