Botched update - Asus ZenFone 3 Questions & Answers

It was a lazy autumn day that fateful afternoon when my Asus Zenfone
3 beeped and told me another occasional FOTA update was ready,
"Estimated time: 10 minutes". I pushed "accept."
Then the reboot ... loading ... reboot ... loading cycles began.
(I don't remember the exact words. It was a month ago and I only now
have regained my composure to write about it.)
Holding down the power button forever didn't help, and one cannot just
take out the battery anymore. It was my first cellphone mid-life
crisis.
Normally geographically astute me got on the wrong bus but at least in
the right direction, got off at this big river on the map that was
easy to follow no matter what mental state, and finally made it to the
Asus Royal Service Center or whatever it is called, in Taichung, TW.
I agreed they could wipe everything off my phone and indeed they fixed
it. Yes it was still under warranty and no I didn't "root" it.
Moral of story: from now on I will only check for updates when I am
nearby their service center and not expecting any important calls, etc.
(I see the version it happened with,
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=184831
was not recalled, meaning the problem only affected me.)

I figured out how to roll back to any firmware I need. Got back my lovely 13.16.5.49 version and with no help from worthless ASUS, who wouldn't even do it even if I RMA it. Apparently they said I should go see a "3rd party phone repair shop, they should be able to do it". What a joke.

Messerschmitt262 said:
I figured out how to roll back to any firmware I need. Got back my lovely 13.16.5.49 version and with no help from worthless ASUS, who wouldn't even do it even if I RMA it. Apparently they said I should go see a "3rd party phone repair shop, they should be able to do it". What a joke.
Click to expand...
Click to collapse
Would you share the rollback method with us, mere mortals?

Just flash the recovery version of the firmware version you want to downgrade to, after which you will have to flash the full firmware image of that firmware version.
Do note that a factory reset might be needed if the phone does not boot after.

Related

Bricked G1, but different solution wanted

I forgot to check what board my phone was when I flashed an SPL to my phone, and now it's bricked.
What I'm looking for is...
How could I call T-Mobile and get my phone swapped out due to something on their end, like an OTA update gone horribly wrong or something
Thanks
exactly what you described as the excuse. you purchased the phone, unboxed it, let it sit overnight and when it asked you to reboot to apply an OTA update (dont use the term OTA or they'll smell something fishy, just say a "software update from you guys" or something), the phone wouldnt turn back on. you tried pulling the battery, restarting it two or three times, and nothing worked. that will get the ball rolling.
unless you're not under your warranty anymore, in which case, youre boned.
Well I got it around November of last year, so it SHOULD still be under warranty.
When did the latest update come out? I would need the date to further push my BS

[Q] Root/Warrant Question Australia

My SGS4 recently stopped working - basically what happened was that it doesn't seem to be drawing power from the battery. The phone will turn on when plugged in (but soon power off), and will show as charging when first plugged into charger (but not charge). However if I unplug it, it won't turn on.
The phone is rooted, and running a custom, Samsung based ROM.
I have tried using a different battery, and the stock battery fully charged with an external charger - and the phone still won't turn on. It's clearly a hardware related issue - drawing current from the battery. I've also tried turning the phone on in download mode, and recovery mode. Both of which do the same as a standard boot - ie. turn on for a while, then turn off.
The phone, being only about 6 months old, was still within warranty period, so I took the phone to Telstra. Not surprisingly, Telstra have said that as there is a Custom ROM on the phone, the warrant is voided. I stated that my understanding is that under Australian law, as it is a hardware fault, and not a fault caused by the ROM, the warranty still stands - however Telstra wouldn't budge and said I have 5 days to decide if I want to pay the $300+ for the repair.
What is my next course of action? Has anybody had a similar issue previously? Is the TIO the next port of call? Or should I be going to NSW Department of Fair Trading?
I'm sure I've read previously that phones are still covered under warranty after rooting etc, if it can be shown that it's a hardware fault, not a software fault. As the battery doesn't seem to be powering the phone, this clearly seems to be the case - esp. as it is the same in download mode and recovery mode.
Any help would be great. Please don't post pointing out that I rooted my phone so THAT's my own fault etc. These posts aren't helpful, I already have know that.
is it too late to throw the original Telstra ROM on it and take it back to another store? If you were careful you would still be on the old bootloader, so there shouldn't be any KNOX concerns.
Thanks for the response.
It may not be too late, however I cannot flash it, as the phone won't stay on for more than a second or two. Even in download mode.
I was on the old bootloader, yes. So knox is fine.
abbaskip said:
Thanks for the response.
It may not be too late, however I cannot flash it, as the phone won't stay on for more than a second or two. Even in download mode.
I was on the old bootloader, yes. So knox is fine.
Click to expand...
Click to collapse
Thats good to hear that your still on oldbootloader but the problem still will remain if you cant do something about it. Can you pls pull the battery out for atleast 5 to 10 minutes to let it settle abit and put it back after. Thanks
Edit: Would you mind checking your battery Serial S/N if it starts with BD ? thank you.
Sent from Hell ?
I am not too sure about Australian law but under EU law you are fine. This does not however apply to the rest of the world.
Either way if you have rooted outisde EU you are pretty much done for (unless there is a law). its extremely hard to prove that your rooting / apps or whatever you have on it has not caused the Hardware fault.
I understand that it is battery not charging etc, is there anyway while phone is connected directly to mains to flash it from usb card? if you could do this and 'unroot' the phone it should be stock or give you enough to trick kies into allowing you to update?
Its a pity you cannot power it through your PC and enter download mode and flash.. (or can you?)
Repulsa said:
Thats good to hear that your still on oldbootloader but the problem still will remain if you cant do something about it. Can you pls pull the battery out for atleast 5 to 10 minutes to let it settle abit and put it back after. Thanks
Edit: Would you mind checking your battery Serial S/N if it starts with BD ? thank you.
Sent from Hell ��
Click to expand...
Click to collapse
Hi,
It's definitely no fault of the battery. I've tried various batteries, left the phone without a battery for days etc. (See this thread for details of this issue: http://forum.xda-developers.com/showthread.php?t=2581229&page=2)
Battery serial starts AA.
A|ex said:
I am not too sure about Australian law but under EU law you are fine. This does not however apply to the rest of the world.
Either way if you have rooted outisde EU you are pretty much done for (unless there is a law). its extremely hard to prove that your rooting / apps or whatever you have on it has not caused the Hardware fault.
Click to expand...
Click to collapse
I think that's the issue here. Basically a big company taking advantage of the small man. They have the upper hand, they know it, so they force you to pay.
It has to be a hardware fault, based on all of the behaviour (ie. phone booting in all modes - but dying in a handful of seconds), but it's easy for them to wash their hands of the warrant, by saying I modified the device - even if it is irrelevant to the problem.
I understand that it is battery not charging etc, is there anyway while phone is connected directly to mains to flash it from usb card? if you could do this and 'unroot' the phone it should be stock or give you enough to trick kies into allowing you to update?
Its a pity you cannot power it through your PC and enter download mode and flash.. (or can you?)
Click to expand...
Click to collapse
Unfortunately not. Even when the phone powers up, it shows 0% and shuts down very soon after. If I plug it into the PC, then turn it on, it powers up and again turns off not long after. This same behaviour carries across to download mode and recovery mode. ie. It boots, but then dies within a few seconds.
Think I'll complain to the ombudsman.
Based on the Australian law, the ombudsman can assist as follows:
The TIO has jurisdiction to investigate complaints about faulty mobile handsets where the handset is supplied as part of a contractual relationship, between the TIO Member carrier or carriage service provider and the complainant, which involves the provision of a carriage service to be accessed via that handset.
The TIO does not have jurisdiction to investigate complaints where the customer supplies the handset (i.e. they have purchased it outright and separately from their purchase of network services), or where the initial contract has expired and the customer retains and continues to use the handset. Where appropriate, the TIO will refer out-of-jurisdiction complaints to the relevant Department of Fair Trading or Consumer Affairs.
This position statement does not relate to any manufacturer's warranty. The TIO will investigate complaints about faulty handsets provided as part of a bundled service, even where the initial handset warranty period may have expired.
Under the TIO's Operational Guidelines the TIO will only investigate complaints about faulty handsets where the fault is caused by an inherent defect or otherwise and is not caused by misuse by the customer. The TIO may also decline to investigate a complaint where a customer has not produced a handset for inspection/assessment after being asked to do so by their provider or the TIO.
As the defect was not caused by myself - as the rooting and custom software did not lead to the hardware defect, I believe it falls under the TIO jurisdiction.
As a long shot would a juice pack for a S4 work such as a morphie as you can charge and also sync? (not sure if the phone uses the pack or whether the pack is used to charge the battery, if the latter it will not work for you)
or maybe a mains powered dock and usb cable to PC?
Given TIO is able to look at something like this as the handset is bundled, go to them. Better them than CA/FT/whomever, as TIO is the specialist industry body.
Or....This sounds like it may be a simple USB board/port failure which is quick/easy/cheap (maybe 15 bucks) to replace yourself. You could always try that, and if that doesn't end up being the issue then go the TIO route.
MistahBungle said:
Given TIO is able to look at something like this as the handset is bundled, go to them. Better them than CA/FT/whomever, as TIO is the specialist industry body.
Or....This sounds like it may be a simple USB board/port failure which is quick/easy/cheap (maybe 15 bucks) to replace yourself. You could always try that, and if that doesn't end up being the issue then go the TIO route.
Click to expand...
Click to collapse
I don't believe it's a usb port failure, as fully charged batteries haven't worked. It's not the USB port that's issue, but that the phone isn't drawing current from the battery.
A|ex said:
As a long shot would a juice pack for a S4 work such as a morphie as you can charge and also sync? (not sure if the phone uses the pack or whether the pack is used to charge the battery, if the latter it will not work for you)
or maybe a mains powered dock and usb cable to PC?
Click to expand...
Click to collapse
What's a juice pack?
I have a dock, bit it has the same issue as charging direct - the phone turns off after about one second
So the latest news – I tried to phone the store again and this Telstra Shop NEVER answer their phone – I have their direct local line, given to me by the Telstra Call Centre, and even tried calling them as I walked through the door – as I'd tried calling throughout the day with no answer. The phone on the desks rang, and was ignored by staff who were standing around having a conversation. Sure explains why they weren't answering the phone throughout the day! So anyway, after not getting through to the store, I called the Telstra Call Centre again, explained the situation, and that I was quoted ~$350 for the quote. The operator looked into it, put me into someone who was escalating the case. After a short chat, the person said they'd call me back after speaking to the tech, getting all the details etc etc. Long story short, they call me back and gave me a waiver code. Said that I can request the store repair the phone, and give that waiver which will mean I'm not charged.
I went into the Telstra store this evening (which is after I kept trying to call them all day as above), and told them the situation. They didn't understand why I was telling them, and said I needed to tell the tech centre – who they can't provide contact number for (and who had told me when giving me the quote to respond to the store within 5 working days). Eventually a guy that knew what he was doing explained to my staff member that he just needed to email/message the tech responsible, provide the waiver and confirm to go ahead with repairs.
Now I've just got to wait for the call saying my phone is ready to be picked up Hopefully they don't stuff that up!!
abbaskip said:
So the latest news – I tried to phone the store again and this Telstra Shop NEVER answer their phone – I have their direct local line, given to me by the Telstra Call Centre, and even tried calling them as I walked through the door – as I'd tried calling throughout the day with no answer. The phone on the desks rang, and was ignored by staff who were standing around having a conversation. Sure explains why they weren't answering the phone throughout the day! So anyway, after not getting through to the store, I called the Telstra Call Centre again, explained the situation, and that I was quoted ~$350 for the quote. The operator looked into it, put me into someone who was escalating the case. After a short chat, the person said they'd call me back after speaking to the tech, getting all the details etc etc. Long story short, they call me back and gave me a waiver code. Said that I can request the store repair the phone, and give that waiver which will mean I'm not charged.
I went into the Telstra store this evening (which is after I kept trying to call them all day as above), and told them the situation. They didn't understand why I was telling them, and said I needed to tell the tech centre – who they can't provide contact number for (and who had told me when giving me the quote to respond to the store within 5 working days). Eventually a guy that knew what he was doing explained to my staff member that he just needed to email/message the tech responsible, provide the waiver and confirm to go ahead with repairs.
Now I've just got to wait for the call saying my phone is ready to be picked up Hopefully they don't stuff that up!!
Click to expand...
Click to collapse
Congrats on the Win! but i bet they will slap you in the face with KNOX
You mean they'll put me on the new BL? Yes, I'm sure of it. Tech centres always do a factory reset and load the latest firmware. They give you a warranty on the repair, so they ensure all is stock.
If you mean they will refuse to repair because of knox, I'm confident they won't. I'm on the old BL, and even so I've been given the quote and waiver for the quote already.
My phone has been returned in working order. Of course, Telstra being Telstra, I was told that they couldn't add the waiver at the shop, so we would be billed, and then have to apply for a credit.
Oh, and they've updated to a Knox enabled ROM obviously but that was expected
Sent from my GT-I9505 using Tapatalk

Information on box updates (bricked box outside USA)

I have posted before how I purchased 3 FireTVs. I set up IP blocking and 2 of the 3 booted fine. 1 of the 3 said there was an update and couldnt pick it up and hence wouldnt boot.
After many frustrations, I thought I would let it update and hope to not get the most recent update.. Various reports have said these dont increment to the most recent one every time. But it still wouldnt update.
I had to shelve the messing around due to travel but tried again last night.. Same situation.
I just had an hour long chat with a tech support at amazon who wasnt dumb.. It seems there was an early firware version which had a forced update and would not skip it. It would seem one of my 3 boxes are on this early firmware. Then to make matters worse, amazon blocks non USA ISPs from downloading the update. Essentially amazon sell a box that wont boot without the update and wont give the update to non USA IPs. Thats a bit sucky !!
Is it well known that the back button and right direction, held for 15 - 30 seconds enables a factory reset ??
The tech guy is now trying with higher level tech to see if he can get me a version of the FW that I can ADP to the box through the recovery console. Has anyone done any testing with this, has anyone flashed a FW via recovery console and ADP ??
Right now one of my 3 boxes is a brick, and I have done nothing to this box, thats entirely amazon, which I do feel pissed off about, selling a box that will only boot in one geographical market is a bit extreme.
Phat Phreddy said:
I have posted before how I purchased 3 FireTVs. I set up IP blocking and 2 of the 3 booted fine. 1 of the 3 said there was an update and couldnt pick it up and hence wouldnt boot.
After many frustrations, I thought I would let it update and hope to not get the most recent update.. Various reports have said these dont increment to the most recent one every time. But it still wouldnt update.
I had to shelve the messing around due to travel but tried again last night.. Same situation.
I just had an hour long chat with a tech support at amazon who wasnt dumb.. It seems there was an early firware version which had a forced update and would not skip it. It would seem one of my 3 boxes are on this early firmware. Then to make matters worse, amazon blocks non USA ISPs from downloading the update. Essentially amazon sell a box that wont boot without the update and wont give the update to non USA IPs. Thats a bit sucky !!
Is it well known that the back button and right direction, held for 15 - 30 seconds enables a factory reset ??
The tech guy is now trying with higher level tech to see if he can get me a version of the FW that I can ADP to the box through the recovery console. Has anyone done any testing with this, has anyone flashed a FW via recovery console and ADP ??
Right now one of my 3 boxes is a brick, and I have done nothing to this box, thats entirely amazon, which I do feel pissed off about, selling a box that will only boot in one geographical market is a bit extreme.
Click to expand...
Click to collapse
use a VPN, problem solved.
How can I put in a VPNs details on a box that wont boot and with only a (dumb) router ??
Sure I could do it on a PC on my net, but not seeing how to set up a VPN without a device in the middle.
Phat Phreddy said:
I have posted before how I purchased 3 FireTVs. I set up IP blocking and 2 of the 3 booted fine. 1 of the 3 said there was an update and couldnt pick it up and hence wouldnt boot.
After many frustrations, I thought I would let it update and hope to not get the most recent update.. Various reports have said these dont increment to the most recent one every time. But it still wouldnt update.
I had to shelve the messing around due to travel but tried again last night.. Same situation.
I just had an hour long chat with a tech support at amazon who wasnt dumb.. It seems there was an early firware version which had a forced update and would not skip it. It would seem one of my 3 boxes are on this early firmware. Then to make matters worse, amazon blocks non USA ISPs from downloading the update. Essentially amazon sell a box that wont boot without the update and wont give the update to non USA IPs. Thats a bit sucky !!
Is it well known that the back button and right direction, held for 15 - 30 seconds enables a factory reset ??
The tech guy is now trying with higher level tech to see if he can get me a version of the FW that I can ADP to the box through the recovery console. Has anyone done any testing with this, has anyone flashed a FW via recovery console and ADP ??
Right now one of my 3 boxes is a brick, and I have done nothing to this box, thats entirely amazon, which I do feel pissed off about, selling a box that will only boot in one geographical market is a bit extreme.
Click to expand...
Click to collapse
If you can get them to give you the update to work through recovery console that would be great. Seems like that would be the way for everyone to be able to downgrade unrootable firmware.
tselling said:
If you can get them to give you the update to work through recovery console that would be great. Seems like that would be the way for everyone to be able to downgrade unrootable firmware.
Click to expand...
Click to collapse
Sure.. And the tech guy was really trying for me.. Wasnt stupid.. and assured me he would push as much and follow up..
But will the upper level tech allow that ?? Who knows..
Phat Phreddy said:
Sure.. And the tech guy was really trying for me.. Wasnt stupid.. and assured me he would push as much and follow up..
But will the upper level tech allow that ?? Who knows..
Click to expand...
Click to collapse
If they do manage to tell you how to update through recovery, make sure you write down everything.
Phat Phreddy said:
Sure.. And the tech guy was really trying for me.. Wasnt stupid.. and assured me he would push as much and follow up..
But will the upper level tech allow that ?? Who knows..
Click to expand...
Click to collapse
What rbox said! Be sure to write down the entire procedure.
Also, I believe the factory reset via remote is holding Home and right direction buttons, not back and right direction. Either I'm mistaken or both work. I'll give back and right direction a try later on.
I believe it was back and right.. he said for 30 seconds but it only took 10 or 15 until a dialogue poped up asking to reset... Maybe if you hold it for 30 it goes past the dialogue.

I am getting a replacement.....but Im rooted......

I asked Verizon to help me with my phone, as it booted into TWRP and not the OS, because I accidentally accepted the OTA update. So they are sending me a replacement, because I pretended I didn't know what happened, and I said I looked up how to back up android and It said to install an app and I installed it and it had a loading bar that just said done. He is sending me a replacement because of this, and he said the broken phone is being sent to LG for repair. I am rooted, but when they find out (if they do) Will they fine me? or will they just try to fix it? The guy said they will only fine you if it has any physical damage. The replacement is coming tomorrow and I have to send the broken one back within 5 days of it arriving. Unfortunately, I found out the next day how to get out of it, but oh well. Its too late now. But will they fine me or force me to give back the replacement?
Anybody?
I did this as well- I was able to use a tool to unroot it, and sent it back and they were none the wiser.
Verizon will charge you the full amount because it's technically out of warranty once you mod it. However, LG doesn't care if you send the phone directly to them.

Random boot loop, can't get anywhere in recovery

I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.
Good luck on either with the warranty or bringing it back to life.
I also have problems such as your support Huawei says four weeks of waiting
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.

Resources