Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom
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
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.
I've managed to get myself so confused and flustered I don't even know where to go at this point.
A couple months ago I got tired of waiting for Samsung to send out the 4.1.2 Android update so I grabbed the Odin version and updated it myself.
I like it well enough but I want to try putting CyanogenMod 10.1 on my P6210. I tried everything last night and it's turned into a long chain of things that won't work.
The bottom line seems to be that I can't change the recovery mode - I've tried installing goo.im; no joy. I have tried several versions of CWM - no luck. Every time I get the "signature verification" error if I try from stock Android Recovery; if I try from Odin I just get a big "FAIL" message; I've tried with Heimdall and I just get partition errors.
I've reached a point where I don't know what to do - I'd really like to strip it down to basics but I've definitely reached a point where I'm over my head.
Any help would be hugely appreciated...
I have the Galaxy Fame DUOS GT-S6812B variant, I installed the Unofficial CM11 from this forum (http://forum.xda-developers.com/galaxy-fame/orig-development/rom-cyanogenmod11-t2897673), and suddenly touch screen and capacitive buttons weren't working. I tried to install back the official stock rom with Odin and I had the same problem (which I didn't have before installing the CM11) after this I tried to install the stock rom with Kies and same thing. Phone loads the OS and shows the "select language" menu but screen is unresponsive and "menu" and "back" buttons don't work at all, not even light up. Only power button, "volume buttons" and "home" work. I'm getting kind of desperate, a relative gave me the phone so I could make it faster and smoother and instead I've broken it. Please, some help would be highly appreciated. I think the problem might be that installing the CM11 messed up with the Drivers and flashing back the stock couldn't fix that. Is there any way to revert the process and get the drivers back?
Thank you all in advance.
I've got an answer in another forum saying it could be the kernel, but, wouldn't the stock ROM had solved that? in case it wouldn't how can I install the original kernel and thus fix this issue?.
ringox said:
I have the Galaxy Fame DUOS GT-S6812B variant, I installed the Unofficial CM11 from this forum (http://forum.xda-developers.com/galaxy-fame/orig-development/rom-cyanogenmod11-t2897673), and suddenly touch screen and capacitive buttons weren't working. I tried to install back the official stock rom with Odin and I had the same problem (which I didn't have before installing the CM11) after this I tried to install the stock rom with Kies and same thing. Phone loads the OS and shows the "select language" menu but screen is unresponsive and "menu" and "back" buttons don't work at all, not even light up. Only power button, "volume buttons" and "home" work. I'm getting kind of desperate, a relative gave me the phone so I could make it faster and smoother and instead I've broken it. Please, some help would be highly appreciated. I think the problem might be that installing the CM11 messed up with the Drivers and flashing back the stock couldn't fix that. Is there any way to revert the process and get the drivers back?
Thank you all in advance.
I've got an answer in another forum saying it could be the kernel, but, wouldn't the stock ROM had solved that? in case it wouldn't how can I install the original kernel and thus fix this issue?.
Click to expand...
Click to collapse
i m facing the same problem!!!!!
don't know how to solve this....
@ringox....Was your problem solved? please help me because i am having the same problem...my gt 6812 stucks on select language as touch is not working...
Nothings gonna work...trust me i have tried everything...your touchscreen got fried up. The only thing you can do is get it to a nearby samsung store or any nearby mobile repairing store to get a brand new touchscreen. I recommend you to not go to samsung store as it would cost you almost rs.2500 whereas if you go to any other repairing store you can get it fixed in less than rs.1000.