Database Info

[Q] Freezing then reboots

Its fixed. It seems that it was stuck and just needed that extra kick with another ROM. Not really sure what the hell happened but its working fine now.
Please delete post.
Yesterday I plugged the HOS into my laptop and it started to act a little weird. It wouldn't show the SDcard but it allowed me to open it. I copied a new ROM to it and installed it. Since I did this, the phone will not work. Once it boots, it just freezes and reboots when I try and do anything. The nand allows me to boot and scroll through the home screens, but if I try and do anything else it freezes and reboots. I can't install any other ROM that's not sense base like AOKP or MIUI as they just boot loop. I can get to recovery and the boot loader no problem.
Update: I can boot a stock nand and get into the app drawer. But, once I click on an app or pull down the notification bar it freezes.
Update 2: Was able to get the cyan alpha to install after a good 5 minutes of bootloops and it runs perfect. WTF is going on here?? haha
Can anyone give me any suggestions to try? Thanks for any help that you can provide me.

[Q] Galaxy S2 Soft Bricked after root....

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.

Stuck in endless loop after CM 10.2 nightly to CM 10.1 downgrade

I think i might have wrecked my P5110!
I rooted it to Cyanogen mod about 6 month ago to CM10.1.1 and that was great.
I had been using the built in updater to get the latest Cyanogen firmware without any problem. Decided to try a CM 10.2 nightly but was having big problems with it draining battery, crashing and rebooting for no apparent reason.
No problems thinks I, just unwind it to an older version of CM from the built in Cyanogen Mod Updater. I selected 10.1.3 RC2, and left it be.
Came back to it some time later to find the old logo spinning there. Figured it was still running and left it some more, and some more, and some more and it just kept spinning. I guess its knackered. I DID NOT wipe the cache and data as i was doing it from within Cyanogen so naively thought it would work okay.
Okay thinks I, go into recovery, wipe the cache. No dice. Try as i may i can NOT get ClockWorkRecovery to come up, only ODIN.
Talk about fools rush in. Simple thinks I, reinstall CWM from ODIN, go back into CWM, wipe the cache, see if that works.
flashing goes smoothly, but try as i may i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Any suggestions for a next step. Had the worst day at work and really shouldn't have bothered touching the damn thing!

Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?

Vannystick said:
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Click to expand...
Click to collapse
Flash stock firmware via pc odin this will solve your issues. ....
Sent from my GT-N7100 using XDA Premium 4 mobile app

Every time you flash with ANY ROM you need to wipe data or bootloop obviously will appear.

Vannystick said:
i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Click to expand...
Click to collapse
Even though your recovery may be screwed up, it's strange that you can't get to the download mode... So, what exactly happens if you force reboot by holding power for several seconds, and immediately after that hold power and Volume Up together while it's powering up?

When stuck in the CM boot up, pressing and holding the power button would force a shut down, but the tab would then instantly reboot.
Holding the volume up (or down, i was desperate) until the samsung logo appeared wouldn't get me to ODIN, it would go to the CM boot screen.
If i plugged it into the charger once in the CM splash, and powered down, it would take me to the charge screen. Pulling the plug would then turn it off, without it rebooting.
Initially this wouldn't work, but perhaps because i was being impatient. All the instructions i had read say that the volume button can be released once the samsung logo pops up, perhaps i've miss read. Ultimately i found (more by accident than anything), you need to keep the volume button pressed until the second time the samsung logo pops up, then it will enter ODIN.
I managed to download a a stock rom from SamMobile, and flash it in.
It still wouldn't boot though, until i went into recovery and wiped data/cache. It also then took rather a long time to boot back up, presumably unpacking various 'stuff', had me a little concerned, so i left it alone for a few hours and came back to find the first boot welcome screen.
Lesson to be learned, always wipe the cache/data before an update, even if the previous half dozen CM updates had been fine.
I think what actually screwed things up was going from a 10.2 beta BACK to a 10.1 RC ROM.
Oh well, its working happily again, and not falling over like on the 10.2 beta. And i dont need to buy a RIFF box!

Constant Reboot

I recently flashed to MM from Lollipop in order to use Tdunham's deodexed ROM coupled with Skyhigh kernel. I haven't had any issues at all with it until today when I tried to use the Aurora kernel. When I tried installing the kernel via TWRP it wouldn't boot up. No biggie there, but when I reinstalled Skyhigh, my phone wouldn't boot. So, instead of messing with things further I reflashed my phone with the MM image via Odin, and now my phone will not work. It boots up without a problem, but will randomly restart, and I can't make it past the "Setting up your phone.. this may take 3 or 4 minutes" prompt. I just tried flashing back to OK3 but I can't get past the sprint logo.
Any input would be greatly appreciated.

nahmanjk said:
I recently flashed to MM from Lollipop in order to use Tdunham's deodexed ROM coupled with Skyhigh kernel. I haven't had any issues at all with it until today when I tried to use the Aurora kernel. When I tried installing the kernel via TWRP it wouldn't boot up. No biggie there, but when I reinstalled Skyhigh, my phone wouldn't boot. So, instead of messing with things further I reflashed my phone with the MM image via Odin, and now my phone will not work. It boots up without a problem, but will randomly restart, and I can't make it past the "Setting up your phone.. this may take 3 or 4 minutes" prompt. I just tried flashing back to OK3 but I can't get past the sprint logo.
Any input would be greatly appreciated.
Click to expand...
Click to collapse
Let it die completely, charge a little, reboot see if fixed, if not let it die completely but take out sim card and let it die in download mode, insert sim, charge a little reboot. Only charge to like 10+ percent in case u gotta let it die again

Every Rom I've tried is just sitting at the boot up logo.

I've tried Carbon but that one wouldn't actually boot up, just shut my screen off and would shut itself off.
AospExtended ROM, is just sitting at these bouncing dots.
Ressurection Remix, sits at the boot screen of whatever that...logo is supposed to be.
I'm at my witts end here and about to smash this piece of junk. Nothing on this phone has ever worked right since I got it. Figured I'd fix it by getting rid of their trash UI and do custom roms but apparently it can't even do THAT right.

Upgrade your device to EMUI 8. Then flash one of the Treble ROMs.

I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.

Spykez0129 said:
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Click to expand...
Click to collapse
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.

SuperSwordSmasher said:
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
Click to expand...
Click to collapse
That's something I do automatically without thinking. That stuff was finicky back in the OG Droid days so I always do it like 3 times just to make sure.
Anything else that would cause it to get stuck at the booting up screen? I get passed the blue screen and the your device is insecure or whatever. Then it just goes into the fancy booting logo and just sits there. Never on any of the phones I've rooted over the past decade ever got stuck like this.
WOHOOO! I MADE PROGRESS!
My phone is now stuck in a never ending bootloop and can't seem to get into any recovery. Can't even shut the phone off because it just turns itself back on. Backwards progress is where it's AT!

Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.

Spykez0129 said:
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Click to expand...
Click to collapse
What honor 8 model do you use? It should not be Bootlooping then, if there is no solution you can always go to stock.
You could flash twrp again, with fastboot
Boot with power + volume up to boot into twrp

Use dload method