Just bought a used Nexus 6p and started through the setup and the phone died at 42%. It came right back on as soon as I plugged it up but this has me worried that this going to be an on going problem. Is anyone else having this problem and is it a sign of something worse?? Thanks in advance
Same problem here,I fixed it by using PureNexus ROM
Sent from my Nexus 6P using Tapatalk
Minh Dao said:
Same problem here,I fixed it by using PureNexus ROM
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks i will root mine and give it a try this weekend
jmcandrews83 said:
Thanks i will root mine and give it a try this weekend
Click to expand...
Click to collapse
Just need to unlock bootloader then install TWRP
To be honest, I bet this is why they sold it, was it mentioned that the device has an early shut down issue? If flashing a custom rom doesn't fix it, you may need to replace the battery.
Triscuit said:
To be honest, I bet this is why they sold it, was it mentioned that the device has an early shut down issue? If flashing a custom rom doesn't fix it, you may need to replace the battery.
Click to expand...
Click to collapse
Yeah i bet it is also. And no he didn't say anything about it when selling. Im hoping root will fix it i gave it a full charge and got it down to about 20 percent today before it shut off
jmcandrews83 said:
Just bought a used Nexus 6p and started through the setup and the phone died at 42%. It came right back on as soon as I plugged it up but this has me worried that this going to be an on going problem. Is anyone else having this problem and is it a sign of something worse?? Thanks in advance
Click to expand...
Click to collapse
Perhaps try deleting the batter stats (settings -> battery -> trash can icon) first and diagnose it with a battery app such as Ampere first? This can be accomplished without root.
AncientDeveloper said:
Perhaps try deleting the batter stats (settings -> battery -> trash can icon) first and diagnose it with a battery app such as Ampere first? This can be accomplished without root.
Click to expand...
Click to collapse
Thanks ill give it a try during my break
Triscuit said:
To be honest, I bet this is why they sold it, was it mentioned that the device has an early shut down issue? If flashing a custom rom doesn't fix it, you may need to replace the battery.
Click to expand...
Click to collapse
I have faced this problem with stock rom and I flashed PureNexus ROM then no more problem
Sent from my Nexus 6P using Tapatalk
Related
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
Ok i just got a new battery today and i thought it was not draining. But with in couple of minutes it started draining again. So i called tmo and they are sending me another one. So i should just do stock odin on this one and i should be good right?
Yeah that works or you can just flash the stock update.zip from clockwork. And afterward just delete the clockwork file from your sd card.
Goog1e Phone said:
Yeah that works or you can just flash the stock update.zip from clockwork. And afterward just delete the clockwork file from your sd card.
Click to expand...
Click to collapse
i think i will just flash the stock odin and i will format my internal sd card
the new one that i will get i wont root it or anything. i learned my lesson lol. i know not all of you had problems after rooting but i think the battery drainage started after i rooted
flameinthefire said:
the new one that i will get i wont root it or anything. i learned my lesson lol. i know not all of you had problems after rooting but i think the battery drainage started after i rooted
Click to expand...
Click to collapse
did you do anything else besides root? install any root apps?
You do realize that rooting your phone would not change a single thing right.....
lolcopter said:
did you do anything else besides root? install any root apps?
Click to expand...
Click to collapse
yes i tried set cpu but i didnt change any settings it was default
s15274n said:
You do realize that rooting your phone would not change a single thing right.....
Click to expand...
Click to collapse
may be it was the set cpu? or the lag fix?
Were you using a profile with SetCPU, that DOES cause an issue.
wait, why didnt you put this in the previous thread you started?
Curious, do you have any way of quantifying this supposed battery drain? Are you aware of the bugs related to reported battery % versus actual battery %?
Chalup said:
Curious, do you have any way of quantifying this supposed battery drain? Are you aware of the bugs related to reported battery % versus actual battery %?
Click to expand...
Click to collapse
yes i am aware of it and i installed the accurate battery % from the theme section. so that was not the issue
Are they goning to send me a refurbished phone? Because the one i have was bought brand new..
bump.......
I got a replacement and could not tell if it was a refurb or not. If it is a refurb I cannot tell.
Typos and other gibberish courtesy of Swype
hockeyrcks9901 said:
I got a replacement and could not tell if it was a refurb or not. If it is a refurb I cannot tell.
Typos and other gibberish courtesy of Swype
Click to expand...
Click to collapse
what was wrong with urs? why did u get a replacement?
flameinthefire said:
what was wrong with urs? why did u get a replacement?
Click to expand...
Click to collapse
The usb port was very loose and the cord had to wiggled occasionally to get it to charge.
Typos and other gibberish courtesy of Swype
flameinthefire said:
Ok i just got a new battery today and i thought it was not draining. But with in couple of minutes it started draining again. So i called tmo and they are sending me another one. So i should just do stock odin on this one and i should be good right?
Click to expand...
Click to collapse
Was your battery draining before root?
Is anyone else having major data drops? Mine is happening like 3x a day now! Very annoying. It has nothing to do with airplane mode. All of a sudden I will see my 3G signal leave, then there's a small x near my status bars then the x will go away but the 3G signal will not come back unless I reboot. When I reboot, my battery level drops all the way to where I need to connect my charger to keep it on.
This started happening about 5 days ago. Never an issue before that. Started happening after I flashed Trigger v1.5 rom. Went back to Bionix V and it's still happening. Wiped, Wiped, reflashed, wiped, wiped reflashed...still an issue.
Any help is appreciated!
You might try flashing a different modem.
Powered by Axura with a dash of Voodoo
Or you might have a SIM getting ready to crap out on you.
jmcghee1973 said:
Or you might have a SIM getting ready to crap out on you.
Click to expand...
Click to collapse
That just may be the problem. Its happening now like every hour. Forgot about that. It happened to me once before. years ago. Forgot, but can I just go into T-mo and get a new sim?
yes..you can tell them whats happening..minus the ROM flashin part..and they will get you a new SIM
jmcghee1973 said:
yes..you can tell them whats happening..minus the ROM flashin part..and they will get you a new SIM
Click to expand...
Click to collapse
Lol. Trust me I know not to let them know I'm a flashaholic.
mainevent3405 said:
Lol. Trust me I know not to let them know I'm a flashaholic.
Click to expand...
Click to collapse
Dear mainevent, Searching found your post. May I ask, did replacing sim handle?
greencloudz said:
Dear mainevent, Searching found your post. May I ask, did replacing sim handle?
Click to expand...
Click to collapse
I did a sim replacement but I really can't tell if it helped me because I'm still having this issue but not really all the time. Are you on 2.2?
Sent from my SGH-T959 using XDA App
I was hoping someone hand any advice on my problem. I was running EF02 rom with EF10 modem and flashed EG22 from this thread:
http://forum.xda-developers.com/showthread.php?t=1123103
Now my phone doesn't turn on. Nothing works. Any help would be great.
Fixed:
I just let the battery and sdcard sit out of the phone for 45 minutes (doesn't have to be this long) then I put the battery back in and was able to get into download mode. I am flashing the phone back to stock as I think I might have messed something else up earlier. Make sure that after you put the pit file in odin you uncheck re-partition if you are just updating the modem.
This is how I brought my phone back from a hard brick. Thanks everyone for their help.
Some suggestions from others that might help:
http://forum.xda-developers.com/showpost.php?p=15958635&postcount=54
http://forum.xda-developers.com/showpost.php?p=15959310&postcount=61
Can you still get into cwm our download mode?
Did you try removing the battery, putting it back in and trying to boot into download mode?
did you uncheck f partition?
Did you use stock cable?
Sent from my SPH-D700
I am not able to get into download mode or clockwork. f partion was unchecked. I tried removing the battery and still no luck.
let it sit without the battery in for about an hour, then plug in with battery out and try download mode
This is why leaks are bad.
- Ron
Ron_91 said:
This is why leaks are bad.
- Ron
Click to expand...
Click to collapse
I know multiple people that have flashed this Modem and are having no issues at all.
And out of the few dozen people who flashed this, only 1 ended up with a brick...
Ron_91 said:
This is why leaks are bad.
- Ron
Click to expand...
Click to collapse
Only bad when you don't know what you're doing
Sent from my Samsung Epic 4G using Tapatalk
piscesjoey said:
Only bad when you don't know what you're doing
Sent from my Samsung Epic 4G using Tapatalk
Click to expand...
Click to collapse
Using unreleased beta software and experiencing issues doesn't necessarily have anything to do with knowing what you are doing or not...
The Root said:
let it sit without the battery in for about an hour, then plug in with battery out and try download mode
Click to expand...
Click to collapse
I will give this a try and get back to you all with the results.
the same thing happened to me. hard bricked my phone flashing eg22 and i know what i was doing. tried to put it into download mode using test jig and its a no go. getting a new phone Wednesday. $35 (sucks). any one Know how to bring it back????
machx0r said:
Using unreleased beta software and experiencing issues doesn't necessarily have anything to do with knowing what you are doing or not...
Click to expand...
Click to collapse
Actually it does if some people are having no problems at all.
Sent from my SPH-D700
ac16313 said:
Actually it does if some people are having no problems at all.
Sent from my SPH-D700
Click to expand...
Click to collapse
You're right, this leak is perfect and has no issues what so ever. The only way anyone could possibly have a problem with it is through their own ignorance and stupidity. My bad...
People who are getting so called "bricks"...
no lights, no samsung logo, no led lights, phone looks completely dead.
Try this:
Remove SD card and battery, leave SD card out, put back battery and try booting into download mode (1 key + power button).
Let us know if this is a go or no go, thanks!
machx0r said:
You're right, this leak is perfect and has no issues what so ever. The only way anyone could possibly have a problem with it is through their own ignorance and stupidity. My bad...
Click to expand...
Click to collapse
Lol your funny, bye.
Sent from my SPH-D700
anand731 said:
I will give this a try and get back to you all with the results.
Click to expand...
Click to collapse
Seems to have worked. Let it sit without the battery and sd card and was able to get back into download mode. Thanks for all the suggestions.
anand731 said:
Seems to have worked. Let it sit without the battery and sd card and was able to get back into download mode. Thanks for all the suggestions.
Click to expand...
Click to collapse
really???? how long was it "bricked?" I bricked mine (pulled in dl mode ALL my fault ha) and too it to sprint store and there ordering me a replacement. can you explain exactly what you did please
Hey XDA,
Am a new user and i need some advice on the new Andriod O.
In the past I had the Andriod 7.1.1 and my got the BLOD. I sent the phone back to and got another one with Andriod 7.0.
I never upgraded the version because i didnt know if it was safe and now seeing that Andriod O is out. Am just wondering if its safe to upgrade?
Am considering to unlock the Bootloader and USB Debugging just in the event something goes wrong i guess i can always install a new ROM or something.
As i really dont want to be hurt again
Any advice for a newbie?
Thanks in advance.
Capt_JuMbO said:
Hey XDA,
Am a new user and i need some advice on the new Andriod O.
In the past I had the Andriod 7.1.1 and my got the BLOD. I sent the phone back to and got another one with Andriod 7.0.
I never upgraded the version because i didnt know if it was safe and now seeing that Andriod O is out. Am just wondering if its safe to upgrade?
Am considering to unlock the Bootloader and USB Debugging just in the event something goes wrong i guess i can always install a new ROM or something.
As i really dont want to be hurt again
Any advice for a newbie?
Thanks in advance.
Click to expand...
Click to collapse
The android version isn't what causes the BLOD but a degraded battery is what causes it. It is completely safe to update to O.
DEVILOPS 007 said:
The android version isn't what causes the BLOD but a degraded battery is what causes it. It is completely safe to update to O.
Click to expand...
Click to collapse
Okay when i called Hauwei support they told me it was a problem with 7.1.1 thats why i never updated.
So does that mean that the BLOD can come back? Or was it due to an inferior battery used on some devices ?
Capt_JuMbO said:
Okay when i called Hauwei support they told me it was a problem with 7.1.1 thats why i never updated.
So does that mean that the BLOD can come back? Or was it due to an inferior battery used on some devices ?
Click to expand...
Click to collapse
It depends on how well you look after your battery. This issue is mostly present on the Nexus 6p as AFAIK but it can happen on any device. Just try to look after your battery by charging to the max of 80% and try not to go under 30% too often. What Huawei told you assuming you understood them correctly was BS and likely a way for them to put the blame on Google and not their hardware. Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
DEVILOPS 007 said:
It depends on how well you look after your battery. This issue is mostly present on the Nexus 6p as AFAIK but it can happen on any device. Just try to look after your battery by charging to the max of 80% and try not to go under 30% too often. What Huawei told you assuming you understood them correctly was BS and likely a way for them to put the blame on Google and not their hardware. Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
Click to expand...
Click to collapse
I guess what Hauwei was saying was BS but google didnt offer any help just said to contact them.
I try honestly try to look after the battery, i normally let it charge to 100% at night and take it off before i sleep. I dont leave it on the charger ever or longer than i need. Then charge it again around 20-15% back to full.
If i was to charging at 30% to 80%, i dont think would give me alot of time and would have to charge more often. Wouldn't that harm the battery more?
DEVILOPS 007 said:
Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
Click to expand...
Click to collapse
This is the second phone they sent me, so it doesnt have any more warranty. Am hopeful it can last and would have to replace anything. :fingers-crossed: Are there any sources for good battery replacement ?
Capt_JuMbO said:
This is the second phone they sent me, so it doesnt have any more warranty. Am hopeful it can last and would have to replace anything. :fingers-crossed: Are there any sources for good battery replacement ?
Click to expand...
Click to collapse
Your first thought was the correct one. Start by unlocking your bootloader and then update to 8.0 and enjoy your phone. If/when you ever have a battery issue there are plenty of places to have it replaced at a reasonable price. Android software version was never the cause (or cure) to a bootlooping phone, so you got some bad information there.