Well i Bricked it I cant get into fast boot with the button combos and all see was a red vodaphone splash screen i called tmo and they are sending me a replacement
have you tried taking battery out for a few minutes, then trying again. that way if you can eventually get into fastboot, you can flash the myTouch splash image, just to make sure replacement process goes smooth. let me know if it works
No luck
I sent it back i called and said i downloaded some apps then i noticed my phone wasnt ringing so i looked and now theres this red screen with vodaphone on it
same thing happened to me and i found a post on here somewhere with a solution that worked for me. If you start the sdk fastboot it will wait on device, plug in phone, then put battery in it will then start fastboot on phone and you can re-flash or run recovery
No luck
I tried that fast boot would not come up
So T-Mobile sent you a replacement and I assume you will have to send the old one back. Do you have insurance? and also did T-Mobile say anything about charging you?
Related
please I've been searching for this
i have only access to the blue led mode (trackball+power) how to use it and with which cable
mine is from Israeli mobile operator: Pelephone
pretty sure it's bricked.
Theres a thread about the cable or whatever, look it up. I have no idea how it works though and I don't even know if the method is succesful.
I'm just sure your phone is dead
that Phone is Dead. Abandon all hope. eBay for parts is all you have left to look forward too.
I just did the same thing. The blue light also gave me some hope. Think positively, now you have an excuse to buy a Nexus One.
don't give up... i had only the blue led function a week ago, my phone is alive and kicking now... not my first one tho.... here is what i did:
I performed a SPL flash, the phone rebooted ,it took long time rebooting so i got panicked i pulled out the battery ( wasn't a smart move ).
tried to start the phone.. now i was stuck at the first splash screen.
-pulled out the battery and back again start the phone... stuck at the first splash screen or boot looping endlessly,
-did all possible key combinations to get in fastboot, recovery mode... nothing.
-cried for help, got directed to a post similar to mo my case... worked for me hope it dose for everyone else.
here is what i did (followed):
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-went to sleep
-woke up in the morning, went back to my old duct taped SE phone
-came home in the evening
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
flashed again but this time checked all steps twice before i check them a third time, and flashed the SPL and radio and the rom.
hotweiss said:
i just did the same thing. The blue light also gave me some hope. Think positively, now you have an excuse to buy a nexus one.
Click to expand...
Click to collapse
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.
Need a little help here. The other day I turned on our old D2 BC I need aa replacement phone and its given me hell. First boot it went into the Liberty boot animation and wouldn't stop looping. My girl rebooted into recovery and flashed Liberty again and apparently it was working fine which I did not know. When she did this she didn't tell me so I was under the impression I needed to do what she did. I went to recovery, wiped and flashed Liberty, I believe its 2.0. Now I can't get it to even go into recovery. The only thing that happens is sometimes when I plug it in to a power source it will go straight to a liberty screen and just sit there. Not even an animation. Any ideas? I'm fixing my Ubuntu right now so maybe I can access ADB commands from there. It won't detect on Windows.
Sent from my Nexus S 4G using xda premium
update: I finally got this phone to do something and idk how? I have tried to let it charge for a few days now and I'm thinking that 'somehow'(???) the battery got f'd up because just now when I plugged it in to finally try to connect through ADB, a black screen popped up. at top it Read: Bootloader > next line > D2.37 then at the bottom two lines that read Battery Low, Unable to Program. ....any thoughts? other than a new battery?
you need to get the battery charged with another phone or an external charger (stay away from homemade chargers as they can mess up stuff). What happened is the battery got too low to either start or finish sbf'ing so it went to bootloader and the phone won't charge without software so until you charge or buy a charged battery you are stuck. It's very fixable but you are stuck.
Hey, this guy at the mall runs a cell phone kiosk, I was talking to him and he has a Sidekick 4G that someone tried to root and messed it up. He is selling it for 50 bucks, and I thought about buying it and had my laptop in the car, but I wasn't able to fix it on the spot. It will go into download mode, Odin will recognize it, then the screen will go blank again..... basically the screen will not stay in any one place, it keeps flashing the empty battery icon, or maybe the Sidekick 4G logo. It also can go into recovery but just for s second, and when you take the battery out and put it back in, it doesn't stay off, it kinda flashes the battery icon. Anyone know if this is a hard-brick?
Edit: just found a thread someone posted with the exact same issue. Sorry for the repost!
Hey guys...
Kinda ultimate noob here, so I'll start from the beginning because I don't know what information could be pertinent. I don't really know much lingo at all, but I have a completely stock, unrooted HTC Inspire 4G from AT&T that my cousin gave me a few months ago. On and off since then, I've had a few random restarts and crashes, no big deal, always came back up. The other day,about a week ago, the headphone icon started blinking and my sound stopped working, so I restarted the phone and it got stuck on the ATT boot screen, so I took out the battery, let it sit, and when I put it back together, everything was fine. Last night, I was in a meeting and my phone battery was at 2%, so I turned it off so avoid it dying. I got home and plugged it in, and when I went to turn it on, it would not load past the ATT boot screen. I let it sit overnight, and a couple hours ago I tried a factory reset, and tried to boot up again, and it got stuck in what I believe is called a boot cycle, where it would go from the HTC startup screen to the ATT screen, go black, then repeat over and over. I did some research, and tried to use an RUU to set everything back to complete stock, but both of the ones I tried gave me the "Please get the correct RUU and try again" error. I have the 1.03.2011 RUU up right now, and it says that my image version is 3.20.502.52, and gives me that same error. I don't know if I completely effed it up or what, so any possible help would be greatly appreciated. I've been looking through guides and trying things for over 12 hours, but I can't get anything to work, so it would be best to start from the beginning. I tried to get everything I know about the problem in there, but if more information is needed, just let me know and I'll do my best to get it for you. I've heard great things about XDA and did most of my research here, so I'm hoping you can work some of your magic on my phone