Related
My phone, which I've had since waiting in line on March 24th quit on me today. I'm not sure if it was the culprit but, I installed a program called Lookout mobile security last night 5/6. When I started the phone this morning put it on the table, got some java and when I got back nothing..no buttons working...ok..no problem tried a soft reset...nothing..ok now starting to get worried. pluged into power source..boot up screen. whew..low battery. then blank, a few seconds..boot up screen AGAIN!..by now I'm in full freakout...Attempted to calm down.. didn't work..thought ok..most everything is backed up..lets do a hard reset..didn't WANT to but anyway! Did the hard reset .. Still had the same problem...Had to pinch myself HARD to make sure this wasn't a nightmare. Went to the TMobile store and the associate put me in touch with technical support (they were Super) Going to give me a new phone but, have to wait until next Friday to get it...and then tweaking and rebuilding it to what I want...I should have been ready for this coming from an iphone...All it takes is one $%@# program again, not saying it was the one mentioned above but, one with a malicious code or something that destroyed over five weeks of building a phone from scratch. Sorry about the rant... I still LOVE this phone. .
so you couldn't even boot it in to the bootloader? wow! Maybe you should flash HardSPL before trying to install that program again as there is far less chance of bricking it if you have HardSPL installed. Even if the rom gets completely stuffed, you can still boot it and reflash from SD.
All I can recommend is install a ROM via Micro SD card and maybe doing a Task 29 before you reinstall a ROM
for US Tmobile: http://forum.xda-developers.com/showthread.php?t=653614
For Leo: http://forum.xda-developers.com/showthread.php?t=609477
Or maybe try this thread: http://forum.xda-developers.com/showthread.php?t=668347
If those don't work then I don't know what else to recommend
They want my old phone back once I get the new one so, I'm going
to let them have it just as I turned it on yesterday. Let them
find out what the problem was created by.
I was about to install that "lookout" software...but after reading this I might as well hold on.
did you leave it on the charger overnight or did you just turn on your phone in the morning.
if you didnt have it charge all night, maybe all you needed to do was leave it on the charger a little longer before starting it back on.
i noticed that some phones with a dead battery and on the charger will sometimes not stay on until it has gotten a minimum charge on the battery.
Damitu said:
..most everything is backed up..<SNIP>...and then tweaking and rebuilding it to what I want...
Click to expand...
Click to collapse
Setting up the new phone shouldn't be a big deal if you did actually backup; just stick the old microSD in the new phone and run whatever backup app you had on the card.
I put it on the power supply and it is in the constant loop of
the first screen that appears. I am going to seriously look into
HardSPL. Thanks to all the good input from everybody.
Well now even customer service is at a loss. They cannot phantom why why two separate phones have the same problem. While I had CS on the phone we went thru various senario's to try to get the phone to operate properly. I even had them give me a new SIM card and that did not work...I suggested the problem might be the battery as it could have gone bad. You guys think the phone is playing hard to get--try to find a replacement battery! No stores within a 20 mile radius had one in stock....! Needless to say they are going to ship me yet another phone. plus a new battery and hopefully it will take care of the problem. The sales associate did a hard reset on both my old and the new phone without results so that unfortnately is not a viable solution. Now I am in the game I hate the most........The waiting one! ..
c_legaspi said:
did you leave it on the charger overnight or did you just turn on your phone in the morning.
if you didnt have it charge all night, maybe all you needed to do was leave it on the charger a little longer before starting it back on.
i noticed that some phones with a dead battery and on the charger will sometimes not stay on until it has gotten a minimum charge on the battery.
Click to expand...
Click to collapse
^^ what the op says above. This happened to me (and my gf as well) on our HD2s. The first time (mines) this happened, i hooked it up onto my car charger and immediately tried to turn it on.. it would go onto the TMO screen, but quickly shut down and loop. After realizing I may be trying to jump the step, I unhooked it from the charger, took the battery off, put it back on, hooked it back onto the charger and let it sit for about 10-20 minutes charging. Turned it back on and viola! It wasn't a brick.. I can almost guarantee this is your problem.
But I may be wrong lol...
So, now after 2 replacement phone sent to me, I find out that
it was the battery all along. Problem is that after the second phone
arrived and I had the same problem I called customer service and
explained it to them....They said a battery would be sent next day
air...Ok...called the next day and was told that the rep never sent
in the order...Long story short....I've almost been without my phone
for two weeks now and, all I need is a frelling battery.
Problem is there are NONE around me..I've tried every tm store in
the area, All radio shacks batteries plus...you name it....
I am being sent a battery UPS ground...could take 7 more days.
Just took the battery from my fiance's phone and it works
so, right now I would pay a ransom for a battery just to have my
phone back!
I had to do a hard reset after downloading that lookout trial.
at this point I don't know what caused it..Has anyone ever heard
of an application causing the battery to go bad?...I worked really
hard to keep the battery I had in good condition.. I hope UPS
delivers soon!
This is odd I have used Lookout Mobile on my phone since I had it. Mind you not had it for long, since April but still its never bricked or did anything that hindered the phone. I maybe another program.
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this
lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.
its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running
yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???
did you try hooking up to kies?
Yes but that does nothing since it never fully boots.
3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.
my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.
So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.
Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.
I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.
I think I have finally, fully bricked my Droid 2.
A little background: This is my fifth one, mostly all for hardware issues stemming from poor craftsmanship in the refurbed phones. This one though, is gone as far as I can see it. I got this phone last week, and had waiting a week to make sure everything was fine. It was, so last night I rooted it and tried to put Epic 2.7 on it. It failed Epicly (no pun intented) and I was forced to do a full SBF on it. In the process, something got a hiccup and I was left with Droid 2 flashing "Service Required" and a RSD Lite telling me it had 100% successfully flashed. I tried once again to flash it using the SBF from a different source, and the battery died halfway through. The USB port won't even engage now so I can't charge my battery, even when it's off. When I try to turn it on, it says "Service Required" then below, it flashed "Battery Low, cannot run" or something to that effect. Well, can't flash it if I can't charge it, eh? I'm stuck in a catch-22 and I can't really see a way out.
I'm going to try my luck tomorrow and take it back to Verizon, claim it's their fault (my ERI reflash code was manually changed in one of my older phones I had received, so anything is possible now) and jump ship to a Galaxy or something non-HTC. In the mean time, is there anything I could try and do to remedy this?
Note: I didn't know where to put this, sorry if it's in the wrong section.
drburke said:
I think I have finally, fully bricked my Droid 2.
A little background: This is my fifth one, mostly all for hardware issues stemming from poor craftsmanship in the refurbed phones. This one though, is gone as far as I can see it. I got this phone last week, and had waiting a week to make sure everything was fine. It was, so last night I rooted it and tried to put Epic 2.7 on it. It failed Epicly (no pun intented) and I was forced to do a full SBF on it. In the process, something got a hiccup and I was left with Droid 2 flashing "Service Required" and a RSD Lite telling me it had 100% successfully flashed. I tried once again to flash it using the SBF from a different source, and the battery died halfway through. The USB port won't even engage now so I can't charge my battery, even when it's off. When I try to turn it on, it says "Service Required" then below, it flashed "Battery Low, cannot run" or something to that effect. Well, can't flash it if I can't charge it, eh? I'm stuck in a catch-22 and I can't really see a way out.
I'm going to try my luck tomorrow and take it back to Verizon, claim it's their fault (my ERI reflash code was manually changed in one of my older phones I had received, so anything is possible now) and jump ship to a Galaxy or something non-HTC. In the mean time, is there anything I could try and do to remedy this?
Note: I didn't know where to put this, sorry if it's in the wrong section.
Click to expand...
Click to collapse
This is the correct section And if your phone turns on at all, it's not bricked Your phone would need to be 100% gone to be bricked
Hmm. Perhaps the statement "My phone hates me and put me in a catch-22" is a better qualified statement then? haha.
drburke said:
Hmm. Perhaps the statement "My phone hates me and put me in a catch-22" is a better qualified statement then? haha.
Click to expand...
Click to collapse
Probably I was just trying to cheer you up
For you to be able to do anything if your battery is really dead you need to find away to charge it or get a charged battery to try to do another SBF. Make sure the SBF is the 2.3.20 verizon version (assuming you have the 2.3.2 update)because the 2.2.0 version won't load on your updated D2. If you aren't succeding in windows there is a linux method that anybody can try via my ubuntu livecd. I'll update this post with links when I get on my laptop.
Sent from my DROID2 using XDA App
Reboot into recovery.you should see the ! Android. Press the search button on the keyboard. Scroll down to wipe data with the arrow keys and press ok. Delete to go back to the main screen. Then go to reboot and hit ok.
Sent from my DROID2 using XDA App
This happened to me as well. You need to find another battery to use or buy a 3rd party external charger.
The phone will only charge the battery when software is installed. The phone is nowhere near bricked but you do need a full battery to SBF back to a workable state.
I don't think Epic 2.7 should be used on updated D2's because I don't think the ROM is compatible with the updated version. I could be wrong though.
I seem to remember an editor at engadget or bgr had this problem on an original droid? I think they made some Frankenstein charger with a jumper or something and got it to charge so they could fix their software. They wrote an article about it.
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.
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.