Develop Bugs

Samsung Galaxy Nexus Suddenly Stopped Working!

I was using the phone today and the screen suddenly locked up on me. It wouldn't respond to any button presses so I just did a battery pull to reset it. However, the phone won't turn back on now. It doesn't do anything, even when plugged into the charger, the phone doesn't even indicate that it's charging or anything at all. It's like it has been completely bricked.
It was completely stock, never unlocked it or rooted and never installed any custom rom or anything of that nature. I've only had the phone for a couple of months and I'm completely baffled as to what could have happened. It certainly wasn't anything that I did.
Any ideas? Or does anyone have any experience with this type of thing happening to their phone?

So I've left the battery out for over 30 minutes and it still won't turn on. I have an extended battery and the regulary battery that came with the phone and it won't turn on with either battery.
I have also tried the volume down and power button method and that doesn't do anything at all either.
Plugging the phone into the computer with the USB cable also does nothing.

How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....

Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium

ptmr3 said:
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Click to expand...
Click to collapse
I got the phone when it was released and I ordered it online right from Verizon's website.

I hope that you have the warranty from the carrier!

gulmat said:
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it was that simple for me.. I held the power button down for over a minute and still, nothing happened. This is really frustrating.

!!!!!!!+111111
evolishesh said:
I hope that you have the warranty from the carrier!
Click to expand...
Click to collapse
.....Clones & Drones.....

ptmr3 said:
!!!!!!!+111111
.....Clones & Drones.....
Click to expand...
Click to collapse
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.

russ4h said:
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
Click to expand...
Click to collapse
I'd definitely go to Verizon with this. Most definitely manufacturer defect.

Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk

You should be able to get a refurbished phone.its probably just a manufacturer defect.
Sent from my Galaxy Nexus using Tapatalk

android01 said:
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?

The phone has a 1 year warranty on it. You shouldn't have to pay anything but you might just get a refurbished replacement.

I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.

russ4h said:
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
Click to expand...
Click to collapse
I'd say go contact Verizon and see what they say. If they can't help you out then you gotta contact Samsung and I believe (if my memory serves me right) all their products have a one year warrenty from the day the phone was used. So you should see what they have to say.

Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.

tandp74 said:
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
Click to expand...
Click to collapse
That's awful man. I've been reading more and more about random reboots happening with this phone and what not.. I just don't know what to think right now, I thought this was supposed to this beast of a phone and now after only a couple of months, it has completely stopped working for no apparent reason at all. Pretty lame, and this has definitely never happened to me before as I always take care of my phones. I just figured that if something were to happen to this phone, it would be from my own doing, just as it has been with every other phone that I've ever owned (ie from modding, from a drop, etc.). Samsung gets a thumbs down from me, I paid a lot of money to get this phone and now I'm going to be stuck with a refurb because they have put out a crap product.
As for you, I wouldn't even tell Samsung that you unlocked it. They probably won't be able to tell if you did or not since the phone won't boot properly. They should offer you a refurb, so you'll be in the same boat as me. I went into Verizon today and that's the best that they could do. I have to wait til Monday for it to come in the mail. I'm stuck without a phone til Monday.

volsey said:
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
Click to expand...
Click to collapse
Yeah, it's looking like this phone has been giving many people similar problems. Samsung must have let a bad batch slip out or something. I was completely stock as well, no unlock, no root, no custom rom, just a plain old basic user here and mine took a dump on me.

Mine does this about every other day and I have to pull the battery and restart, sorry to hear yours won't reboot. Ouch

[Q] Stuck at "erasing userdata..."

Hello,
Recently my Nexus 7 (2013) battery ran out because I forgot to charge it. Since then, it won't boot back into Android when it's turned on - all I get is the black screen with "Google" written on it. I have searched all over the internet for the past few days, but I'm unable to find a solution. I'm hoping that someone here can help me, because the tablet's warranty has expired and I'm completely out of ideas. Here are the things I've tried or noticed:
I can't boot into Android. The tablet gets stuck on the black screen with "Google" written on it.
I can access the bootloader and interact with the tablet via fastboot.
The bootloader is locked. Trying to unlock it via fastboot oem unlock displays the "Unlock bootloader?" screen on the tablet. After I select "Yes", the command line output on the computer shows the following output, but doesn't get any further:
Code:
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Trying to boot into recovery mode from the bootloader results in the tablet being stuck on that black screen with "Google" written on it.
I have removed the back cover from the tablet and reconnected every exposed connector. I couldn't take the battery out because I don't have the appropriate screwdriver. Doing this changed nothing.
Any help would be sincerely appreciated. At this point I'm worried that it is a hardware issue, but I'd like to exhaust all options before declaring it as such, as it would essentially mean the tablet is going in the garbage bin.

How long did you let it sit at "erasing userdata"?
I don't recall specifically on my N7 but I know when I unlocked the bootloader on my 2013 Moto X it seemed like an eternity, which was mostly because there is no progress indicator, it just said "erasing userdata" and sat there for a while. Probably like 5-10 minutes.

fury683 said:
How long did you let it sit at "erasing userdata"?
Click to expand...
Click to collapse
It'll be around 2 hours now.

Wengard said:
It'll be around 2 hours now.
Click to expand...
Click to collapse
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.

fury683 said:
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
Click to expand...
Click to collapse
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo

mo123456789 said:
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
Click to expand...
Click to collapse
Thank you for your response.
I'm sorry to hear about what happened to you. I've been reading around and guessed it's probably a hardware problem based on other people's similar experiences. Unfortunately my tablet is out of warranty as well, and I'm definitely not going to spend more on the repairs than I would on a brand new tablet. I regret purchasing the tablet in the first place, I really expected it to last longer than a year.
If you can, please let me know what ASUS says about this, if you intend to call them. They don't have a subsidiary in my country, but if you get lucky, I might press my chances as well and perhaps I can get this repaired for a reasonable price.

Mine has lasted 5 years more but my Nexus 7 has ended its days the same way as yours. Stuck at google when switched on, and stuck at bootloader when triying to flash it.
Time to go, it seems.

Nexus 5x shut off and won't turn on

If I posted this in the incorrect place or there is something related to my issue, I apologize in advance.
I've been searching here and all over the internet and no progress yet so I decided to make a new account here just to see if anyone can help me because I'm out of ideas right now.
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas. I just want to at least recover some pictures and information I have in it that isn't backed up, if anyone can help me I would greatly appreciate it.
Thanks in advance

It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.

Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA

sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
At this point, I'm willing to try anything. Thanks

driss.sadok said:
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
Click to expand...
Click to collapse
If it's a hardware issue like sfhub suggested, I don't think this will fix it.

PennyScissors said:
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
Click to expand...
Click to collapse
Same here... cannot enter recovery mode, so flashed new rom stock rom.
The flashing was fine but it didn't help.

guys if u can get to the bootloader, sure it can be fixed.. everything is possible with the fastboot, u can fix any issue. if it's a hardware issue the bootloader wouldn't work as well.

Re Nexus 5X won't turn on - I've had same issue
PennyScissors said:
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas...
Click to expand...
Click to collapse
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.

danielledowns01 said:
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
Click to expand...
Click to collapse
I contacted Google and they didn't help me at all because my warranty expired last month, they literally just told me to put in a repair request at the LG repair webpage....this sucks

My experience exactly...
My wife's Nexus 5 exhibited the exact same symptoms this morning. It's been running perfectly for 20 months and today it died, and we're unable to even get into the bootloader screen or power on the phone.
Taking your advice, we put it in the freezer for 15 minutes and were able to perform a factory reset wiping all data from the phone. We are going to take advantage of Google's Christmas 2017 promotion and return the Nexus 5X and buy a Moto 4X. They require you perform a factory reset before returning the phone in order to receive a credit for the returned Nexus 5. Thank you so much for the help!
Dennis
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse

https://forum.xda-developers.com/nexus-5x/help/help-nexus-5x-lg-off-to-t3729739
I've just posted this thread overlooking yours. I think this is becoming another common issue. Has the freezer trick worked with anybody else?

I am having the same issue described here. My Nexus 5x went into a Bootloop about one month ago, but I was able to get it working again by going into Recovery Mode. About 4 days ago it went into a constant Bootloop, just showing the Google screen, and I couldnt get back in to recovery mode. I ordered a new phone on Tuesday (Pixel 2) and as long as I am able to do a factory reset I should get a $150 credit when I send this phone back. So, in desperation, I took a chance on the 15 minute freezer trick, and it worked! I was able to get into recovery mode (power + volume down, select Recovery Mode, little dude on his back came up, pushed power + volume up once) and cleared the cache and applied the factory reset. Ridiculous that this phone only lasted 18 months, but if I get the $150 credit I will be happy.

Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)

d_ckhole said:
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
Click to expand...
Click to collapse
The only way to connect that buddy to PC is to get SoC (CPU) working, so theoretically you can go towards reballing the chip. But I guess it's not an easy thing for such a little chip. Also u will need kinda plate for balls, i think there are no common ones, so u can make it yourself if have a technical education.
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO

orcgoblinsupply said:
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
Click to expand...
Click to collapse
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.

d_ckhole said:
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
Click to expand...
Click to collapse
I've seen a post of a guy who sent his motherboard to china and got reballed it and gained 4gb of ram. Can be wrong, but it was around $50 and a month of time.
---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------
Actually found the post itself: https://4pda.ru/forum/index.php?showtopic=722679&st=3440#entry68093395 (it's in russian, so u're welcome at translate.google.com) In short - a guy fount a Chinese service and men in the middle who could resend his motherboard to china, it cost him $100

Pixel 3 XL shutdown suddenly won't restart

So just now my Pixel 3 XL just suddenly shutdown and won't restart
No matter what button combo I push -- nothing !
No matter how long I push the buttons -- nothing !!
Any suggestions??
I'm assuming hardware but I wasn't doing anything -- just walking through the grocery store -- came out -- dead !

jcrompton said:
So just now my Pixel 3 XL just suddenly shutdown and won't restart
No matter what button combo I push -- nothing !
No matter how long I push the buttons -- nothing !!
Any suggestions??
I'm assuming hardware but I wasn't doing anything -- just walking through the grocery store -- came out -- dead !
Click to expand...
Click to collapse
I am having the same issue with my XL as well. Will only reboot if you boot into recovery ( vol down and power ) then reboot and continue where you left off. No fix yet.

xmattisi said:
I am having the same issue with my XL as well. Will only reboot if you boot into recovery ( vol down and power ) then reboot and continue where you left off. No fix yet.
Click to expand...
Click to collapse
Unfortunately mine won't even boot into recovery

jcrompton said:
Unfortunately mine won't even boot into recovery
Click to expand...
Click to collapse
I am sorry to hear that.

jcrompton said:
Unfortunately mine won't even boot into recovery
Click to expand...
Click to collapse
That definitely sucks! RMA...RMA...RMA! :good:

Badger50 said:
That definitely sucks! RMA...RMA...RMA! :good:
Click to expand...
Click to collapse
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.

xmattisi said:
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
Click to expand...
Click to collapse
Don't blame you a bit my friend. Problem is, what to buy that doesn't have it's problems as well? I wish you well in your search :good:

xmattisi said:
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
Click to expand...
Click to collapse
Why don't you take it back to bestbuy?

jd1639 said:
Why don't you take it back to bestbuy?
Click to expand...
Click to collapse
BestBuy only has a 14 day return policy. Even when they do run the return if its not covered under a protection plan which is for physical damages ( $200 deducible to get the replacement ). On top of that they also have a restocking fee lol. When you try the return under the manufacturer warranty it tells me to Call Google.

I haven't even fully remembered what I lost but this has confirmed one of my concerns about a device that doesn't have an SD card .... Basically either Pixel I've lost everything that doesn't get backed up to the cloud
So I gotta get better at backup routine or get a device with an SD card

I believe titanium might be the way to go. https://www.titaniumtrack.com/titanium-backup.html

Well for sure TiBu would be helpful for your apps and some of the app says if you were doing backups online
I'm mainly taking about the scores of files that were accumulated in out device that may not get backed up ..... Where on a device with an SD card, I use the card mainly to store things.

Dont know if this is related, but i did a restore of a nandroid and when it finished the phone turned off all on its own. When i went to power it back on nothing would happen. Even trying to boot to recovery or fastboot did nothing. When i plugged it in no charging indicator, and it wasnt recognized by a pc. I thought it was bricked for sure. So sure i did a warranty claim. Well while boxing it up to send in i hit the power button and noticed a little white battery icon flash for a second then disapear. This was the most i got it to do since it shut it self off. So i went through the whole process again of trying to power it on again with no luck. Then i got an idea from back in the day i think it was with the droid incredible maby, to hold vol down and power while plugging it in. When i did this i again saw the little white battery icon flash on the screen. So i kept holding vol down and power while plugging and unplugging the power cord over and over again. About the sixth time plugging it in, it booted to fastboot. I screamed and jumped around like a little school girl i was so happy lol. Anyways i flashed the feb ota and it booted right up like it was brand new. Hopefully this may help someone else who thinks their phone is bricked.
Sent from my [device_name] using XDA-Developers Legacy app

cmlusco said:
Dont know if this is related, but i did a restore of a nandroid and when it finished the phone turned off all on its own. When i went to power it back on nothing would happen. Even trying to boot to recovery or fastboot did nothing. When i plugged it in no charging indicator, and it wasnt recognized by a pc. I thought it was bricked for sure. So sure i did a warranty claim. Well while boxing it up to send in i hit the power button and noticed a little white battery icon flash for a second then disapear. This was the most i got it to do since it shut it self off. So i went through the whole process again of trying to power it on again with no luck. Then i got an idea from back in the day i think it was with the droid incredible maby, to hold vol down and power while plugging it in. When i did this i again saw the little white battery icon flash on the screen. So i kept holding vol down and power while plugging and unplugging the power cord over and over again. About the sixth time plugging it in, it booted to fastboot. I screamed and jumped around like a little school girl i was so happy lol. Anyways i flashed the feb ota and it booted right up like it was brand new. Hopefully this may help someone else who thinks their phone is bricked.
Click to expand...
Click to collapse
Absolute unbelievable!!!
Now I'm thankful but maybe even more frustrated
This worked!!!!!
After an hour on the phone with Google support (I obviously knew more than they did) ..... Worse yet with an RMA device in hand ...... My phone is back up and running!!
Now... Should I send the reburbed RMA back or the original phone back? Lol

Awesome glad it worked. Im not sure if this is some sort of issue with the hardware that will eventually happen again, or just a weird software fluke thats over with for good. Its been about a week so far and all is well. I cancled the return and kept it.
Sent from my [device_name] using XDA-Developers Legacy app

cmlusco said:
Awesome glad it worked. Im not sure if this is some sort of issue with the hardware that will eventually happen again, or just a weird software fluke thats over with for good. Its been about a week so far and all is well. I cancled the return and kept it.
Click to expand...
Click to collapse
The DINC! What a great device and learning tool that was! :good::good:

Thread cleaned. Keep it civil.
The lack of respect needs to stop. All users know there will be risks when doing anything to a phone post bootloader unlock.

Question *Urgent Help* Bricked Pixel 6 Pro

I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.

Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.

roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.

Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.

Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!

Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.

2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.

verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.

96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port

Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??

liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try