Develop Bugs

Possibly Bricked T-Mobile T989

So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.

aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?

charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.

Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!

I still have the phone, I'm gonna try this now. Will update with results.

aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.

Well, I tried both suggestions to no avail. Anyone else have any ideas?

aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.

no cigar with the hold for ten seconds method on the power button.

aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.

Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.

What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk

@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).

Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App

aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk

Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.

Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.

aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.

Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.

more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse

[Q] Galaxy Nexus is bricked. Any ideas?

Hi,
About 1,5 months ago I received my first Android phone, a Galaxy Nexus.
I have unlocked the bootloader, rooted it en eventually installed Clockwork Mod Recovery following guides on this excellent forum! Everything went perfectly and it ran very smoothly in that state for about half a month up until yesterday.
I didn't have any custom roms installed, so I received the notification for the Android 4.0.2 update, it failed because of Clockwork Mod which I later found out. So I set about to manually install it, I downloaded the image from the google site and placed it in my home directory on my Phone, when I then wanted to restart to start in recovery mode it didn't do anything.
I tried getting the battery out and in, sim card out and in, recharging it,...
It does nothing, not even a small vibration signaling the phone is trying to start.
Anyone has any ideas to fix it, or might it be possible to send it back to the shop ( even though it is rooted etc. ?)
Thanks in advance,
Exatto

You need to get the stock images and flash using Odin or the ADB/Fastboot method. After which the phone will return to stock. Then you can root and do what you like. Lots of guieds on here on how to do it. Good luck.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
By the way if you send back a rooted phone they will tell you to take a jump. Rooting voids the warranty.

No response at all? A real brick?
Sent from my Galaxy Nexus using xda premium

Can you get into download mode? If you can you can use any of the methods above to sort it.

I don't think there is a real brick. There are restore images. Extremely hard to brick a nexus...borderline impossible.

Yeah I have never heard of a "real" bricked Nexus.

jd1001 said:
Can you get into download mode? If you can you can use any of the methods above to sort it.
Click to expand...
Click to collapse
No, that's the point. I can't get in any modes. It does't react at all. I think it might be a hardware fault, a friend suggested it might be due to a short circuit battery.
I just followed this guide (http://forum.xda-developers.com/showthread.php?t=1419170) to update, using method 1, having clockwork mod installed. And when I shut it down to restart in recovery mode it suddenly stopped reacting. I have had this before, but then taking the battery in and out fixed everything. Now it doesn't anymore.

Cool, well if removing the battery for a few minutes doesnt sort it then you should be able to return it because the carrier won't be able to tell if it is rooted if they can't turn it on.
When you charge it do you get the charging battery icon when you press the power button?

stkiswr said:
I don't think there is a real brick. There are restore images. Extremely hard to brick a nexus...borderline impossible.
Click to expand...
Click to collapse
But I can't do anything with a restore image when I can't even get it started, let alone be recognized by my computer?
P.S.: Sorry for the late reply, but apparently I still have to wait 5 minutes in between posts.

Can you see the charging battery icon when the phone is off and plugged into the wall?

jd1001 said:
Cool, well if removing the battery for a few minutes doesnt sort it then you should be able to return it because the carrier won't be able to tell if it is rooted if they can't turn it on.
When you charge it do you get the charging battery icon when you press the power button?
Click to expand...
Click to collapse
No, not a charging sign. I hope I can return it, but what if the battery is faulty and they just pop a new one in and then see that it is rooted?
Thanks for the help.

Could well be a dead battery dude, if you have a mate with a Nexus you could try yourself first. I know what you mean about the guy in the shop seeing the unlocked bootloader if he tried a different battery but you may be lucky in that he might not know what it is or you could just grab the phone and leg it ha ha
I hope it gets sorted and be sure to post here what happens. Take it easy.

jd1001 said:
Could well be a dead battery dude, if you have a mate with a Nexus you could try yourself first. I know what you mean about the guy in the shop seeing the unlocked bootloader if he tried a different battery but you may be lucky in that he might not know what it is or you could just grab the phone and leg it ha ha
I hope it gets sorted and be sure to post here what happens. Take it easy.
Click to expand...
Click to collapse
Thanks, hope it get's sorted out. Have to send the phone back, because it was imported, so no chance of legging it
Will post the outcome.

As promised the followup:
Luckily they didn't notice my GN was rooted etc. as today I received a brand new one after I sent the broken one in to an official Samsung repair center
I did test some things before I sent it in though, a friend just bought a new one and we tested if my battery worked in his phone (it didn't) and we tested his working battery in my phone (it didn't work either), so something was definitely very screwed up.
Haven't got any idea of what went wrong eventually as the repair service didn't offer any details, although I am off course glad I got a brand new one.

HELP! VZW Galaxy Nexus completely DEAD!!

I've searched & searched thru XDA without any luck or finding someone with a similar situation.
My GNEX is unlocked, rooted & running AOKP 36.
I hung up the phone after a call...locked it...put it in my pocket...took it out a few minutes later and the phone would not turn on. My battery was over 50%, so i thought i pocket-powered the phone down.
The phone does not boot into any mode. I've tried them all. It is not recognized by my Mac or PC. Here are the things i've done so far: Battery pull. Charge overnight. Removed battery overnight. I bought a new battery & i'm still having the same problem.
Any ideas before i call Verizon and take the loss? I would really like to recover my pictures & videos.
Thanks in advance.

So you have tried to boot into recovery by holding down power and the volume buttons?
If not try this to get to recovery to do a restore.
http://www.youtube.com/watch?v=1SDd1DZUs-M
If you tried this, then you might need to send it in.

Thanks for the reply, but i've tried that already. I'm out of ideas...it's unresponsive.

falotm said:
Thanks for the reply, but i've tried that already. I'm out of ideas...it's unresponsive.
Click to expand...
Click to collapse
Do you have another battery or friend with a gnex? My girls died completely while plugged in over night. I got another battery and it fired up.
Needless to say a clean install was the next step.
Sent from my GT-I9300 using Tapatalk 2

Also hold down power button for awhile. And also try.with a different battery.
...

I bought a new battery from Verizon and tried it, but its still unresponsive. I charged both batteries overnight and nothing happens.
I've held all buttons for several minutes with both batteries, but nothing happens. It wont boot and it won't boot into recovery/bootloader/hard reset menu, etc (android with stomach open LOL)
On a few occasions, when i connect to my PC, it says new hardware detected OMAP 4440 (or something like that) & asks to install drivers. I have the Gnex toolkit, but the program does NOT detect my phone.
Thanks for the replies.

This happened to my fiance's vzw gnex. She was on stock though. Just surfing the web and it turned off. Dead as can be. She took it back and they gave her a new one.
Sent from my Xoom using xda premium

Oh.. Man you lost the bootloader.... If you have warranty go ask for a replacement, it's a pain trying to get the phone back up..
They won't know the phone its unlocked since it won't turn on
Nexus Cm9 + Franco

http://forum.gsmhosting.com/vbb/f63...b-prime-via-usb-cable-freeeeeeeeeeee-1465412/
Try this?
Can't hurt...

My Nexus is from Verizon & the tutorial you linked is for the GSM version. Do you think it matters?
I will still give it a shot. Thanks!

Did you check the pin area where the battery connects? Are the pins in good condition or any small foreign object around them?

If you're careful you can *maybe* odin it back to stock (you've already lost the pics tho).
Look in the dev area for any odin threads.....links to files and stuff are in there.

Jubakuba said:
Try this?
Can't hurt...
Click to expand...
Click to collapse
Thanks for the link. I installed the drivers, phone was detected, ran thru the program, but it failed at the very end. I think its because my phone is i515 & not GSM version.
I've given up hope. Time to get a replacement. I hope it never boots and they don't find out its unlocked & rooted.
I appreciate everyone's input.
Thanks!

a friend mine has a similar problem..
phone died without reason
where i can download the drives that you made mention?
i'll suggest him to try that .bat file

!!!HELP!!! My galaxy nexus is not turning on

I need help my galaxy nexus is not turning on. At first it would start charging when connected to a charger and i was able to turn on my phone(although it would not go past the google screen) but as soon as i disconnected my charger the phone would turn off(even though battery was nearly full).I performed all the wipes but it was of no help.My phone then stopped even charging.Now I cant even get it into recovery mode.
I would apreciate any and all help you can offer

Have you already tried swapping the battery ? Because I once was in a similar situation and changing the battery worked for me.

Zanera said:
Have you already tried swapping the battery ? Because I once was in a similar situation and changing the battery worked for me.
Click to expand...
Click to collapse
the battery is fine i have tried another battery but it didnt work

Not so long ago i tried to be the boss and took another guy's i9000 to install CM10 for him, i nailed it, it installed and it was working perfectly fine, then after several reboots the phone got stuck in a bootloop, then it got stuck in recovery, then it got stuck on the samsung logo, and then it just died.(stopped charging) like having literally a brick in your hand, no response.
If you've done alot of mods to the phone I'm guessing something inside died, get your phone to warranty and say you cant turn it on, they'll just change the motherboard and give you the phone back, if you had any custom roms they will never know.

my phone has no warranty that i could claim so my only option is to somehow fix my gnex

CoDe LaZaRuS said:
my phone has no warranty that i could claim so my only option is to somehow fix my gnex
Click to expand...
Click to collapse
Well as i said, you have probably damaged physically some component on the motherboard, it needs to be changed so you can't fix it, find a Service that fixes android devices and tell em it doesn't boot nor makes a reaction at all, they'll prolly say they will change the motherboard if they have one and thats it.
*Edit*
I remember there was a thing called "jtag" that was able to debrick devices broken in such ways. But Rarely do services have them.

Try fastboot, download mode or omap
Sent from my Galaxy Nexus using XDA Premium HD app

[Q] turns off in a few seconds wont boot or download/recovery NOT button issue!

Okay before i get bashed yes I have searched the threds and yes I found the issue but the solution did not apply to my case, So I do appoligize if this for any reason is not the right place and will be happy with any mod that feels necessary to move my thread
That being said, I came across a t-mobile galaxy S3 t-999 the phone is not rooted, has not had any physical damage and does not have water damage and no update was attempted, the occurrence was random with nothing being done, just shut off and wouldn't turn back on. The battery has been swapped with another S3 to confirm there is no battery issue. The cord has also been swapped.
Now the problem
The phone turns off after a couple seconds and does not boot
My initial thought was to first try a factory reset and if that didn't work to re-flash stock with odin.
Well recovery also turns on for 2 seconds and shuts right off.
Download mode? Yupp you got it same thing
cant reflash with odin because it won't stay in download mode
The only thing i seemed to find thats remotely close to this is a stuck power button and the solution seems to be slamming the phone on the table
However this is NOT the problem in my case
The slam method has been attempted as well as the remvoval of the power button, Plus after each time it shuts off It will NOT turn back on until I remove the battery which is when i get that glorious 2 seconds followed by it turning right off. Thats why i made a new post rather then posting this question there, but if I shouldn't have Im sorry The mod can remove it and i will be happy to repost it there.
If anyone can help me please do, because at this point my face looks like thank you.

majicmazo said:
Okay before i get bashed yes I have searched the threds and yes I found the issue but the solution did not apply to my case, So I do appoligize if this for any reason is not the right place and will be happy with any mod that feels necessary to move my thread
That being said, I came across a t-mobile galaxy S3 t-999 the phone is not rooted, has not had any physical damage and does not have water damage and no update was attempted, the occurrence was random with nothing being done, just shut off and wouldn't turn back on. The battery has been swapped with another S3 to confirm there is no battery issue. The cord has also been swapped.
Now the problem
The phone turns off after a couple seconds and does not boot
My initial thought was to first try a factory reset and if that didn't work to re-flash stock with odin.
Well recovery also turns on for 2 seconds and shuts right off.
Download mode? Yupp you got it same thing
cant reflash with odin because it won't stay in download mode
The only thing i seemed to find thats remotely close to this is a stuck power button and the solution seems to be slamming the phone on the table
However this is NOT the problem in my case
The slam method has been attempted as well as the remvoval of the power button, Plus after each time it shuts off It will NOT turn back on until I remove the battery which is when i get that glorious 2 seconds followed by it turning right off. Thats why i made a new post rather then posting this question there, but if I shouldn't have Im sorry The mod can remove it and i will be happy to repost it there.
If anyone can help me please do, because at this point my face looks like thank you.
Click to expand...
Click to collapse
I think you already know the answer. Seems to me that you've done everything possible. Were you on 4.1.2?

Can you call T-Mo or Samsung and Check Warranty Coverage on the IMEI ? They may ask for Serial Number instead.

Not actually my device
Aerowinder said:
I think you already know the answer. Seems to me that you've done everything possible. Were you on 4.1.2?
Click to expand...
Click to collapse
Perseus71 said:
Can you call T-Mo or Samsung and Check Warranty Coverage on the IMEI ? They may ask for Serial Number instead.
Click to expand...
Click to collapse
Yea thats what i was afraid of, I actually don't know the version it was on prior, to be honest this isn't my device I actually run a small time craigslist base business generally rooting peoples phones and installing roms and fixing softbricks, someone asked me if I can help them and i thought it would be a simple softbrick issue until I actually got a hold of the phone and saw this issue now i think its hardware problem but i thought id ask my good friends at xda before completely giving up
[