T-Mobile Galaxy S II Overclock Boot Loop [Download/Recovery Mode Inaccessible]
My type of boot loop has only been seen a couple times, hard to find a thread on google so i’m asking you guys, I did root my phone but i never flashed any roms on my T-Mobile Galaxy SII, i only used the root privileges to backup using titanium backup, then i wanted to overclock my device and so i downloaded the Overclock Widget from Google Play Store, i set the widget to be underclocked when the screen is off and overclocked when it’s on, Half way through the day after i did that, the phone went into boot loop, i’ve experienced bootloop before of my Galaxy S Vibrant and a couple times on my Galaxy S II, But i could always access Download and Recovery Mode, Now my phone will only shut off if i take out the battery and when i do put the battery in, I don’t have to push the power button to boot it, it does it itself, when the first “On” Vibrate happens the Samsung logo comes up, then the ‘Samsung Galaxy S II Android 4g Tmobile’ boot screen shows up, the loading bar fills a fourth of the way and a white line flashes on the screen as the screen blacks out, another vibration and then the vibrations won’t stop until i take out the battery. The situation is a bit different when i plug my usb into the phone into my computer, the computer doesn’t recognize the phone at all neither does odin, kies, or ADB Shell. All the phone does in that situation is show the empty battery screen with a loading circle not moving in the middle. Then the screen turns black and back to boot loop until i take the battery out, I can access Download and Recovery Mode, but only for about 2 seconds, not long enough for Odin to recognize and flash, or to move down the menu to any option in Recovery. I have been able to boot fully every once in a while but all i got accomplished was Restoring the phone to Factory settings [I also saw my battery was at 82% so it wasn't dead or anything], I then set up the phone as a new T-Mobile Galaxy S II Android 4.0.3 ICS Phone, everything was fine until my screen timed out when i set it down for a minute, then the boot loop started again, so then i had the hunch that this was all because i set the phone to underclock while the screen was on standbye, but ever since i figured that part out i wasn’t able to boot the phone fully again, I’ve been trying to use ADB Shell to freeze the phone as soon as it recognizes it before it goes back into boot loop but it isn’t enough time. So my question is, any fixes to this excluding a USB Jig [My last resort]? Please and thank you for reading this.