After flashing Cyanogenmod 10.2 last night on my Galaxy S2, I am getting weird problems.. sometimes back and home button become unresponsive but it goes fine when i press power button and again switch it on... Anyone else experiencing same problem ?
What could be possible solution for this ?
Thanks
Flash the next build. Look on Cm thread for info on your build and if no one has the same issue then it may just be a bad flash. Did you wipe data and system for a clean install or did you just update with a dirty flash? What build are you on?
andrewwright said:
Flash the next build. Look on Cm thread for info on your build and if no one has the same issue then it may just be a bad flash. Did you wipe data and system for a clean install or did you just update with a dirty flash? What build are you on?
Click to expand...
Click to collapse
I did wipe data/factory reset when I flashed CM 10.2 , Its the first time that I flashed CM 10.2 because I was thinking to root my phone but not only this , I notice that cyanogen circle (which appears when restarting phone) appears automatically in between when phone is switched on... I dont know what's going on..
Build number:-cm_i9100-userdebug 4.3 JLS36G ac1d4fdf43 test-keys
CyanogenMod version- 10.2-20131005-Nightly-i9100
Go to mounts and storage and format
Data
System
Cache
In advanced wipe dalvik cache
Then flash the rom and gapps.
Reboot.
Related
If i flash both of them , bootloop will occur and the reaction becomes slow
However , remix 1.4 hasn't this problem
who can tell me why ?
j47d8234554 said:
If i flash both of them , bootloop will occur and the reaction becomes slow
However , remix 1.4 hasn't this problem
who can tell me why ?
Click to expand...
Click to collapse
KERNEL not suit rom..
jje
How to update from v 1.0
this is my first post, so yeah im a noob, but just want to ask if i was on Resurrection ics v1.0, how could i update? do i just jump to the most recent update, or is there a certain update i have to flash first before moving on? ive tried to flash the v1.4 but then it would'nt boot, then i restored a backup, tried a couple times even from a fresh stock rom, but still it couldnt boot, what do you think the problem is?
sorry for all the questions
i was on resurrection now i dual boot 1.8 with siyah 3.1.2 with D4 rom( which is amazing btw) try 3.1.2 siyah and see if it works - im avoiding RC's and betas for kernel since the brickings, unless you want the features from rc5
@yugorisfriwan you don't need to install any update, go straight to the last version.
To install
1- full wipe & wipe cache
2- install rom
3- wipe dalvik
4- reboot (it takes time to boot the first time so be patient)
5- install another kernel (siyah of instance) otherwise you are done.
Now to my question
I have the version 1.8.1 and siyah kernel 3.2b8 everything works great except that I cannot access my external sdcard on my computer. I also tried the default and thoravukk kernels but they give the same result.
Thx in advance for your help
xXlordyXx said:
@yugorisfriwan you don't need to install any update, go straight to the last version.
To install
1- full wipe & wipe cache
2- install rom
3- wipe dalvik
4- reboot (it takes time to boot the first time so be patient)
5- install another kernel (siyah of instance) otherwise you are done.
Now to my question
I have the version 1.8.1 and siyah kernel 3.2b8 everything works great except that I cannot access my external sdcard on my computer. I also tried the default and thoravukk kernels but they give the same result.
Thx in advance for your help
Click to expand...
Click to collapse
Thanks mate!!
yugorisfriwan said:
Thanks mate!!
Click to expand...
Click to collapse
hey i am using this remix rom right from the ver 7.4 now on v1.8.1 what i sugesst u first is 2 install v1.7 then u upgrade it 2 the new v1.8.1 by simply flashing it over v1.7 without any wipes that way u wont have any issues in installation
PS: while installing 1.7 u do a full wipe
ie
wipe data/factory reset
wipe cache part
wipe dalvik cache
then install v1.7
then again wipe cache
wipe dalvik cache
Fix permissions
reboot 2 system
boot takes a while?
So how long do i have to wait for the phone to actually boot after updating? So ive flashed the updates, but when i select reboot now, it then comes to the Galaxy s ii i19100 splash screen. Now i have waited for at least 5 minutes, and nothing happened yet, so just restored my backup in fear of something going wrong am i too inpatient or is that just taking to long? how many minutes do i actually have to wait until its a sure flash fail? thx in advance!
5 minutes is too long, are you sure that you have done a full wipe before installing the rom and then wiped the dalvik cache after. The only time when my phone wouldn't boot was when I had forgotten to do the wipes.
anyway just redo the process and make sure you do everything (don't flash any kernels) and just leave the phone for few more minutes than last time. otherwise try to install another version (1.7 for instance) and see if it boots this time
installation problem
hi ,guys
sorry to post here,but i am having a annoying problem during the installation .
As,i am trying to install it is showing a build prop problem and showing some step7 and displaying msg as installation aborted.I did full wipe,wiped cache did data reset,wiped dalvik everything i did but this problem still annoys me.
rzrdelta said:
hi ,guys
sorry to post here,but i am having a annoying problem during the installation .
As,i am trying to install it is showing a build prop problem and showing some step7 and displaying msg as installation aborted.I did full wipe,wiped cache did data reset,wiped dalvik everything i did but this problem still annoys me.
Click to expand...
Click to collapse
hey which rom ur trying 2 install if its v1.7 of remix then first flash the cm9 kernel dwnld'ng the same from OP (original post in page 1 of remix ics thread) section after that reboot 2 cm9 recovery and then flash 1.7 it will be ok
5 minutes are too long mate. before flashing make sure that the current rom you are on has default CM9 kernel (for version 1-1.8)
After that follow the steps:
1.wipe data/factory reset
2.wipe cache partition
3.install main rom
4.go in advance and wipe dalvik cache and then fix permissions
5.wipe cache partition again and reboot
6.after ur first reboot u can then flash kernels,themes,and mods
enjoy
So... if im still on resurrection version 1.0, would installing the stock cm9 kernel work? .... then i could update?
So any workarounds on accessing the external sd on the computer?!!?
xXlordyXx said:
I have the version 1.8.1 and siyah kernel 3.2b8 everything works great except that I cannot access my external sdcard on my computer. I also tried the default and thoravukk kernels but they give the same result.
Thx in advance for your help
Click to expand...
Click to collapse
This seems to be a bug with the rom. I got the same problem on 1.4 and on 1.8.1. It will only mount the internal mass storage.
To work around this: Mount it with CWM. Works for me.
Hi Guys,
Yesterday i installed Paranoid Android on my phone ( full wipe data and cahe ) and it started to reboot when making calls.
So i decided to install CM9 RC1 and got the same problem.
I reverted back to stock and now my phone is fine.
Someone has a clue of what's happening ?
I tried different kernels but got the same problem.
Your help is appriciated.
Greetings,
PTiT
Have you formatted /system and fixed permissions?
Inviato dal mio GT-I9100 con Tapatalk 2
PTiTDaV said:
Hi Guys,
Yesterday i installed Paranoid Android on my phone ( full wipe data and cahe ) and it started to reboot when making calls.
So i decided to install CM9 RC1 and got the same problem.
I reverted back to stock and now my phone is fine.
Someone has a clue of what's happening ?
I tried different kernels but got the same problem.
Your help is appriciated.
Greetings,
PTiT
Click to expand...
Click to collapse
If you are doing it through CWM
Try installing after wiping Dalvik cache available in advance.
PTiTDaV said:
Hi Guys,
Yesterday i installed Paranoid Android on my phone ( full wipe data and cahe ) and it started to reboot when making calls.
So i decided to install CM9 RC1 and got the same problem.
I reverted back to stock and now my phone is fine.
Someone has a clue of what's happening ?
I tried different kernels but got the same problem.
Your help is appriciated.
Greetings,
PTiT
Click to expand...
Click to collapse
hi.
Had same kind of issue. Random reboot/shutdown.
I installed 1.6 last night. With full wipe of everything I could find in my kernel to wipe.
then, install paranoid.
then install G-apps.
then WIPE cache again.
then fix permission.
as recommended in the official thread by the dev.
It solved my issue.
good luck.
Same problem here.
Any stock rom (including ICS) works well.
I tried installing paranoidandroid 1.6.
Factory reset
Wipe cache
Wipe dalvik
Install gapps and camerafix.
wipe cache.
Set phone dpi to 184
reboot
And basically, everytime i try to make a phone call, it looks like that the phone screen (the one that displays the contact picture and the close-call red button) is crashing.
I can hear 10 seconds of phone ringing/conversation and then the system reboots, showing me the boot animation.
The only way to fix this, so far, is by installing a stock rom
..probably I am missing something, but I cannot get it working.
I resolved mine by reverting to a GB stock rom and flashing the lastest nightly from there.
box2k2 said:
I resolved mine by reverting to a GB stock rom and flashing the lastest nightly from there.
Click to expand...
Click to collapse
So basically you Installed the latest CM9 nightlies rather then paranoidandroid ?
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.
Hi all, currently im using Cyanogenmod 10.2 (20131231) latest official build for android 4.3 JB (CWM 6.0.4.5) and mind to change to omni official build 4.4 KK. After copy and paste the zip files into my SD (ROM 20140101 & Pa_gapps 20131230), i go to recovery mode and wipe everything (wipe data/factory reset, cache , dalvic). after all done then i install the zip files (ROM & Pa_gapps), then i reboot recovery and then reboot system. All installation smoothly with no problem. The problem come after the omni logo loading is done, it should let us to choose a language , register a google account , set up wifi and etc. The screen become blank (black screen), not shows all that particular. The only appear on the screen are battery indicator, line icon and notification bar (can pull it down and can access to all function button there like setting, gps, mobile data, wifi, brightness). When i push home screen button, it become black screen again. I can lock and unlock it but i will become black screen after i unlock it.
so what are actually the problem im facing ? if there any solution i would be thanked
biscuits01 said:
Hi all, currently im using Cyanogenmod 10.2 (20131231) latest official build for android 4.3 JB (CWM 6.0.4.5) and mind to change to omni official build 4.4 KK. After copy and paste the zip files into my SD (ROM 20140101 & Pa_gapps 20131230), i go to recovery mode and wipe everything (wipe data/factory reset, cache , dalvic). after all done then i install the zip files (ROM & Pa_gapps), then i reboot recovery and then reboot system. All installation smoothly with no problem. The problem come after the omni logo loading is done, it should let us to choose a language , register a google account , set up wifi and etc. The screen become blank (black screen), not shows all that particular. The only appear on the screen are battery indicator, line icon and notification bar (can pull it down and can access to all function button there like setting, gps, mobile data, wifi, brightness). When i push home screen button, it become black screen again. I can lock and unlock it but i will become black screen after i unlock it.
so what are actually the problem im facing ? if there any solution i would be thanked
Click to expand...
Click to collapse
Also format system under mounts and storage
And then install zips
Sent from my GT-I9100 using Tapatalk 2
corruptionfreeindia said:
Also format system under mounts and storage
And then install zips
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
thanks,i will try after finnish downloading 20140102 build
already format the system,wipe data/factory reset,wipe cache,wipe dalvic
but still the same.cant set up google account like we just bought a new phone
biscuits01 said:
already format the system,wipe data/factory reset,wipe cache,wipe dalvic
but still the same.cant set up google account like we just bought a new phone
Click to expand...
Click to collapse
might be gapps problem or even the rom but im assuming its the gapps
use this CORE GAPPS
hope this helps
thuva06 said:
might be gapps problem or even the rom but im assuming its the gapps
use this
hope this helps
Click to expand...
Click to collapse
thanks mate, its works. yeah gapps problem.
can i install additional gapps after on ? like camera for KK, galery for KK
biscuits01 said:
thanks mate, its works. yeah gapps problem.
can i install additional gapps after on ? like camera for KK, galery for KK
Click to expand...
Click to collapse
yes your free to flash anythig
dont thank with words mate
So, I made a custom PAC ROM zip for my phone with the pac_i9100-nightly-20150128.zip modded for my phone by removing the device check so it will install on my S959G. And reason for me doing this is the same for OmniRom, all SGH-I777 zips for PAC ROM and OmniROM are deleted for some reason so the I9100 is next in line for me.
Here is my process for installing this rom
Wipe user data/Factory reset
Wipe Cache partition
Wipe Dalvik cache
Installed Mr.Cooks ROM wipe script
Installed pac_i9100-nightly-20150128.zip
Installed Render-KK-03-22-CWM.zip
Installed GAPPS 4.4.4 Pico zip
Wipe user data/Factory reset
Wipe Cache partition
Wipe Dalvik cache
Reboot into PAC
I thought my steps was enough, and I'm coming from Resurrection Remix 4.4.2 KitKat v5.1.5 By SteveMurphy
Is there a step I missed in the flashing process or an app I have installed causing Random Reboot or Reboots in general.
I also checked the last_kmsg file and it said something about rebooting
<0>[ 6993.848196] c1 Rebooting in 1 seconds..
Including a link to the file on my MEGA below
My last_kmsg file
You should be wiping /system before installing the ROM, along with the usual cache wipes. You do not have to do those wipes again after installing. No idea what would be causing random reboots, except the usual suspect being a faulty power button. Try your install again, but wipe /system as well and don't use the ROM Wipe Script. There have been (old) reports of that causing some issues.
One other thing could be the kernel, as Render's kernel is really outdated - could be another cause!
SteveMurphy said:
You should be wiping /system before installing the ROM, along with the usual cache wipes. You do not have to do those wipes again after installing. No idea what would be causing random reboots, except the usual suspect being a faulty power button. Try your install again, but wipe /system as well and don't use the ROM Wipe Script. There have been (old) reports of that causing some issues.
One other thing could be the kernel, as Render's kernel is really outdated - could be another cause!
Click to expand...
Click to collapse
I have CWM recovery installed and it only can wipe data/factory reset, cache and dalvik cache. I could install Omni TWRP to be able to wipe /system. I do have the Shift kernel 1.0 to 5.0 zips as well, i could flash hem but i have no idea if they are compatible with STweaks since I only use it to enable the BLN for the bottom keys. Plus I random rebooted twice today, you want another last_kmsg log from it?
Also logcatting on my Ubuntu 15.04 laptop in terminal with the following command
Code:
adb logcat *:W *:F *:E
for Warnings, Fatal Warnings and Errors until a random reboot occurs
last_kmsg2
Sent from my SGH-I777 using XDA Free mobile app
CWM wipes /system, it's in a sub menu somewhere but I don't remember because I've not used CWM in a very long time. I know it's there because I used to do it! My suspicion is it's kernel related, but you'll need a KK kernel that's updated with the necessary blobs and I don't think there is a newer one for i777.
Unless someone else pops in with another suggestion, I'm out of ideas. Maybe it's time for you to update to LP?
SteveMurphy said:
CWM wipes /system, it's in a sub menu somewhere but I don't remember because I've not used CWM in a very long time. I know it's there because I used to do it! My suspicion is it's kernel related, but you'll need a KK kernel that's updated with the necessary blobs and I don't think there is a newer one for i777.
Unless someone else pops in with another suggestion, I'm out of ideas. Maybe it's time for you to update to LP?
Click to expand...
Click to collapse
I tried CyanideL 5.1.1 ROM for I777 and it would random reboot, but on this PAC ROM, I think I fixed it by turning off Dynamic statusbar colors on screen to disabled and has not rebooted yet but I'm still crossing my fingers still.
Also read about Mr.Cooks ROM Wipe script on Omni 5.1, seen it sticks some S2 phones on the Samsung Galaxy S2 screen for awhile, Not good