Related
Hey guys,
I've been lurking here ever since I got the incredible. Unfortunately, this is the first time I needed to post and it's bad news. My Incredible is rebooting more than 20 times a day, and I mean that not counting the reboot loop it gets stuck in. I have wiped the phone clean, started to go through the start up wizard, and it rebooted there, so I know it's not an bad app. It has rebooted randomly, though not as bad, before I rooted, so it's not that. I live in southern california and I get good service at home so I don't think it's the same problem as those incidents in south carolina. Does anyone have an idea what it could be? I'm running out of solutions and ready to just drop the phone, eat the ETF and go to sprint. Thanks in advance for the help.
Kiyoshi
I would flash it back to stock take it to verizon and show them what it is doing and have them send you another one, I brought mine back for the unresponsive screen issue and they said it was going to take three weeks for me to get another one but I received it 4 days later. so before switching to sprint and paying a big ETF I would try the above first. but if all else fails to ease the pain a little and not have to pay such a big ETF get a crappy verizon flip phone that you can activate on the line use it for a day or two then cancel your account. you will only pay a 175.00 ETF vs a 350.00 ETF. just a little round about way to "stick it" to the man.
Also, does downgrading and unrooting get rid of the wireless-n mod? Just downgraded and was in the wizard and right when I tried to connect to my network, it rebooted.
That's funny I just flashed it back to stock so I could do that. The problem is that I bought it from best buy in april and did not buy the extended warranty ( of course not, damn waste of money). IIRC, verizon does not honor warranties bought from a different store, correct?
twisted origin said:
Also, does downgrading and unrooting get rid of the wireless-n mod? Just downgraded and was in the wizard and right when I tried to connect to my network, it rebooted.
Click to expand...
Click to collapse
if you reflash the stock ROM it wipes everything including root and wireless N, only reflash stock if you want to return it to the store otherwise you will have to go through the sd card root process again.
twisted origin said:
That's funny I just flashed it back to stock so I could do that. The problem is that I bought it from best buy in april and did not buy the extended warranty ( of course not, damn waste of money). IIRC, verizon does not honor warranties bought from a different store, correct?
Click to expand...
Click to collapse
I am not sure if verizon won't exchange it, I think that there is a year warranty on the phone standard and extended warranty is only good for after the manufacturers warranty runs out. I would check with BB first and if they won't exchange it take it to verizon and see what they say, BB is an authorized verizon dealer so I would imagine that verizon will honor the warranty. but there is only one way to find out. Good Luck.
ok, so I took it to verizon today, and luckily for me it was rebooting away right after the CSR personally factory reset it. I actually was happy it did, too. She was so smug, telling me that I should have been using a task killer and that maybe I didn't factory reset it correctly. She starts it up and was giving me a "haha that's how you do it" look, when it rebooted on her. She battery pulled it, and then it went into a reboot loop on her. Her smug look was replaced by a look of defeat. It was worth the fact that I couldn't get it to stop rebooting for five minutes after that.
I then called 611 and they said they had a replacement for me and that it would be at my doorstep in two days. Evidently, they keep a separate stock for warranty issues. Well anyways, thanks for the help and I'll have an incredible back in my hands soon
Have u tried going into airplane mode and see if it does it? Just curious.
Sent from my ADR6300 using XDA App
Haha I just read Ur last post, I find it funny cuz I work for Verizon also and man u would not believe how many reps say u need a task killer, dumbasses.
Sent from my ADR6300 using XDA App
Yes, keeping it in airplane mode definitely helped. With that in mind, I might have an idea of what happened to my phone and potentially to other phones that have had this problem. I ordered the seidio 1750 batt. when I first got my phone, so I have been using it pretty much since the beginning. As you may know it can get unusually warm when in use. I would frequently use it when I'm at work to listen to podcasts and would keep it on the car charger while in use ( I work at a landfill doing gas monitoring, engineering, etc. so always in my work truck). That is first time I could recall a reboot occurring. I don't know how the internal layout is made up, but perhaps the radio or whatever else related received damage due to overheating. Oh well, already received my new incredible and I now have a battery charger so I will avoid charging and using at the same time. You guys are probably saying "Uh, yeah, of course that will happen, dumbass" but I've never had a problem with my other phones.
I think my MyTouch 4G may be another casualty to the bad emmc chip but wanted to ask you guys just to be sure. This morning I woke up and noticed the alarm didn't go off on my phone, so when I picked it up everything seemed normal. However, when I tried to read a text message it forced closed, then it forced closed the launcher and if I tried to open any other app it forced closed. I tried to hold the power button down to do a reboot, but that didn't work (the pop up screen never came up). So I took the battery out and put it back in, the phone hasn't booted since. I've tried holding volume down and power button, but still nothing. Do you think the phone is bricked? If so, do you think it's the emmc chip issue?
Note: It won't boot when it's hooked up to the charger either, the guy at T-Mobile said there is an issue with the phone. The phone was rooted using GFree method because no other method would work. This phone has the bad EMMC, T-Mobile is sending me a replacement phone.
This sounds exactly like what happened to me. I rooted my phone successfully using the gFree -permaroot method. I then proceed to flash the engineering bootloader and after the battery pull I am no longer able to turn on my phone. I tried booting in HBoot but I get nothing. The LED doesnt light up when I plug the phone into a power source either. If I hold UPVOL+PWR the phone vibrates 4 times quickly and the led light starts flashing, but nothing happens after that. I have called T-Mobile to get a new phone and it is on backorder, so I do have some time before they send me a new one but I'm wondering if there is anything I can do to unroot it? Or is my phone bricked? Will T-Mobile void my warranty and make me pay the full price of the new phone? If anyone has any experience with this or can lead me to somewhere where I can fix this problem, I would greatly appreciate it.
mwilliams05: Sorry to threadjack but this is the only thread I saw that was similar to my situation. Let me know what happens with your phone.
dunnny said:
This sounds exactly like what happened to me. I rooted my phone successfully using the gFree -permaroot method. I then proceed to flash the engineering bootloader and after the battery pull I am no longer able to turn on my phone. I tried booting in HBoot but I get nothing. The LED doesnt light up when I plug the phone into a power source either. If I hold UPVOL+PWR the phone vibrates 4 times quickly and the led light starts flashing, but nothing happens after that. I have called T-Mobile to get a new phone and it is on backorder, so I do have some time before they send me a new one but I'm wondering if there is anything I can do to unroot it? Or is my phone bricked? Will T-Mobile void my warranty and make me pay the full price of the new phone?
mwilliams05: Sorry to threadjack but this is the only thread I saw that was similar to my situation. Let me know what happens with your phone.
Click to expand...
Click to collapse
Call customer service and LT them overnight you a phone then etyrn the one you have. They will never find out it was rooted.....its dead! Just let them know it wouldn't boot up all of a sudden. The emmc chips are going out alot. I was lucky enough to get a good one and sold my phone 3 weeks ago.
Yeah the phones on backorder..i wonder why lol. This Mytouch that just broke on me was a replacement from Asurion, it was most likely a refurb or something. But thanks, appreciate the help!
dunnny said:
This sounds exactly like what happened to me. I rooted my phone successfully using the gFree -permaroot method. I then proceed to flash the engineering bootloader and after the battery pull I am no longer able to turn on my phone. I tried booting in HBoot but I get nothing. The LED doesnt light up when I plug the phone into a power source either. If I hold UPVOL+PWR the phone vibrates 4 times quickly and the led light starts flashing, but nothing happens after that. I have called T-Mobile to get a new phone and it is on backorder, so I do have some time before they send me a new one but I'm wondering if there is anything I can do to unroot it? Or is my phone bricked? Will T-Mobile void my warranty and make me pay the full price of the new phone? If anyone has any experience with this or can lead me to somewhere where I can fix this problem, I would greatly appreciate it.
mwilliams05: Sorry to threadjack but this is the only thread I saw that was similar to my situation. Let me know what happens with your phone.
Click to expand...
Click to collapse
I received my replacement and it has the bad emmc too. I don't think tmobile will know the phone was rooted from what ive heard from others.
Sent from my HTC Glacier using XDA App
The SAME thing happened to me! I also used the gfree method. I just want to know do you have to unroot your phone before you can send it back for a replacement because can't they tell you bricked it trying to root by your S=OFF?
holiday29 said:
The SAME thing happened to me! I also used the gfree method. I just want to know do you have to unroot your phone before you can send it back for a replacement because can't they tell you bricked it trying to root by your S=OFF?
Click to expand...
Click to collapse
If the phone wont boot up, I don't think they will be able to tell you rooted it. When I spoke with a Tmobile customer service rep he said the extended warranty (which I purchased for an extra $4/mo) covers the phone as long as it's not water damaged or physically damaged, which I felt meant if the phone is bricked, it's covered under warranty. That was one of the reasons I rooted knowing I had the bad emmc chip.
Sent from my HTC Glacier using XDA App
mwilliams05 said:
If the phone wont boot up, I don't think they will be able to tell you rooted it. When I spoke with a Tmobile customer service rep he said the extended warranty (which I purchased for an extra $4/mo) covers the phone as long as it's not water damaged or physically damaged, which I felt meant if the phone is bricked, it's covered under warranty. That was one of the reasons I rooted knowing I had the bad emmc chip.
Click to expand...
Click to collapse
They can still tell if it's rooted. ClockworkMod recovery is still there, and if the phone has the engineering bootloader, that will also be a dead giveaway. The thing is, I don't think any of that matters. My friend has been a VZW customer service manager for years and swears that they don't care if it's rooted. He says they rarely actually try to boot a phone that's been returned, and if they do, being rooted is a non-issue. I know TMO could have a different policy, but since it's TMO known for their customer service, not VZW, I would assume they'd be even more lenient about returns.
TeeJay3800 said:
They can still tell if it's rooted. ClockworkMod recovery is still there, and if the phone has the engineering bootloader, that will also be a dead giveaway. The thing is, I don't think any of that matters. My friend has been a VZW customer service manager for years and swears that they don't care if it's rooted. He says they rarely actually try to boot a phone that's been returned, and if they do, being rooted is a non-issue. I know TMO could have a different policy, but since it's TMO known for their customer service, not VZW, I would assume they'd be even more lenient about returns.
Click to expand...
Click to collapse
How do they know if clockwork mod recovery is on the phone if it wont turn on? The phone I just sent back wouldn't power on at all. Is there another way for them to find out it's been rooted if the phone won't turn on (I.e. nothing is displayed on the screen) ?
Sent from my HTC Glacier using XDA App
TeeJay3800 said:
They can still tell if it's rooted. ClockworkMod recovery is still there, and if the phone has the engineering bootloader, that will also be a dead giveaway. The thing is, I don't think any of that matters. My friend has been a VZW customer service manager for years and swears that they don't care if it's rooted. He says they rarely actually try to boot a phone that's been returned, and if they do, being rooted is a non-issue. I know TMO could have a different policy, but since it's TMO known for their customer service, not VZW, I would assume they'd be even more lenient about returns.
Click to expand...
Click to collapse
i can back this story up
my phone just took a **** on me a couple days ago with cache errors due to eMMC being the bad one...i worked for 3 hours to unroot the damn thing cause adb or my phone was being a complete asshole...after i unrooted the phone i went to the local tmo store and talked to the dudes up there and they pretty much said...tmo doesnt care if they get rooted phones cause they all get sent back to HTC or Samsung to get refurbed...he said water damage or physical damage is a different story
mwilliams05 said:
How do they know if clockwork mod recovery is on the phone if it wont turn on? The phone I just sent back wouldn't power on at all. Is there another way for them to find out it's been rooted if the phone won't turn on (I.e. nothing is displayed on the screen) ?
Click to expand...
Click to collapse
You didn't say it doesn't turn on. You said "it doesn't boot." Usually when people complain about a phone not booting, it still physically turns on, but ends up going to recovery or the bootloader, or hangs at the myTouch screen. If it won't turn on at all, they can't tell if it's rooted, but my guess is they can get it to turn on even if you can't. However, as the posts above explain, it doesn't really matter because they don't care whether it's rooted or not.
Rooting = voiding warranty is a myth?
So is it safe to assume when you root your phone, it doesn't actually void your warranty because the phone doesn't have physical or water damage, right?
Anyone have success RMAing a phone in with an unlocked BL but no other mods? With all the red light of death stories I've read in the past couple of days I sure don't want to spend over $700 for one N4 that could do the same thing. (kind of wishing I got a Note II now!)
ThaBrickah! said:
Anyone have success RMAing a phone in with an unlocked BL but no other mods? With all the red light of death stories I've read in the past couple of days I sure don't want to spend over $700 for one N4 that could do the same thing. (kind of wishing I got a Note II now!)
Click to expand...
Click to collapse
tiny bump
ThaBrickah! said:
Anyone have success RMAing a phone in with an unlocked BL but no other mods? With all the red light of death stories I've read in the past couple of days I sure don't want to spend over $700 for one N4 that could do the same thing. (kind of wishing I got a Note II now!)
Click to expand...
Click to collapse
$700 dollars??? Jeez, someone ripped you off. Did you buy it from eBay? I bet you did.
The Nexus 4 is available on the U.S Play Store as of time.
( it would be more expensive if it was in another country, but since you're using the dollar sign...)
Sent from my Nexus 7 using Tapatalk HD
scream4cheese said:
$700 dollars??? Jeez, someone ripped you off. Did you buy it from eBay? I bet you did.
The Nexus 4 is available on the U.S Play Store as of time.
( it would be more expensive if it was in another country, but since you're using the dollar sign...)
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
No, I'm sorry. I had edited down my original question and now it doesn't make complete sense. What I meant was that my phone died on me but I left my bootloader unlocked after reflashing with the image from the developer.google site. I never rooted it but failed to lock the bootloader after reflashing. Now I have the red light of death.
The $700 comes from them holding $300 on my credit card during the RMA process, only to find that I've voided my warranty by having an unlocked bootloader and them charging me for it. That would be over $700 for an N4 that could just do the exact same thing again.
I honestly don't want this phone anymore if all of them are going to die after only a couple weeks use.
The phone is designed to be unlockable via a simple command, so the fact that you have done that should in no way invalidate your warranty. You should have no problem with an RMA.
Sent from my Nexus 4
There is a fix for the red light of dead... It's a hardware problem tho, let me find the youtube video.. brb
I can't find the video (i'm at work) and I have it bookmarked at home, it's on xda tho, you must take out the back part and release a part of the hardware.. It's easy and the guy who found out made several examples, in which if he pressed that chip = red light appear, leaving it without much pressure = normal
I guess take the back off , remove the battery connector , reconnect the connector after a few minutes and put it on charge
Sent from my Nexus 4 using Tapatalk 2
If the phone is dead, what does it matter if the bootloader is unlocked?
Sent from my Nexus 4 using Tapatalk 2
Most everyone says that an unlocked BL voids the warranty, but it doesn't specifically say that in the warranty documentation. I think I'm going to let this thing run down as much as possible then try to connect to it over the weekend, then call Google on Monday if I have no success. Wonder if I should be upfront with the unlocked BL?
you haven't voided the warranty. Honestly, these companies rarely check for those kind of things. They don't have much time to investigate so they go straight to fixing it. I sent my rooted epic 4g w/ screwed up NV items (screwed em up while flashing) in for a fix and they fixed it for me no charge. You should be fine.
i have sent a few devices back for rma from google. each one of them had an unlocked bootloader, root, custom recovery, and a custom rom/kernel. google never gave me any issues with the process, and exchanged my devices within days. if its a hardware issue, they wont have any problems with an unlocked bootloader.
simms22 said:
i have sent a few devices back for rma from google. each one of them had an unlocked bootloader, root, custom recovery, and a custom rom/kernel. google never gave me any issues with the process, and exchanged my devices within days. if its a hardware issue, they wont have any problems with an unlocked bootloader.
Click to expand...
Click to collapse
Hope you're right. I went through the RMA process on Monday after them having me try all the various button press combinations that I've tried a million times before. The return sticker they sent me was addressed to an LG repair center in Texas instead of any Google entity - that worries me.
I got my replacement on Thursday but I'm not even going to open the shipping box until I see the pending charges from Google drop off my credit card. If I do get charged then I'll try and sell this thing and cut my losses.
I'm very disappointed in the quality of the N4. I decided to only buy Nexus devices from here on out so that I can get the OS updates, but if they break after a couple of weeks then the only other option is to abandon Android altogether. Too bad because its the Google ecosystem that I like.
ThaBrickah! said:
Hope you're right. I went through the RMA process on Monday after them having me try all the various button press combinations that I've tried a million times before. The return sticker they sent me was addressed to an LG repair center in Texas instead of any Google entity - that worries me.
I got my replacement on Thursday but I'm not even going to open the shipping box until I see the pending charges from Google drop off my credit card. If I do get charged then I'll try and sell this thing and cut my losses.
I'm very disappointed in the quality of the N4. I decided to only buy Nexus devices from here on out so that I can get the OS updates, but if they break after a couple of weeks then the only other option is to abandon Android altogether. Too bad because its the Google ecosystem that I like.
Click to expand...
Click to collapse
That's pretty radical to drop Android altogether, if you just wanted quick updates, why didn't you just leave it locked and stock?
ThaBrickah! said:
Hope you're right. I went through the RMA process on Monday after them having me try all the various button press combinations that I've tried a million times before. The return sticker they sent me was addressed to an LG repair center in Texas instead of any Google entity - that worries me.
I got my replacement on Thursday but I'm not even going to open the shipping box until I see the pending charges from Google drop off my credit card. If I do get charged then I'll try and sell this thing and cut my losses.
I'm very disappointed in the quality of the N4. I decided to only buy Nexus devices from here on out so that I can get the OS updates, but if they break after a couple of weeks then the only other option is to abandon Android altogether. Too bad because its the Google ecosystem that I like.
Click to expand...
Click to collapse
First of all, I don't get it. Nexus has been great to me, and the 3 others I know who bought it, love it too. Build quality is good, and stock, no issues. Even if you root it, chances of something like that happening are low. I used to have all kinds of phones, from gs2&3 to note 2 to HTC one x. None of them were as hard to mess up as the nexus.
But as far as your original question goes... I rmad galaxy nexus to Google because my earpiece became very crackly. Mine was rooted and unlocked. I kept on putting it off until I realized that the label they sent was only good for 14 days. Ended up sending it rooted and with custom ROM on it, figured might as well try. No issues at all. They didn't say a word.
Sent from my Nexus 4 using xda app-developers app
chrisMBP said:
That's pretty radical to drop Android altogether, if you just wanted quick updates, why didn't you just leave it locked and stock?
Click to expand...
Click to collapse
I reflashed stock firmware onto it in hopes of improving battery life - per a thread on this forum. For me, rooting is unnecessary on the Nexi because there isn't any manufacturer or carrier bloatware to get rid of. I honestly did consider rooting it to try an underclocking app to maybe improve battery life, but it seemed too much of a PITA.
They got my old phone last Wednesday, but the charges are still pending as of today. I decided to go ahead and open the replacement and not worry about it anymore. I noticed the replacement has a higher number serial number, so now I'm off to read the thread that tries do decode it!
Thanks all.
:crying::crying::crying: So the phone was working perfect until I noticed it wasn't charging. No red led nor charging indicator on upper right battery icon, checked chargers and cables but still nothing. So I decided to reset the phone but never powered on again at all. No life,
Nada. No red indicator, vabration, no menus nor bottom tricks. Nothing. Out of experience here what do you suggest? I was thinking of buying replacement charging PCB board and battery but not sure if it would even do anything. Also how would I go about warranty specially with the current zte USA issue? I bought the phone on newegg just before they stopped selling it completely so don't know how to proceed. Any advice greatly appreciated and TIA. Quick update: no type of heat seems to be coming off phone when connected to charger for long period of time.
If the phone is still under warranty they've either got to fix it for you for give you a replacement. It just might take longer than usual. Contact Newegg first, and if unsuccessful with them you can contact ZTE directly. Remember ZTE isn't just a phone brand, they're huge and they have to follow the rules. Also, I've heard for 80$ ZTE will send you a refurb Axon 7 as long as you send them your old phone. That might be an option too. You can enquire with them about that before filing an RMA I guess.
I all so had exactly the same issue. Brand new Axon 7, and it just wouldnt charge. Contacted ZTE right away, it was the day after they got in trouble with USA. They answered back first, but now not a word for 2 weeks nearly, I've written to them several times, since they said they would return to me after consulting with their engineer's, but nothing. And they don't even answer back or anything.
That is not okay to treat their customers like that. Have lost all faith in them. Not our fault they got problems for deals that aren't legal.
WOW!!!!
Oliver Aa said:
I all so had exactly the same issue. Brand new Axon 7, and it just wouldnt charge. Contacted ZTE right away, it was the day after they got in trouble with USA. They answered back first, but now not a word for 2 weeks nearly, I've written to them several times, since they said they would return to me after consulting with their engineer's, but nothing. And they don't even answer back or anything.
That is not okay to treat their customers like that. Have lost all faith in them. Not our fault they got problems for deals that aren't legal.
Click to expand...
Click to collapse
WOW so sorry to hear about your experience, I had read your reply before but couldn't get back cause I had to make due with the crappiest LG prepaid phone from Verizon so I'm replying now. My UPS store just called me to let me know they just received it so let's see how that goes. In the last Email they stated it would be a REFURBISHED phone not the one I sent. I hope it's cosmetically new cause that how I had mine. Now my only question is if I should risk rooting it since I suspect that might have caused the damage but still unsure cause it's a common problem even with a stock locked system. All I really want is my backups but don't know how to use Helium. Any advice greatly appreciated.
Hi all.
I just got this phone from swappa in July, and I really like it. Coming from a Pixel 3 which is also a 2 year old phone the 6t is so much better. However, as I was watching youtube one night, the video froze, and the phone was just giving out a "zzzzz" loud noise, not dissimilar to the noise you'd get from a bsod back in the day. I forced restart by pressing all the buttons, and it was stuck on the Tmobile magenta boot up screen, with some visual artifacts (stripes, reminiscing of a GPU dying). It would boot that up, freeze for a few seconds, and then go into a boot loop. The phone would boot into fastboot and recovery, but not able to boot up.
As a last resort, I flashed MSM and 9.0.11. I was able to flash it, but the reboot after flash resulted in a coredump from qualcom with code 0x00000000 (do not count the 0). I rebooted it again, I was stuck on the red dot boot up screen with similar problems as on tmo ROM: it would freeze up, and then reboot again. I then tried flashing 9.0.13, and the same thing. I had put off fastboot unlocking the phone, so I cannot enable developer mode now. As a result, I cannot unlock bootloader after flashing 9.0.11.
So my question is, am I stuck with a dead phone? I've essentially tried 2 ROMs and I can't get the phone to boot up. Given the manifestation before it had died, I don't think this is salvageable. I could wait for the fastboot unlock code from tmobile, unlock it, and then flash everything, but is there a point to it? Could I even sell this on Ebay?
Thanks ahead of time.
I think the failure scenario you describe answers your question. It is not as if you were messing with the software and it caused a brick. Something on the hardware side failed while you were using it fully stock and it is gone. You could send it in for repair with OnePlus but it would likely be cheaper to just buy another on swappa. Not sure why you decided to get a tmo branded when buying used on swappa though? regardless this is probably simply a case of bad luck.
xijar said:
I think the failure scenario you describe answers your question. It is not as if you were messing with the software and it caused a brick. Something on the hardware side failed while you were using it fully stock and it is gone. You could send it in for repair with OnePlus but it would likely be cheaper to just buy another on swappa. Not sure why you decided to get a tmo branded when buying used on swappa though? regardless this is probably simply a case of bad luck.
Click to expand...
Click to collapse
Back in July the price was sky high. There was no international version anywhere. Perhaps I'll get a 7t this time. I think it's a bad luck too. the phone was practically brand new.