First off this is my first post, and I gotta thank everyone cause I've been able to do some cool stuff with my phone and without the support of the community and the vast knowledge some of the guys (and gals) have on xda, I would be just another average consumer. And I'm still learning.
So a few days ago I tried to update my rooted Vibrant (with the lag fix) through Tmobile, like a noob, without unrooting my phone and everything was going great until the phone rebooted and got stuck on the "Samsung" startup screen.
I was able to fix that after reading through the odin3 fix and got the phone up and running again. Decided I didn't need froyo that bad and just reinstalled all my old stuff with Titanium backup.
Then after reading through the forums a little more I got the itch to try 2.2 again, so I was a little smarter this time, undid the lagfix, unrooted the phone and started the update. But once again, frozen at the "Samsung" screen...
Odin to the rescue again. But this time as odin was doing its thing, the power went out in my house, ughhh! Got everything back up and running and when I tried to turn the phone on it goes to a screen I haven't seen before, with a "phone" icon, two dots, a "triangle caution" icon, two dots, and a "computer" icon, and it wont get out of it. It won't connect to my computer so it won't connect to odin.
I'm usually decent at finding the solutions on the forums and I could have sworn I read somewhere about this type of problem, but I guess I'm wording my searches wrong so nothing is coming up.
So how do I get my phone out of this mode? Or is it bricked?
Also does anyone now why the phone would freeze like that after the update? I probably should have just flashed one of the froyo roms, but I figured it would be easier to return if the OS was from Tmobile.
steambrick said:
First off this is my first post, and I gotta thank everyone cause I've been able to do some cool stuff with my phone and without the support of the community and the vast knowledge some of the guys (and gals) have on xda, I would be just another average consumer. And I'm still learning.
So a few days ago I tried to update my rooted Vibrant (with the lag fix) through Tmobile, like a noob, without unrooting my phone and everything was going great until the phone rebooted and got stuck on the "Samsung" startup screen.
I was able to fix that after reading through the odin3 fix and got the phone up and running again. Decided I didn't need froyo that bad and just reinstalled all my old stuff with Titanium backup.
Then after reading through the forums a little more I got the itch to try 2.2 again, so I was a little smarter this time, undid the lagfix, unrooted the phone and started the update. But once again, frozen at the "Samsung" screen...
Odin to the rescue again. But this time as odin was doing its thing, the power went out in my house, ughhh! Got everything back up and running and when I tried to turn the phone on it goes to a screen I haven't seen before, with a "phone" icon, two dots, a "triangle caution" icon, two dots, and a "computer" icon, and it wont get out of it. It won't connect to my computer so it won't connect to odin.
I'm usually decent at finding the solutions on the forums and I could have sworn I read somewhere about this type of problem, but I guess I'm wording my searches wrong so nothing is coming up.
So how do I get my phone out of this mode? Or is it bricked?
Also does anyone now why the phone would freeze like that after the update? I probably should have just flashed one of the froyo roms, but I figured it would be easier to return if the OS was from Tmobile.
Click to expand...
Click to collapse
Email me [email protected]
Thegreat520 said:
Email me [email protected]
Click to expand...
Click to collapse
That's nice of ya GreatOne
+1 vote for personalized help...
~SB
Related
I just don't get it. I literally follow every instruction to a T and still get hosed every time. The Droid is so much easier to hack than these phones. It's unnerving.
Here's a 'quick' recap of what I've done so far.
My girlfriend has a vibrant, I installed one of sombionix's ROMs on it and she loved it. I think the latest one I installed was 1.7 I convinced her to try out a froyo ROM and she didn't like it, so I went into recovery and attempted to restore a nandroid backup I had made of the 2.1 ROM. Little did I know that apparently you have to install a 2.1 kernel on the Vibrant first if moving from a 2.2 ROM to a 2.1 ROM (Nandroid on the droid restores the kernel too, so I wasn't aware of this). So recovery got stuck at 'restoring data'.
I spent a week trying to get the damn phone into download mode, FINALLY got it there and restored back to stock JI6 (I think that's what it's called anyway). At this point I was on a stock 2.1 kernel and thought that restoring the original nandroid backup would work this time. Yet AGAIN the restore got stuck at 'restoring data'. Can someone please tell me what the hell I'm doing wrong? After waiting 45 minutes at 'restoring data' I rebooted the phone again. The odd thing is, the bionix lady started talking and saying she was initializing bionix. I know this normally takes 10 minutes or so, so I am waiting, but I have a hard time believing the phone will work without being fully restored. Is it possible I didn't wait long enough? (45 minutes on 'restoring data')
Any other suggestions for what I've done wrong? Will Vibrant hacking always be this frustrating? If so, I'm probably going to get her back to stock and leave her that way. The only problem is I *NEED* to get this nandroid backup to work to get some important text messages and other things she had saved. Please help.
So I just odin'd back to stock, and this time before attempting to restore the nandroid backup I went into CWM myself to delete data and cache before restoring. The phone hangs at 'formatting data'. It's as if anytime CWM tries to do anything with the data partition the phone freezes. Any suggestions?
Alright, I FINALLY got the restore process to finish. I then rebooted the phone and now I'm stuck at the Vibrant logo. What on earth am I doing wrong? I just don't understand this. It's like every single time I conquer one obstacle, there's another one waiting for me. What do I need to do now? The bionix lady says 'initiating bionix, hardware acceleration sequence enabled', etc. as if it's going to load up but it does nothing. What now?
ARGH. So after getting the restore process to work and getting stuck on the vibrant screen, I again odin'd back to stock JI6. Instead of Odin flashing me back to stock JI6, somehow my phone came on and is exactly the same as when I made the original nandroid backup I've been trying so hard to restore to, except that there is no root, it's the wrong kernel, and things aren't working right (apps do nothing when clicked, text messages won't open, etc). WHAT THE HELL IS GOING ON?!?! UGH.
I absolutely loathe this phone. Its performance is amazing, but this thing is a hacker's nightmare. I feel bad for those of you that own this piece of ****. I just spent the past hour redownloading a bionix 2.1 ROM, manually restoring all of her apps from titanium backup (free version, so had to do it one by one). I FINALLY got the phone to a point that was very similar to the nandroid backup I've been trying so hard to get back to and the damn thing rebooted, and now launcherpro is force closing repeatedly and not allowing me to do anything else at all. This phone is absolute crap as far as hacking goes. And I know, I know, I'm sure plenty of you will respond with wise ass remarks like 'if you knew what you were doing it wouldn't be', or 'I've never had a problem', but just the fact that this phone is only a few months old and its support forum is 5x more active than the most active Droid support forums shows how much harder this thing is to hack than my Droid. I am so frustrated with this thing I'm about to throw it out the damn window. You literally cannot do anything without encountering a new problem.
I guess I'll start the whole process over again. What a waste of good hardware.
It just never ends with this thing. Now after odin'ing back to stock the phone goes to a black screen and just sits there unresponsive. I ****ing hate my life. I really do. Will someone please help me? Please tell me what I did wrong in each of the 6 to 7 different problems I've had in this thread now?
Well it's all over now. After the most recent debacle I found a thread stating that if stuck on a black screen, flash the 'froyo that doesn't brick' through odin, then downgrade to stock JI6. I did that, and the phone boots now, but it wiped the SD card so it's all over now. All my nandroid backups, all files, everything is gone. Somehow the only thing it didn't wipe is an angry birds APK I bluetoothed to her phone the night it came out, since it wasn't showing up in her market yet. This phone may dominate my Droid in performance, but I have never had so many issues with a device in my entire life, not even when I first began hacking my Droid. I am going to leave her on stock and move on with my life. So many hours wasted on this piece of ****, my head is spinning. I do appreciate all the help on this forum but it's all been in vain. Thanks anyway everyone.
You keep posting to yourself. The reason, you are the issue. Some people forget to go to a2.1 kernel, but this thread is crazy. I've been flashing this phone since it came out with no issues at all. Don't bash the phone because YOU are having a problem.
I think he'd have been well advised to steer his girl to an HTC, not samsnot. Sorry you had such a ***** of a time man.
Sent from my PC36100 using XDA App
Oh boy, may I suggest RTFM before you screw with your girlfriend's phone any longer?
http://forum.xda-developers.com/showthread.php?t=732458
http://forum.xda-developers.com/showthread.php?t=771111
velocity92c said:
I absolutely loathe this phone. Its performance is amazing, but this thing is a hacker's nightmare. I feel bad for those of you that own this piece of ****. I just spent the past hour redownloading a bionix 2.1 ROM, manually restoring all of her apps from titanium backup (free version, so had to do it one by one). I FINALLY got the phone to a point that was very similar to the nandroid backup I've been trying so hard to get back to and the damn thing rebooted, and now launcherpro is force closing repeatedly and not allowing me to do anything else at all. This phone is absolute crap as far as hacking goes. And I know, I know, I'm sure plenty of you will respond with wise ass remarks like 'if you knew what you were doing it wouldn't be', or 'I've never had a problem', but just the fact that this phone is only a few months old and its support forum is 5x more active than the most active Droid support forums shows how much harder this thing is to hack than my Droid. I am so frustrated with this thing I'm about to throw it out the damn window. You literally cannot do anything without encountering a new problem.
I guess I'll start the whole process over again. What a waste of good hardware.
Click to expand...
Click to collapse
You say its a hackers nightmare, it is one of the few phones that is almost impossible to brick, do not consider yourself a hacker for using odin, you could not even figure out how to do that right and messed up, that is what happend you are the reason it wouldn't work the phone is great you just suck.
This is the deal:
I bought my wife and I Vibrants back in February and from the minute I got it I started looking into updating from eclair.
I was following the info on xda after researching about rooting phones, so I rooted my phone using the Superonclick method. Just before getting ready to flash custom roms, I read that froyo was available through kies. So I did that. It worked well enough for me, so I updated my wife's phone as well and hers works beautifully. I also changed the home launcher to LauncherPro. love it.
Mine however has been going on the fritz. I'm in the middle of using an app or I'm doing nothing at but turning on my phone and the screen will be all black with nothing but the notification bar showing.
The media scanner is constantly running.
No gsm is detected.
I keeps vibrating after touching the screen.
No amount of turning it on and off gets it past that state.
It just randomly decided to start working on its own.
Any Ideas?
Should I unRoot my phone. I don't want to,
I'm still researching changing the bootanimation, (waiting for a Portal 2 theme, also researching how to do it myself).
SOS guys.
sorry if tldr.
I would suggest restoring your phone back to stock Via Odin, and starting fresh. The problem you most likely had is that you updated to Froyo through Kie's while your phone was rooted.
Or, at the very least do a factory reset on your phone.
But if you need to go the Odin route, just search the forum, can't miss it.
oh wow, I didn't know that was an issue updating while rooted. I must have missed something while reading (so many threads -_-).
Guess I have some more light reading to do...
thanks.
Did a little research, should I unroot my phone first before factory reset? or is there a method that will take care of removing the root?
I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
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.
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.