I had my 4G xoom unlocked and rooted, installed Tiamat 2.2 on it (which then killed the 3G) so I decided to flash back to stock, but somehow screwed up the backup, managed to go back to factory 3G image with the HRI66.zip file I found in another thread. It unrooted my phone and relocked it, but now it's in a constant reboot loop, showing the honeycomb images for nearly 45 minutes now. What's my options? My computer wont talk to it, because I can't even get into it to enable USB debugging.... UGH!
sooo..... I let my device run dead.... then powered it up, went into fastboot mode, which took me straight to the unlock screen.... because I didn't lock it when I unrooted it.... All fixed..... except still NO 3G!!!!!
Okay i rooted my Samsung stellar everything went okay, and the way i rooted it was with a S3 root, so i wanted to back up my rom to play around so i downloaded room manger, i didn't see my device supported for the clockworkmod so i downloaded a s3 one, after that, it went into recovery boating, it went into a loop, and when it finally turnt on MY TOUCHSCREEN AND SOFTKEYS WONT WORK, so i went home and just turnt my phone back to stock. still wont work. i factory reset so now my usb debugging is off. should i just start looking at a new phone? i have no warnty
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'll start from the beginning, II was rooted and I wanted to speed up my phone so I tried to use SWAP. I never got it to work for some reason but then out of no where I was on the home screen and then my phone rebooted but wouldn't start again, it got stuck at the T-Mobile 4g LTE splash screen. I was still able to go into recovery and all that. So I decided to format my phone. The. That screwed it up even more because then it got stuck at the Samsung Galaxy light start up screen. So then I used Odin and flashed a stock rom. But that still didn't help it got stuck at the T-Mobile splash screen again. I went into recovery and it said era error. I managed to fix that and that went a way. Then after an hour of searching I was able to boot up my phone because some forum said all I needed to do was spam the volume up and down buttons at startup to get it to work. After that I set up my phone but then I was getting any 4G and I couldn't make any calls but it said I had 5bars. I kept getting a message saying not registered on network. Nothing would make it work. I called T-Mobile and I went into setting tried fixing my apn, tried connecting to T-Mobile again but nothing. They just called me back today and after I gave them my i di number they said it's not working because I rooted my phone. It doesn't have a bad i eu or anything it's just not working. I did see that my imei on my account is different than the imei my actual phone displays. I am able to do wifi calling and that works. So obviously something got jacked up when I formatted my phone. I want to know if anyone can help. I didn't back up my efs because I didn't know I had to, the only thing I've rooted before was my tablet. I have a Samsung Galaxy light SGH-T399 . Can anyone help. Ik my thread was long but I wanted to kae sure I got every little detail.
XDA Visitor said:
I'll start from the beginning, II was rooted and I wanted to speed up my phone so I tried to use SWAP. I never got it to work for some reason but then out of no where I was on the home screen and then my phone rebooted but wouldn't start again, it got stuck at the T-Mobile 4g LTE splash screen. I was still able to go into recovery and all that. So I decided to format my phone. The. That screwed it up even more because then it got stuck at the Samsung Galaxy light start up screen. So then I used Odin and flashed a stock rom. But that still didn't help it got stuck at the T-Mobile splash screen again. I went into recovery and it said era error. I managed to fix that and that went a way. Then after an hour of searching I was able to boot up my phone because some forum said all I needed to do was spam the volume up and down buttons at startup to get it to work. After that I set up my phone but then I was getting any 4G and I couldn't make any calls but it said I had 5bars. I kept getting a message saying not registered on network. Nothing would make it work. I called T-Mobile and I went into setting tried fixing my apn, tried connecting to T-Mobile again but nothing. They just called me back today and after I gave them my i di number they said it's not working because I rooted my phone. It doesn't have a bad i eu or anything it's just not working. I did see that my imei on my account is different than the imei my actual phone displays. I am able to do wifi calling and that works. So obviously something got jacked up when I formatted my phone. I want to know if anyone can help. I didn't back up my efs because I didn't know I had to, the only thing I've rooted before was my tablet. I have a Samsung Galaxy light SGH-T399 . Can anyone help. Ik my thread was long but I wanted to kae sure I got every little detail.
Click to expand...
Click to collapse
Good news is, that we have a forum for your device on xda: Samsung Galaxy Light Discussion.
Bad news is that it seems that your IMEI (and maybe your EFS data) is corrupt/lost now.
Here is a guide how to recover your IMEI: [GUIDE] Recover your IMEI in 9 steps.
Hopefully it works on your phone too.
Good luck !
Thread closed. Thanks you!
Hi everyone,
My S6 (SM-G920T on T-Mobile) suddenly froze when making a phone call the other day and wouldn't turn back on. It would only go to the Galaxy S6 screen and freeze there.
I downloaded the stock firmware using samfirm and reflashed the stock firmware using Odin. After that it went to the little Android symbol said it installed update and seemed to work. I got the phone to reboot to the setup made it about half way (adding e-mail accounts, etc.) and it froze and just shut off again and wouldn't turn back on.
I reflashed with Odin again. Said it succeeded. This time it died at the end of the Android installing update process. Now just stuck at S6 screen again.
It seems pretty well borked. Just wondering if there is anything else I should do before giving up to get a new phone?