I've had my rooted N5 on 5.0.1 for a while now. I recently unrooted it to upgrade to 5.1.1, and then I would reroot it. I downloaded 5.1.1 and the phone asked if I wanted to install the upgrade. I said yes and the phone then reboots. But when I looked at which software I was running it said 5.0.1. At that point I went through another reset so I could start over. And that's when the problem began. When the phone boots up it tries to boot into TWRP. My screen flashes TEAMWIN, but won't go any further. It just continues flashing without actually going into TWRP. If I hold the power button and the down volume button I can get the phone into bootloader mode, and that allows me to shut the phone off but that's all I can do. Can someone tell me where I screwed up and how can I get the phone to quit trying unsuccessfully to boot into TWRP? Thanks in advance.
Mark
Austexcat said:
I've had my rooted N5 on 5.0.1 for a while now. I recently unrooted it to upgrade to 5.1.1, and then I would reroot it. I downloaded 5.1.1 and the phone asked if I wanted to install the upgrade. I said yes and the phone then reboots. But when I looked at which software I was running it said 5.0.1. At that point I went through another reset so I could start over. And that's when the problem began. When the phone boots up it tries to boot into TWRP. My screen flashes TEAMWIN, but won't go any further. It just continues flashing without actually going into TWRP. If I hold the power button and the down volume button I can get the phone into bootloader mode, and that allows me to shut the phone off but that's all I can do. Can someone tell me where I screwed up and how can I get the phone to quit trying unsuccessfully to boot into TWRP? Thanks in advance.
Mark
Click to expand...
Click to collapse
Flash the 5.1.1 factory image with fastboot and start all over.
Sent from my Nexus 9 using XDA Free mobile app
Related
My friends phone is stuck in a boot loop its running stock rom he hasn't rooted his phone. This happen when his phone started running slow so he turned it off that's when the happened boot loop. Any suggestions?
Rapol said:
My friends phone is stuck in a boot loop its running stock rom he hasn't rooted his phone. This happen when his phone started running slow so he turned it off that's when the happened boot loop. Any suggestions?
Click to expand...
Click to collapse
If the phone is still under waranty, you should send it in for repair.
If it is out of waranty, try factory resetting and clearing cache from stock recovery by holding vol+ and vol- while the phone is off, and press the power button until the phone turns on. then only let go of the power button. If you see a recovery menu, you will want to factory wipe and clear the cache. Make sure your battery is charged first.
(EDIT: forgot to mention that vol+ and vol- are up and down in recovery, and power is enter)
Let the phone reboot and let it sit for 10 minutes to build it's initial cache entries.
If that doesn't help, let us know
He already went to tmobile and did the factoy reset and no result. The samsung warranty is on vacation for two weeks and then wait for them to repair it so he came to me because i got my inspire rooted he thought that i could help him but i dont know what else to do.
Rapol said:
He already went to tmobile and did the factoy reset and no result. The samsung warranty is on vacation for two weeks and then wait for them to repair it so he came to me because i got my inspire rooted he thought that i could help him but i dont know what else to do.
Click to expand...
Click to collapse
Did what I say work, or not?
Nope i think its better to get it replace by samsung so he will wait. Thx by the way.
Try flashin a rom via odin. It should be able to be put in download mode.
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, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.
Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait
So I have a weird bootloop issue. I am running 4.4.4 firmware, with GPE 5.0, s-off, unlocked.
The phone gets hung on the android boot screen (where the little dots circle around). I can restart the phone, and get it into the recovery screen with power and vol down. However, once there, the phone automatically tosses me into HBOOT where my only option is to update the HBOOT or cancel the update. Either way I go, it asks to restart the phone, and I am right back where i started. I cannot for the life of me figure out how to get out of this.
Thanks for the help in advance.
DrMurawski said:
So I have a weird bootloop issue. I am running 4.4.4 firmware, with GPE 5.0, s-off, unlocked.
The phone gets hung on the android boot screen (where the little dots circle around). I can restart the phone, and get it into the recovery screen with power and vol down. However, once there, the phone automatically tosses me into HBOOT where my only option is to update the HBOOT or cancel the update. Either way I go, it asks to restart the phone, and I am right back where i started. I cannot for the life of me figure out how to get out of this.
Thanks for the help in advance.
Click to expand...
Click to collapse
Pull your sd card and you will be able to enter recovery.
I've had my S7 since March. Worked flawlessly until around 2 weeks back. The first issue I got was that the phone stopped responding. I haven't linked that to any specific application. It happened at random. So the phone freezes and screen goes black. I used the Power button + Lower Volume button to power up the phone again and it worked. But then the no response problem happened more often. So I decided to go for a factory reset. I did this using recovery. But I continued to get the freezing issue. And the last time I got it was a few hours ago. But this time when I used the power button+ down volume button, the phone got stuck in a boot loop. I managed to bring up recovery to power down the phone. When I booted into recovery, I got the a dead android logo with a yellow exclamation mark in a triangle. I tried to power up my phone back, but it again got stuck in a boot loop. I know I can resolve this situation by doing a reset again. But I suppose this is not the solution as I will continue to get the freezing and not responding problem again.
Any advice please?
Thank you.
itsmystie said:
I've had my S7 since March. Worked flawlessly until around 2 weeks back. The first issue I got was that the phone stopped responding. I haven't linked that to any specific application. It happened at random. So the phone freezes and screen goes black. I used the Power button + Lower Volume button to power up the phone again and it worked. But then the no response problem happened more often. So I decided to go for a factory reset. I did this using recovery. But I continued to get the freezing issue. And the last time I got it was a few hours ago. But this time when I used the power button+ down volume button, the phone got stuck in a boot loop. I managed to bring up recovery to power down the phone. When I booted into recovery, I got the a dead android logo with a yellow exclamation mark in a triangle. I tried to power up my phone back, but it again got stuck in a boot loop. I know I can resolve this situation by doing a reset again. But I suppose this is not the solution as I will continue to get the freezing and not responding problem again.
Any advice please?
Thank you.
Click to expand...
Click to collapse
Hi mate
after you factory reset it , did you use the phone for a while without restoring any app?..so you are sure is not an app making the mess
My first option would be flash ( odin) firmware again.....
Check his guide
Use home_csc instead of CSC so you do not lose anything
I actually didn't restore any app after reset. I rather re-installed only 2 apps I use most. And I've been using these apps since I started using my mobile. I don't think they could be responsible for the crashes.
If I have to flash, I've been wondering if I could have a go at Nougat.
Would that be a good idea?
itsmystie said:
I actually didn't restore any app after reset. I rather re-installed only 2 apps I use most. And I've been using these apps since I started using my mobile. I don't think they could be responsible for the crashes.
If I have to flash, I've been wondering if I could have a go at Nougat.
Would that be a good idea?
Click to expand...
Click to collapse
Hi
Yes you can flash nougat, seems to be stable......but still is a Beta version
Hi
I got the same problem ... did you find any solution for this problem ??
Replacing motherboard fixes this issue. Its not software related. Faulty board. With Nougat this will happen even more. I know because happened to me..
ohhh
how much did cost you for that ?