Good evening, good morning and good afternoon! (Depends what time zone you're in but I like to be polite).
I have a slight problem with a my brothers S2 that I need some advice on please:
Preface - I am not new to flashing phones but nor would I say I'm on the level as some of the people here. This is my third root, custom flash and recovery and I've kinda hit a funny bug. (First being a Samsung Galaxy Ace, second being my old Google nexus 5 due to 5.11 crashing it out & this is my third yay )
To my problem and what appears to be a bug or something I'm doing wrong-
There is no problem with the flashing or rooting of the phone when I've put on a nightly build of 12.1, latest version.
It's stable and runs like a dream. But when I reboot the phone, BOOTLOOP! So, like anyone would, I've reflashed the phone and it works fine - till you restart it.
Would I be correct in thinking I might have just got an unstable version OR do I need to install the latest Gapps? (? = not sure on spelling) to break from this boot loop? Effectively, the phone is dead after a reboot, power down or whatever the case is. But it does make me wonder why it works in the first place only to crash out after a reboot.
Now, thinking that it might be an issue with the nightly version, I've reflashed with a stable CM11 and there is no bootloop on restart/reboot. But I really want my brother to have the CM12.1. It's cleaner, faster and looks better IMO.
So, can anyone point me in the right direction?
May I thank in advance anyone who stumbles across this thread and reads and is/is not able to help me.
EDIT REASON: Naughty commers.
Cm 12.1 is known to be buggy. You compound the issue with that old of a device. Best bet would be search around for the threads on how to pull a bootlog from it.
Related
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
rcfcyl said:
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
Click to expand...
Click to collapse
What about the cm-7-20120722-NIGHTLY?
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
gsstudios said:
What about the cm-7-20120722-NIGHTLY?
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
Click to expand...
Click to collapse
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Hi @gsstudios,
Ah I see, I did wonder why there was 2x seperate branches for the same device... I could understand if one was for the HD or the LTE version, but I guess they already have their own variant name in CM already... Just thought it was odd to have 2x i9100 builds going on together.... lol
Anyway, regarding CM7.... I've finally managed to get it to work!!!! YIPPIE!!!!!!! Finally... Although I swear it wasn't as hard as this when the phone DIDN'T belong to me, and I did it as a test for my mate... But anyway, got it installed and loving it... It's nice to go back once in a while to where it all began (well, for me anyway.... My first device came with Android eClair, I think Android 2.1 or summit??) But CM7.x was my first custom OS ever installed on ZTE Blade.
It would seem all the CM7 builds that I can find, both on CM site, and other hosts are all BORKED (broken) and that they lack Boot info, hence the BootLoops... and that all their recoveries are broken, as not a single one would go back into recovery after flash, had to Odin it back to life with a PC. Not cool if ya gone out for the day... lol So basically I found some random GB kernel, and flashed that after CM7 + GApps + Recovery.... and thank the lord, it all boots again...
I'd just like to THANK YOU, for always consistently and continually coming to my support needs..... Your help/advice has been extremely helpful.... thanks
Lister
gsstudios said:
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Click to expand...
Click to collapse
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
NOTE: Most, if not all of these ROMs are designed for ATT.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
I had the same problem and switched to Philz Touch instead of TWRP, I like TWRP a lot more and most people say its more stable, but that's what fixed it for me.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Umm... Don't reboot
Sent from my SCH-I545 using xda app-developers app
I have read, on CM's site somewhere I believe, they recommend using CWM for a recovery. I use 6.0.4.4 and have no issues with getting stuck at the boot logo. There was an issue with that but CM addressed it in one of the nightlies about two weeks ago.
I had that issue when I had a newer twrp recovery I have the .2 whatever one and I havnt had it since.
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
I am currently running CM11 and dealing with a lot of the problems that cm10 had. So tried CM12. Basically dead in the water. Never got past registration.
Very sluggish and the keyboard keeps disappearing. The installation of CM11 went pretty smoothly following the install instructions. Not so with CM12.
Maybe there is something I am missing. The instructions say that repartitioning is not necessary !?!??!
Anyway followed the instructions to the letter. Got the suggested recovery and flashed it just like on cm11. The correct gapps to use is always a crap shoot so I tried several. I even installed without gapps still had problems.
So any help here would be appreciated.
thanks
I have been testing CM12 for a few weeks and have a few of the same problems. It seemed like at first it was pretty snappy, but now it's sluggish, keyboard disappears constantly, and my biggest pet peeve is that quite a few of my apps are now unavailable for this device. They worked before, so it's a bug in CM or one of the newer Android versions. I'm just going back to an older ROM for now.
Hi cosmic_kid
I'm asking these same questions in the cm12 QA and dev pages and not getting anywhere. They all tell me to go read some more or stop being rude !?!??!?!
I am currently running cm11 and only have the usual problems just like cm10 had. i.e. battery, black out, losing wallpaper.
So I thought cm12 should be a piece of cake !!! NOT SO !!
There must be something different with the install that is screwing something up.
I tried the recommended eng recovery and the latest TWRP and CWM. Same results. After gapps is installed things go to heck.
I did try running cm12 before installing gapps and it ran smooth. After gapps sluggish and never got past registration. Keyboard never came up !?!?!?
I don't know what to do so I will download the latest nightly and try again.
I Feel Your Pain!
Guys, I know exactly how you feel. I merged the partitions according to the other posts, formatted cache and userdata to f2fs and tried all the nightlies that came out, but keyboard problems, superuser problems and setup crashes just made it impossible to get anything going on my trusty 8gb Nook (BNTV250A). The closest I got to getting anywhere with CM 12 on it was when I updated the CM 12 March 26th nightly on CM 11-M12 and added pa_gapps-modular-nano-5.0.1-20150315-signed. Play store worked, I was able to get into developer options and enable root access and it looked hopeful, but alas it was so slow and lagging that I have given up for now. I used repart.img to go back to stock, (touch pad didn't work on stock since I had upgraded to 10 touch!) booted off SD and installed CMW recovery to restore my CM 11 -M12 configuration. I'm staying in touch through all the threads and hopefully we will one day have a smooth CM12 on our beloved Nooks!
CM12 is now working very smoothly on my 16gb nook. I didn't have to repartition anything. I just about got rid of my 16gb nook because it's older and slower than the newer 8gb nook. Glad I didn't.
So until there is a "how to" thread on how to get it to work on the 8gb nooks I will be using the older one.
The devs said that they didn't have a 8gb model to test their nightlys on. I'm wondering if they test them at all ???
What did you do to get it to run smoothly? I have the 16GB and it slows down all the time with CM12. I read gapps causes a lot of head-aches so I've been tempted to run without it and just side-load all my apps... :/
cosmic_kid said:
What did you do to get it to run smoothly? I have the 16GB and it slows down all the time with CM12. I read gapps causes a lot of head-aches so I've been tempted to run without it and just side-load all my apps... :/
Click to expand...
Click to collapse
pico gapps and Demetris' 16GB CM12 with the Tricker Mod stuff = faster than they day I bought it.
Now I just need 8GB working the same, since I have two of those!