Clockwork recovery - Fascinate Q&A, Help & Troubleshooting

Trying to make a nandroid backup using CW 6.0.3.3, however I continue running into an error during the backup of /cache, I wiped cache and dalvik, any suggestions?

is this the recovery that comes with official cm10.1? i know that it has issues (the Warning: No file_contexts thing on startup is an example)
if it is, and you're running cm10.1 (or another 4.2.2 ROM) try this: http://d-h.st/xkk
cm kernel, comes with an older but most likely bug-free version of CWM 6.0.3.0
let me know if this helped

skepticmisfit said:
cm kernel, comes with an older but most likely bug-free version of CWM 6.0.3.0
let me know if this helped
Click to expand...
Click to collapse
Will this kernel also allow me to install cm-11-20131123-UNOFFICIAL-fascinatemtd? I have tried to install but recieved a message stating it will change my /data? I proceeded and it failed.
And won't CM10.1 just overwrite the new kernel every time I flash a nightly?

philosoweed said:
Will this kernel also allow me to install cm-11-20131123-UNOFFICIAL-fascinatemtd? I have tried to install but recieved a message stating it will change my /data? I proceeded and it failed.
And won't CM10.1 just overwrite the new kernel every time I flash a nightly?
Click to expand...
Click to collapse
You should be able to flash cm11, but flash hhp's kernel first, which will replace clockwork with twrp. Follow the guide in the cm11 thread if you're still confused
And yes, but there hasn't been a new nightly in months, so unless you're building your own nightlies, chances are there won't be a new build and you can flash whatever kernel you want and be fine.

Related

Flashing new roms / New recoveries.

Hello,
I am really a beginner with flashing roms and I just flashed my first CWM and CM 10.1 rom.
But the version I chose has a few bugs, so I want to flash a different CM version. should I do it the same way as I changed from the stock ROM to CM 10.1, by moving it to root path and then via recovery choose install zip from sd card? What I also don't know is what will happen with the GAPPS. I flashed it right away the first CM flashing. but will I need to flash GAPPS again?
Also, If I want to change from non-touch CWM to touch-CWM, I do it via Odin in the same way I first flashed the non-touch CWM? Will that over-write the existing CWM?
Sorry I am really a beginner, but at least I flashed the first rom
Thanks to everyone who helps :good:
verynoob said:
Hello,
I am really a beginner with flashing roms and I just flashed my first CWM and CM 10.1 rom.
But the version I chose has a few bugs, so I want to flash a different CM version. should I do it the same way as I changed from the stock ROM to CM 10.1, by moving it to root path and then via recovery choose install zip from sd card? What I also don't know is what will happen with the GAPPS. I flashed it right away the first CM flashing. but will I need to flash GAPPS again?
Also, If I want to change from non-touch CWM to touch-CWM, I do it via Odin in the same way I first flashed the non-touch CWM? Will that over-write the existing CWM?
Sorry I am really a beginner, but at least I flashed the first rom
Thanks to everyone who helps :good:
Click to expand...
Click to collapse
Yes, all you said is the correct way. Its that way itself.
To sum it up, if you want to flash a different CM, reboot into CWM recovery, Wipe Data/Cache/Dalvik cache and flash the zip package and flash the gapps and do a wipe data/cache/dalvik cache again. Yes you need to flash GAPPS each time when you install CM.
For changing recovery, if you have another version installable via Odin, then you can go on with it, and it will replace your existing recovery.
Be sure to check this Table to know which GAPPS should be installed for which CM version.
Happy Flashing!

[Q] CWM versions

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.

[Q] CM 11 EXPERIMENTAL NiGHTLY - Error status 7

------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works

[Q] Need help I777 starting from 4.0.3 moving to 4.4.4 (SOLVED STEPS IN POST)

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..

[SOLVED] Installing a ROM without a recovery change

Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Al-Dazzlez said:
Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Click to expand...
Click to collapse
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
warrior1208 said:
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
Click to expand...
Click to collapse
Well that clears up a lot othings so thanks for the reply

Categories

Resources