hi all,
im brand new to this website, got my galaxy S a couple weeks ago and wanted to start customizing it, so i signed up.
anyway. i tried rooting my phone with the mac one click root, which originally worked, then i accidently unrooted it.. kinda. i can't boot into recovery mode so i booted into recovery from pressing unroot coz that force enters boot recovery mode.. it went bad from there
i tried to do the one click lag fix. there was an error and when i restarted the phone it would not boot up, also my boot animation was gone...
so lag fix didnt work and its screwed up my phone because now i cant use mac root/unroot at all, it just doesnt work.. has any one ANY suggestions? please!
thanks in advance.
James
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.
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Appears you have already been helped here...http://forum.xda-developers.com/general/help/help-fast-boot-loop-vega-iron-normal-t2836120
Rooted stock Kit Kat tablet (V500) 2 weeks ago, and all went well. Used ioroot24. however 3/4 days ago started tablet, and tablet in boot loop.
Have searched and tried LG Hard Reset , gets to android robot deleting (only for very short time) and restarts in root loop
Also Used LG mobile support tool which d/loads recovery file, appears to load on tablet (in d/Load mode) and reboots in boot loop again.
Button set to factory reset does not work either.
Should I install Linux distro and use adb/fast boot commands? Am using win 8.1 x64 at present.
On starting shows LG logo, seems to boot for 15/20 seconds then reboots.
Point in the right direction would be greatly appreciated. Thank you in advance.
If you wish to register you will be able to ask that question here There are lots of knowledgeable users there to help you.
Good luck
good day,
i have a Nvidia Shield Tablet, non rooted, not unlocked, stock ROM, updated via OTA only and its included in the RMA.
so i was cleaning a bunch of files first then i did a factory reset on the tablet but after rebooting after the Nvidia logo, it just got stuck on a blank screen.
how can i go about this? i wanted to give this to my child once i got the new tablet.
if any kind sir can point me to do a recovery OS and its rom file that would be very helpful.
thank you
Did you already receive the replacement? If you did and you used it already, you are hooped. Your old one has been deactivated
Just force reboot the tablet with the Power button, and you will be fine. But why would you give your child a tablet that could possibly explode??
Phen0m said:
Just force reboot the tablet with the Power button, and you will be fine. But why would you give your child a tablet that could possibly explode??
Click to expand...
Click to collapse
I was wondering the same thing...
will it really explode? i thought it will just die down?
yesterday we decided we will just use it during drumming session. mounted on a tablet holder
i waited 15 mins from the blank screen and eventually the android animation for the factory reset showed up.