I am having problems with Faryaab's AOKP rom camera causing FC's. Can someone who is using this rom without camera FC's confirm what kernal they are using?
I came from Omega 6.0 with Siyah kernal 1.2.6. and did this:
1. factory reset
2. wipe cache / wipe dalvik cache
3. format system
4. flash build 40 of AOKP by Faryaab
5. flash gapps 29th of June
6. reboot
Deminetix said:
I am having problems with Faryaab's AOKP rom camera causing FC's. Can someone who is using this rom without camera FC's confirm what kernal they are using?
I came from Omega 6.0 with Siyah kernal 1.2.6. and did this:
1. factory reset
2. wipe cache / wipe dalvik cache
3. format system
4. flash build 40 of AOKP by Faryaab
5. flash gapps 29th of June
6. reboot
Click to expand...
Click to collapse
The camera FCs are a (very) known issue and is covered quite extensively in both the AOKP and the CM9 (they both have the same problem) threads. I believe that just recently, Codeworkx got a finger on the problem.
In short: it's not just you, and it's known. Also looks like the problem is in the app, not the kernel.
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.
I recently flashed my nightly build from 7/15 to 7/16 and now I am experiencing some problems. Main things I have noticed thus far are my weather widget not working and Google Play will not open. Anyone have any solutions to this?
Simplest troubleshoot:
Boot Clockwork Mod
Wipe Cache
Wipe Dalvik Cache
Reflash Gapps
Reboot
You need to reflash Gapps with each ROM flash.
Thank you! I have never had to flash my gapps for a nightly before but this solved the problem. I'm embarrassed that it was this simple
Hi all,
Can someone help me please?
I have an S3, and have come from an S1 and several HTC's before that. Well versed in the world of flashing.
My friend has an S2, and is trying to flash a custom ROM (has tried several different ones).
He has successfully rooted and install CWM using CF-root, but when he flashes ROMs they do not work. They don't get errors when flashing, but then always gets bootloops he reboots.
The only thing that I could think was missing was from my S1 days when there was recovery 2e, but I understand the recovery is within the kernel on the S2, so thats not it.
I'm sure there is something simple missing.. he has followed the myriad of guides on here to the letter, with no joy.
His current ROM (flashed through Odin) is XWLPO (which according to several sources can be rooted with cf-root for XXLQ5)
Before flashing a custom rom, he needs to wipe at least cache and dalvik in recovery. If still not fixed, wipe data. But, never and never do this wipe in cwm while on lpo (despite the fixed v 5.6 cf root lq5 should be fine)
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Before flashing a custom rom, he needs to wipe at least cache and dalvik in recovery. If still not fixed, wipe data. But, never and never do this wipe in cwm while on lpo (despite the fixed v 5.6 cf root lq5 should be fine)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thank buddy.
Just to clarify, is it only the wipe data that doesn't work from recovery, or the cache & dalvik as well?
And I assume if you don't do it through recovery, then you do it through settings --> Backup and reset?
It is best to perform full wipe, wipe cache and dalvik.
from my personal expirience its better to flash a custom rom via CWM and not via odin and defenatly full wipe and fix permissions bevor reboot
darkside super wipe?
cant i just run darkside super wipe the flash a new rom thats it right or am i missing something
I believe someone here will find this helpful
General steps before flashing a new ROM.
Requirements: ROOT access, CWM recovery
***Backup your present ROM just incase***
1. Wipe data/ factory reset
2. Wipe cache partition
3. Wipe dalvik cache (under advanced)
4. Format /system (under mount)
5. Flash your desired Rom/zips
6. Fix permissions (under advanced)
Notes:
- If you are moving from from an AOSP ROM to Samsung (vice versa), perform all the steps above.
- If you are upgrading / downgrading from one android version to another e.g ICS to jellybean or 4.0.3 to 4.0.4, also perform all the steps above.
- If you are upgrading from a Samsung ROM to another wipe the same android version, you may skip step 1.
- if you are upgrading your Aosp/aokp Rom with another with the same android version e.g 4.0.4 Aosp to 4.0.4 aokp, you may also skip
step 1.
*******Important******
If you are presently running a Samsung based 4.0.4 Rom that is using Samsung based kernel e.g CF-ROOT or stock kernel, please flash Siyah kernel before performing any of the above steps. You will end up with ash unusable device if you don't adhere to this important information.
Swyped from my Samsung Galaxy SII
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.
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