Hello,
A month ago I flashed Arter97 kernel on my GS3 with JustArchi's CM12.1 Unofficial (Android 5.1.1) and I was experiencing no issues, until I flashed a new custom ROM.
The device began bootlooping at every custom kernel/ROM I install and it can only be fixed by flashing the Arter97 kernel itself, but I want to switch to the Boeffla kernel instead because of performance issues I'm having.
It also can't seem to mount the preload partition in the recovery, not sure if it has to do with anything.
Is there anyway to fix this?
I'm running the Blekota S5 Lite V12 (Android 4.4.2) custom ROM with Arter97 kernel installed.
I've already tried this:
Full wipe in TWRP.
Using CWM to flash another kernel/ROM (I normally use TWRP 2.8.6.1)
Restoring the stock TouchWiz ROM using Nandroid Backup and a full wipe afterwards than installed a custom ROM.
Flashing Boeffla kernel in TWRP and CWM.
I fixed it by flashing stock TouchWiz 4.3 ROM using Odin and flashing CM12.1 afterwards
You have to go back to stock rom via odin.
I wish I stole my HTC M9.
Related
Is it possible to upgrade CWM on my S2 or are the particular CWM versions matched to particular kernels, like Samsung stock or CM? I am running NeatROM with Philz kernel, which uses CWM 6.0.3.7. I see there is a newer versions of CWM that can be flashed which is KK compatible (thinking about giving Cyanfox a whirl in near future). Thanks.
Recovery is baked into the kernel on the S2, so any recovery you flash independently of it will only persist until the next reboot. If you want a particular CWM version permanently, you'll need to run a kernel which has it.
MistahBungle said:
Recovery is baked into the kernel on the S2, so any recovery you flash independently of it will only persist until the next reboot. If you want a particular CWM version permanently, you'll need to run a kernel which has it.
Click to expand...
Click to collapse
Thanks. That is very helpful to know. So if you "temporarily" flash the latest CWM for kitkat in order load Cyanfox, then does Cyanfox reinstall the CM11 kernel with the appropriate permanent CWM for kitkat?
corvus.corax said:
Thanks. That is very helpful to know. So if you "temporarily" flash the latest CWM for kitkat in order load Cyanfox, then does Cyanfox reinstall the CM11 kernel with the appropriate permanent CWM for kitkat?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2222843
downlaod the CM11 kernel, flash it via your current one, wipe data/factory reset from the new kernel, wipe system too just incase, and install cyanfox and its gapps.
I'm planning to use Custom ROM for my JB using Custom Kernels from my Rooted ICS, and I have questions and doubts. Here's the steps and the Q's they have:
So, here's the steps I planned based on my S2 Guide Surfing:
1. Root my ICS (Done)
2. Flash Stock JB Official Firmware via Odin XWMS1? XWMS2? or XWLSW?
Questions Regarding This Step:
A. Do I have to backup my /efs folder from ICS here?
B. Do I have to Wipe Data/Factory Reset + Wipe Cache BEFORE/AFTER flashing the JB Firmware?
3. Flash Siyah? or DorimanX? Kernel via Odin
Questions Regarding This Step:
A. Can I run these kernels on my Stock JB ROM (if succeededly flashed)?
B. If I do a backup on Siyah via its CWM, and changed to DorimanX, then noticed that the kernel's not my type, can I restore my backup from Siyah's to DorimanX's CWM? Or does the both kernel have the same CWM?
4. Flashing Custom ROM via Custom CWM
Questions Regarding This Step:
A. If I flashed a Custom ROM which has a Cusrom Kernel inside (like NeatROM, I suppose), will it be overwritten my Siyah/DorimanX kernel? Or they will still be there?
Thanks for Noticing My Questions! And Very Thanks for Answering Them!
1) Yes, I'd backup up EFS immediately after you root your phone (and even before you do a nandroid backup with CWM). Use Hellcat's kTool from Google Play (and buy Hellcat a beer after you download it).
2) No. No need to wipe when flashing stock firmware (you can if you want though if you like a really clean install) because you're going to be wiping before you do a custom rom install anyway.
3) Yes. You should be able to run Siyah or Dorimanx just fine on stock JB (make sure you choose the right build though; read the threads devoted to these kernels to work out which build you need).
4) Yes, if you do a nandroid backup with CWM while running Siyah, and you switch to Dorimanx & decide you don't like it, you can restore your backup & go back to Siyah.
Though you could just easily re-flash Siyah with CWM to achieve the same result. That will probably be quicker than restoring a backup (say, 2 minutes Vs 10 minutes). If you re-flash a kernel, just the kernel changes, none of your settings/apps/anything else does, so restoring a nandroid just to go back to a particular kernel is overkill.
5) Yes. If you flash a custom rom, the kernel bundled with that rom will overwrite/replace your current kernel. If you don't like the kernel bundled with the rom, you should be able to use any other kernel you want with it provided the kernel you want to use works with the base of the rom (I.E the kernel you want to use works with TW roms if you're running a TW rom, or AOSP if you're running an AOSP rom) & the Android version of the rom you're running. Again, read the thread devoted to the kernel to determine compatibility before you flash it (worse thing that can happen if it isn't compatible is the phone will bootloop though; unlikely to brick your phone outright).
I was using stock ROM with root i followed the following procedure to install 12.1 nighties but after installing OS keyboard keep on FC's and OS reboots
i am using i9100T version of S2
noppy22 said:
I'm assuming you have stock unrooted firmware? The easiest way is to install philz kernel from stock(3e) recovery, then reboot to recovery and flash a newer recovery that is capable of flashing the newer versions of android. If you just want to install CM12.1 straight away just back up your efs then:
1. Download the DVLSH kernel .zip from HERE
2. Download the philz 6.48.4 from HERE
3. Reboot into stock recovery, flash the DVLSH kernel(if your firmware build is DVL**, you could probably reboot into system no problem)
4. Reboot to recovery(not system), flash the philz 6.48.4
5. Reboot to recovery(not system), follow the steps for installing in the CM12.1 thread after backing up etc
Keep the DVLSH kernel. Once you install CM, you will have CM recovery, which only allows you to flash signed .zips(which this one is)
EDIT - The philz 6.48.4 is also signed and is probably the more useful one to keep, being compatible with the newer roms
Click to expand...
Click to collapse
Currenlty my phone is without OS , kindly provide a way to Fix this issue or kindly provide me link to goback to STABLE stock version
Phone i9100T
KiranP23 said:
I was using stock ROM with root i followed the following procedure to install 12.1 nighties but after installing OS keyboard keep on FC's and OS reboots
i am using i9100T version of S2
Currenlty my phone is without OS , kindly provide a way to Fix this issue or kindly provide me link to goback to STABLE stock version
Phone i9100T
Click to expand...
Click to collapse
You could try doing a full wipe and installing again. Try installing the rom, reboot to system, then let the system settle for a few minutes, then going back to recovery and install gapps.
Which gapps did you use? I would try the pico gapps from
The alternatives are:
1. You could download the stock rom for your region from sammobile.com or one of the other websites that provide stock roms, then install with odin
2. You could read up on some of the older custom kitkat or jellybean roms that are more stable and try those.
[url]http://forum.xda-developers.com/galaxy-s2/development-derivatives
A couple that come to mind are Slimsaber 4.4.4 by Fusionjack and the latest unofficial CM11 by Lanchon
FYI if your priority is stability, it's probably best to steer clear of lollipop roms atm. They all have their issues
noppy22 said:
You could try doing a full wipe and installing again. Try installing the rom, reboot to system, then let the system settle for a few minutes, then going back to recovery and install gapps.
Which gapps did you use? I would try the pico gapps from
The alternatives are:
1. You could download the stock rom for your region from sammobile.com or one of the other websites that provide stock roms, then install with odin
2. You could read up on some of the older custom kitkat or jellybean roms that are more stable and try those.
[url]http://forum.xda-developers.com/galaxy-s2/development-derivatives
A couple that come to mind are Slimsaber 4.4.4 by Fusionjack and the latest unofficial CM11 by Lanchon
FYI if your priority is stability, it's probably best to steer clear of lollipop roms atm. They all have their issues
Click to expand...
Click to collapse
Keyboard FC happened even when i didnt flash gapps , i did try clean flash multiple times , still same, ok downloading slimsaber Rom and kernel
to flash this slim rom
i first flash a recovery using ODIN then From CM recovery i flash slim kernel.zip ? then reboot then flash Slimsaber ROM ?
KiranP23 said:
Keyboard FC happened even when i didnt flash gapps , i did try clean flash multiple times , still same, ok downloading slimsaber Rom and kernel
to flash this slim rom
i first flash a recovery using ODIN then From CM recovery i flash slim kernel.zip ? then reboot then flash Slimsaber ROM ?
Click to expand...
Click to collapse
All you need to do is
1. Flash either of the philz kernels
2. Turn phone off and reboot to recovery
3. Full wipe, flash slimsaber(and 4.4.x gapps if you want)
4. Reboot to system
You don't need the slim kernel
Hi all,
I own a brand new Galaxy S6 Edge, SM-G925F, bought just 3 days ago in European Union/
Germany.
It has installed the latest Samsung Stock:
Android version: 5.1.1
Base band version: G925FXXU3COI9
Build number: LMY47X.G925FXXU3COI9
Security Software: MDF v2.0 Release 3 und VPN v1.4 Release 5.2
Latest Stock: G925FXXU3COI9_G925FDBT3COI6_DBT.zip
After updating OTA to the latest stock I tried to root the phone.
First of all I have flashed TWRP 2.8.7.1 via Odin 3.10.6. Then I have installed
Hacker Kernel V5 and XPosed v75.8 by WANAM (20151030) (using TWRP).
After finishing configuring the phone I have seen the next day that my akku has
been eaten and found out that the phone *never* enters deep sleep mode.
As soon as I go back to Stock ROM, Stock Kernel, Stock Recovery
(G925FXXU3COI9_G925FDBT3COI6_DBT.zip), deep sleep mode is working instantly
(controlled with CPU Spy).
What I have done without success to solve the problem:
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. trying the solutions from zidroid (fix-battery-drain-and-deep-sleep-issue-on-galaxy-s6-and-s6-edge)
Method 1 (zip file flasing and Method 2 (terminal).
Both in several combinations with different kernels, alternative ROM, stock ROM,
root only (flashing kernel using Odin without TWRP)
3. trying differenz kernels:
- Hacker Kernel v4, v5
- UniKernel v8
- AELMultiVariant_v2_9_311015
4. trying the kernels without custom recovery, i.e. first flashing stock ROM, then
flashing the kernels directly using Odin.
5. trying the next solution that I have found in the forum:
first stock firmware again, then TWRP, then kernel (for root). Afterwards extracting stock
recovery image from G925FXXU3COI9_G925FDBT3COI6_DBT.zip, flashing this one only.
Running stock recovery, erasing cache, reboot (repeated several times).
Again no deep sleep.
6. first stock firmware again, then flashing TWRP and CarHDRom_V.14_3COJH.
All these tries without XPosed framework, starting from a fresh installed stock system
(i.e. resetting the whole phone to default, then erasing/formatting everything (without
EFS) from TWRP, then flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
Even tried everything without a SIM card.
As soon as I flash something (kernel only, TWRP only, combinations or complete ROM) the
phone never enters deep sleep mode. In "best" case it is working with 200 Mhz only.
Can this be a problem with Samsung's latest boot loader?
Thanks for your assistance!
Problem solved, reason unknown
In the end I have found a working solution.
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
3. flashing TWRP
4. flashing hacker kernel (enabling root)
5. flashing XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S.zip
Deep Sleep is working now, even in combination with XPosed framework and XPrivacy.
As XtreStoLite_ROM_v2.4_Deo-Mod-Edition is based on XXU3COI9 , I assume there could
be a problem with the lasted boot loader from the stock firmware XXU3COI9 that I had installed
previously.
yoda947 said:
In the end I have found a working solution.
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
3. flashing TWRP
4. flashing hacker kernel (enabling root)
5. flashing XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S.zip
Deep Sleep is working now, even in combination with XPosed framework and XPrivacy.
As XtreStoLite_ROM_v2.4_Deo-Mod-Edition is based on XXU3COI9 , I assume there could
be a problem with the lasted boot loader from the stock firmware XXU3COI9 that I had installed
previously.
Click to expand...
Click to collapse
fixed!
[SOLVED]
Recently I've installed Oreo AOSP, I wanted to return flashing from TWRP but stucks on bootanimation, I tried with XGen but the problem persists
Also I tried through flashhtool but the program it doesn't detect my phone, also I tried with Emma, the process was completed correctly but when I boot up the phone the custom ROM is there
Im going to try flashing the Loire kernel through TWRP, at least I want to move to LineageOS
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
n0k0m3 said:
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
Click to expand...
Click to collapse
Already I solved the problem, i flashed the AOSP kernel in Existenz N, then I can boot as usual, however thanks for your answer