Related
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
jcip17 said:
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
Click to expand...
Click to collapse
Thanks man. You're one of the people who make XDA such a cool place. It ain't like this is goodbye forever. I'll be in here fairly often. Tapatalk keeps me notified of what goes on. See you later.
Sent from my SCH-I535 using Tapatalk
Sorry to hear you're leaving. You've been a great help to a lot of us. I share your feelings toward Verizon, they are just too big to care. So go on.... have some fun with the new toy....there's so much development over there... I'm actually over in the note4 snapdragon side more recently because I'm running all other than Verizon MM stuff. Anyways thanks Stuey for your contributions and help!
Sent from my SM-N920V using XDA-Developers mobile app
stueycaster said:
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Click to expand...
Click to collapse
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Nice.
Sent from my SM-N920V using XDA-Developers mobile app
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
ryanbg said:
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
Click to expand...
Click to collapse
Isn't that going to overwrite the Dev Ed bootloader? I guess that's ok though because it's useless as a Developer Edition anyway right? And then I can do the unlock procedure.
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
stueycaster said:
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
Click to expand...
Click to collapse
We'll get DE back after you are stable. Uninstall Verizon Software Repair Assistant and Kies if you have it. To me, it looks like a USB/Driver/Software conflict going on preventing a successful flash. Try a different computer, and a different USB cable. Something is interrupting the write process.
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
stueycaster said:
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
Click to expand...
Click to collapse
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Dark_Plasma said:
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Click to expand...
Click to collapse
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Sorry to hear that....hoped you could revive it. For sure these things get blistering hot! I've been flashing like crazy this past week thinking my phone is cookin! So I know what your saying could be the culprit. Still hoping you find a way!
Sent from my SM-N920V using XDA-Developers mobile app
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.
AND WE CAN'T. If i'm wrong I'd sure appreciate a link. All the solutions i've tried result with password./pin/pattern corruption issues making it impossible to use a screen lock (and correspondingly google pay).
jaysonic88 said:
AND WE CAN'T. If i'm wrong I'd sure appreciate a link. All the solutions i've tried result with password./pin/pattern corruption issues making it impossible to use a screen lock (and correspondingly google pay).
Click to expand...
Click to collapse
Just use latest twrp and encrypted device. Works well. Twrp can decrypt so all works just fine.
Sent from my ONEPLUS A6013 using Tapatalk
It is much improved on 3.3.1-30 but id still prefer true decryption. I just find it odd that the models prior and following can do it but not 6T.
jaysonic88 said:
It is much improved on 3.3.1-30 but id still prefer true decryption. I just find it odd that the models prior and following can do it but not 6T.
Click to expand...
Click to collapse
What do you care about decryption, what do you need it for?
Sent from my ONEPLUS A6013 using Tapatalk
Decryption just seems like a fairly stupid thing to do from a security standpoint, and I don't see any benefit.
DaOldMan said:
What do you care about decryption, what do you need it for?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Well for one you can still scramble your data if you mess up while updating to a new rom. For another fiddling with the passcode every time i go into TWRP is tedious. What if i don't have any damn data i'm concerned about being stolen? What are the damn odds that i'm going to have my phone picked up by a stranger who then knows how to get into TWRP and delete the files that enable the passcodes. And then oh heaven forbid they have access to pictures of my dog. Why do i have to justify this? Obviously i'm not the only one as every other model supports it.
jaysonic88 said:
Well for one you can still scramble your data if you mess up while updating to a new rom. For another fiddling with the passcode every time i go into TWRP is tedious. What if i don't have any damn data i'm concerned about being stolen? What are the damn odds that i'm going to have my phone picked up by a stranger who then knows how to get into TWRP and delete the files that enable the passcodes. And then oh heaven forbid they have access to pictures of my dog. Why do i have to justify this? Obviously i'm not the only one as every other model supports it.
Click to expand...
Click to collapse
You have some good points there. I also miss my decrypted Note 3. But we are not alone on this planet, so some may have more then pictures of their dog. So I guess encryption is needed by many other people. About why this device behaves badly if you try to use it decrypted, I am not really sure. Maybe @kristofpetho knows about this a bit more then me, especially if it's kernel related.
DaOldMan said:
You have some good points there. I also miss my decrypted Note 3. But we are not alone on this planet, so some may have more then pictures of their dog. So I guess encryption is needed by many other people. About why this device behaves badly if you try to use it decrypted, I am not really sure. Maybe @kristofpetho knows about this a bit more then me, especially if it's kernel related.
Click to expand...
Click to collapse
Thanks for the courteous reply (these days i expect to get blasted). I agree that encryption is a worthwhile feature for many...most even. For me though, i like the flexibility. I bet it's a minor fix over it's big brother OP7pro, but could be wrong.
jaysonic88 said:
Well for one you can still scramble your data if you mess up while updating to a new rom. For another fiddling with the passcode every time i go into TWRP is tedious. What if i don't have any damn data i'm concerned about being stolen? What are the damn odds that i'm going to have my phone picked up by a stranger who then knows how to get into TWRP and delete the files that enable the passcodes. And then oh heaven forbid they have access to pictures of my dog. Why do i have to justify this? Obviously i'm not the only one as every other model supports it.
Click to expand...
Click to collapse
???
I hear ya. I don't even use a lockscreen pw much of the time. Unless someone killed me nobody even has a chance to get my phone. It's either in my pocket or I'm on it 24/7.
My Moto G7 Power is same way. Decrypt and lockscreen goes out.
Sent from my moto g(7) power using XDA Labs
So I've had this for a few days now and I've noticed it's dropped connection quite a few times, and when, IF it reconnects without rebooting, it usually gets stuck on H+.
I'm currently on OOS 10.3.0. Tried a custom ROM, same issue. Tried regarding to 9.0.11, same issue. Bought a new SIM card, same issue. I'm thinking I have to get back to the T-Mobile 9.0.16 and send this back. I'm getting sick of this. Anyone have any ideas what the issue could be?
Sorry you are having so much trouble. This won't help, but my 6T global model (not T-mo) is the best reception phone I've ever had, at least on the ATT network.
It's hard to tell whether your problem is hardware based, something to do with the T-mo to global OS transition, or something else.
I have had it a full year and have no plans to swap it any time soon. I'm stock, unrooted (first time ever), and still on Pie for now, having deferred the update until it settles in a bit.
Good luck whatever you decide to do!
Sent from my ONEPLUS A6013 using Tapatalk
Signal is still dropping!
I'm having second thoughts about this phone. Two SIM cards and several calls to my cell provider and still no fix in sight.
I'm gonna see if the Swappa seller will send me a replacement.
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Frankenscript said:
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Scott said:
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Click to expand...
Click to collapse
I did exactly that, back to T-Mobile firmware, and the issue still existed. So I returned the device.