Database Users

HTC incredible endless boot loop

i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?

hard reset may work
Sent from my Incredible using XDA App

i tried hard resetting it. this did not solve the problem.

ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App

jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.

Are you root?
When and how did this start happening?

jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.

JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App

JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?

RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.

theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App

Try the RUU that was posted.

jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen

theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App

jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html

theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App

jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.

theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App

Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.

I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure

[Q] myTouch 3G vs LG Optimus-T (T-Moble Offered Trade-In)

T-Mobile support confirmed that there have been alot of complaints regarding sluggish phones after updating to OS 2.2.1. They said that they are offering to exchange myTouch 3G phones with the LG Optimus-T phone due to the problems caused by the update. I checked the specs on each phone and they are quite similar; the LG's processor is a bit faster. Has anyone tried the LG Optimus-T? I'm gonna go to the T-Mobile store to test it out, but I figured I'd check out all your opinions before I make a decision.
Thanks,
-Adam

optimus is way faster. it feels better in the hand too. and it can run lwp smoothly without lags

Think I'm going to have to look into this.

g1user101 said:
optimus is way faster. it feels better in the hand too. and it can run lwp smoothly without lags
Click to expand...
Click to collapse
I tried out the Optimus-T at the T-Mobile store; the extra 80Mhz of processor really makes a drastic difference! I'm definitely gonna swap the myTouch for an Optimus-T. The one thing that I wasn't able to test out at the store was the built-in microphone. I'm a musician and I use the mic alot to record guitar riffs if I think I'm going to forget them. I tried out a couple different smart phones before I went with the myTouch and the mics on some of the other phones were terrible. Anyone have any comments on the quality of the Optimus-T's mic? When it comes down to it, I really don't have any option but to swap phones; 2.2 drools on the myTouch.
-Adam

adam79 said:
2.2 drools on the myTouch.
Click to expand...
Click to collapse
That's fixable, but I would definitely be OK with a new phone.

DonJuan692006 said:
That's fixable, but I would definitely be OK with a new phone.
Click to expand...
Click to collapse
How is it fixable? I've tried multiple hard resets. Running it with no applications or widgets running, no GPS, no anything and it still is sloooooow. What do you suggest because I'd rather keep the myTouch. Please advise.
Thanks,
-Adam

Easy day. Download this file and rename it sappimg.zip (not sappimg.zip.zip)(To make sure go to Start->Control Panel->Folder Options->View Tab-> Uncheck "Hide known file extensions"). Then download this file and rename it to update.zip. Next, put them both on the root of your SD card. Boot into hboot (volume down+power) and the phone will pickup the SAPPIMG on it's own and do a file check. When prompted, hit the trackball to continue, it'll run the updates, then hit the trackball again to reboot. When you get to the activation screen, turn the phone off. Power on holding (home+power) which will get you to a screen showing a triangle with an exclamation point and a phone. Hit (home+power) again to bring up the recovery menu. Select the "wipe data/factory reset" option, then select "apply update.zip from SD card". Let it do it's thing and sit until your back at the activation screen. I'm sure you can figure it out from there.

DonJuan692006 said:
Easy day. Download this file and rename it sappimg.zip (not sappimg.zip.zip)(To make sure go to Start->Control Panel->Folder Options->View Tab-> Uncheck "Hide known file extensions"). Then download this file and rename it to update.zip. Next...
Click to expand...
Click to collapse
What does this do to the phone? Will it void the warranty?

No, everything is stock. Your basically downgrading back to Android 1.6 and then reapplying the update, but doing it properly. The update should have included a script that would clean up the phones cache, but it apparently doesn't which is the root of the sluggish phone. I had the same issue until doing what I told you to do. Of course, I've been rooting/ROMing/theming my phone for 6 months, so I kind of figured that was the problem. Also to note, doing a factory reset after applying the update just doesn't seem to be cutting it. With my method, you'll come to the update as clean as possible.

DonJuan692006 said:
No, everything is stock. Your basically downgrading back to Android 1.6 and then reapplying the update, but doing it properly. The update should have included a script that would clean up the phones cache, but it apparently doesn't which is the root of the sluggish phone. I had the same issue until doing what I told you to do. Of course, I've been rooting/ROMing/theming my phone for 6 months, so I kind of figured that was the problem. Also to note, doing a factory reset after applying the update just doesn't seem to be cutting it. With my method, you'll come to the update as clean as possible.
Click to expand...
Click to collapse
Oh yeah, one more thing.. Can I do this on a Mac, or do you need a Windows computer?
Thanks,
-Adam

A Mac will be fine.
Sent from my T-Mobile myTouch 3G using Tapatalk

if I re-root and use clockworkmod recovery, will the cache cleaner on there be suitable for this?
Sent from my T-Mobile myTouch 3G using XDA App

No, you need a fresh install, not just to clear out cache.

[Q] Mytouch 1.2 trade in?
So I've been hearing that tmobile is offering a phone trade in for devices bricked by the ota update. It seems that the replacement for the mytouch 1.2 is the optimus t. The fender edition receives a vibrant.Is this the same as the optimus GT540? And is it worth manually bricking my phone to get it? And since the fender is switched for a much better phone, would it be possible to get that instead of the optimus? Please let me know.
Edit: Yes I did read the other thread about this, but that one moved off topic.
Sent from my T-Mobile myTouch 3G using XDA App

The Optimus T is also the Optimus One P500. You won't be able to get the Vibrant, even if you offer to pay the difference, I tried. Maybe if your persistant enough and get a nice CS Rep you may be able to weasle one out. Either way, your getting a better phone.
Sent from my T-Mobile myTouch 3G using Tapatalk

So you're saying I could pretend it was a fender to get the vibrant? Because I know the ship you the phone first, before requiring you to send it back. And will they let me trade in for lagginess, or do I manually have to flash the wrong update?
Sent from my T-Mobile myTouch 3G using XDA App

Vibrant is out unless you find a CS that's just really nice or you annoy them to the point they'll do anything to shut you up. Their going to base the swap out off of what device your account has on it. So if your account says you have a regular 1.2 then your getting the Optimus. Unless, like I said, pigs start flying and cows start pooping fossil fuel. From what I've read they're doing it for lag as well but only after you go through the facade of them having you do a factory reset from recovery and waiting a day or so.
Sent from my T-Mobile myTouch 3G using Tapatalk

Note that I can manipulate these people well. I bricked two mytouches trying to get root(before androot existed), and ive gotten mine replaced every time. I'll try and keep you posted.
Sent from my T-Mobile myTouch 3G using XDA App

The exact same thing happened to me but in my case, i bricked three phones and this is my forth one that i am using now. Pissed off one of the reps, he said i cleaned out their stock. Hhaha
Sent from my GBRider_v4.0FR using XDA App

Does this apply to the original my touch 3g? If so I would like something different than this phone. I am happy with it if not but if I can get a new phone because of the OTA update I am all for it.

Is there ever going to be a version of recovery that works 100%?

First off, my tone is from frustration. I've experienced this snafu now on both versions of clockwork recovery. The phone won't completely shut off while charging. If I power the phone down unplugged, then plug it in while off, recovery boots up. If it's plugged in while powering down, recovery boots up after a few seconds.
I suppose I could flash cwm when I need it then flash back to stock recovery. I guess that's what I'm going to have to do until it might get fixed. I thought going to version 3 would fix the bug but apparently not. I've tried to flash a new recovery with rom manager but an error always happens.
I flashed version 2 the way the root guide said and flashed 3 with fastboot. I forgot if thats the way it was done with 2 or what. I am starting to wonder if I'm doing something wrong because I don't see anyone else complaining about this.

herbthehammer said:
First off, my tone is from frustration. I've experienced this snafu now on both versions of clockwork recovery. The phone won't completely shut off while charging. If I power the phone down unplugged, then plug it in while off, recovery boots up. If it's plugged in while powering down, recovery boots up after a few seconds.
I suppose I could flash cwm when I need it then flash back to stock recovery. I guess that's what I'm going to have to do until it might get fixed. I thought going to version 3 would fix the bug but apparently not. I've tried to flash a new recovery with rom manager but an error always happens.
I flashed version 2 the way the root guide said and flashed 3 with fastboot. I forgot if thats the way it was done with 2 or what. I am starting to wonder if I'm doing something wrong because I don't see anyone else complaining about this.
Click to expand...
Click to collapse
Are you looking to bump charge? You've asked this issue a multitude of times and each time its been responded to. (at least in my mind, might be others too) and it is a known issue with CWM recovery and from what I've read Koush isn't really looking at fixing it.

I can't speak for what'll happen in the future but it's not you. That is a known issue with the recoveries we currently have. I believe most of the complaints are in the how to root thread.
^ Shift Faced

I am not talented enough to "fix" the problem but it is discouraging to hear that it isn't deemed important. Maybe I was spoiled with my moment, evo, and epic. It seems as if the shift has the smallest developer base so far. When the evo came out, the devs were all over the place.
Come to think of it, I don't think I've even seen anyone besides myself that has a shift.

You don't think not being able to charge while turned off isn't really a minor problem? And you're using the Moment as a model of progress??
^ Shift Faced

That's what I started on

Yeah, me too. And every ROM was basically themed stock. No CM7, no MIUi, no cool ish like the New Sense. Jeez, they just finally got 2.2 working on it! I'd be using CM7 right now if the headphone jack worked. That ish there excites me.
^ Shift Faced

herbthehammer said:
I am not talented enough to "fix" the problem but it is discouraging to hear that it isn't deemed important. Maybe I was spoiled with my moment, evo, and epic. It seems as if the shift has the smallest developer base so far. When the evo came out, the devs were all over the place.
Come to think of it, I don't think I've even seen anyone besides myself that has a shift.
Click to expand...
Click to collapse
First..the facts show the shift as a far more superior platform to any samsung..probably even the tab..let alone its not that your problem isn't important...it just isn't to anyone but you so there is some importance..with everyone complaining about all these issues and the limited dev support maybe we should figure out whether we want a rom..a kernel..a recovery fixed or a genie in the bottle..patience is the virtue here because everyone keeps flaming about support for this and that..maybe the devs have a life..maybe they died..maybe they think its funny to see people whine and complain like they owe us some kind of development
Sent from my PG06100 using XDA App

google gave everyone a evo that went to the I/O when it comes to the devs the all had a free one from jump i too want cyanogenmod on my shift for the reason i love cyanogenmod BUT its not supported by him oficially

everydaysince87 said:
google gave everyone a evo that went to the I/O when it comes to the devs the all had a free one from jump i too want cyanogenmod on my shift for the reason i love cyanogenmod BUT its not supported by him oficially
Click to expand...
Click to collapse
Toastcfh has a CM7 where everything works but sending MMS and the headphone output. And he's been working on it everyday. And Cyanogen responded to someone asking him on Twitter if there'd be CM support for the Shift and he said "Yes, soon". I think it was on 2/17.
I have a feeling my Shift is gonna be very happy soon
^ Shift Faced

Soon isn't official yet tho I may look into a way to donate to toastcfh then
jesusice said:
Toastcfh has a CM7 where everything works but sending MMS and the headphone output. And he's been working on it everyday. And Cyanogen responded to someone asking him on Twitter if there'd be CM support for the Shift and he said "Yes, soon". I think it was on 2/17.
I have a feeling my Shift is gonna be very happy soon
^ Shift Faced
Click to expand...
Click to collapse
Sent from my PG06100 using XDA Premium App

My clockwork recovery hasn't gaven me any problems

Rob_ec said:
My clockwork recovery hasn't gaven me any problems
Click to expand...
Click to collapse
+1 and I use cwm 3
Sent from my HTC Knight using XDA App

Rob_ec said:
My clockwork recovery hasn't gaven me any problems
Click to expand...
Click to collapse
How did you install yours? Maybe your hardware version of the phone is different than mine? I bought my phone the day after it went on sale. Hardware version 4

This is the tutorial I had to follow to install my recovery..at the bottom of the page someone rewrote the 2nd command to enter and it worked for me..but I had to follow this tutorial & not the one stickied..let me know if this works..
http://forum.xda-developers.com/showthread.php?t=908267&page=6
Sent from my PG06100 using XDA App

herbthehammer said:
How did you install yours? Maybe your hardware version of the phone is different than mine? I bought my phone the day after it went on sale. Hardware version 4
Click to expand...
Click to collapse
They didn't read your post. The boot to recovery from power off while charging is univeral. Its just that very few people care very much.

Jeezimus said:
They didn't read your post. The boot to recovery from power off while charging is univeral. Its just that very few people care very much.
Click to expand...
Click to collapse
Lol +1 to not caring much
Sent from my PG06100 using XDA App

You actually turn your phone off?

there is at least now an official release of clockwordmod:
http://forum.xda-developers.com/showthread.php?t=979778

grandebob said:
You actually turn your phone off?
Click to expand...
Click to collapse
I turn it off and on no problem..I haven't tried while its plugged in..why would I even do that unless I want to boot to recovery which is what people complain about so actually its a benefit to me..
Sent from my PG06100 using XDA App

[Q] In Desperate Need of Help! Touchscreen is Non-Responsive After Update.

Greetings to all. Last week while powering up my phone, I accidentally entered into the Bootloader screen. It found the last T-mobile update that I had done (I forgot to remove it from the SD) and I hit yes to update (at the time thinking it was a new update). After it finished with the update, my phone booted back up to the familiar "zebras" T-mobile stock lock screen. At this point, my touchscreen was, and still is, completely non-responsive.
With the very basic knowledge that I have with Androids, I searched for and downloaded many different PD15IMG.zip files (always re-named PD15IMG properly), dropped them onto my SD (one by one of course), booted into the Bootloader screen and applied the update. In every instance, when my phone finished updating and loaded the familiar zebras, same problem. I even tried a Factory Restore (several times) with the same result. Also, USB Debugging was never turned on on the phone.
Now, here is where it gets interesting: when I was looking closer at my lock-screen, I noticed that the date is set to: Jan. 6, 1980!? I am at the "end of my rope" here and am only repeating the same steps at this point as if something magical is going to happen....
Any and all help would be most appreciated!
Brian

Are you S-On of S-Off?
Sent from my HTC Glacier using XDA App

I am not sure what that means, my knowledge with these things is elementary at best. I was running a stock T-mobile rom if that answers your question.

noah1127 said:
I am not sure what that means, my knowledge with these things is elementary at best. I was running a stock T-mobile rom if that answers your question.
Click to expand...
Click to collapse
when you boot into the bootloader... at the top
does it say Glacier PVT S-On or S-Off?

Ok, just looked it up; I believe I am S-off, because I have had custom roms installed before.

....actually, it says: Glacier PVT S-On

noah1127 said:
Ok, just looked it up; I believe I am S-off, because I have had custom roms installed before.
Click to expand...
Click to collapse
you have a custom recovery installed?

I had at one point installed Clockworkmod if that is what you are asking, but to be honest, realized that it was beyond my understanding and never used it. I did never uninstall it however....I hope I am answering your questions correctly, sorry.

noah1127 said:
I had at one point installed Clockworkmod if that is what you are asking, but to be honest, realized that it was beyond my understanding and never used it. I did never uninstall it however....I hope I am answering your questions correctly, sorry.
Click to expand...
Click to collapse
You did have it installed, but you flashed other PD15IMGs right? That flash would replace the recovery to stock recovery, so I'm guessing you don't have a custom recovery.

Ok, right, that makes sense. So I would say everything is stock again.

...any advice at all?

If you are not rooted and can't get it to boot then your options are few. Warranty exchange a possibility?
Sent from my HTC Glacier using xda premium

It does boot, everything looks fine (except for the date of 1980!?), I can see the wallpaper and the "lock/unlock-bar", battery status, etc. I just can not swipe the "lock-bar" down to unlock the phone, the touchscreen is completely non-responsive.

noah1127 said:
It does boot, everything looks fine (except for the date of 1980!?), I can see the wallpaper and the "lock/unlock-bar", battery status, etc. I just can not swipe the "lock-bar" down to unlock the phone, the touchscreen is completely non-responsive.
Click to expand...
Click to collapse
Does it respond to any touches on the screen or does it just timeout and turn the screen off?
Sent from my HTC Glacier using xda premium

No response what-so-ever, it just times out and goes blank.
My gut tells me it has something to do with the date being 30 years off (1980) ...but I am new to all this!
BTW, there has been no physical damage, I have not dropped it or anything like that.
I really do appreciate your time!

noah1127 said:
Ok, right, that makes sense. So I would say everything is stock again.
Click to expand...
Click to collapse
That would be correct! Still unsure about the touchscreen unresponsiveness though...sorry.

No problem, I appreciate your time!
What about the 1980 date, have you ever heard of anything like that before?

noah1127 said:
No problem, I appreciate your time!
What about the 1980 date, have you ever heard of anything like that before?
Click to expand...
Click to collapse
I wouldn't get too hung up on it. Could just be a messed up setting... Unless you believe someone from the past is trying to communicate with you.
Sent from my HTC Glacier using xda premium

..."Unless you believe someone from the past is trying to communicate with you." I wish!
No, I just thought that like on a computer, if the date is far in the past it can mess up the "communications" within the device. The date was correct before and then after the "update" is went back to 1980, was just wondering if that is "confusing" the phone...I know it worked on me!!

eqjunkie829 said:
I wouldn't get too hung up on it. Could just be a messed up setting... Unless you believe someone from the past is trying to communicate with you.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
lmao, obviously HE'S from the past, where the MT4G doesn't exist! reason why his touchscreen won't work
well... i would wait... sometimes it might magically work again O_O

[Q] Bricked phone?

I was running Core Droid 1.2. I WASNT flashing a rom, I WASNT flashing anything or messing with anything. I was just watching a youtube video. The phone froze. I didnt want to remove the battery as i thought it was bad. I tried finding a way to emergency shutdown my phone like volume up and down and power or something but it seems there wasnt one. I took out the battery and put it back in. I turned the phone on but all that came up was a black screen. I took it out and put it back in again. It won't turn on period.
Any ideas?

tradejak66 said:
I was running Core Droid 1.2. I WASNT flashing a rom, I WASNT flashing anything or messing with anything. I was just watching a youtube video. The phone froze. I didnt want to remove the battery as i thought it was bad. I tried finding a way to emergency shutdown my phone like volume up and down and power or something but it seems there wasnt one. I took out the battery and put it back in. I turned the phone on but all that came up was a black screen. I took it out and put it back in again. It won't turn on period.
Any ideas?
Click to expand...
Click to collapse
Read my sticky in the general section
Sent from my Infernalized Glacier!
-Team Inferno

saranhai said:
Read my sticky in the general section
Sent from my Infernalized Glacier!
-Team Inferno
Click to expand...
Click to collapse
Yeah I did. And its funny cause when i read it 2 days ago I got scared that my bad eMMC chip would die any second... now it looks like it just did.
I just posted this anyways cause I was desperate >.> but t-mobile says my warranty hasnt run out yet. And since it cant boot up whatsoever they cant tell its rooted. SO I get a free replacement
I was kind of hoping they'd claim the phone was defective and give me a sensation or something

This doesn't look like eMMC failure at all.

Jack_R1 said:
This doesn't look like eMMC failure at all.
Click to expand...
Click to collapse
what would you think it is then? My new phone comes today and i have to ship this one off to tmobile, so its too late. But I still want to know

Most likely - corrupted SBL. It doesn't necessarily mean eMMC failure - though it could be. Pulling the battery out while there is some eMMC activity could have caused it.

sorry im nooby. whats SBL and can it be fixed easily?

SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.

Jack_R1 said:
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Click to expand...
Click to collapse
I don't think that was it. He obviously could get to HBOOT by flashing PD15IMG.zip and getting failed-pu error. But I may be wrong, feel free to correct.

To flash PD15IMG, he needs HBOOT running - it's the HBOOT that flashes these files, it's the first screen on your phone that you can actually see and interact with. If HBOOT is gone, you don't boot - because you have nothing to boot to. Or actually, the phone boots to some state, but you don't know it - because you can't interact with it anymore.

invasion2 said:
I don't think that was it. He obviously could get to HBOOT by flashing PD15IMG.zip and getting failed-pu error. But I may be wrong, feel free to correct.
Click to expand...
Click to collapse
Nope. I cant flash PD15 if i cant get to HBOOT. the phone doesnt turn on at all, just a backlight for one second. Which looks like its attempting to turn on but failing.

Jack_R1 said:
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Click to expand...
Click to collapse
hmm. you'd think these phones would have some sort of fail-safe feature when it comes to pulling the battery, cause people obviously do it alot.

tradejak66 said:
Nope. I cant flash PD15 if i cant get to HBOOT. the phone doesnt turn on at all, just a backlight for one second. Which looks like its attempting to turn on but failing.
Click to expand...
Click to collapse
Ahhh my bad, sorry. Didn't read Definitely seems like you are bricked! >.<