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.
Hey guys.
I'm new in the Android world and bought an LG G2 back in november.
I had originally intended to custom install cyanogenmod or KitKat 4.4 to replace stock rom, but I couldn't find a way to install a custom recovery, and was only able to root my device via Kingo Android Root.
A while later I saw an update that popped up, and not knowing any better I clicked install. It was about 114MB. That was about 3 days ago, and my LG G2 has been stuck in a bootloop ever since.
When I try to turn it on the LG logo shows up, then it says "secure booting error"and "Cause: boot certification verify" on the top left corner of the screen in white text.
I tried doing a hard reset, but that didn't work. I don't have a custom recovery so that I can clear the cache and data or something. So pretty much I have a bootlooped phone with no custom recovery, I can't do a hard reset, and it's Sprint and everything's new so it's harder to find a fix.
Does anyone here know of a way I can fix this? It would be much appreciated.
Thanks in advance
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)
I have a T-Mobile Galaxy S5, stock and rooted. Today, I used Kies to update to the latest G900TUVS1FOJ4 patch. That worked fine with no issue, but it did clear my root. No problem. So then I used the tutorial on this site:
http://nasirtech.blogspot.com/2015/02/root-g900tuvu1dob1-android-50-stock.html
to try to re-obtain root. (This was the tutorial I used previously and it worked fine.) However, this time, at the end, after Odin said "PASS" and the phone rebooted, it got stuck on the Samsung logo screen, and it will not go past it. I have gone into recovery and cleared the cache and done a factory wipe/reset, but it still gets stuck on the logo screen.
[Edit:] I am adding that after a long time of showing the Samsung logo screen (not sure how long), it does switch over to the white T-Mobile logo screen. Then that screen stays for a long time. I gave up and pulled battery to start over, but now it's doing it all over again.
[Edit 2:] I also want to add that the Samsung logo screen it is stuck on is not the colorful one, but the static black&white one, with "Powered by Android" at the bottom. In case that matters.
I can't figure out what to do next. I'm wary of following a tutorial on the web now, for fear it will be incorrect and do more damage.
What I want is to get past this, and end up with my phone on the new G900TUVS1FOJ4 patch, stock, and rooted.
Thank you,
Chris
Ok, I was able to flash stock G900TUVS1FOJ4, so my phone is no longer stuck, and I'm on the latest stock, but unrooted.
Now I am having trouble finding how to safely root it without doing the same thing again.
Any instructions out there for safely rooting this version?
Hi,
Thanks for writing to us at XDA Assist.
You can post your question in your device forum help section to get further help:
T-Mobile Galaxy S 5 Q&A, Help & Troubleshooting
Good luck!
Hey guys, so I'm up for a new phone (had this phone for 2 years) and I remember having a friend root + flash me the cyanogenmod on my Samsung Galaxy S3
I decided to root/flash my current phone (Galaxy S5) and i ended up ****ing in on several fronts.
The following is what I did and where I ended up
Rooted phone through Odin - was successful but I got a feeling it was outdated as I got the Seandroid kernal thing in red
Got ROM Manager and flashed recovery to TWRP - successful
Flashed ROM to Cyanogenmod nightly 7/14/16 - used the wrong version so i couldn't use my phone to call
Flashed Rom to the correct version - successful
Installed Gapps zip so i can use the app store and etc - experienced issues as it was always saying the store failed and etc
Now where I am currently
I ended up wiping all the data and etc so I can flash back to the Stock ROM/firmware since I couldn't get the Gapps to work.
I tried to flash the firmware but everytime I flash it and it boots to the stock recovery and says "installing android update" it gets to 1/3rd where it says "Erasing" and boots up to the Sprint Logo where the Blue notif is on and it is stuck.
I'm assuming its soft bricked and on a bootloop and I am trying to see if I can salvage this phone.
I tried flashing different version of the firmware (my brother has the same phone his version is G900PVPS3CPE2) and i tried that and G900PVPU3CPA. Both times its says its successful on odin but upon booting it only gets 30% before it says erasing and returns to get stuck on the boot.
Can I salvage this phone and if so can someone guide me through the proccess (links to proper firmware download/etc)
I do not care if any data/apps is lost (i have important stuff backed up on my gmail), I just want my phone to work.
That being said, my phone is salvageable instead of guiding me to repairing my phone to stock, if they can guide me to set my phone to a custom ROM (cyanogenmod or anything they suggest assuming they can get the googleapps to work on it) can someone please guide me through that.
Thanks again for reading.
Edit: All info in a TLR format incase my wall of text was messy
Phone: Samsung Galaxy S5 SM-G900P (SPR) Android 6.0.1
problem: ****ed up with flashing now phone is stuck in bootloop
What I want: Find a solution to make my phone work, ideally to make it work using a custom rom(any works) that has a working google apps installed.