Related
Hi Everyone,
I searched and read many threads but didn't see my problem listed. I apologize if it has and I missed it. I received a Kindle Fire for Christmas yesterday. I plugged it in and let it reach a full charge. I then went through the registration steps. Upon completing registration, it automatically went to an updating screen. I left it alone to finish updating. After returning over an hour later I find it stuck on the "kindle fire" black screen. I've tried many hard resets but it always boots to the same black screen.
As I mentioned, it was brand new and I did not attempt to do any rooting or custom installs. If I plug it into my computer, Windows XP recognizes a device but does not having any drivers to install for it. Is there anything I can do to unbrick it?
Thank you in advance.
if u didnt install any roms like cm7 or havent even rooted it yet then its probably a hardware prob.. Try holding down power for like 20 secsand see what happens
Thanks for the suggestion movieaddict, but I've tried that many times now and it still just brings up the kindle fire screen.
Not as helpful as I would like a post to be, but I've had it freeze on that screen a few times as well and a hardware reset has always fixed it. If you have not rooted or done anytthing to void your warranty I see no reason to not contact amazon customer support as it is their problem to fix and hopefully they can, or get you a new one in a hurry. Good Luck, I know this is frustrating, my first one had a flickering line on the lcd and had to be rma'd.
Sent from my Epic (sleeper rom) using XDA App
Thanks Kapurnicus. I've already placed a called to Amazon and they are sending a new one and it should arrive later this week. I just thought I could play around and possibly fix this one in the meantime.
I don't blame you. Might as well try. Sorry I couldn't be of more help, mine is still stock lol. I only screw with the phone for now. Just have a new launcher and some streaming apps on the kindle, although, I still love it. Haven't put it down in days. Its going to be your best friend lol.
Sent from my Epic (sleeper rom) using XDA App.
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app
wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:
Ok well skip this first part if you don't want a story,
I got my nexus around febuary as a gift for my birthday as a little toy and music, I went right ahead and unlocked the bootloader and rooted it for future use as well as going ahead and putting TWRP on it with multirom for ubuntu tinkering but never bothered flashing a new android and only flashed a new kernal to be able to tweek the clock speeds and never bothered with that ether becuase the nexus was fast enfough for everything i could throw at it.
Now a few days ago I decided to do a factory reset from TWRP to put a stock rom on it and clean everything off it, Then it just refused to boot BUT i still had bootloader access so all was well and i used the lazy option and oppted to use the nexus toolkit and told it to just flash the stock rom onto it. It finished then i went to restart it and it died.
Now since that death it will not boot, it will not get to the bootloader or recovery menu, it wont respond to any buttons at all, It won't dispaly the chargeing icon when pluged it nor will the screen turn on at all and to top it all off even when i plug it into my laptop it will not even notace it at all.
I have seen simlar problems but none exactly the same, I tryed to return it today but to put it lightly pc world are a bunch of asshats who woudent exchange or repair it becuase the receipt was slightly damaged so returning it isent an option.
Feel free to call me an idiot and everything but for any help at all I thank you in advance.
You should still be covered under the 12 month warranty from Asus with the warranty card you got along with your device.
Username invalid said:
You should still be covered under the 12 month warranty from Asus with the warranty card you got along with your device.
Click to expand...
Click to collapse
Will they not not just tell me to go to the resaler?
My headset from asus broke and they told me I had to set up the rma with the online resaler i bought it from here.
There's no harm in atleast going to the Asus website and make an account then register your tablet.
Username invalid said:
There's no harm in atleast going to the Asus website and make an account then register your tablet.
Click to expand...
Click to collapse
I've done so now, but I hold no hope with the support asus offers
Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,
Rest in peace. Contact Oneplus support m8 and send that **** back
Sent from my ONE A2003 using XDA Free mobile app
Small Update: I just wish you all to never wait for the OP customer service / technical support. (waiting time is really outrageous for a company which support customers online).
In addition, the technical support team sent me files to download (while i'm explaining her that i tried all of those already) + sending me ROM for OPO (Cyanogen........)
I was in a kind of a shock, while i'm correcting her and telling her there's no CM for OPT and the files she sent me (CM11s?!) are not the correct ones, she sent another mail.
Anyways, i guess you have to go for that "entire process" until they allow you to get a refund.
Hate to type it, but for me it's probably "Never Again" instead of "Never Settle".
CS is the same for most companies, someone in a call centre with little knowledge and a book of instructions to follow. There's no point you saying "I did this already" because they get in trouble if they don't follow the script they have.
I have got the black screen of death too and im a couple of mot=nths into using it
[/COLOR]
Tricepz said:
Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,
Click to expand...
Click to collapse
So the phone should be responsive even if you cant see the screen. SOOO forget letting it drain, but instead, connect it to pc and install latest twrp. Or crm. Unlocking the bootloader may be difficult as you have to use the power and volume buttons to choose yes or no but i think it starts on yes so just press the power button. Now copy over any rom and gapps (i used exodus and lollipop gapps). Flash them and the phone will boot up surprisingly quickly. This will hopefully stop you from wasting time with support teams that are already overloaded with queries. I hope this helped
I have the same problem I dont know what to do! please someone help !
This is really old news, I'll just add that I've sent the device back and got my money back,rocking a new lg v10 and happy a hell.
Sent from my LG-H960 using Tapatalk
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.