Hello all,
This past Saturday my Galaxy S8+ froze up and the display showed a bunch or discolored horizontal lines, then it shut down and went into a bootloop. I know this isn't an uncommon issue but it seems this usually happens from a botched upgrade/flash attempt. I've never attempted this and was just using my phone as normal. I have read through many bootloop threads and tried many of the troubleshooting steps, but I haven't had any success.
I'm starting to wonder if there's a hardware issue now. I'm hoping someone might have a new suggestion I could try, or point out any mistakes I made in my previous troubleshooting. I'm new here, so sorry if I left out any important details below, please let me know.
Thanks for helping!
Symptoms:
Phone is in a bootloop.
On occasion it comes out of the loop and displays some new phone setup menus (since I did a factory reset), but it crashes fairly quickly (and display gets distorted again) and re-enters the bootloop. It varies how far I can get into the new setup, before it crashes, but generally it's a matter of seconds.
On occasion, it comes out of the loop and displays a "System software not authorized by AT&T" message.
Attempts to fix:
Went into recovery*mode, wiped cache. Same results on reboot.
Went into recovery*mode, factory reset device. Same results on reboot.
Odin tool (3.13.1) and flashed lastest G955USQ8DTJ1_G955UOYN8DTJ1_VZW from sammobile. Device reached 32%, stayed for a while, then rebooted and back to bootloop.
Samsung Smart Switch, but then I discovered they neutered the app and it won't recover a device anymore.
Tried iMyFone Fixppo, but it failed to find latest FW for the device.
Phone details:
S8+ (SKU: SM-G955UZKV)
Bought it reburb 2 years ago.
It has never been rooted by me, so everything is stock.
Memory was close to full, but I still think I had a few GB left.
It was on VZW when bought, but I had it unlocked so I could use on AT&T.
In downloader mode, it says "Carrier: VZW", "Current Binary: Samsung Official", "FRP Lock: On", "Warranty Void: 0x0"
BlackbirdKM said:
Hello all,
This past Saturday my Galaxy S8+ froze up and the display showed a bunch or discolored horizontal lines, then it shut down and went into a bootloop. I know this isn't an uncommon issue but it seems this usually happens from a botched upgrade/flash attempt. I've never attempted this and was just using my phone as normal. I have read through many bootloop threads and tried many of the troubleshooting steps, but I haven't had any success.
I'm starting to wonder if there's a hardware issue now. I'm hoping someone might have a new suggestion I could try, or point out any mistakes I made in my previous troubleshooting. I'm new here, so sorry if I left out any important details below, please let me know.
Thanks for helping!
Symptoms:
Phone is in a bootloop.
On occasion it comes out of the loop and displays some new phone setup menus (since I did a factory reset), but it crashes fairly quickly (and display gets distorted again) and re-enters the bootloop. It varies how far I can get into the new setup, before it crashes, but generally it's a matter of seconds.
On occasion, it comes out of the loop and displays a "System software not authorized by AT&T" message.
Attempts to fix:
Went into recovery*mode, wiped cache. Same results on reboot.
Went into recovery*mode, factory reset device. Same results on reboot.
Odin tool (3.13.1) and flashed lastest G955USQ8DTJ1_G955UOYN8DTJ1_VZW from sammobile. Device reached 32%, stayed for a while, then rebooted and back to bootloop.
Samsung Smart Switch, but then I discovered they neutered the app and it won't recover a device anymore.
Tried iMyFone Fixppo, but it failed to find latest FW for the device.
Phone details:
S8+ (SKU: SM-G955UZKV)
Bought it reburb 2 years ago.
It has never been rooted by me, so everything is stock.
Memory was close to full, but I still think I had a few GB left.
It was on VZW when bought, but I had it unlocked so I could use on AT&T.
In downloader mode, it says "Carrier: VZW", "Current Binary: Samsung Official", "FRP Lock: On", "Warranty Void: 0x0"
Click to expand...
Click to collapse
Can you run graphics test from recovery mode? i guess something is overheating during boot. Can you put the device on a water/ice bag to lower the temp, and do factory reset ? as you said it displays some setup menus so its worth a shot
d3athAdd3r said:
Can you run graphics test from recovery mode? i guess something is overheating during boot. Can you put the device on a water/ice bag to lower the temp, and do factory reset ? as you said it displays some setup menus so its worth a shot
Click to expand...
Click to collapse
Seems to perform the graphics test fine. It cycles through all the graphics tests and then returns to the recovery menu.
I tossed the phone in the freezer for a few minutes and then tried a normal reboot. To my surprise it booted into the new phone setup menu, but this time it didn't crash right away. I was actually able to get through the complete setup and restore all my old apps (hooray google backups). In all, it probably worked for about 5 minutes before crashing again. I repeated the test, and verified that cooling it down does help.
So, great call! But what does that mean? Is there anyway to determine what is causing is this without a tearing it open?
BlackbirdKM said:
Seems to perform the graphics test fine. It cycles through all the graphics tests and then returns to the recovery menu.
I tossed the phone in the freezer for a few minutes and then tried a normal reboot. To my surprise it booted into the new phone setup menu, but this time it didn't crash right away. I was actually able to get through the complete setup and restore all my old apps (hooray google backups). In all, it probably worked for about 5 minutes before crashing again. I repeated the test, and verified that cooling it down does help.
So, great call! But what does that mean? Is there anyway to determine what is causing is this without a tearing it open?
Click to expand...
Click to collapse
Nice i guess it should be the processor thats heating.
You can find the location of the heatsink/thermal paste/process here (around 3:30 min mark)
https://www.youtube.com/watch?v=GRmY-4HKVIk&t=362s&ab_channel=JerryRigEverything
The processor seems to be located below Bixby button.
You can also try gently pressing the spot where processor is located to seat it back, but am not sure how long it may stay. if the thermal paste is dry and not in contact with processor, you have to open the device.
Or you can take it to a local repair shop for some assistance.
Related
Soo I have a Galaxy S II I9100. And it was great until something happened. Lord knows what happened to it. But I was running the latest version of Sensation ROM (1.6) smoothly. Then yesterday all of the sudden my phone kinda stops working more or less. The screen became unresponsive at times, the screen would activate on its own and then I would not be able to use it. After taking the battery out and restarting it things were OK for about 5 minutes.
Then after trying to open any sort of applications the Voice Command app would start and I wouldn't be able to exit out of it. After mashing the home button I could get out of it and then trying to open anything would result in a black screen (status bar active at top). So I figured maybe something went wrong with the software. I happened to have an update .zip of Sensation from 1.5 to 1.6, so I reflashed. This did not really help out. Even plugging in the USB cable was a 50/50 chance, Windows would tell me that the device is seemingly defective and sometimes it would work. But then trying to open USB Mass Storage was a big headache as well.
So I let it sit the night and then this morning I used Odin to flash a stock kernel. This seemed to help out somewhat, it made the system more stable and usable for a little bit. In the meantime I went to the so called "Samsung Cell Phone Service Center" in my city which turned out to be some repair shop for iPhones (go figure). After elaborately explaining my problems they said "must be a software issue". Which it is't. Anyways in the meantime I called Samsung America for direction, after talking to 3 different CS reps they referred me to call Samsung UK because that's where the phone was manufactured.
After that I did a factory reset and that made the issues even worse.
So I'm at a cross roads. I am probably going to be putting a call into Samsung UK tomorrow to try and figure something out.
Do a FULL wipe in CWM and then flash a stock rom. See if that helps. If not, then it's a hardware problem.
I had done that and then flashed a stock ROM which removed CWM, root, and the Sensation ROM. While that seemed to have helped, it would still randomly reboot (fewer than now) and the same issues persisted but less frequently. In the SGS2 stock recovery mode I did factory reset and wiped all data and cache and the problems are back and more frequent. I did take the phone to the beach but it was in a bag wrapped in a shirt..
could that have somehow caused this issue with the hardware?
I'm thinking that this is a hardware issue.
Yes, I think it is. One thing that comes to mind, did your modem change when flashing different roms? If not try a different modem. Otherwise it's really a hardware problem.
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months. I haven't installed any new apps in a few weeks, but my phone has been doing any regular updates. Today, my phone completely locked up about 5 separate times (about 2-3 hours apart for each). Each time, the only way to get my phone back was by pulling the battery (even the 10+ second press of the power button didn't work)... annoying, but manageable.
After the last lock up, my phone got stuck on the SAMSUNG logo (not the S-III logo). I let it sit there for about 45 minutes, and it was pulsing the entire time. Finally, I gave up and pulled the battery one more time. After putting it back in, the phone gets to the S-III logo, but the S is not pulsing. I've let it sit on that for over an hour - with no luck.
The failed root threads all suggest installing ODIN, rooting, wiping everything, then installing a stock firmware. I'm really hoping there is something else I can try, since wiping my phone would be extremely painful at the moment...
Anyone have any ideas?
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Sadly as this may be, mine derped out exactly like yours one week after I bought it. It would randomly reboot, lag a lot until the day I woke up to that brilliant Samsung boot screen and nothing more helped.
Had not done anything to it so I returned it for a replacement. Turns out I had a faulty unit.
Sorry bro, guessing it's the only thing that will get yours sorted again. While I know in every product there will always be faulty units, I'm seeing dead sgs3 threads very frequently, I'm guessing Samsung's build quality isn't that good...
Sent from my GT-I9300 using XDA Premium App
It might be worth remembering ...
shaunco said:
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months.
...
Click to expand...
Click to collapse
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
JJEgan said:
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Click to expand...
Click to collapse
I would love to backup my data, but since I had a stock bootloader (not CWM or one of the others) and the PIT seems gone, I'm SOL.
xclub_101 said:
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
Click to expand...
Click to collapse
Yeah, bad wording on my part. When I bought it (the first day Amazon sold the I9300), it had 4.0.4. It has had 4.1.1 since mid-October. My comment of it "working great" was in relation to the random lockups (and now the stuck at logo issue).
Lucky for me, the phone is a work phone, so I bought a new I9300 at Fry's this morning and at least got my service and all my apps back, along with the data for the apps that were nice enough to put it on the SD...
This means my focus has shifted from returning my old I9300 to a working state to simply getting data off of it. If the bootloader shows "no product", it seems that the partition table is shot. Loading a new partition table would destroy the underlying data... so, is there anything I can do (even things that are physically destructive to the phone) to get the data (even as a single binary blob) off the internal 16GB storage?
As I said, I'm happy to rip this thing to pieces, if there is a way.
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
BladedYouth said:
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
Click to expand...
Click to collapse
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Tonyco1 said:
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Click to expand...
Click to collapse
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
BladedYouth said:
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
Click to expand...
Click to collapse
Yes just browse this forum but only section about Windows Phone 7 Development and Hacking. You will find DFT exclamation of how to install HSPL. In mine it was very easy because I not receive Country ID fail my phone was buy in Europe. If you receive Country ID error you need to proceed with goldcard it is explained there but first proceed without goldcard if it work it is very easy. Also when you proceed SPL2.05 it is not clear in the topic but you need to be in bootloader so you should start your phone with VolUp and VolDn keys pushed this is not explained in the topic and I waist a lot of time till figured out. After that just download one of the 7.8 ROMs here in Radar section and write it down. Also download new radio and use some RUU to put it on the phone before the ROM other wise the phone can not boot. Try and after that if you have problems write down here.
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
BladedYouth said:
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
Click to expand...
Click to collapse
OK but you need to but some custom ROM my phone turn back on when I put custom ROM a lot of features and works really good.
I bought an LG Mach LS860 (4.0.4 Ice Cream Sandwich) about a week ago, and I just found out about rooting. (This is my first Android.) I had no luck last night, but I tried today and I got it rooted.
Anyway... here's the problem: I was altering some settings with an app (I believe it was called Pimp My ROM.) and everything was fine. When I restarted, the battery was lower by about 7%. I figured the changes I made were the reason for this, so I went back and reverted them. However, when I restarted the phone this time, it wouldn't get past the boot screen. It would flash the Boost logo, go dark, then flash it again with an animation and a short vibrate. That's all. So I tried restoring the factory settings. (Volume down + power button, then power button and power button.) The phone went through and reverted settings, then rebooted. But THIS time, I got messages popping up like "Unfortunately, System UI has stopped." I believe there was something along the lines of "Unfortunately, Home has stopped." as well. On a layer below that at the bottom of the screen, there was another type of error. I think it had to do with voicemail. After the phone sat there for a bit as I looked online for a solution, the phone restarted again. Now it just goes to the problem from the beginning with the boot screen. My computer makes a noise indicating the USB is connected, but all my phone does is charge off it.
Any help would be much appreciated.
It's not necessarily that I'm inexperienced. I've done all sorts of flashing and things on PSP. Obviously Android is much more complex. But I know that it's not bricked unless it won't turn on at all. Because that's not a brick.
There's also very little (if any) development for this specific model. No one cares about the LG Mach because there are much more well-known phones. But I digress.
Please help. I'm extremely desperate to get this working again.
EDIT: I recently thought of another question. Would the hard reset erase all evidence of the root access? Considering I just bought the phone, I might be able to send it back. But obviously if they know I accessed the root, the warranty is void.
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.