Related
Hi all,
I recently sent my GN (Running 4.0.2 stock, yakju build) back to be repaired because my phones wifi stopped working. what happens is that the phone's wifi seems be stuck "turning on", but never actually does. No wifi icon or anything appears. wifi hotspot doesnt work either. I had my GN from about a week after it was released (I'm in australia so that was about the 22nd December), and around the 15th January is stopped working. This issue cannot be fixed with a reboot, a hard reset, flashing stock roms, toggling airplane mode or anything trivial like that, as I (and others) have tried.
Now i have searched a while on google while i have been without my phone and I'm finding this problem is surfacing for other people too. From what i have seen there seems to be a correlation between 4.0.2 and this issue. Also, it seems to happen some time into the phones life; they do not have this issue when first purchased. I am concerned that this may be a recurring issue which surfaces over time, due to a design flaw or some sort of software issue. If so, this problem will start affecting a lot more people. If anyone who reads this has the same problem, could you please post when it started occuring and what rom, build etc (and anything else which may be helpful) you are running so we can shed a little light on this issue. which many more users i am sure will experience. cheers in advance
just incase anyone actually reads this Galaxy Nexus was sent back, and it was found that the printed ciruit board (PCB) needed replacing. More forums have surfaced since i last checked up on this problem so numbers are slowly rising. Once again, post here if you get the issue, we need numbers
Hi same issue i have butni solve i am living in turkey and i use habertürk news and i saw this application make notification wifi turning om.i reset my phone i load factory firmware but nothing happen ...always say wifi turning on...you need to change your system language another still write wifi turning on on screen in eglish and a application cause to this like my haberturk app
Sent from my Galaxy Nexus using XDA
same problem
Hi,
i had the same problem, wifi mac info was not showing anymore on the Nexus. Reboot and factory reset didn't help. Wifi wouldn't come on anymore.
Ask for a replacement, that's the only thing you can do
Can i ask what version of android you guys had? I'm wondering if this is going to be a recurring problem with hardware due to software issues or if it is purely a design flaw (PCB burning out, etc..) Cheers!
I have the same problem which happened last Saturday and it frustrated the hell out of me, i flashed to different versions of OS....didnt help...
restored to factory firmware and didnt backup the pictures and stuff on the phone!! (FML)
and brought it in to Fido on monday to have it serviced....
talking about bad luck...sigh....
they told me the turn around time is 10-15 business days... (N)
will report back once i hear from them
Before the issue happened, did your phone have any other issues? Say heating up while charging or running the WiFi?
I received a device in for repair with this issue and the customer reported it got really hot before the issue started happening. Everything looked fine on the motherboard - the WiFi antennas were intact. Reloading the software did nothing which means it's a hardware issue..
So very strange. I wonder what's causing this.
i remember when my wifi stopped working i was running 4.0.2. I was actually on holidays in Japan at the time and i was wifi hopping quite a lot around the airport (i was walking around and the wifi would go out of range, latch on again... etc) not sure if that had anything to do with it. Hopped on the plane home and i remember i was on airplane mode using an app called colornote. the phone hung pretty hard and i had to pull the battery. rebooted and tried again and after 10 mins, phone crashed again doing the same thing. Got home and the wifi wasnt working. Not sure if any of this had anything to do with it, but maybe. Didnt notice any overheating, but then again i was around snow haha
hi mrmiklepower
just wondering if your phone has been good since you got it back from repair?
i noticed the phone would reboot itself over and over again after i flashed it back to the stock rom. I just called the third party repair shop that my carrier sent the phone to, they told me its still being fixed.
Oh i hope they will return me my phone soon.
My phone is actually still being repaired also. It's been a total of 2 months since i sent if back! they contacted me and all i know so far is that the phones PCD needed replacing. when my phone arrives i will update as soon as i can. should receive it sometime this week, but its not certain. the majority of my ownership of this phone has been me waiting for its return
Holy mother of lord...
I actually called the third party repair shop that my carrier uses to check on the status of the repair. And they told me its actually In quality control which means the problem was fixed and they're just testing it before they send it back to the store where I brought the phone too. Hoping they'll send it in on Monday so I can either pick it up on the day of or the next day.....keeping my fingers crossed.
Will keep you posted on the status of it too.
Sigh
Ok I got my phone back today.
on the reference sheet I got from the repair shop
it states REPLACED PBA, BGA Failure
I looked it up online and PBA means Printed Board Assembly
which probably means the motherboard was defective and had to be replaced.
and now the phone is working fine. So i guess when this phone was made, there were some flaws with the motherboard on it, thus causing this problem.
Anyways, I hope this information helps with others who experience the same problem
Thanks for letting us know! O got mine back today with the same thing. So looks like there is no way of fixing besides sending it back. Good luck to anyone else who gets this problem
Sent from my Galaxy Nexus using xda premium
So it seems there's no fix for this?
I've been doing some research and it doesn't seem anyone can fix this.. I tried reflashing, wiping every possible thing, etc.. even flashing the stock software via odin. Still no luck.. It seems that we are indeed stuck with sending it back in for a supposedly defective part which seriously blows.
My other question is.. you guys who already received your phones back, did anyone end up with the problem again?
PLEASE if anyone knows how to fix this.. chime in!!!
I had an issue similar to that with my transformer and to fix it I just flash a new kernel im not sure itwill fix the problem for you but it's worth a try
Sent from my Galaxy Nexus using xda premium
Since getting my phone back the problem has not occurred again. I don't think there is anything that can be done as a component needed to be changed apparently. Good luck :/
Zeon45 said:
I had an issue similar to that with my transformer and to fix it I just flash a new kernel im not sure itwill fix the problem for you but it's worth a try
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, when returning to stock it flashes a new kernel. Also tried it again for the hell of it with faux's kernel, still no luck .
This sucks! This very same thing happened to me yesterday! I Odined back to stock.. no luck! Now after finding this thread, it looks like a hardware issue! That blows! I'll have to give Sprint a call tomorrow!
Hmm sucks to hear it's still cropping up around the place, I heard someone say this issue entered quality control. But anyway, if it helps I've had my phone back for about a month and a bit and its still going strong. hopefully it doesn't happen again though. good luck, hopefully it won't take too long for your phone to come back!
Hi,
I'm with Telus in Canada and had the exact same problem and had my GN repaired. It took only 2 weeks and I just got my unit back. I had already read a lot online about this issue so I asked the Telus rep to tell me what the issue was. She told me that the report states that the board was replaced. This is definitely a hardware problem. I'm hoping that the new board doesn't have this problem and my phone won't need to be repaired again,
I run 4.0.1 on my phone. Telus hasn't released an update yet. I was going to update mine by switching to yakju, but that's when I noticed that the wifi is not working and I thought it's not a good idea to change the stock ROM.
my phone is rooted i'm on 13B everything was fine since i got my phone back in august till today i was listening music and was gonna skip to next song that moment is when my phone froze completely after pressing the power button the phone reboot by itself but got stuck on the lg screen i removed the battery after a few attempts it turned on. after 30 minutes or so it rebooted it self again but now even removing the battery it won't pass the lg screen. any ideas? suggestions?
probably the same problem a lot of other people are having. I also had the same symptoms as you, on rooted 13B.
you can try resetting or reflashing your phone but most likely you need a replacement.
theirs a problem with the motherboard going bad, i just had the same problem and lg sent me a replacement under warranty but i wasnt rooted
dagnisaun said:
probably the same problem a lot of other people are having. I also had the same symptoms as you, on rooted 13B.
you can try resetting or reflashing your phone but most likely you need a replacement.
Click to expand...
Click to collapse
bayniner said:
theirs a problem with the motherboard going bad, i just had the same problem and lg sent me a replacement under warranty but i wasnt rooted
Click to expand...
Click to collapse
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
killa408shark said:
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
Click to expand...
Click to collapse
How were you able to flash 13B if it was stuck in a bootloop, ive already recieved my replacement but id like to factory reset my old one before i send it back
bayniner said:
How were you able to flash 13B if it was stuck in a bootloop, ive already recieved my replacement but id like to factory reset my old one before i send it back
Click to expand...
Click to collapse
I put the phone in download mode and flashed 13B KDZ. But unfortunately my phone got back in the bootlop. Good thing I'm gettingmy replacement
It's a hardware issue, not software. A lot of the earlier G4s have "loose contacts" that cause the bootloop to occur. LG has acknolwedged it and are replacing any affected phones without incident. Just call verizon and they'll ship a new one.
Yup, happened to me just his week. VZW shipped another one to arrive the next day. FWIW, I strongly recommend everyone backup their phone to removable SD card using LG's on board Backup utility. If this challenge happens to you, getting back up and running quickly will be much easier if you have this backup ready to go.
...my $.02.
Happened to me as well last night. Took it back to Verizon today and they are sending me another one. I didn't have insurance and no questions were asked. Obviously they recognize the problem. Last LG phone I will own! Unless the G5 is insane. Hehe
Happened to me as well, yesterday. Interesting how this is happening to everyone at almost the same timeframe. I'll take it to Verizon to get a replacement shipped.
I had the same problem, and contacted LG support and they said it will take 9 business days to repair the phone. This seemed like an awful long time to be without a phone, I asked if there was any way to speed the process up and they said no. Thankfully I was able to borrow a phone from work for the duration of the repairs. Considering how this is a major problem with many handsets, I think LG is handling the whole situation pretty badly.
I finally ran into the bootloop problem that is common with early G4's (if you have a serial number that starts with 505, you're basically gonna be screwed at some point). Since it's a hardware issue that LG acknowledges, I sent it back to the factory under warranty, waited for two weeks using my old backup phone, and finally received it back today.
Ready for the fun part? They had repaired something that wasn't broken (kind of like surgery on the wrong body part) and had not touched the bootloop issue! They fixed "No power with cable" by replacing the flash memory. This was never an issue. The frustrating thing is that they didn't even restart the phone to find out if it had been fixed, because if they had it would have gone right back into the bootloop. Arg!
The G4 is now back on route to LG. I said they should give me a new phone, but customer service said they only do that if it cannot be repaired. I'll keep my fingers crossed that they go to the trouble to turn on the phone after "repair" this time.
Thanks for letting me rant!
I have currently my 2nd G4 that has run into this issue. This one has serial number starting with 506, so I guess it might stem a little further into production also. This is driving me nuts, I could not send my phone to LG because of how long it takes so had Verizon send me one and of course I run into the same exact issue with the bootloops. Last time I was able to still flash kdz's, this time won't even go past the LG boot screen. Really wish I could wipe my data at least.
I can attest to LG's incompetence. On March 2nd I sent in my G4 because it was bootlooping. Sent it in no problem, and after about a week I received my G4 back with the problem "fixed" by flashing the memory. Well guess what, it wasn't fixed. As soon as I turned it on, it started to bootloop again. I called LG and they arranged another RMA. Sent it back again, and about a week and a half later, I had my G4 back. This time they "fixed" it by replacing a capacitor. Guess what! Still not fixed. It still continued to bootloop. Called LG extremely angry and filed a complaint. LG arranged another RMA. At this point I had been without my phone for over 20 days. Finally, LG fixed it properly by replacing the motherboard. Now its fixed and it only took them over a month to figure it out.
While I applaud their easy RMA process, whoever the idiots are actually doing the repair are just that.. idiots. Its as if they don't even turn the phone on and ensure it fully boots up before they claim its fixed and ship it back. Whats worse for me is my phone was rooted on VS986B. Got the phone back on Marshmallow 24C and it took the update to 25a overnight. Now I'm stuck with no way of rooting.....
When you get your phone back from LG, chances are it will be on 24C. If you plan on rooting, do so quickly and downgrade.
dcorrea said:
I can attest to LG's incompetence. On March 2nd I sent in my G4 because it was bootlooping. Sent it in no problem, and after about a week I received my G4 back with the problem "fixed" by flashing the memory. Well guess what, it wasn't fixed. As soon as I turned it on, it started to bootloop again. I called LG and they arranged another RMA. Sent it back again, and about a week and a half later, I had my G4 back. This time they "fixed" it by replacing a capacitor. Guess what! Still not fixed. It still continued to bootloop. Called LG extremely angry and filed a complaint. LG arranged another RMA. At this point I had been without my phone for over 20 days. Finally, LG fixed it properly by replacing the motherboard. Now its fixed and it only took them over a month to figure it out.
While I applaud their easy RMA process, whoever the idiots are actually doing the repair are just that.. idiots. Its as if they don't even turn the phone on and ensure it fully boots up before they claim its fixed and ship it back. Whats worse for me is my phone was rooted on VS986B. Got the phone back on Marshmallow 24C and it took the update to 25a overnight. Now I'm stuck with no way of rooting.....
When you get your phone back from LG, chances are it will be on 24C. If you plan on rooting, do so quickly and downgrade.
Click to expand...
Click to collapse
When they finally replaced the motherboard, did the physical serial number on the phone change?
enduser23 said:
When they finally replaced the motherboard, did the physical serial number on the phone change?
Click to expand...
Click to collapse
No, that's the same. The board was replaced, but the plastic piece that holds that battery, which is on top of the board, was not replaced.
Happy to report that all is well after the second repair. Came back with 6.0, but I downgraded to 5.1, rooted, and have just about everything working again (can't get Exposed to work, but I'm sure I'll figure it out eventually). Nothing like spending 3+ weeks on a 2011 Droid Bionic to make me appreciate my G4!
Would one of you care to explain how you contacted LG to set up the repair. I have filled out the online form twice and have never heard a word. Thanks.
illek46 said:
Would one of you care to explain how you contacted LG to set up the repair. I have filled out the online form twice and have never heard a word. Thanks.
Click to expand...
Click to collapse
Im not sure if you are in the U.S., but here's their support phone number 800 243-0000. They are usually pretty easy to deal with over the phone.
I am still kicking myself that I didn't downgrade as soon as I got my phone back. I hate not having root anymore.
---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------
harpdoc said:
No, that's the same. The board was replaced, but the plastic piece that holds that battery, which is on top of the board, was not replaced.
Happy to report that all is well after the second repair. Came back with 6.0, but I downgraded to 5.1, rooted, and have just about everything working again (can't get Exposed to work, but I'm sure I'll figure it out eventually). Nothing like spending 3+ weeks on a 2011 Droid Bionic to make me appreciate my G4!
Click to expand...
Click to collapse
Droid bionic.. I wish! I originally dug up my old Galaxy Nexus, but the battery life was so bad that I swapped it out for my son's old Droid Razr. Of course, I had to safestrap it and put a custom ROM on there because I have a LG G Watch R and android wear was not compatible with the factory software on the Razr. It was a pretty horrible experience overall. I'm glad I have my G4 back, but I really miss root.
You can still downgrade to 5.1 and root. Mine was on the latest version when it came from the factory and I didn't have any problems with the process.
Same thing happened to me. It took 3 RMA's in a row and about 60 days until they finally fixed it. They scratched it, too. OP, I highly recommend you start documenting everything. LG CS will also tell you escalating will get you nowhere; but with persistence you can get a hold of someone. You can only go up to a supervisor, and that's it. LG has specifically designed their CS (including their facebook and twitter) to contain and ignore you.
In less than 1 calendar year i am on my 3rd phone.. Figuring the 1st phone was a flop... serial numbers since my 1st phone are 511 and 505. So yeah.. im debating at what a ticking timebomb i havenow. The 3rd one came w/ MM installed but I downgraded to LL to keep root. Im sure it goes w/o saying that I'll not buy an LG phone ever again.. and this was my 1st one. They could offer to upgrade me to a G5, but honestly there are NO guarantees this sort of thing will happen again. You break trust you pay the price, look at Samsung w/ the no MicroSD card fiasco.
LG just accepted my 15 month old G4 for warranty repair
Even though my phone is 15 months old, LG has accepted it under warranty repair. When requesting repair I wrote that it was the bootloop issue but their repair confirmation states the issue is "No Power with Cable". I hope they fix the correct issue! BTW, my serial number began with 511
The US warranty is 18 months, so LG didn't do you any favors. I have three of these POS phones to get warranty repaired and hope they fix them correctly the first time.
keithfur said:
Even though my phone is 15 months old, LG has accepted it under warranty repair. When requesting repair I wrote that it was the bootloop issue but their repair confirmation states the issue is "No Power with Cable". I hope they fix the correct issue! BTW, my serial number began with 511
Click to expand...
Click to collapse
I just got mine back today june 1st 2017, Sent G4 for bootloops 1st time a week ago. No power / Mainboard was replaced. it was purchased november 2015 and Serial number is 511 which is right after the supposed bad batch. I got the phone back in the same great condition it left. The repair guy reported phone condition has minor scratches when it doesn't, Not sure why he would report that. So far its working great, like a new phone. I can only hope this board has been redesigned to not fail under a year and a half, but thats just wishful thinking. Everything was completely free even though phone was like 5months+ after its warranty. Even though costumer service on phone sounded like she was doped out on crack and ignoring all my questions, it was still ez to do and I got it back fast. The IEMI number or whatever was also changed and they put a new sticker over top the old one under the battery. I tried checking the number on that website and it doesn't even have it registered so i can only hope its brand new.
Got a couple of VS986s back from bootloop warranty repair. Mainboards supposedly repaired, but IMEI stayed the same and nothing on label under battery changed . I recall other people mentioned changes to label information.
Last week a representative told me the current warranty on the G4 for this issue is 27 months from date of manufacture or 24 months from date of purchase.
Mine has S/N 508. It started bootlooping while I was pooping (browsing Facebook on Chrome browser) on June 5.
I attempted the hot-air rework station fix 5 times (for processor on mainboard), and that worked on the 2nd, 3rd, and 4th tries. Each time the phone worked for up to ~4 hours. On the 5th try the phone no longer booted or even showed the LG logo.
It's en-route to LG right now. I opted to ship it without battery or back cover (my back cover has a wireless charging tag).
Using my old Samsung Galaxy S3 running an AOSP-variant on 4.4.2. Actually isn't a bad phone.
My old LG G2's touchscreen no longer responds to touches on roughly 50% of the screen... can't even unlock it via pattern lock any more.
Thinking LG won't be the next new phone I buy...
Well, my G4 is on its way back to me after LG's warranty repair. Turn-around time at the LG service facility was ONE (1) DAY!! So that was super fast. Should get it tomorrow or the day after. Contemplating putting it back up for sale or trade-in though... it's basically gonna be a virgin device that will require root, xposed, restoring apps/messages/call log/etc., then adjusting everything else to my liking. Would be a shame to do all that work and then the bootlooping problem happens again.
Hi all, I have a HTC 10 unlocked version which is running Android 7.0, Software version 2.41.617.3.
I've owned the phone since October, around November it started randomly rebooting. It occurred maybe once every few days or once a week and the frequency increased.
I sent the phone to HTC for repair earlier this month, and they sent it back saying they couldn't reproduce the error.
I had thought the issue was my SD card, so since receiving the phone this week from HTC I have not installed my SD card. The phone worked 3 days before randomly rebooting an hour ago.
I've sent all the crash log files to HTC, and now realize that I might have not sent them at all.
I know others have had this issue with their HTC 10, has anyone figured out a cause?
Also, is the replacement phone from Uh-Oh protection new in box or a refurbished phone?
Highlyanimated said:
Hi all, I have a HTC 10 unlocked version which is running Android 7.0, Software version 2.41.617.3.
I've owned the phone since October, around November it started randomly rebooting. It occurred maybe once every few days or once a week and the frequency increased.
I sent the phone to HTC for repair earlier this month, and they sent it back saying they couldn't reproduce the error.
I had thought the issue was my SD card, so since receiving the phone this week from HTC I have not installed my SD card. The phone worked 3 days before randomly rebooting an hour ago.
I've sent all the crash log files to HTC, and now realize that I might have not sent them at all.
I know others have had this issue with their HTC 10, has anyone figured out a cause?
Also, is the replacement phone from Uh-Oh protection new in box or a refurbished phone?
Click to expand...
Click to collapse
Did they send it back in the same condition, or did your phone come back with all of your apps and data still intact?
You could try to run the US Unlocked RUU to see if that fixes it ( it should), and run it without restoring any data.
xunholyx said:
Did they send it back in the same condition, or did your phone come back with all of your apps and data still intact?
You could try to run the US Unlocked RUU to see if that fixes it ( it should), and run it without restoring any data.
Click to expand...
Click to collapse
Thank you for the suggestion.
I went through all of the standard troubleshooting before they escalated me to repair status.
First I did safe mode, after it rebooted in safe mode I did a factory data reset. After the reset I did a cache wipe and that didn't work. I also did a cache wipe, and factor data reset. Finally, I installed the RUU from their webpage and the problem persisted.
I wiped the phone and set it back to them, they were unable to get the phone to reboot during the 2-3wks they had it.
Any other suggestions, or answers to the question about Uh-Oh protection?
Highlyanimated said:
Any other suggestions, or answers to the question about Uh-Oh protection?
Click to expand...
Click to collapse
The replacement phone can be either refurbished or new, according to the ToS from HTC.
I just received my Uh Oh replacement from HTC the other day, and it looked new but was not in a retail box. It was shipped by Ingram Micro which is a wholesaler.
Too bad my replacement is doing the exact reboot thing you described, which is why I am reading the forums tonight. Sigh.
auggie721 said:
The replacement phone can be either refurbished or new, according to the ToS from HTC.
I just received my Uh Oh replacement from HTC the other day, and it looked new but was not in a retail box. It was shipped by Ingram Micro which is a wholesaler.
Too bad my replacement is doing the exact reboot thing you described, which is why I am reading the forums tonight. Sigh.
Click to expand...
Click to collapse
Sorry to hear that Auggie,
For the past 9 days I haven't had any reboots. Solution, turn off 4G LTE and use only GSM/WCDMA. Perhaps give that a try, if the same thing happens, then I think it means there's an issue with the radio (firmware/hardware).
Sucks, because service here on AT&T in LA is worse than when I lived in NYC and no LTE is like torture.
Thanks, this workaround solved my HTC reboot issue, keep using 3g is a pain but at least no need to buy a new phone. HTC supports or technicians really don't understand and know how to solve the issue
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
This sounds really similar to what I had happen after a while with my first Pixel XL. I tried to document everything HERE.
Wiping dalvik cache through TWRP seemed to be a short term fix (daily), but even that eventually stopped working. I ended up being able to jump into an "open enrollment" period for adding insurance for the phone with Verizon and then was able to use their extended warranty system to get a replacement phone (which was confusing since they said it was not an insurance claim since it appeared to be a phone defect out of my control, so I'm not 100% sure I even needed the insurance? Your mileage may vary.) The replacement was a refurb but has worked perfectly ever since I got it. They still had them in stock at the time or else I'd have tried to push for a 2 (or maybe now push for a 3 or 3a?). Good luck!
just went through the same thing. research shows it was most likely a known motherboard issue. its out of warranty so i bought a used one on swappa for 80 bucks and then sold my non functioning one at an ecoATM for 30 bucks. so im only net -50.
tgumina said:
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z
↑extract and fastboot flash this