Related
Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.
You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app
LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.
I was excited to see that one of my Nexus 7 tablets was getting the 4.4.3 update today. I started the update and let it go. When I came back I was at the lock screen. I only have the simple swipe to unlock. I couldn't unlock it at all. Held in the power button for several seconds until it shut off. Thought maybe something didn't load right. When I booted it back up, same thing. No touch screen.
Here is a little background. This is a Nexus 7 v2. Unlocked it and rooted it using the Nexus Root Toolkit version 1.8.2. During the process I did install the recommended recovery option. Everything worked great until the update today. Seems like I can't do anything. I can't use this toolkit to restore from the backup I made because I can't get into the tablet to turn on USB debugging or whatever it is asking me to do. I tried booting into recovery by holding the volume down and power button. The result was a picture of the android with a red triangle and an exclamation point. Not sure what else to do so I am posting this for all of you guys with more experience than me. Can anyone give me any suggestions?
opreda said:
I was excited to see that one of my Nexus 7 tablets was getting the 4.4.3 update today. I started the update and let it go. When I came back I was at the lock screen. I only have the simple swipe to unlock. I couldn't unlock it at all. Held in the power button for several seconds until it shut off. Thought maybe something didn't load right. When I booted it back up, same thing. No touch screen.
Here is a little background. This is a Nexus 7 v2. Unlocked it and rooted it using the Nexus Root Toolkit version 1.8.2. During the process I did install the recommended recovery option. Everything worked great until the update today. Seems like I can't do anything. I can't use this toolkit to restore from the backup I made because I can't get into the tablet to turn on USB debugging or whatever it is asking me to do. I tried booting into recovery by holding the volume down and power button. The result was a picture of the android with a red triangle and an exclamation point. Not sure what else to do so I am posting this for all of you guys with more experience than me. Can anyone give me any suggestions?
Click to expand...
Click to collapse
Once you are back at the android lying on its back, hold down power and tap the volume up key, this will get you a recovery menu, from there you can try to wipe cache and dalvik, and if need be, factory reset.
Touch screen is still dead.
Thanks for the quick update. I did all of the above and was able to reset the tablet. Not I am at the Welcome screen and tapping the screen does nothing I find it hard to believe that the touchscreen died during the update. I guess I will need to look on EBay for some parts. Can anyone suggest what parts to look for? Touch screen digitizer assembly is listing for around $65.
opreda said:
Thanks for the quick update. I did all of the above and was able to reset the tablet. Not I am at the Welcome screen and tapping the screen does nothing I find it hard to believe that the touchscreen died during the update. I guess I will need to look on EBay for some parts. Can anyone suggest what parts to look for? Touch screen digitizer assembly is listing for around $65.
Click to expand...
Click to collapse
I might suggest you open it up now (you're going to have to anyways to replace it), and make sure the cable is securely inserted.
opreda said:
Thanks for the quick update. I did all of the above and was able to reset the tablet. Not I am at the Welcome screen and tapping the screen does nothing I find it hard to believe that the touchscreen died during the update. I guess I will need to look on EBay for some parts. Can anyone suggest what parts to look for? Touch screen digitizer assembly is listing for around $65.
Click to expand...
Click to collapse
If touch works in TWRP then its not hardware related
Sent from my Nexus 4 using XDA Free mobile app
Tried the cables...
I found a tear down video on YouTube and was able to disconnect and then reconnect the long cable that goes across the battery connecting the 2 circuit boards. I believe this cable is connected to the digitizer. I was hoping that maybe this would fix my problem. No such luck.
Here is my question. This tablet was purchased on EBay and was sold as a refurbushed tablet with a 90 day warranty from Asus. I purchased it about a month ago so I should be in the warranty period. Since I unlocked the bootloader and rooted it, should I even try to send it to Asus for repair or should I just spend the $65 and buy the replacement parts on EBay? Instead of just buying the digitizer, I was thinking I would get the combo digitizer and lcd screen since it would save me having to use a heat gun to unglue the screen from the digitizer.
What do you think would be my best bet?
Thanks to everyone for all your suggestions.
opreda said:
I found a tear down video on YouTube and was able to disconnect and then reconnect the long cable that goes across the battery connecting the 2 circuit boards. I believe this cable is connected to the digitizer. I was hoping that maybe this would fix my problem. No such luck.
Here is my question. This tablet was purchased on EBay and was sold as a refurbushed tablet with a 90 day warranty from Asus. I purchased it about a month ago so I should be in the warranty period. Since I unlocked the bootloader and rooted it, should I even try to send it to Asus for repair or should I just spend the $65 and buy the replacement parts on EBay? Instead of just buying the digitizer, I was thinking I would get the combo digitizer and lcd screen since it would save me having to use a heat gun to unglue the screen from the digitizer.
What do you think would be my best bet?
Thanks to everyone for all your suggestions.
Click to expand...
Click to collapse
You can always unroot and relock the bootloader (you can use this to get it back to factory), if it's under warranty I'd go that route.
USB debugging...
Wouldn't this require me to have USB debugging enabled on the tablet? Since I went into recovery and restored it back to factory defaults, I can't get past the "Welcome" screen because I can't touch the screen. I am going to try and chat with the Asus support team and see if I can get an RMA. I'd rather go that route than take the whole thing apart myself. I like messing with computers but I don't like messing with phones and tablets. They are just too small and fragile for my unskilled hands. Thanks for your help. I will post an update if I am able to send the tablet out for repair.
opreda said:
Wouldn't this require me to have USB debugging enabled on the tablet? Since I went into recovery and restored it back to factory defaults, I can't get past the "Welcome" screen because I can't touch the screen. I am going to try and chat with the Asus support team and see if I can get an RMA. I'd rather go that route than take the whole thing apart myself. I like messing with computers but I don't like messing with phones and tablets. They are just too small and fragile for my unskilled hands. Thanks for your help. I will post an update if I am able to send the tablet out for repair.
Click to expand...
Click to collapse
It uses fastboot, I don't think it needs it (in spite of what the OP says). And if I'm wrong, the worst that will happen is it won't work. You will need the fastboot drivers correctly installed in your windows or linux environment though.
worked
Thanks for the link. I ran the dead_nexus7.bat file since I couldn't turn on the USB debugging. It wiped out everything. I then ran the command to relock the bootloader. All set. Talked with Asus (web chat) and got an RMA number. They even sent me a FedEx label to use. Now I am more comfortable sending this unit back since it has been restored to stock and the bootloader is locked again. Thank you for all of your help.
opreda said:
Thanks for the link. I ran the dead_nexus7.bat file since I couldn't turn on the USB debugging. It wiped out everything. I then ran the command to relock the bootloader. All set. Talked with Asus (web chat) and got an RMA number. They even sent me a FedEx label to use. Now I am more comfortable sending this unit back since it has been restored to stock and the bootloader is locked again. Thank you for all of your help.
Click to expand...
Click to collapse
No problem, please let me know how it worked out. Good luck!
Update to my issue...
I contacted Asus using their web chat. Told the CSR about my issue and confirmed my Nexus 7 serial number. They emailed me paperwork to take to my local FedEx shipping location. It happened to be our local Office Max store. They scanned in the bar-code and processed it. I got a confirmation email with the tracking number. This was around June 6th. They received it in Texas 4-5 days later (because of the weekend). I checked the status almost every day. About 10 days after they received it I saw a status update. They included a FedEx tracking number but every time I entered it into the FedEx website, it showed up as invalid. I gave it a couple of days and then called FedEx. They were able to track the package and it was delivered to my house in late June. All in all it took about 3 weeks but they did repair it. I thought they would have just sent me a refurbished tablet. They actually fixed my tablet because it still had my screen protector on it. Just wanted to update you with the good news. My son was so excited to finally get his tablet back. I wasn't expecting it to take so long but I guess I can't complain. It didn't cost me anything out of pocket even to ship it to them. Thank you for your help with getting everything back to stock and the boot-loader locked.
Tablet was originally purchased as a refurbished tablet from a seller on EBay. It was supposed to have a 90-day warranty from Asus. Glad they held up their end. It all worked out in the end.
opreda said:
I contacted Asus using their web chat. Told the CSR about my issue and confirmed my Nexus 7 serial number. They emailed me paperwork to take to my local FedEx shipping location. It happened to be our local Office Max store. They scanned in the bar-code and processed it. I got a confirmation email with the tracking number. This was around June 6th. They received it in Texas 4-5 days later (because of the weekend). I checked the status almost every day. About 10 days after they received it I saw a status update. They included a FedEx tracking number but every time I entered it into the FedEx website, it showed up as invalid. I gave it a couple of days and then called FedEx. They were able to track the package and it was delivered to my house in late June. All in all it took about 3 weeks but they did repair it. I thought they would have just sent me a refurbished tablet. They actually fixed my tablet because it still had my screen protector on it. Just wanted to update you with the good news. My son was so excited to finally get his tablet back. I wasn't expecting it to take so long but I guess I can't complain. It didn't cost me anything out of pocket even to ship it to them. Thank you for your help with getting everything back to stock and the boot-loader locked.
Tablet was originally purchased as a refurbished tablet from a seller on EBay. It was supposed to have a 90-day warranty from Asus. Glad they held up their end. It all worked out in the end.
Click to expand...
Click to collapse
Good to hear, thanks for the update.
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
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
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