Related
Phone randomly reset and just keeps saying turning on wifi. I dont know what to do please help
Jasonfares said:
Phone randomly reset and just keeps saying turning on wifi. I dont know what to do please help
Click to expand...
Click to collapse
More information is needed
(1) What phone do you have (model number)
(2) What rom do you have
(3) Was there anything you did just before it happened
(4) Have you tried anything to fix it.
tallman43 said:
More information is needed
(1) What phone do you have (model number)
(2) What rom do you have
(3) Was there anything you did just before it happened
(4) Have you tried anything to fix it.
Click to expand...
Click to collapse
I have att d850
Im on stock but have adblock from root
I literally opened spotify and then phone crashed then restarted and wifi wont turn on.
Ive restarted multiple times. Ive turned airplane mode on. Idk what more to do
Jasonfares said:
I have att d850
Im on stock but have adblock from root
I literally opened spotify and then phone crashed then restarted and wifi wont turn on.
Ive restarted multiple times. Ive turned airplane mode on. Idk what more to do
Click to expand...
Click to collapse
Personally I would first delete spotify then reboot see if it fixes it,I personally don't think its the app spotify but worth a try. I would then also backup my data and try a factory reset. If that also does not work consider re flashing a new stock rom.
tallman43 said:
Personally I would first delete spotify then reboot see if it fixes it,I personally don't think its the app spotify but worth a try. I would then also backup my data and try a factory reset. If that also does not work consider re flashing a new stock rom.
Click to expand...
Click to collapse
I backed up some things and im factory reseting right now. What would be a good rom to flash? A while ago this phone was soft bricked and I flashed kitkat and reupgraded to lolipop and this just happened.
Jasonfares said:
I backed up some things and im factory reseting right now. What would be a good rom to flash? A while ago this phone was soft bricked and I flashed kitkat and reupgraded to lolipop and this just happened.
Click to expand...
Click to collapse
To be honest I can't recommend any because I have a LG 855 sorry.
tallman43 said:
To be honest I can't recommend any because I have a LG 855 sorry.
Click to expand...
Click to collapse
**** well I factory reset and its still doing it. I think im just going to go to att tommorow and see whats up
Jasonfares said:
**** well I factory reset and its still doing it. I think im just going to go to att tommorow and see whats up
Click to expand...
Click to collapse
Don't forget if you take it to service to unroot your phone.
tallman43 said:
Don't forget if you take it to service to unroot your phone.
Click to expand...
Click to collapse
wait do what with it? I factory reset it does that not take out the root?
Jasonfares said:
wait do what with it? I factory reset it does that not take out the root?
Click to expand...
Click to collapse
Nope it may remove the app but not root and service will be able to tell if it's rooted..Best way is to flash a stock kdz to get rid of any traces of it.
tallman43 said:
Nope it may remove the app but not root and service will be able to tell if it's rooted..Best way is to flash a stock kdz to get rid of any traces of it.
Click to expand...
Click to collapse
Could you give me a way how with wifi not on the phone?
Jasonfares said:
Could you give me a way how with wifi not on the phone?
Click to expand...
Click to collapse
Sorry I don't understand your question? do you mean how to flash a stock kdz if so look here >> http://forum.xda-developers.com/showthread.php?t=2785089 <<
Hi, sorry to hijack the thread but my LG G3 d855 is exactly the same. on 29th December i noticed that the wifi wasn't connected to my home network, so did a reboot and still the same. I spent an hour or 2 googling this to find i wasn't the only one. Most had suggested a factory data reset, however said that this doesn't always work. I tried that and still the same so rang my network provider who passed me through to LG UK. It was booked in for a repair and collected on the 5th Jan. I got the phone back on the 26th Jan, and it took me less than 10 minutes to get the same wifi not connecting issue again. On the repair note it states they have changed the ic/pa/filter and updated the software to v20l (although I'm sure i was on later than that anyway). I rang LG again and it was collected the next day. I received the handset on tuesday, and the note this time said software updated, phone tested. I put the battery in, turned the phone on and within a minute found that the wifi would not turn on at all. I also noticed that the build version was V20h, which is a downgrade from the version that was on the phone when i sent it back to them.
I have rang LG again, and was told that they would look at it, but that i might need a new phone. When i questioned the new phone statement and asked why i needed to buyt a new phone, the woman didnt answer me. Anyway, the phone is getting collected today, and i really dont hold out much hope that it will be repaired. I have mailed LG direct to complain about this but i am at the point where i might move away altogether from LG. I am stuck until June waiting for my contract to expire, but am so frustrated with LG and their repair service as they have had my phone over a month now and havent fixed it.
This phone (g3) have bad quality components....my last lg....back to Samsung....I want my S5 again or a new S7 or note 4. Fantastics super amoled displays, great conections, all works. I'm tired of suffering...kkk
labpedro said:
Hi, sorry to hijack the thread but my LG G3 d855 is exactly the same. on 29th December i noticed that the wifi wasn't connected to my home network, so did a reboot and still the same. I spent an hour or 2 googling this to find i wasn't the only one. Most had suggested a factory data reset, however said that this doesn't always work. I tried that and still the same so rang my network provider who passed me through to LG UK. It was booked in for a repair and collected on the 5th Jan. I got the phone back on the 26th Jan, and it took me less than 10 minutes to get the same wifi not connecting issue again. On the repair note it states they have changed the ic/pa/filter and updated the software to v20l (although I'm sure i was on later than that anyway). I rang LG again and it was collected the next day. I received the handset on tuesday, and the note this time said software updated, phone tested. I put the battery in, turned the phone on and within a minute found that the wifi would not turn on at all. I also noticed that the build version was V20h, which is a downgrade from the version that was on the phone when i sent it back to them.
I have rang LG again, and was told that they would look at it, but that i might need a new phone. When i questioned the new phone statement and asked why i needed to buyt a new phone, the woman didnt answer me. Anyway, the phone is getting collected today, and i really dont hold out much hope that it will be repaired. I have mailed LG direct to complain about this but i am at the point where i might move away altogether from LG. I am stuck until June waiting for my contract to expire, but am so frustrated with LG and their repair service as they have had my phone over a month now and havent fixed it.
Click to expand...
Click to collapse
Yea Ive been a month without WiFi on it and I've taken it to 2 phone repair shops and its been said to be a motherboard problem and lg would have a big fee to fix it. I'm going to get a new phone soon because this problem is happening a lot right now with lgs
Jasonfares said:
Yea Ive been a month without WiFi on it and I've taken it to 2 phone repair shops and its been said to be a motherboard problem and lg would have a big fee to fix it. I'm going to get a new phone soon because this problem is happening a lot right now with lgs
Click to expand...
Click to collapse
Well, update so far is they have "repaired" the handset and its on its way back to me so will get it on monday. I was going to bet a guy at work that it wouldnt be repaired but he wouldnt take the bet. if its still not fixed i think i need to go down the replacement route. I have tried to be polite about this, but the fact that they have ignored 3 emails from me trying to raise a complaint, numerous tweets and facebook messages is making me feel like LG are not a company that can be trusted. I realise that I am a tiny insignificant stone on the bottom of their shoe and am meaningless in the grand scheme of things, but i've never dealt with a company that simply ignores you....
I will update on monday when i turn the phone on
So as a follow up, I got the phone back on Monday and so far it is working fine, WiFi is connecting with no problems. The fix that has been reported is replacing the mainboard. 1 niggle now though is that there is now a hiss in the headphones that comes and goes which wasn't there when i sent the phone in for the million repair attempts. I cant be bothered to go through the hassle of reporting it and sending it off for repair so I'm just going to live with it (its not too bad, just annoying when the music is quiet or paused). I only have a couple of months before I can upgrade, and had thought about a G4 or G5 but after the past 2 months i don't think i'll bother.
Ray
labpedro said:
So as a follow up, I got the phone back on Monday and so far it is working fine, WiFi is connecting with no problems. The fix that has been reported is replacing the mainboard. 1 niggle now though is that there is now a hiss in the headphones that comes and goes which wasn't there when i sent the phone in for the million repair attempts. I cant be bothered to go through the hassle of reporting it and sending it off for repair so I'm just going to live with it (its not too bad, just annoying when the music is quiet or paused). I only have a couple of months before I can upgrade, and had thought about a G4 or G5 but after the past 2 months i don't think i'll bother.
Ray
Click to expand...
Click to collapse
How much did you pay for LG to repair it?
Jasonfares said:
How much did you pay for LG to repair it?
Click to expand...
Click to collapse
so sorry for late reply, didnt know you had asked a question. Mine was done under warranty (apparently LG have a 2 year warranty with Three) so mine was fixed under that. I would guess that it would of been about 100 quid though for the work that they did, if not more. It took them far too many attempts to fix it though, which has left me with a bitter taste towards LG, so not sure whether to get the G5 next, the G4 or move onto a different make altogether
labpedro said:
so sorry for late reply, didnt know you had asked a question. Mine was done under warranty (apparently LG have a 2 year warranty with Three) so mine was fixed under that. I would guess that it would of been about 100 quid though for the work that they did, if not more. It took them far too many attempts to fix it though, which has left me with a bitter taste towards LG, so not sure whether to get the G5 next, the G4 or move onto a different make altogether
Click to expand...
Click to collapse
I actually havent got it repaired and im still using it. I called lg and they told me there was a one year warranty on the g3 so im just keeping it until i decide on a new phone to get
I was regularly using my G4, it was on cyanogenmod 13 nightlys for a good while now and i updated it every week or so. (haven't updated it in at least 10 days this time but it shouldn't be an issue) Suddenly the device turned itself off and went into a bootloop. I found a couple of weird things with this bootloop.
1. it wont boot into the device ever. it just shows the LG logo for a few seconds, goes black for a second then repeat.
2. I cant enter recovery mode, i used the button combination and go to the "factory reset" screen, selected 'yes' twice and i should have been sent to TWRP, which i have installed. But instead it just took a while on the yes/no screen and then blacked out, and rebooted back into the loop.
3. Sometimes it goes a bit further in the loop, and gets a little into the boot animation i have. I found that letting it run a longer time gets me a higher chance to see my little boot animation.
ive heard there was a hardware issue with LG G4's that were bought back in September of 2015 but i bought mine in June last year so i don't think that's the issue.
i didn't backup my phone for a long time so i'd love to get my files back! (otherwise I'm getting a new phone in a couple of days but i still need it until then)
Any and all help will be greatly appreciated! thanks!
What is your phone's S/N?
Sent from my LG-H815 using Tapatalk
I have the exact same problem, my phone died like this yesterday. The colder the phone is the longer it runs without rebooting so that might be a hint for you, although i have never seen it boot up completely. Maybe you can put it in the freezer or something like that. I was lucky because i just switched to cm13 and make backups of all my data the day before.
joelalmeidaptg said:
What is your phone's S/N?
Click to expand...
Click to collapse
no idea. I know it hits some within a specific range but i did check the back of the phone where the battery is and it says there H815 0506 twice H815 0430 once and H815 0508 and H815 0501 both once. Does this mean anything? how can i check the S/N if its in a loop?
helgenet said:
I have the exact same problem, my phone died like this yesterday. The colder the phone is the longer it runs without rebooting so that might be a hint for you, although i have never seen it boot up completely. Maybe you can put it in the freezer or something like that. I was lucky because i just switched to cm13 and make backups of all my data the day before.
Click to expand...
Click to collapse
heard about that, i didnt try freezer because that sounds kinda stupid and i dont feel safe doing it but i put it in front of my A/C and it cooled down but i dont think it made any special change.
SynderBlack said:
no idea. I know it hits some within a specific range but i did check the back of the phone where the battery is and it says there H815 0506 twice H815 0430 once and H815 0508 and H815 0501 both once. Does this mean anything? how can i check the S/N if its in a loop?
I saw my S/N in the box the phone came in, right above the IMEI (mine is 602).
Click to expand...
Click to collapse
I'm sorry but it seems you both have THE bootloop problem not a weird bootloop.. It does affect many more than "bought in September" devices. Actually more of the June devices..
Sorry.
joelalmeidaptg said:
I saw my S/N in the box the phone came in, right above the IMEI (mine is 602).
Click to expand...
Click to collapse
EPa said:
I'm sorry but it seems you both have THE bootloop problem not a weird bootloop.. It does affect many more than "bought in September" devices. Actually more of the June devices..
Sorry.
Click to expand...
Click to collapse
just checked the box, mines 506.
Damn that sucks! Any way confirmed to fix this issue? I dont think warranty will fix a boot loader unlocked phone.
SynderBlack said:
just checked the box, mines 506.
Damn that sucks! Any way confirmed to fix this issue? I dont think warranty will fix a boot loader unlocked phone.
Click to expand...
Click to collapse
People in the US and some European countries (ie Germany) didn't have a problem getting it fixed under warranty despite unlocked bootloader, root or even custom roms (because it's a known hardware issue unrelated to software).
Others did.
Try, you got nothing lose..
As for a fix, there is a process that involves disabling CPU cores, has worked for some. Check http://forum.xda-developers.com/showthread.php?p=67149552
EPa said:
People in the US and some European countries (ie Germany) didn't have a problem getting it fixed under warranty despite unlocked bootloader, root or even custom roms (because it's a known hardware issue unrelated to software).
Others did.
Try, you got nothing lose..
As for a fix, there is a process that involves disabling CPU cores, has worked for some. Check http://forum.xda-developers.com/showthread.php?p=67149552
Click to expand...
Click to collapse
I bought the phone as an international phone from a phone store. I dont have an LG center here and if i try to ask the store to fix it under warrently i'll probably get turned down because the bootloader is unlocked (you can clearly see that in the LG screen)
I will try talking to them but with ~20 days of warranty remaining i doubt my success chances are high
I brought mine from a phone store unlocked too (Carphone Warehouse in the UK) and it also had an unlocked bootloader running Cm13.
When it started suffering the bootloop problem they repaired it no questions asked. Worth a go.
Mine done that but wouldn't turn on after I took battery out I didn't try asking on here but no luck so I took it to insurance and I ended up with the g5 as they had no g4 repaired and ready to come back to me in 24 hours lol. Carphone warehouse ? big thanks to them now to wait for g5 to get some good stuff ... ?
Sent from my LG-H850 using Tapatalk
hi freind i need your advice.i have a nexus 5x 32GB running android 7.0 40 days ago.i show that some people have bootloop probleme after nougat update.what are you advising me???keep my nexus 5x without fear?or I sold it quickly and keep a new phone???i love my nexus 5x but iam afraid what we advising me
NOTE:i dont have warranty because i bay my phone used from a shop
If something happen and you will send it RMA you will receive phone with replaced motherboard or refund of your money, depends if there are still replacements of motherboards available
Domin_PL said:
If something happen and you will send it RMA you will receive phone with replaced motherboard or refund of your money, depends if there are still replacements of motherboards available
Click to expand...
Click to collapse
i dont have warranty my friend bcz i bay it used from a shop
Aww so haven't you been given original receipt?
So there are two ways, you can keep your phone and disable two big cores of CPU to keep your phone safely from bootlop, or sell it.
Domin_PL said:
Aww so haven't you been given original receipt?
So there are two ways, you can keep your phone and disable two big cores of CPU to keep your phone safely from bootlop, or sell it.
Click to expand...
Click to collapse
tnx friend how to disable the two big cores?and i still have ota update?
This is it:
http://forum.xda-developers.com/nexus-5x/help/bootloped-hw-please-try-t3505392
You can keep just your bootloader unlocked or in developer settings OEM unlock state enabled to unlock bootloader when it is necessary, then you will still receive ota updates
Domin_PL said:
This is it:
http://forum.xda-developers.com/nexus-5x/help/bootloped-hw-please-try-t3505392
You can keep just your bootloader unlocked or in developer settings OEM unlock state enabled to unlock bootloader when it is necessary, then you will still receive ota updates
Click to expand...
Click to collapse
tnx my dear tell me i dont do this now.if i have bootloop probleme in the future can i do this method even if i have the bootloop?
Yes but you need to have ability to unlock bootloader enabled or unlocked bootloader
Domin_PL said:
Yes but you need to have ability to unlock bootloader enabled or unlocked bootloader
Click to expand...
Click to collapse
how to know if my bootloader is unlock??and if is lock how to unlock it?
Here you got a huge instruction:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Bootloader state is in bootloader mode, on turned off device you keep holding volume - and power button
Domin_PL said:
Here you got a huge instruction:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Bootloader state is in bootloader mode, on turned off device you keep holding volume - and power button
Click to expand...
Click to collapse
tnxxxx for your great help my dear
Domin_PL said:
Here you got a huge instruction:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Bootloader state is in bootloader mode, on turned off device you keep holding volume - and power button
Click to expand...
Click to collapse
my stat of my bootloader is locked its fine or not?
I'd just gamble and keep using the phone as long as it works. If it bootloops later on, you'd worry about it then. Not to mention, the smartphone prices are constantly dropping and new hardware is coming to the market all the time, so a new phone you could buy a half year later will be superior to what you get now on the same budget.
znayver said:
hi freind i need your advice.i have a nexus 5x 32GB running android 7.0 40 days ago.i show that some people have bootloop probleme after nougat update.what are you advising me???keep my nexus 5x without fear?or I sold it quickly and keep a new phone???i love my nexus 5x but iam afraid what we advising me
NOTE:i dont have warranty because i bay my phone used from a shop
Click to expand...
Click to collapse
Remember the bootloop issue on N5X is hard ware related. Maybe the phone gets hot on a large update like the Nougat one, and the bad soldered 808 SOC fails. Its not about the Nougat itself.
It only happens to a small % of N5X owners, so you should not be afraid. Just use it as normal. And if you dissable the large cores its not much of a Nexus left.
Thanks
KnieveI
So my wife has had her Note 8 a couple months and has been experiencing soft brick problems. Her phone will go to sleep and then won't wake up. It can only be started in safe mode and then restarted normal. We started to think it was the phone so we sent it back and Verizon sent one of their lovely factory referbs as a replacement. I felt after having the phone for only a month she should get a new one but that's a whole other story. Anyway back on topic, her replacement has the same problem. I'm starting to think this is more of a problem with the software and not a hardware issue and was wondering if anyone here has had the same type of problem? Before anyone comments with searching Goggle, yes I've done that, cleared the cache,reset the phone, and it still randomly soft bricks.
xVallex said:
So my wife has had her Note 8 a couple months and has been experiencing soft brick problems. Her phone will go to sleep and then won't wake up. It can only be started in safe mode and then restarted normal. We started to think it was the phone so we sent it back and Verizon sent one of their lovely factory referbs as a replacement. I felt after having the phone for only a month she should get a new one but that's a whole other story. Anyway back on topic, her replacement has the same problem. I'm starting to think this is more of a problem with the software and not a hardware issue and was wondering if anyone here has had the same type of problem? Before anyone comments with searching Goggle, yes I've done that, cleared the cache,reset the phone, and it still randomly soft bricks.
Click to expand...
Click to collapse
why you don' try to install the current software that your wife phone is running using odin?
android-incredible said:
why you don' try to install the current software that your wife phone is running using odin?
Click to expand...
Click to collapse
She has the current software. I'm starting to think the last update might have been the problem.
The phone has the December security patch?.
android-incredible said:
The phone has the December security patch?.
Click to expand...
Click to collapse
Yes the phone has the December security patch. It's been soft bricking since before that though.
xVallex said:
So my wife has had her Note 8 a couple months and has been experiencing soft brick problems. Her phone will go to sleep and then won't wake up. It can only be started in safe mode and then restarted normal. We started to think it was the phone so we sent it back and Verizon sent one of their lovely factory referbs as a replacement. I felt after having the phone for only a month she should get a new one but that's a whole other story. Anyway back on topic, her replacement has the same problem. I'm starting to think this is more of a problem with the software and not a hardware issue and was wondering if anyone here has had the same type of problem? Before anyone comments with searching Goggle, yes I've done that, cleared the cache,reset the phone, and it still randomly soft bricks.
Click to expand...
Click to collapse
Sorry you are having issues and that you have been sent a refurbished replacement. It would probably be a good idea to download the factory firmware and flash in Odin, even though it is the same version...reason being, a factory firmware flash can eliminate most corrupted software issues...
You can download your firmware and then follow the guide here:
https://forum.xda-developers.com/showpost.php?p=74087340&postcount=1
If the device continues to do the same thing...there may be an app or setting causing the disturbance...
Where can i download the stock firmware?
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
sliding_billy said:
Are you BL locked or unlocked? If unlocked, you can at least try installing the factory image (with or without the -w) and see what it does.
Click to expand...
Click to collapse
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
lpiratel said:
unfortunately, BL is locked and I can't do anything that I know of on my end. Time to go back to my back up oneplus 3T
Click to expand...
Click to collapse
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
sliding_billy said:
Can you see the device in Fastboot with fastboot devices from a command prompt? Are you locked and not unlockable (Verizon) or just not unlocked? If just not unlocked you could try unlocking the BL (assuming you had at least toggled OEM Unlocking in developer settings)? I don't know if the command works on a locked BL (I suspect it doesn't, but it is worth a try), but fastboot reboot fastboot would get you to fastbootd where you can do ADB sideload.
Click to expand...
Click to collapse
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Suggestion: Call Google support
lpiratel said:
my phone is not Version version, bought it directly from google. oem is unlocked for sure. I tried the command, but it keep restarting after 3 seconds in fastboot mode. I think the power button board is messed up.
Click to expand...
Click to collapse
Homeboy76 said:
Suggestion: Call Google support
Click to expand...
Click to collapse
Same suggestion as Homeboy at this point. Sorry.
lpiratel said:
so I woke up this morning and the phone was off, i tried to turn it on with no luck. Plug in the original OEM charger and been getting stuck in bootloop.
tried to follow recovery mode but everytime i get to the "fastboot" screen and try to toogle the menu, the phone reset back to the "Google" logo....so now i can't even enter recovery mode to side load. have anyone run into this issue before? and what is the solution?
thanks
Click to expand...
Click to collapse
They will rma it, I had a similar issue on my pixel 2 (slot unbootable load error) and they shipped me once right away.
lpiratel said:
So after i let the phone run out of the battery, i noticed the no battery icon keep flashing. plus when i was only holding down the Volume down button, i can go to fastboot mood. it seems like the power button is stuck causing the phone to reset all the time. I think this is a hardware issue.
Click to expand...
Click to collapse
This just happened to me yesterday. Plugged my Pixel 3 XL in to the wall charger and it immediately went into a bootloop. Nothing would stop it as if it were a hardware issue. Tried to boot into recovery and fastboot but it would immediately bootloop again. Eventually after the battery died I was able to start it up and get it working again. My issue now is that I'm worried it will happen in the future. Didn't plan on upgrading but might have to move to the 4 XL as I use this phone for work.
holy crap - this happened to my wife's phone last week. We ended up getting a Pixel 3A XL for her.
She plugged in her 3XL at around 10% and it started boot looping. I couldnt' do anything with it. The only way I could try and keep it on is blasting it with a flipped can of CO2. I tried everything from factory reset to reflashing. Finally I gave up, and let it sit for a week. Started the phone, and it stayed on for 3 days and let the battery drain again to 10% - plugged the phone it and it started bootlooping again. I'm wondering if the battery just gave out. I wonder if we can see if there is some manufacturing correlation here, maybe all of our phones came from the same batch. I ended up buying in Nov 2018 for Black Friday sale.
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
This *just* happened to me, too! Happened at 330pm EDT right before I had a meeting, so I had to quickly swap the sim into another phone. I'm also out of warranty, and the fact that there are a number of us reporting this same issue in a quick span of time leads me to think this is something on Google's end
Sam Nakamura said:
I'd simply try to get support for this, it looks like the next big flaw and is likely class action lawsuit material, assuming hardware failure can be proven - to which I have not a single doubt in my mind, from reading alone the reports a few red flags can be seen instantly!
From not being able to reach fastboot or get past Google logo it appears to be the UFS storage chip that went bad! However it also seems that there's a relation to the charging mechanism, potentially involving the battery itself..
I think we'll start to see more an more reports about this flaw the next month, I hope not but after all Google released to the public on hardware level alone I wouldn't be surprised either - don't get me wrong, I love their devices and most Nexus and Pixel in daily use, I wouldn't even consider switching to another brand as love those devices to much but after all the years I also know that Google doesn't always execute their plans well on hardware level! Their 'lemon count' is statistically higher than elsewhere!
Good luck everyone, I'm definitely keeping an eye on this thread and issue!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Since my original reply to this post, it has happened a couple of more times on my phone. Both times I've noticed the phone gets extremely hot but as soon as the battery dies and the temperature cools for a while, the phone will power back on. My uneducated guess is that something in the processor or battery connection is causing the phone to overheat. Excuse the layman's terms lol.
I too have been a big fan of the Nexus and PIxel lineups over the years but my reason for upgrading to the newer model was always because my old phone had some sort of hardware defect. Galaxy Nexus microphone died, Nexus 6P wouldn't power on, OG PIxel bootlooped. Pixel 2 XL had screen issues. Pixel 3 XL, here we are now lol. Each one lasted me at least over a year and the software is unmatched in my opinion. I'm proud of how far they've come with software, hardware and camera. I just wish they'd put a little "oomph" in their quality control department.
Google doesn't help with bootloop
hazeem96 said:
Hey i'm currently going through this exact issue right now with my Pixel 3 XL. However my phone is out of warranty, it expired back in november, anyone has had experience with Google over the handling of this issue once the phone is out of warranty?
Would be great for your feedback! literally cried when this happened. I experienced the bootloop issue with the 6P. couldn't believe it was happening again with a phone of lifespan still less than 2 years.
Thanks!
Click to expand...
Click to collapse
----------------------------------------
I bought my Pixel 3 XL November 2018 from the Google Store.
The phone has been great, but the bootloop started happening with me 4-5 days ago. I had to buy a new phone (yes, I'm stuck in the modern world, unfortunately. i need a phone)
Recovery buttons get to a menu...and then back to the bootloop within 2 seconds, There was little time to press volume buttons etc and no response when I do so on this screen, other than the dead Android with it's hatch open.
But no matter what I do - it goes back to the bootloop within a few seconds.
I spoke w rep from Google for 40 minutes or so, I was polite. No help; he said he could not send me a new or renewed device. he suggested repair shops. Which....the shop told me they do not deal with bootloops, "probably a hardware issue", he said.
So...idea....use my credit card extended warranty! But....for this purchase, strangely...I used PayPal. ughhhh!
Disapointing. Not quite 2 years out of my Pixel, and I was hoping to capitalize on the resale / trade-in value. Not possible now, even a trade in requires a factory wipe.
I did think of using ADB / fastboot, but I do not have time to futz around right now.
You could try Google, but...if you are out of warranty, it is unlikely they will help. Did you buy it with a credit card w extended warranty?
good luck
this just happened to me google is saying that because the phone is out of warranty (by 8 months)
there is nothing they can do about it
at least I have the extended care