Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
theking1st said:
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
Click to expand...
Click to collapse
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
cars1189 said:
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
Click to expand...
Click to collapse
Thank you @cars1189 for your answer. I used the device thread to do it but the problem is, I let it spinning for more than 5 hours. I have flashed many roms in my phone since i had it (more than 10 times or more) and i know that it does not take more than 10 mins max to install. But don't worry after that i went back and restored my previous CM 9 rom and right now i'm on the CM 11 build of 1-29-14 of your CM mass thread. It works fine, not at 100% but it doesn't drain my battery like your CM 10.2 build of 1-11-14 and it is almost stable. I will try tonight to use your ADC kernel with the jfbs CM 11 rom that first didn't work for me because I saw in your thread that this kernel may help it to load and install without the spinning issue. So i will give it a shoot. But anyways thanks for your answer and it means a lot to me really. :good:
GOOD
@cars1189 , I'm actually running the 6-18-14 build of CM11 and as far as it goes, i'm not encountering any major issue at the moment. The theme engine is working fine for me and battery life is great for my usage. I use this build as a daily driver, and it does a great job. Calls, texts, data, wifi, Bluetooth and GPS are all working. I had issues before with the amount of RAM available, but now that it has 375MB of RAM, it is more snappy. Just :good: Thank you for your work on our to make our phone still valuable today!! THANKS MAN!!!!!!
Related
I've search and I don't think I've seen an answer to this question yet and as my first question/post I'd like to say:
I'm running CM9.04 and I love it, but I'd like to assist in testing out the nightlies and AOKP etc..., but no matter what I do I always get a bootloop (Sometime shows the booting android for about half a second then reboot, sometime not even that). I see others say that these ROMs are working (as well as development ROMs do ) I clear all caches, factory reset and always the same thing (except on the .04 alpha release). Anyone else have this issue or a solution or suggestions?
Hey guys,
I upgraded to the irish official 4.3 (I9300XXUGMJ9_I9300VFGGMJ5_I9300BUUGMJ3_HOME) from cm 10.2.
I now have a battery drain, it takes about 8 hours from 100% to 0% with an hour screen time. Also sometimes after turning off the screen I can't get the phone to start again without taking out the battery.
I did a full wipe after installing 4.3 and I'm considering another factory reset/wipe, but wanted to see if there is another solution before doing this.
Thanks for any help.
Read that roms thread multiple posts on the subject no need for a new thread .
JJEgan said:
Read that roms thread multiple posts on the subject no need for a new thread .
Click to expand...
Click to collapse
True true. I read a few extra pages back and it seems a few people are having issues.
I remember having this issue a few months back, go into your settings and go to battery. Is "Android OS" at the top or very close? If it is then the reason was (in my case) the device couldn't go into deep sleep mode which should happen when you lock your device, this means that instead of nearly shutting down and only having the data connection on (maybe wifi aswell), the device was running the same as before you hit the power button, the only difference is that the screen is that the screen is off. There are different reasons for this happening but for my device it was a kernel issue, this means that these steps may not work for you, because like i said, this issue is different every time.
All i had to do to fix this issue was flash a new kernel, i chose the googy max kernel 1.7.5 for CWM, which is a continued development of the siyah kernel, after the developer abandoned it.
Yoiu just have to flash it the same way you did Cyanogenmod, go into CWM (or another custom recovery) and flash it to the device.
Hi guys, I was using my phone messaging my friends. I put the phone down for about half an hour. When I pick it up again it is hot and will boot to the glowing slimbean logo (boot animation). I assume the phone ran out of battery, but even when I plug it in it will not boot past the logo. Do you guys have any idea as to what is going on, and how I can get my phone working again?
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
SteveMurphy said:
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
Click to expand...
Click to collapse
Thanks for your reply Steve!!
The reason why I'm still using 7.1 is because I was having battery problems on 8.0. I wasn't sure if the bug I had was fixed so I decided to stay behind. This was probably not the best choice but convenience and stability were something I wanted. I will try 8.1 after I backup my current setup if it works.
I believe its Google Now that has been causing me problems. Ever since I started using it my battery drains much faster, and the phone is hotter than usual. If wiping the cache works then I will delete it , otherwise I will probably have to wipe to factory which I really don't want to do.
OK so wiping the dalvik cache has allowed my phone to get past the bootloop. I get this message "Android is Upgrading.. starting apps" and its been stuck on it for a while. Any ideas?
This is weird, don't really know why - out of nowhere - your rom just all of a sudden won't boot.
And yes Google Now will kill ANY battery!
One other method would be to dirty flash 7.1 without doing any more wiping, if you want to keep it. If that doesn't work, full wipe/format system and start over.
Hope you get it working again!
So, i have an used xt910 with Carbonrom KK 4.4.4, Safestrap v3.72 and Stock ROM. I have been having problems with the network since two weeks ago. Sometimes it just runs out of network out of the blue (Vodafone), even though my roommate still gets full signal. Sometimes by just restarting it the network would come back. Last saturday i rebooted it but then it would not turn on anymore, entering in a very annoying boot loop. And when i could boot into Recovery, a little surprise: The touchscreen would not work. First i thought it might be a hardware problem, tried dissasembling it and everything but nothing worked. But then out of the blue, around three hours later it started working properly again. Ok so i thought it could be some kind of bug with the rom so i installed CM 11 (the nightly version from the 22.11.). But it was running slowly, compared to Carbonrom. And i did not want to go back to carbon so i installed the Dirty Unicorns rom that i found here. And then today when i started it i saw that i was out of network signal again! So i tried rebooting it but it started with that stupid boot loop. Right now it is working okay, but it is really annoying to always go through this. So i do not think it was a problem with carbonrom (i am newbie with it). Has anyone ever encountered this problem bzw how did you manage to fix it?
Thanks a lot in advance!
(sorry for my english xD)
valderi.segundo said:
So, i have an used xt910 with Carbonrom KK 4.4.4, Safestrap v3.72 and Stock ROM. I have been having problems with the network since two weeks ago. Sometimes it just runs out of network out of the blue (Vodafone), even though my roommate still gets full signal. Sometimes by just restarting it the network would come back. Last saturday i rebooted it but then it would not turn on anymore, entering in a very annoying boot loop. And when i could boot into Recovery, a little surprise: The touchscreen would not work. First i thought it might be a hardware problem, tried dissasembling it and everything but nothing worked. But then out of the blue, around three hours later it started working properly again. Ok so i thought it could be some kind of bug with the rom so i installed CM 11 (the nightly version from the 22.11.). But it was running slowly, compared to Carbonrom. And i did not want to go back to carbon so i installed the Dirty Unicorns rom that i found here. And then today when i started it i saw that i was out of network signal again! So i tried rebooting it but it started with that stupid boot loop. Right now it is working okay, but it is really annoying to always go through this. So i do not think it was a problem with carbonrom (i am newbie with it). Has anyone ever encountered this problem bzw how did you manage to fix it?
Thanks a lot in advance!
(sorry for my english xD)
Click to expand...
Click to collapse
About the signal loss,just delete CellBroadcastReceiver.apk from system/app.
Sent from my Razr XT910
thanks!! I was looking into some other posts and i did it
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .