Related
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
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Top5a said:
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Click to expand...
Click to collapse
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
thorur said:
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
Click to expand...
Click to collapse
Did it die closely after the unlocking/flashing? Or a long time after? Or was the unlocking/flashing an attempt to save the phone? Ever get it fixed? I'm so anxious!
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
Well, thanks for the input! Makes me feel a better hopefully the emmc isn't completely fried. I just really want my files, and am continually irritated at myself for having been so stupid to not make backups.. although I have phones from 10+ years ago that have never completely died in such an unexpected manner. It's quite the agonizing wait for a JTAG programmer to come in the mail. If I can manage to get it to boot from SD, which I haven't been able to do so far, do you think it's logical for me to simply reflash the bootloader/CWM, then attempt boot? It shouldn't erase files, right?
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I've also searched everywhere for a debrick image for 4.1.1 AT&T... anyone know where I can get one? All I can find are ones for 4.1.3 =\
EXACT same problem here, let me know if you find anything
(Btw, my phone also had the "power button stuck down" issue, but your phone will vibrate when you put the battery in if this is the issue.)
If I'm not mistaken you will be able to Odin to 4.1.1 while using the 4.3 SD card debrick (again this is just guessing)
Sent from my ATT Samsung Galaxy SIII using TapaTalk
I've tried the SD card debricks for 4.3, and still nothing happens. Yea, I also don't get vibrate. As a long shot, I actually installed the qualcomm drivers and ran the qdload.sh script to attempt to send a signal which kicks the phone out of that mode (works on some... I want to say, HTC, phones), but, yea, I think the emmc just failed somehow. I'm hoping that the failure is just in the bootloader segment, and that by jtag reflashing the bootloader area, I should be able to boot. Either that, or even if one of the memory sectors died, hopefully it's not the one with my data partition. I still can't believe this ! Out of all the electronics I've ever used, aside from a hard drive or two, I've never had something like a phone just kick the bucket with no warning. gha !
Also, thanks for all the tips and stuff, guys and gals. Tell me if you figure out anything, and I'll let you know if I get it fixed with jtag.
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ZOMG SO RUDE > haha, j/k ;P Yea, no problem, dude/dudette! I know how it feels reading threads with no followup... I'm actually surprised that people have come out of the proverbial woodwork mentioning having similar problems to me ! It really sucks spending inordinate amounts of time reading threads and not arriving at a definitive conclusion... so, yea, I especially want to let people know if there is a fix, and/or how I did it.
So, with regard to what you said about the snapdragons not failing... yea. This is rekking my mind, tbh, because I've just never had a device insta-fail on me like this (aside from some old computer hard drives that were server backed up, but yea that's essentially par for the course on that medium [yay for S.M.A.R.T.]). Especially a device that I'd only had for less than 2 years, and though my GS3 has heavy usage, I treat it very well (no drops, water, etc.)... so, yea.
Also, a minority of people with whom I have spoken via the æther have also experienced similar emmc failures on i747s, as well ! Which I was not expecting. It's still insane, though, to believe that, out of such a small percentage of phones that could potentially experience SDS, and then which ones actually do experience it... and then to not even have an i9000 and /still/ experience it on an i747... I feel as though I've won the lotto. Except ****ty.
I'm waiting on parts to come in, then surgery will commence.
Did you try going into download mode? If you can so that then the phone is fine. Another thing is try reflashing stock Odin which will erase msgs and stuff but not music or pics unless u tick "repartition".
Sent from my SGH-I747M using Tapatalk
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung I747 V1.0.5095.46594]
Connecting to the dead body...OK
Detected dead body ID: 0xhexhereisOK[redacted] - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is 1 MHz
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (000000, 0x000400000000 Bytes = 16.00 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)
No Resurrection Data is available for the eMMC Chip with Capacity = 16.00GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x0003AB3FBE00
Had to reduce the speed to that 2MHz/1MHz to get communication to work. So, 0x51 is a DCC power failure problem... but it is able to detect the initialized chips. So.. not really sure how to proceed at this point. I haven't checked the signal quality on my NRST line, which apparently can cause problems. Some people have increased the voltage from 1.8 to say 1.9, but doing something like that requires me to actually make my own resurrection file, which I haven't had the time to do yet.
Anyone seen a problem with something like this before?
The 000000 is somewhat unsettling, as the chip is apparently supposed to report some ID#? Although, the failures that I'm getting don't seem to be the typical ones that happen when the emmc becomes completely toasted.
Oh, yea... I can't seem to figure out wth is up with --> WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Like..... ??? I think I'm using the most up to date resurrector?!
EDIT: Dumping out the entire contents of the emmc (haven't had errors so far, but it will take a while at 1 MHz), into a bin file (this avoids the bad sectors in the bootloader).
Does anyone know what to do with the resultant *.bin file? I think that if I got another surrogate GS3, I'd be able to write that onto the phone, essentially cloning my dead phone. I'd like to avoid having to do that, though -- does anyone know how to write one of DCC bin jtag file dumps into a readable file system?
on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Quote100 said:
on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Click to expand...
Click to collapse
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
startswithPendswithOOH said:
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
Click to expand...
Click to collapse
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Board expired
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
It's time to move on.same happened to me a week ago.and I found the reason that my charger was at fault .the charger damaged one of the ics.it causes the board to draw a lot of current and causing severe heating issue within seconds.
So,better buy a new phone.
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
startswithPendswithOOH said:
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
I also ventured for the oven.and within 2 seconds.my board was gone...oven trick is just a sarcasm.don't go for it.
You can extra life of 30 minutes by giving it a Sunbath for some time.
My bad - misquoted a poster.
I kind of forgot about this thread whoops
Well I have news for you guys, I got a used g3 from eBay and wanted my apps from my old phone back and you know what I did?
I stuck it into the oven. I **** you not, after 375 for 5 minutes it started working again and I was able to get my apps and data to an SD card. Its still working but I took the battery out of it to use with the replacement. Can't believe it worked tbh
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
Hi
The other day I was looking for cell ID info on my LG G4 that I have had for a long time in the "hidden menus". I accidentally clicked on the radio test and the screen froze up. I tried to get out of it, but noting would work, not even the power button. After a few minutes, I saw the power off sequence. When I went to turn if back on, it would not power on. I plugged it in, no charge. I tried to boot to recover, nothing. I have the service manual for the h815 variant which differs from mine. I do not have a boardview or anything.
I know trying to permanently fix it is a lost cause, it is old and it had other problems, such as the headphone jack not working even after I replaced it, and the read camera's autofocus being stuck after I replaced it with a cheap knockoff. However, I want to get it running long enough to get important things off of it. I was foolish and a few of my 2FAs are only on that device, and while I have gotten most of them switched to my alternate, I need to make sure to get the rest. I'm not sure which troubleshooting route to follow: Power? Crash/No Boot? No charge? I would follow each but some of the differences between the board I have and the service manual includes a few of the test points I need. Currently I have to attach wires to my multimeter leads to get small enough tips.
If anyone has anything that can help me get this running for a bit, let me know please.\
edit: biggest problem is I don't know how to tell from the schematic what pin is which on the board
Catt0s said:
Hi
The other day I was looking for cell ID info on my LG G4 that I have had for a long time in the "hidden menus". I accidentally clicked on the radio test and the screen froze up. I tried to get out of it, but noting would work, not even the power button. After a few minutes, I saw the power off sequence. When I went to turn if back on, it would not power on. I plugged it in, no charge. I tried to boot to recover, nothing. I have the service manual for the h815 variant which differs from mine. I do not have a boardview or anything.
I know trying to permanently fix it is a lost cause, it is old and it had other problems, such as the headphone jack not working even after I replaced it, and the read camera's autofocus being stuck after I replaced it with a cheap knockoff. However, I want to get it running long enough to get important things off of it. I was foolish and a few of my 2FAs are only on that device, and while I have gotten most of them switched to my alternate, I need to make sure to get the rest. I'm not sure which troubleshooting route to follow: Power? Crash/No Boot? No charge? I would follow each but some of the differences between the board I have and the service manual includes a few of the test points I need. Currently I have to attach wires to my multimeter leads to get small enough tips.
If anyone has anything that can help me get this running for a bit, let me know please.\
edit: biggest problem is I don't know how to tell from the schematic what pin is which on the board
Click to expand...
Click to collapse
Sounds like the ilapo but as you have modified the hardware it can be everything of course . anyways it wouldn't hurt to try some of the Bootloop fixes which you can find in my signature . Your best chance might be flashing the TWRP version for the ilapo and trying to load the recovery. Another option is of course to get into download mode and use salt to backup the user data partition.
Ilapo TWRP (when your device is unlocked only):
https://leech.binbash.rocks:8008/TWRP/ILAPO-O/
SALT (included in mAid / fwul): http://bit.do/FWULatXDA
Sent from my OnePlus 7T Pro using XDA Labs