Database Info

New phone wont turn on. Fix or return?

I bought a brand new Blaze a few days ago while vacationing in Florida. I neglected to check it out while i was there and Im home now (in Bermuda) checking it out for the first time and the phone wont boot! I popped the battery in and nothing happens when i try to power it on. So thinking the battery was dead, i plugged it in and now it just vibrates. It vibrates continuously every 2 seconds. buzzz...buzzz...buzzz...buzzz. The screen never powers on at all. Im guessing i have a bricked phone out of the box? Or is there a simple fix for this that i havent been able to find?
If i do return this, can it be returned to any authorized T-Mobile dealer? I wont be going back to Florida but i know someone who is visiting Boston next week.
Thanks

Jaa-Yoo said:
I bought a brand new Blaze a few days ago while vacationing in Florida. I neglected to check it out while i was there and Im home now (in Bermuda) checking it out for the first time and the phone wont boot! I popped the battery in and nothing happens when i try to power it on. So thinking the battery was dead, i plugged it in and now it just vibrates. It vibrates continuously every 2 seconds. buzzz...buzzz...buzzz...buzzz. The screen never powers on at all. Im guessing i have a bricked phone out of the box? Or is there a simple fix for this that i havent been able to find?
If i do return this, can it be returned to any authorized T-Mobile dealer? I wont be going back to Florida but i know someone who is visiting Boston next week.
Thanks
Click to expand...
Click to collapse
Try tmobile customer support they have gotten a lot better the last few years
I'm not a Dev, I just flash alot.

I'd return it personally. Same goes for any gadgets that fail before the initial return policy expires. Things happen, but I never liked that feeling of doubt that happens later, when something else goes wrong with the device. You'll be thinking, "I KNEW I should have exchanged this!"

Jaa-Yoo said:
I bought a brand new Blaze a few days ago while vacationing in Florida. I neglected to check it out while i was there and Im home now (in Bermuda) checking it out for the first time and the phone wont boot! I popped the battery in and nothing happens when i try to power it on. So thinking the battery was dead, i plugged it in and now it just vibrates. It vibrates continuously every 2 seconds. buzzz...buzzz...buzzz...buzzz. The screen never powers on at all. Im guessing i have a bricked phone out of the box? Or is there a simple fix for this that i havent been able to find?
If i do return this, can it be returned to any authorized T-Mobile dealer? I wont be going back to Florida but i know someone who is visiting Boston next week.
Thanks
Click to expand...
Click to collapse
Have you charged it fully? This is the default behavior if there isn't enough power to boot. Let it charge for 24 hours... then try again.

It vibrates like that when the device is plugged in and there's no battery detected or installed. My guess is the battery is defective or the orientation of the battery in the phone is incorrect (hey, it happens sometimes), or there is an obstruction preventing the pins in the phone from making contact with the battery or the pins don't properly align with the battery (defect with the phone or battery).
But I would agree that you should return it for another - especially if the pins aren't fully aligned with the battery when it's inserted.

Thanks guys, you were right, the battery was the culprit, it was dead flat.
I popped it into my universal charger, gave it a full charge and it was good to go, the phone booted and is working normally.
Thanks again.

[Q] Help - dead N8010

Hi All,
I'm hoping somebody can help me here. I have an N8010 which is stuck on a constant reboot cycle.
It displays the "Samsung Galaxy Note 10.1" Logo and then blanks the screen. After a couple of seconds, then it redisplays the same logo.
It first did this on Thursday after being in use for about 30 Mins. The Tablet just hung and rebooted. It got stuck in this loop until somehow I managed to turn it off. After about an hour, it started up and worked OK, but I didn't try prolonged use.
This morning, it did the same thing, hung (Editing contacts) and rebooted. This time it started back up, but almost immediately id hung again and now it's stuck in the Reboot/Logo loop. I cannot even turn it off - It's just displaying the Logo.
I can press and hold Power/Vol Down to invoke Odin. Selecting Restart Phone just returns me to the loop.
Earlier I could press and hold Power /Vol up to invoke the Reboot/Reset screen and I have done a factory reset.
Oddly - Now I can no longer use the Power/Vol up combination to get to the reboot/reset screen, but I have managed to use it to turn of the tablet.
Occasionally there are a number of corrupted pixels flashing on the screen.
I am assuming that there is some sort of dry joint/bad connection that is warming up and causing these issues.
This Note has not been flashed with any software at all - It's stock.
Anyone seen anything like this before or should I just return it
Thanks in Advance
Steve

Return it, don't try to flash anything to it.
Sent from my GT-N8010 using Tapatalk HD

If it is under warranty and you are on your stock market rom then give it to a service center

samir_a said:
If it is under warranty and you are on your stock market rom then give it to a service center
Click to expand...
Click to collapse
Did you try to root it or flash another rom? If not just send it to service.

gpgalanis said:
Did you try to root it or flash another rom? If not just send it to service.
Click to expand...
Click to collapse
Thanks guys - No didn't try to root or flash at all. I'm waiting for the JB update to see if I need to.
It's working perfectly right now, While it was rebooting endlessly, I managed to get the battery display to appear - It seemed to be completely discharged. (85% a few minutes before) . So I connected it to the charger.
After 35 mins, the charge was showing 92% and it booted and has been running happily ever since.
Exactly what it did on Thursday - showed empty and then charged after about 30 mins.
I think I'll take it back and see if they'll swap it for one with the 3G. Hope that they don't have to send it away, it's gonna be my Christmas present
Steve

Good luck! Since you didn't flash a custom rom or anything, there's no reason you should have to deal with that stress.. Just return it and demand an exchange or something. If you got it at a store, they'd probably be happy to exchange it. If you got it online, it'd be a little harder and more delayed, but still doable! Good luck again!

Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....

ultramag69 said:
Unfortunately there are lemons in all manufactured goods, looks like you got 1... I hope it doesnt sour your attitude towards a really good product, as long as it works....
Click to expand...
Click to collapse
I thought that I should let you guys know the outcome.
I was not soured at all, I took it back to the store, and was told that they would have to return it
So while I was there I bought a N8000
Jelly Beaned it, rooted etc This thing rocks

No response.

Phone was working fine this morning, screen flashed and phone vibrated, I went to unlock it, nothing. Tried to power it on, thinking it had powered off, nothing. No response at all. I had just plugged in a MicroUSB to USB adapter with a USB flash drive plugged in when this happened.
No boot to recovery, no boot to download mode. No charging light when plugged into wall or laptop.
Any help?

If I return it to my local store, and ask for a replacement exchange, what are the chances of them finding out it's rooted? If I can't turn it on, can they?

Caustyk said:
If I return it to my local store, and ask for a replacement exchange, what are the chances of them finding out it's rooted? If I can't turn it on, can they?
Click to expand...
Click to collapse
Verizon doesnt give replacement phones in store unless its under 14 days old. You just need to call them and they will next day air a replacement. As for the phone when you plug it in does it show a led light or the battery icon on the screen? Also was the battery extremely low when it went off?

Wasn't aware of that, thanks. This was my first phone to have an issue...
When I plug it in, there is no light. No reaction of any kind. The battery was ~90%, I had taken it off the charger and made a call or two.
P.S. Any chance a USB Jig would be able to get my phone into download mode? Once there, I would have no problem getting to stock and starting from scratch...

Caustyk said:
Wasn't aware of that, thanks. This was my first phone to have an issue...
When I plug it in, there is no light. No reaction of any kind. The battery was ~90%, I had taken it off the charger and made a call or two.
P.S. Any chance a USB Jig would be able to get my phone into download mode? Once there, I would have no problem getting to stock and starting from scratch...
Click to expand...
Click to collapse
What recovery do you use?
Sent from my SCH-I535 using Tapatalk 2

TWRP, but I can't get it to boot at all.

does it vibrate?
Last resort would be something called heimdall or something like that. I don't know if it will work but supposedly on older samsung phones it is the ultimate last resort even when odin doesn't work. Just google it and try to find some info.

Doesn't vibrate. Isn't heimdall for Mac?

Just downloaded and ran Heimdall, no recognition of my phone with stock cord or after market cord.
Edit: I guess at this point I just want to make know if there is any way for Verizon to find out my phone is rooted, and the exact process of getting it replaced?

Heimdall wont do anything for you since it connects to the phone the same way odin does, and you still have to be in download mode. If it doesnt vibrate or react in anyway when pluggin it in then its safe to say its dead. You should be safe switching it out as a dead phone with verizon too. You should call them early in the day so the phone will get sent out that day too, if they dont offer to next day air it then tell them you need the phone asap and they will free of charge (you may just need to tell them you need it and you lost all ur data, ect and they will help you out). Sometimes they will say you will receive it in 2-3 days free of charge, which is unacceptable.

Alright, I'm guessing I just ship mine back to them in the same box or...?
Thanks for the help, too.

Caustyk said:
Alright, I'm guessing I just ship mine back to them in the same box or...?
Thanks for the help, too.
Click to expand...
Click to collapse
Ya you will get a replacement phone with no back cover, you keep your sim card and back cover. There will be a shipping label for the return shipping which you can either drop off at a fedex or usps location. You have 5 days to return the bad phone from the day you get the replacement. They will explain everything to you on the phone.

Alright, so I'm really nervous about making this call. If I send it in, and they get it working enough to run their tests, and it comes up rooted, I don't have the money to pay for the phone at full retail price. Does anyone have any suggestions as to what I should do? I know a lot of people brick their phones by misfollowing instructions, or flashing things they shouldn't be, but I did neither of which. The phone just shut down, and won't turn back on.
Sending the phone to a 3rd party service is also not possible for me, at this time.
Edit: Just found this thread (http://forum.xda-developers.com/showthread.php?t=1981582), which sounds almost exactly like what happened to mine. So I guess my chances should be good of getting a replacement, without any troubles. I tried to find other threads involving people who sent in bricked phone to find their experiences, but I didn't know quite what to search for..

[Q] Dead S3?

Hi all,
I went to take my break at work, phone in hand, working, put it in my pocket. Signed out, proceeded to the elevators to go downstairs, take it back out and no response. Okay. Fine. Hold power...nothing. Pop the battery out for 30ish seconds, back in, case on...power...still nothing. Get to my car thinking maybe it died even though it had 50% left to the battery. Plug it into my car mount and the LED doesn't light up. I work minutes away from a Verizon store so I decide to stop by. I explain to the rep what was going on, he plugs it in and nothing. He tries a different battery and nothing. We both tried vol up + power + home and nothing.
I have not rooted my phone, and the only thing I did recently was factory reset it over the weekend just to give it a "fresh start."
After I got home not too long ago, plugged the phone in using the cable I usually take with me (just happened to leave it home today of course) and no response from the phone. However, if I remove the back cover and take the battery out the LED light DOES come on if I plug the phone in again for several minutes and then it goes out.
From what I've read here and elsewhere there was something about a bad EMMC chip that caused phones to just suddenly die, could this possibly be it?
Thanks.

Sounds like a hard brick to me. Try this
http://m.youtube.com/watch?v=dU5H8NJ7vTM&desktop_uri=/watch%=dU5H8NJ7vTM
Sent from my SCH-I535 using Tapatalk 4

If ur not rooted wat so ever then jst get a warranty replacement

If you don't have the ability to software flash it or if you honestly think its a hardware issue you could try getting a warranty replacement through your carrier as suggested or if you'd like to keep your phone and not get a refurb and are willing to wait a couple weeks, you could always send it to Samsung for warranty repair.
Feel free to pm me if you wanna troubleshoot
Sent from CM 10.2 optimized sph-l710

[Q] Scary Experience With HTC One M8

As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?

ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.

Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.

I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.

question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..

blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.

Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.

blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.

Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.

hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.

In my mind, this validates my decision to go over to the CM11 nightlies and never look back.

Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app

I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.

I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk

It isn't necessary to hold both volume keys, just volume up and power.

Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.

andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.

This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.

This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app

Sounds like SOD.