Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
Related
Just bought my phone a couple of days ago, I was looking to root it as I had an Incredible but stepped up to this. Rooting went pretty good, failed first time but went through the second. Then I installed rom manager and flashed clockwork. I then went into the recovery but saw that I had an issue with with it about signatuire verification so I figured I still had the stock recovery. I went in and got the modded recovery file and just renamed the old one. Rebooted into recovery and the phone would lock at the samsung screen and not go anywhere. So i booted it back up like regular and flashed clockwork again and tried to boot into recovery again with the same issue but now I can't get the phone to boot up regularly. Its just hanging at the samsung screen, I have the battery pulled while I wait just to make sure its not an issue like that. Did I miss something when I was doing this? I watched the videos on how to root and install the recovery but I'm lost as to what is going on now. I thought my only issue was the stock recovery was still installed for some reason so I replaced that with the modded version. Thanks for you help and I hope I don't have to redo everything again.
Alright, delete this as I got inpatient and figured my phone was screwed anyways so I went ahead and used odin and I'm in clockwork right now. Sorry for creating a useless thread.
Ok so I have tried on another thread that kind of went dry mainly cause I was MIA....but now I am back and have done some more reading up and think it is safe to say rooting and trying customer ROM's is not for me...lol I pretty much messed up a new Galaxy Tab 2 7' brand new only after a few weeks trying to root it. I had another thread link below:
http://forum.xda-developers.com/showthread.php?t=1834368&page=2
But I did not get anything to work right. At this point I am really just looking to get the tablet working. I don't really care what firmware rooted or unrooted...i just want to be able to use it....do some more research and and maybe join the rooting community again when I get a Galaxy S3.
I'd appreciate any help. I am pretty stuck right now!
Go into Download mode "power" plus "down volume", then up volume. Use ODIN to load this:
http://forum.xda-developers.com/showthread.php?t=1645295
ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=581913...
You will need driver from Samsung Keis install for P3113
http://www.samsung.com/us/support/owners/product/GT-P3113TSYXAR
FYI - I needed to load CMOC10-Kernel to get my tab to stop boot looping when I flashed JB AOKP
bark777 said:
Go into Download mode "power" plus "down volume", then up volume. Use ODIN to load this:
http://forum.xda-developers.com/showthread.php?t=1645295
ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=581913...
You will need driver from Samsung Keis install for P3113
http://www.samsung.com/us/support/owners/product/GT-P3113TSYXAR
FYI - I needed to load CMOC10-Kernel to get my tab to stop boot looping when I flashed JB AOKP
Click to expand...
Click to collapse
Worked like a charm....you made it simple! Thanks!
Continous boot loop on tab 2 p3113
My problems are kind of different from all the others I have read. Yes it is similar that it boot loops. But mine freezes at different areas in boot mode. This is driving me crazy and I am spending way too much time and effort trying to fix it. Hopefully you can help.
I don't really know for sure if the android os was 4.1.1 or 4.1.2 or some other rom but it did state in download mode that it was original and not custom rom.
I received this tab from ebay and it is new never used, but somehow whoever had it probably tried to flash it and now I received it with a continuous loop. They stated that it stuck in SAMSUNG logo. I found it true but it also stuck other places as well. I did do a reset first before I attempted to flash it.
I did the Odin flashing.I found the 4.2.2 xar file HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.tar.md5 and did according to instructions. But that didn't work. It did boot into android but it didn't stay there very long and rebooted itself. I couldn't stay more than 20-30 seconds and it would reboot itself or freeze at various places in android. I also hard reset it. Still same thing. It would also freeze on the first samsung logo tab 2 screen and also at the blue circle with samsung logo. It was different every time. I would have to hold down the on button until it rebooted. It also stalls or freezes during Android upgrading... Optimizing app at various number stages sometimes it goes thru that and then to the next phase of installing apps then it freezes again. I cannot get it to work if I try to upgrade via wireless upgrade to samsung. it will freeze even before it downloads the upgrade file.
I then flashed back to the original xar file P3113UECLK7_P3113XACCLK7_XAC which is 4.1.1 That worked a little better, but it freezes and also the sound chatters when it freezes on bootup you know, when the samsung sound comes on then the blue circle.
Finally I tried to recover or flash from the recovery mode using the upgrade from a sdcard. using the original 4.1.1 xar file. It hewlped a little but still doing the continuous boot loop at different stages but it gets to the Android is upgrading... more often. It freezes always now.
So I don't know what else to do. You mentioned a CMOC10-Kernel to load, how does one go about doing that and what are the steps.
Thanks in return if you can suggest things.
Wayne
Sorry everyone... I tried one more time (my 5th attempt!) and it worked this time! I have no idea what happened with the earlier attempts. Thanks
Hello everyone. I'm having a problem with a Rogers Skyrocket here and hope someone can help. It was running a custom ROM, but I was given the task of returning it to stock. I don't recall which ROM was on it, but it worked nicely. I should have just kept it that way!
Thanks to vincom's super helpful posts, I got the info & file(s) needed to get this thing back to stock. I installed Odin 1.85, and extracted
I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
from the zip. I started by doing a wipe/factory reset (from inside the custom rom) first, and rebooted to see that it showed the initial setup screen. Then pulled battery and booted the phone into ODIN mode. I made sure to kill Kies completely before connecting the phone to my laptop (WinXP). Then launched Odin, hit the PDA button, loaded up the above file, left the check-boxes as they were, and flashed. It was successful, and rebooted the phone.
The rogers logo appears, and the samsung galaxy bootanimation comes up, and it continues to animate.... forever (for the record, I waited 20 minutes, more than enough time). I can pull the battery and try to boot again but it still stays on the bootanimation. I'm not sure what else to do? I can still get into stock recovery or Odin mode. Can anyone help? Thanks
Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
Hello everyone! I was sincerely hoping that someone would be able to help. I believe I messed up my phone beyond repair by trying to root it for the 2nd time. I rooted my phone in Sept 2014 and accidentally dropped it and broke the LCD (not the actual screen, but a piece inside of the phone). Samsung replaced the screen but they had to reset it so I lost the root. I wanted to try to root it again today. I already had all the tools; Odin, Superuser, and Philz Recovery. I put the phone into download mode, flashed Philz, and Odin said "Passed". When I put the phone into recovery mode, it didn't look like it did before. It just looked like the android stock recovery. I assumed (noob) that I may have done something wrong. So I tried flashing it again and it failed and was stuck in the download mode (Do not turn Target off). I waited approx 30 min and just said, "Screw it" and pulled the battery. I know stupid. Then I got the "Firmware upgrade encountered an issue message..." I did some research and many people on here and other android forums were telling others with somewhat of the same problem to download the stock rom. I'm currently downloading it but am worried it's going to do the same thing; "fail". I will update as soon as I try to flash the stock rom, but if anyone has other options, I'd so appreciate them.
Thanks so much for helping.....
Hedup34
P.s. I had the most up to date software for Sprint (maybe that was the problem)