Hey,
I've tried searching similar threads for this issue but haven't found a solution that works quite yet.
I have Samsung S Vibrant GT-I9000M on which I tried to originally flash CyanogenMod. At first I tried using Clockworkmod and discovered I couldn't actually get into it because of the Samsung 3e recovery utils. So I tried flashing to a different firmware (I've tried a lot now) to get to 2e but I am unable to get past the loading screen, which is flashing the samsung galaxy s logo. I've followed a lot of guides to try to get back to stock firmware but I haven't had any success at all.
I can't get into recovery mode anymore but I can get into download mode, and I've been trying to get back to stock firmware but whatever I try it just reboots and starts flashing a loading icon (if the usb is still plugged in, without it just flashes the samsung s galaxy screen). I've also noticed that the model number changed from GT-I9000M to GT-I9000.
I'm new to all of this, so if anyone can lend a helping hand I'd really appreciate it. So to summarize, I can get back into download mode but I cant' get into recovery. I've tried at least 5 or 6 times to reflash stock firmware (following the guides in this forum, I can link if needed) but its the same result each time. A cycling loading screen.
this guy is having the same problem.. see my posts in his thread.. do all the things i have told him to do..
http://forum.xda-developers.com/showthread.php?t=1022688
About 2 months ago, I got a Samsung Infuse 4g. I was thrilled. At first I was satisfied with the stock rom and its limited functions, but then I got really interested into custom roms. I rooted my phone, installed Clockworkmod recovery and flashed Cyanogen 7 rom. During the reboot process, I pulled out the battery just like the tutorial said and thats where everything went wrong. My infuse got stuck into the bootloop, but I was able to get into recovery. I flashed Cyanogen 7 again and it work. However, my home, back, search and menu buttons all stopped working. I figured it was the customed Rom, so I flashed MiUi. The buttons still did not work. What is worst of all, is that My computer refuses to recognize my phone(yes I installed Samsung Kies)(download mode is unrecognizable too). It only recognize it as a storage device. As a result, Odin does not pick it up. neither does heimdall. I need some serious help. I have tried everything. I am currently running Miui and apparently, now I can't get into recovery mode. Guys, please help.
if you cant access the phone from usb and you cant get into recovery then you re screwed.I had a similar problem and had to return the phone to vodafone to fix it
After screwing around with it, I factory resetted and Tried download mode on a different computer and luckily it worked. Odin was able to pick up my infuse and I used Ultimate Debrick. Thanx a million to those within the Community who are consistently developing and coming up with programs such as Odin. Big thanx to everyelse who shares their thoughts and advice.
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 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)
Okay, so i have a galaxy s blaze 4g and i am having troubles booting up my phone i tried installing the stock rom back onto it after having cm11 on it for a couple days but it was not letting me use the internet it would always give me errors and i am having trouble just getting it back to the stock rom it loads up says samsung and then goes blank i have no idea what to do i have been scrolling through the internet for hours on end trying to find a solution please help!! :c
Hi,
Thanks for using XDA Assist.
Did you try a factory reset from your recovery mode?