Hello everyone! So, my problem started when I tried to install the latest ROM on my i9100 with CyanogenMod Installer which failed. After the instalation on the boot appeared the yellow triangle and didn't start, automatically sending me to CWM menu. After that I manually installer the 10.1.3 ROM Stable (jb 4.2.2) which worked fine. After that I updated from the Settings the latest ROM (CM 11, kitkat 4.4.4). After some hours my phone started to turn off by itself (I was just finding my phone turned off). I flashed the M8 ROM and same thind happened. Now I re-flashed the CM 10.1.3 and after one day it started to turn off by itself again. I need some help with the yellow triangle and some explanations with the "turn off" problem. Sorry for my english. Thank you!
never had this "turn off" problem you have but usually you have to wipe before downgrading android versions otherwise you get boot loops
I always wiped before flashing
@UkUrapp the triangle means you flashed your phone with odin, you can remove this triangle but its risky and i dont think that you wanna remove it. Im finding it actually nice i dont know but if that turn on/shutdown issue happens even when going back to cm10.1.3 with full wipe then could you try a different modem if there is any flashable i don't know i don't have this device anymore for 1 year. Maybe you can try to flash stock and see if this issue still appears.
I didn't flashed the phone with Odin. I removed the triangle with Triangle away [.apk] hoping that it will fix the auto shutdown problem. It didn't. I don't know what you mean "different modem", can you be more specific? I updated to CM 11 kk 4.4.4 [Nightly] from Cyanogenmod Updates (in the phone settings) and the turning off problem is the same. Then I taught the battery it's broken because of flashing and I used the Battery Calibration .apk and nothing. I will flash the stock but I don't know where to find it. Can you help me with a link? Thank you!
[I'm from Romania, sorry for my bad english]
Related
Hi all...
Please could someone help me?
I am running the latest UK Sim Free ICS Stock ROM - and yesterday I updated the kernel as I wasn't best pleased with battery life.
Initially, I flashed Siyah 3.1.1 via Odin - and after initial boot up, "android upgrading" etc... I rebooted phone, went into recovery, and loaded the "Battery" profile.
The only other adjustment I made was turning off Auto-root and changed USB charging to 650mA in ExTweaks so that it charges via USB at the same speed as AC.
I made no other changes.
Then, the Siyah 3.1.2 Kernel was released, just a couple of hours after. So, I downloaded the CWM zip version this time, and also the Kernel cleaning script that is available on here (more for cleaning up the old stock kernel files than the Siyah)...
I rebooted into CWM and did the Update from zip - ran the Kernel cleaning script first, then flashed Siyah 3.1.2. I rebooted - let it do its "Android Upgrading" stuff and so on, then rebooted, loaded "Battery" profile, and made the same changes as originally - nothing more.
However, now, whenever phone reboots or powers on - I briefly get the "Android Upgrading" screen up for a few seconds. I didnt have this with the 3.1.1 - and am wondering how I can resolve this? I have definitely turned off Auto-Root, so it cant be this.
Another question, I recall reading, but cant find the post anywhere, that to disable the Siyah boot-animation that comes on just before the default Galaxy S2 one (in the same way a Carriers logo's does) - you need to create a file somewhere called .nobootanimation or something?
Does anybody know how to disable this so it just starts up like a stock S2 would? I love the kernel, but I personally prefer my phone to "appear" and feel as stock as possible.
Any help much appreciated - Thanks!
EDIT: I managed to find the post regarding the boot logo and have sorted that - but still found nothing on the Android Upgrading issue - Ive just reset ExTweaks profile through recovery options, no joy...
shadow2981 said:
Hi all...
Please could someone help me?
I am running the latest UK Sim Free ICS Stock ROM - and yesterday I updated the kernel as I wasn't best pleased with battery life.
Initially, I flashed Siyah 3.1.1 via Odin - and after initial boot up, "android upgrading" etc... I rebooted phone, went into recovery, and loaded the "Battery" profile.
The only other adjustment I made was turning off Auto-root and changed USB charging to 650mA in ExTweaks so that it charges via USB at the same speed as AC.
I made no other changes.
Then, the Siyah 3.1.2 Kernel was released, just a couple of hours after. So, I downloaded the CWM zip version this time, and also the Kernel cleaning script that is available on here (more for cleaning up the old stock kernel files than the Siyah)...
I rebooted into CWM and did the Update from zip - ran the Kernel cleaning script first, then flashed Siyah 3.1.2. I rebooted - let it do its "Android Upgrading" stuff and so on, then rebooted, loaded "Battery" profile, and made the same changes as originally - nothing more.
However, now, whenever phone reboots or powers on - I briefly get the "Android Upgrading" screen up for a few seconds. I didnt have this with the 3.1.1 - and am wondering how I can resolve this? I have definitely turned off Auto-Root, so it cant be this.
Another question, I recall reading, but cant find the post anywhere, that to disable the Siyah boot-animation that comes on just before the default Galaxy S2 one (in the same way a Carriers logo's does) - you need to create a file somewhere called .nobootanimation or something?
Does anybody know how to disable this so it just starts up like a stock S2 would? I love the kernel, but I personally prefer my phone to "appear" and feel as stock as possible.
Any help much appreciated - Thanks!
EDIT: I managed to find the post regarding the boot logo and have sorted that - but still found nothing on the Android Upgrading issue - Ive just reset ExTweaks profile through recovery options, no joy...
Click to expand...
Click to collapse
You would be better asking this question on the SiyahKernel thread
Thanks, I tried there first, and it said I couldnt post as i had less than 10 posts... :/
If this helps:
I re-flashed the 3.1.2 Kernel, this time via Odin (so no Kernel cleaning script run this time prior to flash), but I have the same problem.
I cleared dalvik cache afterwards, and as expected at first boot after clearing I get the:
Android Upgrading:
Optimising Applications
prompt.
Rebooted after this - but still get the:
Android Upgrading:
Starting Apps
at every bootup...
I tried "Fix Permissions" (even though I know this is not what it is for, on the off-chance)... but made no difference.
I reboot phone a lot - and whilst this doesnt effect the functionality of the phone, it does get quite irritating
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
Hello XDA Dev. I, Azeem, come to you guys with a problem and I need you all's help on solving it. Here's the story.
I was previously on Cyanogenmod 10.1.3 Stable for my phone and decided to try out the new 9-28 nightly of CM 10.2. However, when installing the rom, I rebooted in to recovery after installing it, gapps 4.3, and ajk 4.9 AOSP, but it got stuck at the Samsung logo and I could not enter recovery mode anymore nor could I boot to the homescreen. Knowing using odin to go back to stock would fix the issue, I did just that, and booted to the homescreen. Btw, I odined back to ICS 4.0.4 since I couldn't find an Odin-able tar file for Jellybean UCMD8 (if you know of any, please tell and link it to me). Anyway, I went and installed Mobile Odin to my phone and the N.E.A.K kernel ( http://forum.xda-developers.com/showthread.php?t=1614150 ) for the ICS stock ROM, booted into recovery, wiped data, cache, and dalvik cacke, installed Cyanogenmod 10.2 nightly, gapps 4.2, went to advanced, and clicked reboot into recovery.
Next thing I knew, guess what? It was back to being stuck on the damn samsung logo and I couldn't boot into recovery, yet again! I went and though why not give it another try, so I redid all the procedures I had done prior, but this time flashed the 10.1.3 stable, AND IT HAPPENED AGAIN! I was like wtf! That leads me to the question. Is there anything I can do to prevent this from happening again? I really like cyanogenmod and would love to go back, but I don't want to repeat all of this a 4th time. Thanks for your help in advance!
EDIT: Nevermind. I got UCMD8 Cooked to work, but I am scared to flash 10.1.3/10.2 because I don't want to have to deal with doing all that I did in OP again. However, I really want CM 10.1.3/10.2 back. A dilema.
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
creepyncrawly said:
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
Click to expand...
Click to collapse
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
azeem40 said:
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
Click to expand...
Click to collapse
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
votinh said:
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
Click to expand...
Click to collapse
I fixed the issue by doing the OP things and just restoring nandroid backup.
Hi guys,
A couple days ago I installed CM10 with the installer and then CM11 over the air. However I have some problems with the ROM apart from the battery drain and heat, my phone sometimes just randomly freezes, turns itself off and when I turn it back on, the battery dropped at least 20%. My very first question would be, if anyone has a fix for this? I already tried wiping system cache, but it did not fix the issue.
I googled around to find some solution, and it seems that CM 10 is more stable and there are fewer issues with it. I would like to go back to this version, however I'm not entirely sure what should I do. My first step would be wiping everything and factory resetting the phone, as there might be stuff left from the previous ROMs on the phone. I reckon I have two options from this point:
1. Running the CM installer again and have it install CM 10. Is this even possible? Or the installer won't even start given that I have a fresher version of CM?
2. Downloading the latest official ROM from sammobile, flashing that with ODIN and then running the CM installer. If I have to do this method, is there anything that I should extremely be cautious about? Also, I bought the phone in Hungary, but now I'm in England, and I installed CM here. I reckon I'll have to download the Hungarian ROM from sammobile for my phone, could someone please confirm this? The phone is not locked to a carrier anymore (they removed it), can I just flash the general (XEH) Hungarian ROM?
Thank you very much for the help in advance, and sorry for the noob questions!
gravisone said:
Hi guys,
A couple days ago I installed CM10 with the installer and then CM11 over the air. However I have some problems with the ROM apart from the battery drain and heat, my phone sometimes just randomly freezes, turns itself off and when I turn it back on, the battery dropped at least 20%. My very first question would be, if anyone has a fix for this? I already tried wiping system cache, but it did not fix the issue.
I googled around to find some solution, and it seems that CM 10 is more stable and there are fewer issues with it. I would like to go back to this version, however I'm not entirely sure what should I do. My first step would be wiping everything and factory resetting the phone, as there might be stuff left from the previous ROMs on the phone. I reckon I have two options from this point:
1. Running the CM installer again and have it install CM 10. Is this even possible? Or the installer won't even start given that I have a fresher version of CM?
2. Downloading the latest official ROM from sammobile, flashing that with ODIN and then running the CM installer. If I have to do this method, is there anything that I should extremely be cautious about? Also, I bought the phone in Hungary, but now I'm in England, and I installed CM here. I reckon I'll have to download the Hungarian ROM from sammobile for my phone, could someone please confirm this? The phone is not locked to a carrier anymore (they removed it), can I just flash the general (XEH) Hungarian ROM?
Thank you very much for the help in advance, and sorry for the noob questions!
Click to expand...
Click to collapse
If you want to downgrade to CM10, just download the cm10.zip and flash it on recovery (remember to wipe /system and all user data first).
If you want the stock rom you can flash a stock rom from any country, althrough it's recommended to flash the rom for the country you are in now.
Also, the battery bug is a device specific bug and cannot be fixed, maybe wiping the battery stats can help.
Thank you! Do you have a Galaxy SII? If yes, do you think that it's worth going back to 10.2 or should I just stick with 11, regardless of the bug?
gravisone said:
Thank you! Do you have a Galaxy SII? If yes, do you think that it's worth going back to 10.2 or should I just stick with 11, regardless of the bug?
Click to expand...
Click to collapse
I'm using cm11 m12 snapshot latest over i9100 .. I dont find any battery bugs as you've explained above !! Battery life is pretty good actually gives me life of around 5-7 hours with wifi on always !! Try this
Can somebody help me? I used the CM for a long time, but less than a month when I was with the CyanogenMod, the phone restarted and did not turn on anyway (something like a bootloop, but the darkened screen as if you were about to turn on, then lit again).
I tried to reinstall CM, but always after a short time of use, it restarts, and bootloop again.
I reinstalled the stock, but the frustration and willingness to use CM was so big that I tried to install again. Result: bootloop.
Anyway, I'm using the stock rom for a while, but still want to use CM.
Does anyone have any idea what could have happened? (All Xposed modules and mods that put into CM are the same I'm using now, but the stock has no problems)
This happened with RR rom too.
Sorry for this long text and my bad english
I want suggest you to wipe all thing system and data , cash/dalvik, (after backup) and then try to flash the ROM and just try another ROM instead CM and RR
Sent from my GT-I8190 using Tapatalk
But I've never had this problem before!