[Q] Help with AOKP rom - General Questions and Answers

I don't know if this question has been asked before, I'm new here. But I have an at&t galaxy s3 running the aokp task 650 rom with cwm recovery. Every single time my phone battery dies or my phone turns off, i have to clear the cache, otherwise i go into a boot loop. It's really annoying and i need a way to fix it. I only have a mac computer so odin is not an option. All help is appreciated, thanks.

Related

[Q] Optimus S Recovery Loop

I have an LG Optimus S with Sprint. I rooted it and put a rom on it and everything worked fine. I booted into recovery one time, and now I can't get out of it. Every time I reboot the phone it goes right back to recovery. I tried to wipe and reflash but it does the same thing. Is there anything I can do to fix this? I don't mind going back to stock, but I'm not sure how to do that when I can't even turn the phone on. I just want my phone to work! Any help would be awesome! Thanks.
omg
I have the same problem- I tried wiping all, and flashing 3 different roms and it still doesn't work!!! :-((
Try forums.androidcentral.com/lg-optimus-s-rooting-roms-hacks/100739-stuck-recovery-mode.html
This may be a stupidly simple answer or it may not help at all, but have you tried flashing any kernels recently?

NS4G only working with AOKP

Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101

[Q] need help

my friend gave me his galaxy captivate. he was messing with the software an screwed something up an he gave up trying to fix it an gave me the phone. it is a galaxy captivate with froyo 2.2 what happened as he told me is he flashed a new kernel with rom manager, but rebooted the phone before he was suppose to. now when it boots it shows the i896 on startup but goes to this glitched out screen with random colors in lines, the phone vibrates a few times then restarts itself an repeats. is there anything i can do to fix this?
If you can go into recovery, reflash a stock ROM and see if that will help. There are plenty of resources on this site that will teach you how to recover from a bootloop (which is what it sounds like it is from your description).
Seems like a bootloop. If you can get into recovery: factory reset, wipe everything. Go mounts/usb storage (or something like that) and mount it to your pc. Download a stock rom if you can. Hope it helps. Sorry if it doesn't.

[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.

[Q] Unusual problem!

I'm new to this forum and idk if this is the right place to ask for help! Excuse me if it isn't
I recently flashed a custom ROM from aospal.com and it turned out to be a disaster. After installation, it deleted my recovery software (now I can't use/ don't have cwm or twrp). I can't boot into recovery anymore. Whenever I try doing so, the screen just goes blank after the note logo (I have a note n7000) but the soft-keys glow. I can only restart the phone after connecting it to the charger. The ROM is highly unstable and it eats up my battery very quickly. I've flashed many ROMs before and they were all fine. No problem. But this particular one messed up my phone. Someone please help me out! I can go into the download mode!!

Categories

Resources