Related
Just got a software update. I wonder what has changed or improved.
Sent from my SM-G935T using Tapatalk
Not sure. But bootloader is still locked with this, and experts are recommending to hold off on install if you plan on trying to root the device (in case a root exploit is found for the original software version). Remember, once you flash a new software, you cannot go back.
Seems to fix static over bluetooth, at least for me. Persisting with cabled headphones, though.
I noticed that it re-enables the things you have disabled with Package Disabler Pro.
Samsung Galaxy S7 Edge
How do you disable automatic updates ?
Sent from my SM-G935T using Tapatalk
I just did the update, TOOK FOREVER IT SEEMED....but I am very impatient. Afterwards, it seems that things are smoother and faster, but it could just be the placebo effect. I will be watching battery life today and see if it improves.
Dr. Fed said:
Not sure. But bootloader is still locked with this, and experts are recommending to hold off on install if you plan on trying to root the device (in case a root exploit is found for the original software version). Remember, once you flash a new software, you cannot go back.
Click to expand...
Click to collapse
Lucky for my, I don't root or anything like that. I'm kind of ocd I like things to be the way they are supposed to be. I tried it once and hated it.
Sent from my SM-G935T using Tapatalk
Dr. Fed said:
Not sure. But bootloader is still locked with this, and experts are recommending to hold off on install if you plan on trying to root the device (in case a root exploit is found for the original software version). Remember, once you flash a new software, you cannot go back.
Click to expand...
Click to collapse
Although I do believe that Samsung should unlock the bootloader and let people make their own choice about their phone. They just need to make it very clear that if you modify your phone your warranty is voided and your on your own. Sad part is some people will go out there and start playing with stuff and not know what they are doing and then want to blame Samsung when the phone gets messed up.
Sent from my SM-G935T using Tapatalk
My next phone im not rooting
Sent from my SM-N920T using Tapatalk
Cyberguycpt said:
Although I do believe that Samsung should unlock the bootloader and let people make their own choice about their phone. They just need to make it very clear that if you modify your phone your warranty is voided and your on your own. Sad part is some people will go out there and start playing with stuff and not know what they are doing and then want to blame Samsung when the phone gets messed up.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I think they've made it abundantly clear that flashing unsigned firmware voids the warranty. And Samsung can then refurb the phone and resell it. The Knox flag effectively protects Samsung from any liability regarding this sort of thing. Making it impossible to "downgrade" to previous software versions, a practice Samsung started a few years ago, was a bad omen. The dawn of the Knox flag added to this downward spiral. Locking the bootloader is a level of control unprecedented for carriers like T Mobile and Sprint, and continues the evolution of Samsung's security deathgrip.
Popped up when I unlocked my phone this morning. It's installing now will play around with it .
nano303 said:
My next phone im not rooting
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
then you have nothing to worry about, it is a great phone.
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
I "chatted" with T Mobile support around 8:30 am today, they had no idea this update was live. Apparently their databases have not updated.
Probably a good idea to hold off on this for now. What if they find an exploit that lets us root but only for the previous version? This is becoming a lot like iPhone jailbreaking... that's why I switched to this S7 Edge lol. I should have read more about it first.
slayerh4x said:
Probably a good idea to hold off on this for now. What if they find an exploit that lets us root but only for the previous version? This is becoming a lot like iPhone jailbreaking... that's why I switched to this S7 Edge lol. I should have read more about it first.
Click to expand...
Click to collapse
Samsung devices on T Mobile have always had unlocked bootloaders (as long as I can remember anyhow), this was a huge surprise for everybody.
It's also not the March security update as its still flagged as Feb 1
Sent from my SM-G935T using Tapatalk
Just rebooted after installing the update. Got a pop-up saying:
"The operating system on your device has been modified in an unauthorized way. Try downloading software updates using Smart Switch on your computer or visit a customer service center"
I haven't modified anything. I haven't even disabled packages. There is obviously no root so I haven't done that either. Weird. Will try a factory restore.
Edit: This was happening after I attempted to check for updates after this mornings update installed. Checked for update again after a 2nd restart and message no longer comes up.
Dr. Fed said:
Samsung devices on T Mobile have always had unlocked bootloaders (as long as I can remember anyhow), this was a huge surprise for everybody.
Click to expand...
Click to collapse
Yeah it does seem that way. It really sucks, rooting the phone was one of the big reasons I wanted to switch over. I hope someone is able to find an exploit that allows root. I had android a long time ago and ran Cyanogen mod, that thing was cool. It took the super slow stock LG G1 or whatever it was and made it really fast. I would pay for that on this phone, it has so much potential.
Dr. Fed said:
I think they've made it abundantly clear that flashing unsigned firmware voids the warranty. And Samsung can then refurb the phone and resell it. The Knox flag effectively protects Samsung from any liability regarding this sort of thing. Making it impossible to "downgrade" to previous software versions, a practice Samsung started a few years ago, was a bad omen. The dawn of the Knox flag added to this downward spiral. Locking the bootloader is a level of control unprecedented for carriers like T Mobile and Sprint, and continues the evolution of Samsung's security deathgrip.
Click to expand...
Click to collapse
The only issue I have with modding phones is that sometimes when buying used phones the seller doesn't tend to inform the buyer if something is wrong. I bought a phone a few years ago on At&t and realized later that it had Internet but could not make calls out. Apparently the last owner flashed something and messed it up. I ended up selling it for cheap, luckily it worked out for the buyer because the phone would not make calls on At&t but would on T-Mobile and he had T-Mobile.
There should be a bootloader unlocking tool that will let you forfeit all your claiming rights but also put you on a list by you imei number that can tell potential buyer your phone has been modified. While you may wont to modify it I wouldn't wont any of your problems. Worst of all is when you hear there is an update for your phone but you cant get it because your phone was modded with out your knowledge when purchasing.
Sent from my SM-G935T using Tapatalk
idtheftvictim said:
I just did the update, TOOK FOREVER IT SEEMED....but I am very impatient. Afterwards, it seems that things are smoother and faster, but it could just be the placebo effect. I will be watching battery life today and see if it improves.
Click to expand...
Click to collapse
I actually don't think its a placebo effect. Could be wrong. On restart, it was much quicker to get to a usable state. The micro stutters I was having seem to be gone. Things are opening quicker as well.
A welcomed update, I have installed on my phone and will see if it improves my battery life which has not been too good.
Hello guys.
I live in South Korea and just had contact with customer service.
They said once my warranty is now passed, they might not be able to provide me a free repair, but google will soon release an update that is supposed to fix the BLOD(Boot Loop Of Death), so I'd better wait for it.
I don't know if it will work, but for me, and people having a phone which can't even get to recovery but only bootloader, who seem to have nothing to lose, this update will worth the wait.
Let's hope that's true and we can get our 6P back to life.
Didnt Google mentioned BLOD is a hardware issue earlier?
Aswin08 said:
Didnt Google mentioned BLOD is a hardware issue earlier?
Click to expand...
Click to collapse
Yeah. There's a news that Google said it's hardware problem, but Huawei did say the upcoming update will fix it.
IDK which one is truth.. just hoping simply updating software will fix it.
frostydawn said:
Yeah. There's a news that Google said it's hardware problem, but Huawei did say the upcoming update will fix it.
IDK which one is truth.. just hoping simply updating software will fix it.
Click to expand...
Click to collapse
If it's a software issue why does it happen with Marshmallow, Nougat and custom ROMs? I don't think Huawei is being honest.
jhs39 said:
If it's a software issue why does it happen with Marshmallow, Nougat and custom ROMs? I don't think Huawei is being honest.
Click to expand...
Click to collapse
Oh it didn't occured to me..
I also have some doubt that it's a software-related problem, because downgrading to MM doesn't even work.
Well, maybe they are fixing bugs that they haven't found before, or also maybe, the defective OS has triggered something..
I'm not sure that update will fix my phone, but for now, this is my last hope.
frostydawn said:
Oh it didn't occured to me..
I also have some doubt that it's a software-related problem, because downgrading to MM doesn't even work.
Well, maybe they are fixing bugs that they haven't found before, or also maybe, the defective OS has triggered something..
I'm not sure that update will fix my phone, but for now, this is my last hope.
Click to expand...
Click to collapse
Good luck but I honestly wouldn't get my hopes up too high. But you aren't the first person Huawei told this to. Hopefully there is something to it besides them trying to brush people off. I personally think people should file a class action suit against Huawai since the phone appears to be defective and it should last for more than a year given its premium price. I've never had a phone from HTC, LG or Samsung break, no matter how long I kept using them. I've never even heard of another phone that has all the issues the 6P does.
jhs39 said:
Good luck but I honestly wouldn't get my hopes up too high. But you aren't the first person Huawei told this to. Hopefully there is something to it besides them trying to brush people off. I personally think people should file a class action suit against Huawai since the phone appears to be defective and it should last for more than a year given its premium price. I've never had a phone from HTC, LG or Samsung break, no matter how long I kept using them. I've never even heard of another phone that has all the issues the 6P does.
Click to expand...
Click to collapse
Yeah I'm suspecting if there's an inherent hardware defects, and if that's the case, I think they should provide us a proper support like LG providing refund of Nexus 5x in US.
But, I'm not an expert and don't know what caused boot loop.
As I saw another person who may live in another country of mine, heard from Huawei that update will fix the problem, there may be something google is preparing for.
For now, there best thing I can do, is wait android 7.1.2 beta image.
If it won't work, that's a problem of then.
p.s. luckily I have unlocked bootloader, but considering boot looping devices can update their software only through unlocked bootloader, what should normal people having locked bootloader should do?
frostydawn said:
Yeah I'm suspecting if there's an inherent hardware defects, and if that's the case, I think they should provide us a proper support like LG providing refund of Nexus 5x in US.
But, I'm not an expert and don't know what caused boot loop.
As I saw another person who may live in another country of mine, heard from Huawei that update will fix the problem, there may be something google is preparing for.
For now, there best thing I can do, is wait android 7.1.2 beta image.
If it won't work, that's a problem of then.
p.s. luckily I have unlocked bootloader, but considering looping devices can update their software only through unlocked bootloader, what should normal people having locked bootloader should do?
Click to expand...
Click to collapse
Exactly, with those people have warranty expired and locked bootloader as well will have to throw it away?
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
dontbeweakvato said:
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
Click to expand...
Click to collapse
Battery life of death...
dontbeweakvato said:
Blod, I assume thats bootloader something something. Wish everyone would just write ..... Nevermind.
Click to expand...
Click to collapse
Sorry for not writing post in a way everyone can understand easily and using only abbreviation.
BLOD means Boot Loop Of Death
tigsandmitch said:
Battery life of death...
Click to expand...
Click to collapse
*Boot Loop of death
Hardware Issue
frostydawn said:
I don't know if it will work, but for me, and people having a phone which can't even get to recovery but only bootloader, who seem to have nothing to lose, this update will worth the wait. Let's hope that's true and we can get our 6P back to life.
Click to expand...
Click to collapse
If you have exhausted your warranty options, it's time to put the phone down and move on.
v12xke said:
If you have exhausted your warranty options, it's time to put the phone down and move on.
Click to expand...
Click to collapse
Maybe you're right.
I'm not sure if the update will fix my phone, and whether they meant 7.1.2 beta or officially update.
I also have a bad feeling that my phone won't back, but if this phone doesn't return, I have no choice but keep using my old-fashioned Nexus 5.
If the beta update doesn't fix it, maybe I'll just give up or give it a second chance for official update.. but for now, I can see some hope because Huawei said it to me.
There's some news about what I tried, but there ain't good things.
First, I downloaded N4F26O update(https://developers.google.com/android/images), which was uploaded in 2 days ago(Yeah, I only thought about 7.1.2 beta, abd didn't think about this) and installed it.
It didn't work.
So I contacted with Huawei and Google's consumer care center.
Huawei said, to talk about softwares, I should contact with Google.
Google said, they didn't receive any plan of the update which is supposed to fix boot loop. I got confused, since a days ago, Huawei once did say there will be that update.
They also said, if I have a secondary phone, I'd better use that phone and see if the update will be released and fix my phone.
So... I didn't gain anything. Google and Huawei both said they can't assure the update will fix the bootloop, and the only clear solution is to change its motherboard.
Well, I won't give up, at least unti thel 7.1.2 beta's release, but I'm tired and for now, have nothing to do.
I'll just wait for the 7.1.2 beta.
I'll just keep waiting...
If you feel compelled to support, and bring attention to this issue.
https://www.change.org/p/google-inc...utm_source=share_petition&utm_medium=copylink
frostydawn said:
There's some news about what I tried, but there ain't good things... I'll just keep waiting...
Click to expand...
Click to collapse
Since you have nothing to lose, why not try this while you are waiting. I would direct any questions you have about this method to the dev.
v12xke said:
Since you have nothing to lose, why not try this while you are waiting. I would direct any questions you have about this method to the dev.
Click to expand...
Click to collapse
But that's seems to be for devices that's stuck in EDL mode.
I still can access bootloader, so thank you for your advice, but that seems to not work.
I'm afraid that you'll have to let this go.. Huawei is know for telling customers BS on the phone. Even the warranty repair center sucks. They downgrade people their phones and say that the battery issue is now resolved. It really is a shame, but they don't give a rat's *ss about you or any other customer who has already paid for the product.
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Are you S-Off? Does your computer see it?
@dottat
acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.
Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.
acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk
Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk
If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.
Outside of rooting to flash custom Roms is there an official way to downgrade. Nougat is junk. Both of my phone's will not hold a charge more than a couple hours and have issues waking up from sleep, and a myriad of other issues I have with the update.
If not I'll have to smash these and hope for a non updated model upon replacement.
https://forum.xda-developers.com/showthread.php?t=3549458
Sent from my SM-G935V using Tapatalk
Yeah I saw that, I've yet to get Odin to recognize my phone. I guess I'm going to have to try another PC.
Do any of those have the update function killed?
xjman said:
Outside of rooting to flash custom Roms is there an official way to downgrade. Nougat is junk. Both of my phone's will not hold a charge more than a couple hours and have issues waking up from sleep, and a myriad of other issues I have with the update.
If not I'll have to smash these and hope for a non updated model upon replacement.
Click to expand...
Click to collapse
I think problem is with some app you have. Check this first then try to downgrade. Or try clean install by downgrading to APK1 and OTA to BQA6.
If you have problem with phone not recognised by PC, maybe you have problem with hardware it self. Go and exchange. Nougat for me holds battery about 25% longer.
Clicking from Edge of Galaxy
Yeah resetting the phones was my first step. They do it without any other app installed.
I'm just going to have to mess with Odin until my driver's accept the phone. It's been ages since I've had to mess with it, and it js just frustrating
xjman said:
Yeah resetting the phones was my first step. They do it without any other app installed.
I'm just going to have to mess with Odin until my driver's accept the phone. It's been ages since I've had to mess with it, and it js just frustrating
Click to expand...
Click to collapse
Did you yet Princes Odin?
Sent from my SM-G935V using Tapatalk
What? I haven't messed with it since Saturday. I'll update when I get a chance. Today was the first nice day since a storm wed that downed a bunch of junk in my yard, and damaged the roof to my barn.
I likely could have bad drivers or the wrong version of Odin. I've not used Odin since the days of the Samsung moment.
xjman said:
What? I haven't messed with it since Saturday. I'll update when I get a chance. Today was the first nice day since a storm wed that downed a bunch of junk in my yard, and damaged the roof to my barn.
I likely could have bad drivers or the wrong version of Odin. I've not used Odin since the days of the Samsung moment.
Click to expand...
Click to collapse
Try Princes Odin* sorry, autocorrect messed me up.
I have it here https://mega.nz/#!CwQhVCqb!yq_p3ZsUB8kXTSxlhK8XFG6MZRhx7cH3XzSiw36_wc0
Try it with the 4APK1 Firmware. Hope this works.
Sent from my SM-G935V using Tapatalk
Well my problem as escalated on one phone. Now any time I plug it in to charge it tells me moisture detected. Never been wet, never been damp.
Yeah I think I'm just going to move on to different phones. I'm not a fan of the bugs I've encountered on both, and they don't inspire confidence in longer term ownership. Thanks for the help folks.
And now the second phone has the same issue.
There is no way this is hardware related. Is anyone else having issues with theirs. I find it extremely hard to believe two phones having identical issues after an update is coincidence.
Standard OTA update to BQA6 with no problems.
xjman said:
Yeah I saw that, I've yet to get Odin to recognize my phone. I guess I'm going to have to try another PC.
Do any of those have the update function killed?
Click to expand...
Click to collapse
norbarb said:
I think problem is with some app you have. Check this first then try to downgrade. Or try clean install by downgrading to APK1 and OTA to BQA6.
If you have problem with phone not recognised by PC, maybe you have problem with hardware it self. Go and exchange. Nougat for me holds battery about 25% longer.
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Anytime I had an Odin issue it was because of USB drivers. I uninstalled all USB drivers from that device the (complex way) and then everything worked properly. It would seem if I switched USB ports it would work again, then not long after that I would run out of USB ports. I would have to uninstall the drivers manually and reinstall them.
Sent from my SAMSUNG-SM-G935A using Tapatalk
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.