I downloaded Rom Manager from the market and through that program, I flashed the latest CWM recovery image (3.1.0.0), I rebooted into recovery to check the work and sure enough it was the right recovery....I then found out that Franco had released a new kernel so before I even flashed it, I backed up the phone, than I flashed the franco kernel, that being v18.1 cfs, since I do not have 2.3 I didnt use v18.1 bfs...Its now stuck at the LG screen is franco's kernel's compatible with Clockworkmod recovery ?
Root: Gingerbreak 1.2
Rom: Devoid Froyo Final
Recovery: CWM 3.1.0.0
P.S.- Ive also attempted at flashing franco kernel v17 since I know that was the kernel I was using before I attempted to flash the new kernel
Im not to sure if it's a partial brick or my phone's completely ****ed
I would like to go back to using AmonRA's recovery image considering Ive always used AmonRa....the only reason I even attempted anything with CWM is because I heard it provided more options in recovery
What should I do ?
francos kernel is compatible...its something messed up with the phone....install the backup you had earlier...before flashing a new kernel you have to wipe everything...that may be the cause of error..
If you can boot into recovery then your phone is recoverable. Restore your backup and try again, this time by wiping cache (not everything). And you can easily switch between recoveries, click the ciaox's flashable recoveries link in my signature.
Sent from my LG-P500 using XDA App
Related
Ok, so long story short - I went through a lot of steps to restore my fascinate to stock, and then rooted it through recovery. It worked fine until I installed Rom Manager and now my phone won't boot into recovery again. My question is - did I do something wrong?
I restored my phone to stock using Heimdall
Updated it to the latest version
Rooted it using odin and flashing recovery
then installed Rom Manager
Thank you for all your help guys!!!
kuczynt said:
Ok, so long story short - I went through a lot of steps to restore my fascinate to stock, and then rooted it through recovery. It worked fine until I installed Rom Manager and now my phone won't boot into recovery again. My question is - did I do something wrong?
I restored my phone to stock using Heimdall
Updated it to the latest version
Rooted it using odin and flashing recovery
then installed Rom Manager
Thank you for all your help guys!!!
Click to expand...
Click to collapse
download odin (onto pc), a non stock kernel and the recovery.zip that you want to use.(both recovery.zip and non stock kernel on your sd card)
Put your phone in dl mode and flash recovery via odin...when odin is done, immediately three finger boot into recovery and flash non stock kernel, and reboot.
Unless your on cm7 rom manager is useless and will bring more hurt then help, and your recovery is being overwritten by the stock kernel every time you boot which is why you need the non stock kernel...I personally would recommend a rom that contains a kernel...you can find a list of all roms, kernels, and recoveries in the dev section stickies.
Do you know how to properly flash roms, and kernels? I ask because I don't want to get you stuck even worse...if you need step by step instructions I'll reply later when I'm at a pc
Sent from my SCH-I500 using XDA App
You can give me a few tips and hints. That would be appreciated. Also, I thought the easiest way was through Rom Manager.
On a side note - what would be the most stable ROM to flash to the fascinate?
EDIT: Ok, so I installed PowerWashed 1.2 ROM and can handle this on my own a little bit. I'm still a little unsure on which roms are most stable/trustworthy, but I might stick with this one for a while.
Hi all,
I rooted my SGS2 (KE7) with CF-Root ages ago and haven't done much since then, aside from take regular backups.
Looking at the Cyanogenmod stuff, I fancy giving it a go. All the guides talk about using the kernel at http://forum.xda-developers.com/showthread.php?t=1118693 .
Does anyone know if I can flash the cyanogenmod ROM using the recovery mode I have with CF-Root, or if I need to get use the kernel from the above patch first?
This morning I tried installing the kernel (from the CF-Root CWM), when my phone rebooted, the touchscreen worked on the unlock page but not once I unlocked (I use LauncherPro as my launcher). Rebooting into recovery mode didn't work (the phone just booted normally) so I reflashed CF-Root but still had the same problem however I could boot into recovery mode and restore this morning's backup.
Now, the phone boots (with the warning triangle, expected) but there is no response after I unlock for a minute or so. Setting the stock launcher back works but I'm confused about why this should happen and what I should do next.
Does anyone know why my non-stock launcher is now being non-responsive for the first minute after boot / what I can do to get it back?
Am I able to install cyanogen with CF-root, or do I need to use the kernel in the above link? and if so, do I need to do anything other than just flash and if not why didn't the phone boot into recovery when I tried it earlier?
Any suggestions gratefully received!
-Jeff
The cf-root kernel is all you need to install cm7.
peachpuff said:
The cf-root kernel is all you need to install cm7.
Click to expand...
Click to collapse
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Electroz said:
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Click to expand...
Click to collapse
Don't quite understand this. I've got the cm_galaxys2_full-39.zip (100MB), I was going to put this on the SD card, boot into recovery mode and install from there. Are you saying I need to do this same process twice? (and if so, why does it only install the kernel the first time when it is the complete zip file?)
Cheers,
-Jeff
CF-root => Cyanogen mod
Hello everybody,
There are a few threads that discuss this question, but they all draw a different conclusion.
This one for instance : http://forum.xda-developers.com/showthread.php?t=1367933 (or if the link is broken, search for : How can i use cf-root kernel for cm7?).
In the thread above they claim that CF-root is not compatible with CM7, however in this very thread there is said that when installing the .zip file twice, it should work just fine. As i'd like to install CM7 on my CF-rooted S2, i have to know for sure:
Is there a way to install CM7 on a CF-rooted device?
Many thanks
Rom manager doesnt work with cf root, so to flash cm7 download the zip, boot into recovery, and flash the zip twice, and it will work.
Make sure you wipe data and cache, and take backups before you do.
Sent from my GT-I9100 using Tapatalk
Ok, i'll give it a go .
Thanks for the quick response, it is much appreciated!
so, I've had my SG2 for like a month now, rooted and all, but the problem is , i can't flash any other ROMs(but stock ROMs) or kernels (except for CF root,stock and siyah kernels ) on it via CMW... each time i tried to flash anything, i end up stuck at "galaxy s2 GT-I9100" boot-up logo.... I've tried flashing CM7 then i got the boot-loop ( even with double flash, or triple didn't work for me) and i can't get into CWM when i got the boot-loop....
someone please help me.. i read alotta threads and none of them got similar issue like mine...
i guess its true what they say : every galaxy s2 is different from the rest.
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
InFa_ReD_1 said:
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
Click to expand...
Click to collapse
If you already have root then you won't loose it.
geko95gek said:
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
Click to expand...
Click to collapse
I used to use VR 3.0 but could only work with stock kernel or cf root kernel has never booted with the ROM's kernel..
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
My phone came with CM7, but i flashed it with rooted stock coz i wanted to have a feel of it... but now i'm done with it but i can't get any roms to work... so frustrating.
i literally have tried flashing ALL Roms (ligtnung, gingerbread,vr, cm7), during the 1st few days that i got my phone it worked with VR 2.5 and 3.0, even MIUI.. but after i flashed with some Asian stock ROM via odin... nothing would work through cmw anymore...
i seriously don't know what i did wrong...
btw, right now im using basebad ver: I9100XXXKI4, kernel: 2.6.35.7-siyah [email protected]#20, build number GINGERBREAD.ZSKI3.
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuse to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
tomascunill said:
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
Click to expand...
Click to collapse
well, i'm gonna try that and see if it works, am also goin' try to see if downgrading to 2.3.4 or something would work too...
but please if you got any more ideas, just keep it coming..
thanks
Phew! NOW I HAVE CM7 RUNNING ON MY PHONE!!
I'm gonna try to explain how i fixed my issue, as clear and explanatory as i can..
lucky i didn't brick my phone during all this, because I tried so many things and none worked.I unsuccessfully tried downgrading to XWkI4, ZCKI4, and alot others via Odin... after flashing all i get is tons of error messages(on 3e recorvery) E: can't open/cache or E:failed blah bla bla to load /efs... i thought OMG! my phone is bricked! then i recalled reading somewhere that flashing the 3 tar (PDA,MODEM,CSC) files usually should work(maybe better than flashing a 1 tar file), so i found a 3 files xxKI3 rom, flashed it and BAM! it booted up this time without any error. so now i went ahead and rooted it since the tar files came unrooted, then went into CWM to flash cm7 ROM, flashed it twice and ofc i got stuck on boot logo.....i didn't panic much, i pulled out the battery, and restarted to CWM where i cleared cache/ dalvik/ and did wipe/factory reset, then i reflashed CM7 again (twice) and it worked!!!! YES, CM7 is fiannly working on my SG2!
thanks for everyone for helping, and i hope this can help others on the same boat as me..
Currently I have jellybeer with cyanogen mod 10.1 on it with s-on.
This rom http://forum.xda-developers.com/showthread.php?t=2315077 and I downloaded the kernel which is on the 2nd page as instructed.
I can flash roms no problem however when I attempt to flash a kernel via clockwork recovery it NEVER works. It says its replacing the boot image, install went great, no signs of trouble. However when I reboot the phone and check the kernel version its always default kernel and it never updates, in this case "3.4.10.cm-gc3a49c6 any incite on this would be great
eurofraid said:
Currently I have jellybeer with cyanogen mod 10.1 on it with s-on.
This rom http://forum.xda-developers.com/showthread.php?t=2315077 and I downloaded the kernel which is on the 2nd page as instructed.
I can flash roms no problem however when I attempt to flash a kernel via clockwork recovery it NEVER works. It says its replacing the boot image, install went great, no signs of trouble. However when I reboot the phone and check the kernel version its always default kernel and it never updates, in this case "3.4.10.cm-gc3a49c6 any incite on this would be great
Click to expand...
Click to collapse
S-on can't flash boot via recovery. There's an awesome app for this, flash GUI, or you can s-off and flash in recovery with the Roms. You can also fastboot flash it and move the modules over yourself.
Sent from my AT300 using Tapatalk 2
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..