So my Galaxy Note 5 was water damaged a few months ago and I just got it back up by replacing the battery. Problem is, I was trying to flash stock rom with ODIN and it seems like it doesn't do anything at all. When I try booting up the phone myself, it boots onto odin mode instead, and if I try going into recovery, it gets stuck on the TWRP logo (it had custom firmware before it was water damaged). I use the latest ROM sammobile has. ODIN isn't frozen or anything. It doesn't say that it isn't responding. It just doesn't progress further. Can anyone help me?
Related
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)
Hello;
several days ago, suddenly my N8013 restarted. After rebooting, it stuck at Samsung logo, and I couldn't go to Recovery mode. I flashed an official rom from sammobile. the process was passed but my N8013 problem didn't solve.
What's the solution? Is it a hardware problem??
I don't know exactly what happened, mine did the same thing. I fiddled around with it enough that i got it to reload back to samsung 'new' but it never recovered where it was at the time it went haywire. I installed Kies on my PC and let it update the kernel to the latest stock. I had not rooted or anything up to that point. it just went kapuut. Now I am rooted and tried a couple ROMS, but so far I keep coming back to stock because I can't get something or another to work right (or at least the way I am used to)
I had my phone just sitting on a wireless charger this morning and had been there for about 15-30 minutes. I noticed it was rebooting, odd I thought? I took it off and then realized it was going into a boot loop. I gave it a soft reset and then it would turn on and stay on for about 10 seconds before boot looping again. I again gave it a soft reset after a couple loops and now it seems to totally dead, as the title implies.
No button combination has worked and I've held them all down for well over 30 seconds each. I've tried plugging it into my PC and haven't gotten any response that way. The blue LED is on so I know it's not dead...I think? To make matters worse, I bought this phone off Craigslist about 5 months ago and it's the Exynos version so I definitely can't get any kind of warranty on it. I'm hoping someone has had this problem and can help or just has some advice. Thanks everyone.
EDIT: To keep this updated, I have been able to get into Odin Mode and have tried to flash stock firmware. Odin says everything went fine but the phone hangs up at the Samsung Galaxy S7 logo. I'm unable to boot into recovery mode and I've even tried to reinstall TWRP with Odin and that has not worked.
Seen the LED only problem before, waiting for the battery to drain and the phone to turn off seems to be the only known cure atm
Once it does, connect the charger for 15 mins, then boot directly into recovery and clear caches to try fix the bootloop, possible it may need factory resetting / clean flash of stock ROM
Using the MicroUSB > USB white adapter, you may be able to connect a power hungry USB peripheral to the phone to drain the battery faster, I use a USB desktop fan, but some people report it not working when it is stuck in this LED loop and have just had to wait it out
Thanks for that advice, I'll let it drain over night. However, I have been able to get it to boot into Odin Mode and Odin v.3 recognized it. I flashed the stock firmware but upon rebooting nothing happened and now it gets stuck at the Samsung logo screen. I can still get it back into Odin mode, which I believe will be the fastest way to kill the battery, but I find it odd that I can get into that but not recovery? I am rooted and have TWRP installed, if that matters at all.
If you can get into Download (ODIN) mode, then letting the battery drain probably won't help, that only seems to help when the phone is completely stuck with nothing but the LED working
Make sure you flash CSC (Not HOME_CSC) along with the other 3 sections of the ROM, using ODIN 3.12.3, that should factory reset the phone after the flash
If you successfully flashed stock with ODIN already, you are no longer rooted and do not have TWRP installed, flashing stock with ODIN replaces all that with stock
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
jonny727272 said:
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
Click to expand...
Click to collapse
Any region would work, and the F firmware works for the FD too
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.