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.
1.) Yes several times, sometimes it would work and let me in until the screen timed out again but i haven't been able to do it and i let it sit for about 2 hours, like an hour ago.
2.)Nope the only things i've done that required superuser permissions is Titanium Backup and OverClock/UnderClock Widget.
Have you tried holding both volume buttons, plugging in the usb cable and then manually enter your info into Kies under tools for an emergency firmware recovery? You'll need the S/N # under the battery. I don't know if it will work while in a boot loop, but this has helped other people when Kies didn't recognize their phone.
If nothing works you can contact mobiletechvideos.com. They have a fairly inexpensive JTAG service and a lot of good reviews.
Device(s): Samsung Galaxy S4 (T-Mobile) (rooted stock), Samsung Galaxy S 2 (T-Mobile) (retired), HP Touchpad (R
Carrier: T-Mobile (2gig data plan)
Thanked 123 Times in 104 Posts
I am sorry I have been a little absent here as I asked the questions first but I cannot seem to come up with anything more useful than the guys above me here. The only thing is to boot into download mode long enough to give Odin time to start patching the rom and recovery.
I guess some pre existing preperation is necessary - load up the rom/stock image into odin. While odin is active on your computer try putting the phone into download mode and hopefully the yellow square appears in odin so you can begin the flash. I think once it starts flashing it will prevent the phone from restarting itself so if you can get it to that point you might be able to save it!
Also I think the reason this happened is that stock Kernel does not allow very much flexibility with overclocking. As far as I have read one of the best kernels to OC on is dark venom kernel from the XDA and that one has limit of 1.7 or 1.8. I guess this is just an afterthought that's why I am editing the post.
Last edited by alextop30; July 19th, 2012 at 09:31 AM.
I can click the recovery code but it opens to a window telling me to input the recovery code from the other computer that my device is connected to. So i guess that isn't for the serial number
Again, once in download mode the bootloop starts again
I've tried so many times to get the timing right but only once has odin recognized it, it was a good thing i preloaded the stock into odin and clicked it as soon as it showed up but it just shut off and went back into bootloop again after 2 seconds.
Last edited by schmooterpie; July 19th, 2012 at 12:20 PM.
I got my Jig today, i downloaded the drivers, odin, the ics stock rom and got set up.
I put the battery in the phone, it immediately turned on, i put the jig in and it still went into bootloop. And so i figured i probably did it wrong. So i tried again, this time pluging both the jig and my battery in at the same time. It worked, it got me to download mode. But about 5 seconds later the entire screen flashed blue and white and then it shut off and went back into download mode. I don't even think it reset the counter that says if i've rooted the phone before. I would at least like to reset that counter so i can take it to tmobile. Any ideas now guys?
OH! i accidentally put that it went back into download mode after it flashed the screen, i meant bootloop, so i still can get my computer enough time for any program to finish doing anything to the phone
Just got back from tmobile, they didnt detect anything and said i am under warranty, haha the tmobile guy was like 'you're lucky the manufacturer can't tell you rooted this.' and i just smiled and said 'rooted? is that like the jailbreak thing for iphones?' he laughed and ordered me a new phone. It's in the mail. I wish i had been able to fix this and help anyone else with this problem but it seems i completely destroyed my phone :/
Thank you for signing up to receive updates for the 433
An email has been dispatched to confirm your signup. Please click the link in the email.
Buy the Samsung Galaxy S II 4G
Sign up for instant notification when the Samsung Galaxy S II 4G goes on sale!
The Galaxy S2 (sometimes known as the Galaxy S II) is the follow up to Samsung's widely successful Galaxy S lineup. This time, the Galaxy S2 raises all the stakes and Samsung has found a way to double almost every spec in a true, one of a kind ... Read More