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.
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
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.
So I have had my S3 rooted for a long while. But the past few weeks it's been running a bit slower. This week it started randomly turning off. I thought it was my battery at first. But then when I tried to turn it back on it got stuck at the Galaxy s3 screen and would not get into the OS.
I tried to get into recovery, it froze on the splash screen. I made sure both were actually frozen by leaving it sitting there for 30 min to an hour.
Tried to flash using this thread: http://forum.xda-developers.com/showthread.php?t=1974114
It kept just sitting at writing NAND.
Now my phone says "Firmare Upgrade encountered an issue, please select recovery mode in kies and try again"
Kies will not connect my device. It sees it but will not complete the connection. I tried using the model and IMEI number to upgrade firmware but it still would not connect to do that.
More searching lead me to this: http://forum.xda-developers.com/showthread.php?t=2581166&page=11
But I can't get into OS or recovery so I don't think this would work.
Any suggestions on what I can do from here? I only really need the phone to work for a few more months. My old Droid incredible just doesn't cut it at this point.
Sorry to bump, but nobody has anything for this? I haven't really found any other options.
Your bootloader is fine so that thread won't help you. What was the last version of touch wiz that was on your phone before you ran into problems?
Hello there, short story, flashed with odin 3.12 the stock firmware a SM-531F Grand Prime, and the power got cut in the middle of the phone flashing, after i restarted the phone, he ran in Emergency Donwload mode, requesting kies recovery, i tried to reflash the firmware, but odin said is failed, i though if i restart one more time will be fine, and from this point, the phone have absolute 0 life, is not booting, is not vibrate, no light, doesn't make connection even with the pc, what should i do? as i think the phone is still locked up in that edl session, exist a test point method or something? i really need to revive this phone.
I know there is a solution, thins thing could happen on any samsung, did someone faced the same problerm?
Did you try to flash the stock rom again?
Just try flashing stock ROM again.