Related
I have flashed my three mobile to the latest .184 release, and just before doing this I used flashtools to make a backup. Somewhat stupidly I went ahead and flashed without checking if my backup actually works, I have checked since and it just tells me to unplug and turn on debugging etc (they are both on).
Has anybody got an original three firmware they can upload in case I need it - since doing this I have also noticed problems with wifi tethering so it might need sending back
If no one can help (if anyone can it would still be appreciated), can anyone tell me if it will cause me problems getting my phone repaired.
Although I originally flashed the .184 update uploaded here I have since run a SEUS reinstall so technically the firmware is 100% official SE generic firmware. Will this mean it will be fixed as all they will know is that it is their software on.
I had some worrying news when I asked in a carphone warehouse repair center today, the engineer (I have doubts they actually hire engineers) told me if he finds I have changed the software he is required to inform SE themselves the phone details and have the warranty voided. This was after actually telling him that I had changed it though, and he might have been thinking custom - I also didn't explain the SEUS update that means it is completely official.
Anyone any advice? I definitely have a hardware problem that needs fixing so I am desperate now.
from what I remember the only difference was the bootscreen and the three app and a couple of games I doubt you will have any major problems. I'm pretty sure the main thing they didn't like with debranded firmware was you could set it to just use the Orange network which cost them more money, but now they are 3G only...
With WIFI tethering try changing the name of the hotspot I couldn't get it to connect at all, changed the name and it worked fine.
Thanks for the suggestion, I just tried renaming but it has the same problem. I can connect for 2 minutes then it stops working and needs turning off and on. It is identicle no matter what I do; after using SEUS or restaring the phone. I am pretty sure it is a hardware problem now (it seems unlikely to be software otherwise more people would have this exact problem). I'm also having problem connecting to wifi while out that I didn't notice untill I started using it more.
Ill give it a couple of days to see if anyone gets hold of the three firmware just in case (I don't want to give them a reason to try and screw me around, I like the plan and unlimited internet but their CS is abysmal sometimes), I will just go for it and send it back if not.
How long have you had the phone? I got mine switched over about a week after I got it because the camera had a problem. I have actually in general had some great customer service from them over the last couple of years they even just refunded me £40 of internet data usage because they did not explain it to me properly (One plan didn't start for a month apparently :/).
Good luck though hopefully they will just swap it over if they have some in stock. Make sure you take everything you got back in order to get an exchange.
Just over a week - got it on the 26th. The problem is I upgraded over the phone and had some problems then with overcharging, this is when I found out that the shops don't like dealing with phone customers and would not help me at all. Maybe they will be more accommodating for a hardware problem - or maybe if I refuse to leave until they behave like I am the one paying £40 a month to the company whos shop I am standing in I will get some service (Im actually getting prematurely angry lol).
Ill give the store a go first if I can't find the fw soon.
Thanks,
Hi everyone,
So about five days ago I was in the middle of using my Galaxy S4 (I think I was playing a game or something) and all of the sudden my cellular signal dropped out completely—from 4 bars to zero with a little X in it. There it's remained ever since.
My first thought was that I ought to reboot the thing and see if that would solve anything. The answer was no.
My second thought was that maybe my contract was up (as that was due to happen this month), and rather than auto-renewing, they kicked me off. Weird, but possible. But that's not it: I phoned up my provider and they said that all systems are go, there are no outages, your account is active for a week still, and even past that contract expiry I'll just get bumped to month-to-month and never experience a blip in service. So that's not it.
So then I put my SIM in another unlocked phone, and lo-and-behold, it connects just fine. So clearly the problem is with my phone.
My i337M is running Liquid Smooth 2.9 and KToonSez' kernel. I decided to make a nandroid and flash back to stock ROM/kernel. Still I could not connect to the network.
I can only think of two potential problems. First, I unlocked the phone myself via FastGSM.com's tethered USB method. It was a Bell-locked phone, and I'm on Rogers. This was accomplished back in July, and since then, there haven't been any issues to speak of (i.e., the unlock worked flawlessly). I tried to see if those unlocks ever expire, and couldn't find any reason why they ought to. I personally don't think it's that, but I mention it out of interest in being thorough.
Second, I messed around with my phones NVData a few weeks back to enable the AWS network via this method. I didn't experience any signal problems after doing so. Again I mention this out of interests of being thorough. Could that have had something to do with it? I suppose I could try flashing back my original NVData, but honestly I don't see why that would suddenly kick in now since I did it weeks ago originally.
Any thoughts? This is really bizarre, and it sucks being without connection.
I was also thinking of flashing back to stock and going to a Bell shop to see what happens when I put a tester SIM in.
It sounds to me like it's hardware related. Don't see anything you've done that would have caused it. I'd flash back to stock and if it still persists I'd file a warranty claim.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi, thanks for your reply.
An additional thought's occurred to me: I lost signal at or about the same day I setup Android Device Manager to allow for remote lock/wipe directly from Google. That couldn't possibly be responsible for signal loss, could it...?
Currently flashing back to stock, and I'll unroot/restore kernel/restore NVData and make it look factory, and see what the store says about it. Hopefully I don't have to pay for another unlock at some point.
Okay, this is very messed up. Nobody has any idea why my phone isn't getting signal. I can scan for networks and everything shows up, but in any case with any SIM it says "unable to connect to network". It doesn't matter what ROM I'm on. I flashed back to stock and updated to latest using KIES of all things, which found a firmware/modem/baseband update, and still no dice. I don't know what to do with this thing except take it to an unlocking store that might be able to figure something out for me, but it'll cost me. This is messed, I've never had to get someone else to look at my tech for me.
Okay, so the situation is that it most probably is a hardware failure related to the radio.
I am a Rogers customer who bought the phone from a guy from CraigsList who apparently got it from Bell. I went into Bell and explained the situation, and they scanned the IMEI and printed me out a proof of purchase of the guy's name and told me I should take that to the Bell service centre, and it doesn't matter if I'm not the guy. I also had them check to see if he reported the phone stolen; it turns out he did not—though it should be known that if he had done so, then that could have very well been the reason I wasn't getting signal from anyone, as all providers across Canada apparently share their blacklists with one another now (including the little guys like Wind/Mobilicity).
So now I am in the process of making it look like it's never ever been hacked before: I shall restore my NVData, unroot, and update everything using KIES, and then perform a factory data reset. I'm also on the hunt to figure out what the heck the "flash counter" is and whether or not I need to reset that, but perhaps since mine is the i337M Canadian variant, I don't need to worry about that. (Any advice on restoring my phone to factory condition would be welcome, thanks.)
Edit: Figured out TriangleAway and everything associated. I'm all stock now and ready to bring it back to the factory.
MAJOR UPDATE: PROBLEM IDENTIFIED
So I got my phone back from the factory today. They reported that everything is 100% a-ok on the hardware/software side of things. The radio IC is NOT blown as was suspected.
You know what they said? The problem is on the network. I have a story to tell that I think people should hear, as I've learned something very valuable today and people need to learn this lest they get conned themselves.
Today I phoned in Rogers again, armed with new information, to ask what's up. They ran the IMEI number, and this time... it's come up on the blacklist.
It wasn't there last week. In fact, it wasn't even there an hour ago. It actually only appeared there as the clock ticked past midnight Eastern time... as that is EXACTLY 90 days from when the phone was reported missing. It took them a long time to track down this information.
To reiterate, I did not steal the phone. I bought it from a guy on Craigslist who had it brand new in box with the screen-protector sticker still on the front of it. I checked it out, tried it, and unlocked it myself and have been using it since July without issue, until a week ago.
There is the trouble of, why now? Why only now does the IMEI come up blocked? What the senior rep at Rogers thinks happened was that the guy had it delivered to his house, didn't sign for it, kept it in box, reported it as "undelivered", and flipped it to me for cash. Insurance has meanwhile hooked him up with a new phone, and the factory kept my phone in the "we're looking for it" pile for the requisite 90 days, after which they officially publish its IMEI as "blacklisted". That would explain why it worked for a while but doesn't now; and this 90-day TO THE DAY period is the same for Rogers as it is for AT&T apparently (which is where the rep used to work for 10+ years).
I am in possession of stolen property. I've little hope of recuperating my losses. I've been advised to file a police report, and I think I will actually, given that I've got a receipt with the "anonymous" guy from Craigslist's name on it which I had printed out from Bell after they scanned the IMEI number for my factory warranty receipt. This phone will officially never work in Canada, as there is no way for it to be removed from the blacklist. I've been very unfortunate in this case, and it's a real shame.
People should take note: If buying a phone, ALWAYS do it in-store and have the IMEI number run first to check and see if it's on the blacklist. Next, have the phone transferred into your name so that the IMEI and you are officially linked, and the guy can't report his gear stolen or lost. That should suffice in most cases... except in the case of insurance fraud, which is my case, where there is a 90-day delay period in the IMEI number being added to the blacklist (which is why it didn't come up on the blacklist last week when I had the Bell rep run it in-store for me). Another point of interest is that in my case, I found it was possible to lose service BEFORE the number is on the blacklist—assuming the Bell guy didn't run the number wrong last week.
So f**k me. All I can do is try to hack the number, I guess, or find a way to spoof the IMEI.
Edit: Unf***ing believeable—I somehow reenabled data and texting by messing around with QPST. Calls still not happening, though.
Hi all,
I got a Nexus 4 from Ebay. Cellphone is in flawless condition, it probably has less than a couple of months of use. Unfortunately, I am not able to pick up a signal in any way. I just get a constant "No Service" message, and occasionally it will jump to "Emergency Calls Only".
Testing menu says Signal Strenght is 0 dBm 99 asu, no neighboring cells and location is unknown.
I've tried changing the prefered network to WCDMA only (as suggested in other threads), also tried with the other available settings with no luck. Tried playing around with the Change Bands setting as well but it makes no difference
Tried with a few different sim cards as well but that didn't work either, just got signal momentarily and but it would go on and off.
Cellphone came with 4.2.2 and I upgraded to 4.3 as requested by the system. Same issue.
Tried basebands 48 and 84.
Tried CM 10.2.
Replaced SIM card with a brand new one.
Cellphone doesn't appear to be blacklisted either.
Not sure what to do next. I'll try to get in contact with the seller but I don't expect much from him or eBay. Maybe I can sell off the device very cheap for spare parts, or send it for repair somewhere? Leave it as a dev device (which would virtually indistinguishable from a N5 that I plan to get anyway), Anyone else has any other suggestions or ideas?
Try to install a factory stock image: http://forum.xda-developers.com/showthread.php?t=2010312
If you pay with PayPal you get buyer protection so you can try to get your money back.
Could be a hardware or antenna issue.
To me it seems like its been blocked for certain reasons. Either it was reported stolen or the person who sold it to you didn't pay his/her bill for which the carrier blocked it. In that case you can't do much about it.
I would contact the seller right away. If you get no response contact paypal and eBay.
Sent from my Nexus 4 using Tapatalk 4
This problem is occurring for a lot of Nexus 4 users, including me. Its some sort of pandemic. Here’s what you can do to atleast restore service to your phone : flash the factory 4.3 image to your phone, again. However, try flashing a radio that is 54 or older with it. Make sure you wipe the cache and flash all the partitions, system, boot, bootloader and the old radio. This will bring back service to your phone (did for me), however you will be left with no in call audio and your phone wont connect to the internet through the mobile network, only wifi. After doing this, you will see your baseband and IMEI in the phone.
You can use this as some sort of “test” to verify if your phone really isn’t stolen. What is the ultimate resolution to this problem ? I really don’t know yet. I’ve been breaking my head over this for the past 4 days now. Maybe I’m going to try out the unbrick method mentioned over here to see if that helps.
As an update I am getting intermittent signal in some areas, but it's really spotty and only lasts a little while : (
I'll be giving different basebands a try tomorrow but I don't think it'll help much. I'll also try the full factory flash posted above.
Same problem here, had the phone for about 2-3 months, bought it off Kijiji, I tried flashing 4.2.2, went back to 4.3, flashed every baseband and still no success. The SIM works perfectly in another N4, tried a few other sim in mine and still the same results. Any other ways somebody got this fixed ?
QuebecFanat1c said:
Same problem here, had the phone for about 2-3 months, bought it off Kijiji, I tried flashing 4.2.2, went back to 4.3, flashed every baseband and still no success. The SIM works perfectly in another N4, tried a few other sim in mine and still the same results. Any other ways somebody got this fixed ?
Click to expand...
Click to collapse
I'm talking to the seller, see if the phone is still under warranty. My other options would be to change the antenna myself (see if it works), or resell it at loss for spare parts, or wait to see what eBay says.
Just to give you guys some hope, that this is not just a problem faced by second hand phones - My phone is bought directly from the Play store - I contacted Google service a few days back and they asked me to return the phone for a replacement. Only problem is I have to ship this back to the US (where I purchased from), since they dont provide replacement service outside the country of purchase. I'm in India now.
I've tried absolutely everything myself. Flashed many many radios, 4.3, 4.2.2, I'm only able to get it to the point where there is network coverage, I can make and receive calls but there is no in call audio, nor is there any mobile internet connectivity (Only through wifi).
Something tells me this is a problem with the latest OTA update that caused this issue - I was completely stock and everything was working properly, when this problem appeared one fine day - It started with me not able to connect to the mobile internet network for a few days, and then one fine morning, BAM. No service. It was only after this that I started flashing and re-installing stuff on my phone, desperately trying everything to get the phone back to normal again.
I think the last OTA update somehow "bricked" the radio (dont know if something like this is possible, just a noob guess). My only hope is the 4.4 update has some fix for this, else I'm going to try the unbrick method mentioned on these forums to see if that works. Only then will I take the pain to send this back to the US.
What's the unbrick method you are planning to follow?
I was considering using the unbrick method listed here : http://forum.xda-developers.com/showthread.php?t=2347060
Although I'm not completely sure it will work. Do you or anyone else have any suggestions for this ? I'm hoping 4.4 gets released ASAP, I'll download and root that as quickly as I can, hopefully Google has some resolution to this stupid problem
i have exactly the same problem
i have exactly the same problem. i bought my phone at US from Google play.
the phone worked fine for two month and then i got - No Service, and its swipe in a sec to emergency call only.
i try to replaced some sim cards, and factory reset with no success.
i also read a bug report that opened in Google : 58317
they told that there is a problem with the radio interface and radio driver at the 4.3 update, and they will fix it in 4.4 kitkat version.
i hope that 4.4 will fix this terrible problem, if not the phone is totally a door blocker..
Did anyone ever find a solution for this issue?
My friend has this problem with his Nexus 4.
I've searched A LOT and to this day (half a year later) haven't been able to find someone who reports this problem was solved.
I've also tried every suggestion I could find: flashed every stock image available, tried every combination of stock/custom ROM/recovery/radio, even tried the unbrick method mentioned above.
Nothing helps. I always get the same symptoms:
- Radios 54 and below - no in call audio.
- Radios 83 and above - Baseband unknown, IMEI / IMEI SV unknown, no cellular reception.
Also, RMA is not an option because the people at the store (a) don't know how to fix it and (b) claim the warranty doesn't cover this issue so they won't replace the device.
Any suggestions? I'm willing to try anything...
Maybe its a simple hardware failure like a loosely connected antenna? It doesn't really seem to be connected to any specific software setup
Something that happens to me rarely: when I'm in an area with very low/no reception sometimes the phone won't reconnect itself again and just stay on no reception until I reboot. Only happens like one or two times a month though.
Sent from my Nexus 4 using xda app-developers app
Thanks, but I really don't think it could be an antenna issue.
I can see how a malfunctioning antenna could cause cellular reception problems, but it shouldn't affect IMEI or Baseband version readings. Those things have nothing to do with the antenna.
Also, the fact that the symptoms change with different radio firmwares says there's a big chance this is a software issue after all.
I just can't figure out what the cause is and how to eliminate it.
Flash any full factory image. If the problem persists after you can be pretty sure it's hardware. No signal for most of the time and occasionally picking it up could be something as simple as the antenna being unplugged, which can sometimes happen after a drop, or a forgetful repair.
NoobNexus said:
I was considering using the unbrick method listed here : http://forum.xda-developers.com/showthread.php?t=2347060
Although I'm not completely sure it will work. Do you or anyone else have any suggestions for this ? I'm hoping 4.4 gets released ASAP, I'll download and root that as quickly as I can, hopefully Google has some resolution to this stupid problem
Click to expand...
Click to collapse
Guys... mine is signalless too... any progress on this? :crying:
michalhainc said:
Guys... mine is signalless too... any progress on this? :crying:
Click to expand...
Click to collapse
Could be a broken or badly connected antenna. They are very fragile. Have a look at how to replace the antenna maybe?
Sent from my Nexus 4 using Tapatalk
sp99 said:
Could be a broken or badly connected antenna. They are very fragile. Have a look at how to replace the antenna maybe?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
yup I am waiting for the ordered tools to break into it and look around...
michalhainc said:
yup I am waiting for the ordered tools to break into it and look around...
Click to expand...
Click to collapse
I've opened up lots of my old phones (not my nexus 4 yet) and its normally easy to find and change as it's separate from the motherboard and looks basically like a piece of plastic!
Sent from my Nexus 4 using Tapatalk
I have the same problem no connection but the phone recognize the sim and the number of the phone. I've tryed to return to stock using a factory firmware but I'm not able to fix the problem... (this morning is working fine and my phone never fell down or something like that)
If I open btw the case and try to remove and reinsert correctly the antenna the phone will recognize the signal?
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.
I have an LG G6, international version (H870DS) that has been having bootloop issues for a while now. For the first few months it would come and go -- sometimes it would be a week between issues, sometimes just a few minutes. I tried many things, multiple factory resets, removed the SD card, deleted possible troubles apps, basically anything I could find online to try. But, for a while the phone would work pretty much normally until it decided to restart and loop.
But... about two weeks ago the phone got into its bootloop and never came out -- I can't get past the LG logo screen anymore. If I let the phone go for a while eventually it gets to a green screen talking about a RAM dump. One time I managed to get it to a screen talking about unlocking the bootloader but that part got a bit over my head. Basically, I can let the batter die but as soon as I plug it in, the phone starts lopping again for 15 minutes or so, eventually ending at that green screen.
Over the last few days I have tried downloading a stock KDZ file to try to flash stock ROM back onto the phone. The problem is, I can't get the phone to communicate with my computer no matter what I do. I've downloaded LGUP, installed all the drivers, tried the LG Flash Tool and pretty much anything else I could find -- but I just can't get anything to recognize the phone, even when I get it into download mode. I know the problem isn't with drivers because when I try my wife's identical G6 on my computer it gets recognized right away.
I should mention that I never tried to tweak anything with the phone -- the issue has been occurring since it was basically brand new. I am by no means an idiot when it comes to tech but also far from an expert, but I have done my research and tried everything I could.
So -- basically I am out of options and appealing to anyone who can help. I currently live in Africa and have no access to LG service centers. I have spent upwards of 10 hours trying to figure this out now and I just don't know what else to try. Any tips or advice would be incredibly appreciated. Thank you!
This looks like a hardware failure. if you have warranty, you should send it back to them. The seller can't take care of the warranty ?