Anyone having problems with CWM Recovery on the latest ICS LPQ release using cf-root? If I boot into recovery and select backup/restore it says no files found. Opening CWM from inside the phone and selecting a rom to restore works but deleting does not work I hit confirm and its still there.
Maybe re-flash the CH-Root Kernel, see if that fixes it.
Might be a different CWM version to the one you backed up with .
jje
I've reflashed a couple times with the original and cf-root also using wanams deodexed rom and I've made a backup with the new version of CWM and it doesn't see that one as well from recovery. No one has the same problem?
tazer4 said:
Anyone having problems with CWM Recovery on the latest ICS LPQ release using cf-root? If I boot into recovery and select backup/restore it says no files found. Opening CWM from inside the phone and selecting a rom to restore works but deleting does not work I hit confirm and its still there.
Click to expand...
Click to collapse
proper fixed cf-root released
Related
Hi All,
Eventough I bought my SGS2 about a year ago, I decided to root it recently. I read various threads on this forum, and then decided to root my phone using CF_Root. Since my Kernel was XXKL1, I downloaded the appropriate file and used odin to flash PDA. Everything worked and I was able to successfully root my phone and install root apps like Titanium Backup Pro.
Now, I wanted to install CM7 on my phone, as it is know to be very stable and doesn't have random reboots. However, after I flashed the .zip file using manual Clockworkmod recovery , the phone refused to boot and went into a bootloop. Upon research, I found that CF-Root Kernal will only be able to install the firmwars which are in Samsung format (factoryfs.img, zImage etc) and the CM7 is not in that format.
I now decided to flash a kernel with standard ClockworkMod and downloaded it from Koush's site. After flashing this (Odin, PDA), the phone got stuck in Bootscreen, with the yellow triangle.
So, as of now, I can only use CF-Root Kernel (stock Kernel works too). Is there any way I can install stock CWM on my phone and be able to install CM7?
PS: I also tried flashing back stock rom, install clockworkmod using the wiki at CM7 SGS2 page. The Phone again went into a bootloop. So basically I am not able to install any kernel which has clockworkmod built into it
jithinsarath said:
Hi All,
any way I can install stock CWM on my phone and be able to install CM7?
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery no cwm then .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Click to expand...
Click to collapse
Thanks JJEgan for the reply...
Well, I guess my original post was long, but unclear.
1. My phone is working perfectly.
2. I am able to root using Chainfire's method.
3. I am able to remove the yellow triangle by flashing the stock kernel via odin and then reflashing chainfire's zImage via CWM
4. When I install CM7 via clockwork recovery, the phone bootloops. Even flashing the CF-Root kernel doesn't help. Only option is to restore from backup.
5. When I try to install any kernel with Koush's clockworkmod recovery, the phone restartes after flashing and gets stuck at the yellow triangle screen.
6. I am able to flash odia's insecure kernel without any issues.
I am looking for solutions for points 4 & 5, so that I can install CM7.
JJEgan said:
jithinsarath said:
Hi All,
any way I can install stock CWM on my phone and be able to install CM7?
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery no cwm then .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Logic says read the CM7 thread ask in the thread
http://forum.xda-developers.com/showpost.php?p=21462574&postcount=141
Not a rom i use so no further idea .
jje
jithinsarath said:
Thanks JJEgan for the reply...
Well, I guess my original post was long, but unclear.
1. My phone is working perfectly.
2. I am able to root using Chainfire's method.
3. I am able to remove the yellow triangle by flashing the stock kernel via odin and then reflashing chainfire's zImage via CWM
4. When I install CM7 via clockwork recovery, the phone bootloops. Even flashing the CF-Root kernel doesn't help. Only option is to restore from backup.
5. When I try to install any kernel with Koush's clockworkmod recovery, the phone restartes after flashing and gets stuck at the yellow triangle screen.
6. I am able to flash odia's insecure kernel without any issues.
I am looking for solutions for points 4 & 5, so that I can install CM7.
Hi mate, I've never tried cm7 nor cf-root kernel on my galaxy s2 but once i got into boot loop so i searched in xda forum and i found the answer.now I drive stock rom + siyah kernel which also provide CWM 5 for you.
I think befor doing anything first flash your drive with stock kernel which also removes yellow triangle then do you should be out of boot loops. if didn't work flash the whole stock kernel then go on with flashing cm7.
I guess then you could flash siyah kernel next flash cm7 using CWM. The benefit if using siyah kernel is that it's compatible with either stock or cm7 firmware.
Click to expand...
Click to collapse
@JJEgan: I made sure I read all the posts in the CM7 thread before putting up a thread myself. No clues there. My problem is that I am unable to get the custom recovery working via clockworkmod recovery... and then flash CM7
I also tried doing it the CM7 way, as described in their wiki but faced the same problem..
@mekhonte: Thanks for the suggestion on siyah kernel. I will try that. What about battery life on it?
I know how to come out of the bootloop, and have successfully done that. But, I am still unable to go into CM7.
I had cm7 installed via cf-root. Maybe you didn't wipe data, cache and dalvik csche?
Sent from my GT-I9100 using XDA App
I tried siyah kernel on cm7 and it didn't work, probably because it us not for cm7. Just flash KL1 then related cfroot, then download an install cm7:
1. In cwm clean data, cache and dalvik cache
2. Install cm7 zip TWICE (that is important)
3. Install gaps
4. Clean caches and data one more time
5. Reboot
And don't mess with the kernel. Cm7 comes with its own kernel which is optimised.
Sent from my GT-I9100 using XDA App
golcheck said:
I tried siyah kernel on cm7 and it didn't work, probably because it us not for cm7. Just flash KL1 then related cfroot, then download an install cm7:
1. In cwm clean data, cache and dalvik cache
2. Install cm7 zip TWICE (that is important)
3. Install gaps
4. Clean caches and data one more time
5. Reboot
And don't mess with the kernel. Cm7 comes with its own kernel which is optimised.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
well, I tried all of the above (including twice flashing cm7) except installing GAPPS. Will try that and report back.
jithinsarath said:
@JJEgan: I made sure I read all the posts in the CM7 thread before putting up a thread myself. No clues there. My problem is that I am unable to get the custom recovery working via clockworkmod recovery... and then flash CM7
I also tried doing it the CM7 way, as described in their wiki but faced the same problem..
@mekhonte: Thanks for the suggestion on siyah kernel. I will try that. What about battery life on it?
I know how to come out of the bootloop, and have successfully done that. But, I am still unable to go into CM7.
Click to expand...
Click to collapse
this is the link of the siyah kernel thread http://forum.xda-developers.com/showthread.php?t=1263838
the developer claims the the kernel is as stable as stock kernel which i believe as long as you do not mess around with CPU frequencies and governors or under volting, it is. i think it has improved my battery life some how, auto brightness script has been modified and also you can down-clock your CPU. I think it's worthy to give it a shot.
---------- Post added at 04:27 PM ---------- Previous post was at 04:21 PM ----------
golcheck said:
I tried siyah kernel on cm7 and it didn't work, probably because it us not for cm7. Just flash KL1 then related cfroot, then download an install cm7:
1. In cwm clean data, cache and dalvik cache
2. Install cm7 zip TWICE (that is important)
3. Install gaps
4. Clean caches and data one more time
5. Reboot
And don't mess with the kernel. Cm7 comes with its own kernel which is optimised.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Q: Does this kernel support CM7 or any other AOSP based roms?
A: Yes, but it only support cm7 or miui based roms for now. If you are using another aosp based Rom tell me and I will support it.
original post : http://forum.xda-developers.com/showthread.php?t=1263838
post#2
Originally Posted by jithinsarath
@JJEgan: I made sure I read all the posts in the CM7 thread before putting up a thread myself. No clues there. My problem is that I am unable to get the custom recovery working via clockworkmod recovery... and then flash CM7
I also tried doing it the CM7 way, as described in their wiki but faced the same problem..
My suggestion is as always one you have a broken phone or two you are doing something wrong hence read the guides and double check .
It worked for me last week .
jje
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Originally Posted by jithinsarath
@JJEgan: I made sure I read all the posts in the CM7 thread before putting up a thread myself. No clues there. My problem is that I am unable to get the custom recovery working via clockworkmod recovery... and then flash CM7
I also tried doing it the CM7 way, as described in their wiki but faced the same problem..
My suggestion is as always one you have a broken phone or two you are doing something wrong hence read the guides and double check .
Install worked for me last week .
jje
Are you able to get into clockworkmod recovery?
Sent from my GT-I9100 using XDA App
Ok here we go followed my instructions then flashed stock rom and rooted cwm .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
This is meant to clear all user multiple errors and start from a clean phone .
Then to CM7 instructions .
http://forum.xda-developers.com/showthread.php?t=1297557
First time flashing CyanogenMod 7 to the Samsung Galaxy S II, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
have to flash the rom twice in a row to get it booting...is plastered all over the CM7 thread so i did .
Going by your post in CM7 thread you do not have CWM custom recovery installed
CWM and root same as my fix post .
I flashed I9100XXLP2 ROM from this tread: http://forum.xda-developers.com/showthread.php?t=1420996 ,
After that i flashed Chainfire's CF-Root XXLP2 (Rooted Kernel) from the same tread.
After testing i decide to go back to my previously created CWM backup...
Restoring backup results in boot loop.... TO fix this i need to flash kernel again trough odin.. Tried multiple times....
Why does my old backups not working any more? What has changed?
mad_max911 said:
I flashed I9100XXLP2 ROM from this tread: http://forum.xda-developers.com/showthread.php?t=1420996 ,
After that i flashed Chainfire's CF-Root XXLP2 (Rooted Kernel) from the same tread.
After testing i decide to go back to my previously created CWM backup...
Restoring backup results in boot loop.... TO fix this i need to flash kernel again trough odin.. Tried multiple times....
Why does my old backups not working any more? What has changed?
Click to expand...
Click to collapse
CWM version has changed in the CF-root kernal. Many times the backup done with old CWM is not properly recoverable.
Try wiping the data/cache and dalvik cache and recovering nandroid backup.IF this doesnt work , then Best option would be to get your nandroid backup to PC , format the system , flash a stock ROM,root it and try getting to get the backup working again.
Hope this helps!
I think ICS has a different bootloader to that of GB? If so, flash original bootloader from Intratech thread post #2 with Odin in PDA or Bootloader section:
http://forum.xda-developers.com/showthread.php?t=1075278
Then try restore nan-droid backup again.
Maybe I'm wrong, but you won't hurt anything if you follow his Odin flashing instructions.
Sent from my GT-I9100 using xda premium
Interesting... Ill try some off suggestions later. Just to clarify little more: after boot loop i flash kernel trough ODIN, (syah kernel [same kernel that is in recovery]) and everything works (i boot into previously recover system and all fine...), then going into recovery once again after restoring problem occurs again. So problem is not in CWM as kernel itself contains it...
So, maybe better question would be what part of android system does CWM NOT backup... For example, i now that it does not backup camera firmware... What else? It would be great if this backup/recovery would be more complete (including all software/flash/drivers parts of android system...).
Best regards!
Its simple you require the version of clockwork mode recovery on your phone that you used for the backup to recover .
Caught me out last week and took an age to realize the solution .
jje
Yes, backup was created witth syah 2.6.6 and its CWM version... So, i flashed that kernel trough ODIN, booted CWM and recover- stuck at boot once again...
Sent from my GT-I9100 using XDA App
Hi. I'm running CyanogenMod on my Samsung Galaxy S II i777 (the AT&T one). I was running UnNamed ROM on it, and that had ClockworkMod Recovery v5.0.2.7. But after I flashed CyanogenMod, the ClockworkMod Recovery downgraded to v5.0.2.3. How can I update back to the 5.0.2.7 version?
The reason I ask is because in v5.0.2.3, the backup options are limited, and it doesn't allow me to restore my old, v5.0.27 Nandroid backups in case I need to. I've done a Google search and searched the XDA forums, and the only help I found was to use the ROM Manager app. However, in this post, user creepyncrawly advises me not to use ROM Manager because it "has problems on this phone." I also found some custom kernels, but those were for different phone models.
So how can I update ClockworkMod Recovery without losing any data?
You need to install a kernel that has the newer CWM.
Your post doesn't make sense unless you installed a VERY old CM7 release, considering that the CWM 5.0.2.7 binary in my kernels was pulled FROM CyanogenMod.
I made a mistake. I meant to say that I have CWM Recovery 5.0.2.6, not 5.0.2.7. But my problem is still the same: in CWM Recovery, I don't have the option to "Advanced Restore from SD card." Even when I move my old Nandroid backups (created under CWM Recovery 5.0.2.7) to my phone, they're still not picked up by CWM Recovery 5.0.2.6.
Anyway, thanks for letting me know how to update. Any zImage from any custom ROM will work, right? I'm just trying to do this without incrementing the flash counter on my phone. So I need to choose one from this subforum, and flash with Mobile Odin?
Completely_Clueless said:
I made a mistake. I meant to say that I have CWM Recovery 5.0.2.6, not 5.0.2.7. But my problem is still the same: in CWM Recovery, I don't have the option to "Advanced Restore from SD card." Even when I move my old Nandroid backups (created under CWM Recovery 5.0.2.7) to my phone, they're still not picked up by CWM Recovery 5.0.2.6.
Anyway, thanks for letting me know how to update. Any zImage from any custom ROM will work, right? I'm just trying to do this without incrementing the flash counter on my phone. So I need to choose one from this subforum, and flash with Mobile Odin?
Click to expand...
Click to collapse
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Solved!
jcracken said:
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Click to expand...
Click to collapse
This worked beautifully! I now have CWM Recovery 5.0.2.7, and my phone info shows that I have SiyahKernel as well.
Thank you very much!
jcracken said:
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Click to expand...
Click to collapse
It doesn't support CM7, but should be able to restore a CM7 Nandroid.
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Nyssa1104 said:
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
Thanks for your reply.
I only use mobile odin to flash official firmware so its a fresh start before installing a rom.
I've tried to restore from philz before but had the same problem. Normally use Dorimanx.
I myself had no probles with Mobile odin pro of CWM in Philz kernals and since Philz kernal this tends to be the normal backup or flashing aid for me. Since I have a Micro SD card install back up and roms are place on this..
by the way Im using SuperSUPro and not Superuser for root.
symondo12 said:
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Click to expand...
Click to collapse
I have a possible solution just flash entire original rom(the one you are going to restore) once, then restore your nandroid backup, clear cache/dalvik, reboot. I have a hunch on the problem that it might be caused by another roms /preload partition data (our nandroid backup won't usually backup it by default so it actually never gets wiped or overwritten)
Edit :I forgot to mention a factory reset at the beginning.
Sent from my GT-I9100 using xda app-developers app
I am aware that this has been asked before but there are conflicting answers withing the threads that I have read.
I am running 4.1.2 WLSW having worked my way through the various jb releases over time. Root has been retained using everroot in mobile odin. The kernel is stock.
Having decided to install a stable release of cyanogenmod (10.1.3) I have been reading around for days to avoid pitfalls or to know what to do should a problem arise.
The only one thing that I am still unsure about is whether it is indeed safe to use a temporary cwm (flashed via stock recovery) to install cyanogenmod. I have downloaded the latest temporary cwn from the rommanager site and it appears to work just fine - I have created a backup without issues so I can get back to where I am now if I don't like or have problems with cyanogenmod.
I was planning to flash [KERNEL] ClockworkMod Recovery 6.0.2.9 from this thread http://forum.xda-developers.com/showthread.php?t=1118693 - but in the last couple of pages in the thread there are users that have had boot failures after flashing it. This is what has lead me to ask the question is it safe to use the temporary cwm?
I am aware that there are other kernels that I could use (Philz/Siyah) but would like to know which cwm is safest/best for the installation of cyanogenmod.
Install philz kernel by flashing in stock recovery and put that zip on ext sd. Stay away from rom manager. Dont use it. When you have philz installed make a nandroid bkup and make sure preload is included too. Also bk up you're efs folder with ktool free from playstore. As you have root get that and bk efs up asap. once you have done a nandroid bkup and done the efs bkup then flash cm. May be good to get a copy of you're modem now too.
andrewwright said:
Install philz kernel by flashing in stock recovery and put that zip on ext sd. Stay away from rom manager. Dont use it. When you have philz installed make a nandroid bkup and make sure preload is included too. Also bk up you're efs folder with ktool free from playstore. As you have root get that and bk efs up asap. once you have done a nandroid bkup and done the efs bkup then flash cm. May be good to get a copy of you're modem now too.
Click to expand...
Click to collapse
I have backed up efs already using ktool and have already made a nandroid backup using temporary cwm - good advice none the less.
I have read that rommanager is problematic with the i9100 so am not planning to use it.
My method of choice to flash Philz would be mobile odin (unless there is some disadvantage by doing it this way?).
Regarding my modem, it is included in the stock firmware so I could flash just the modem from this using mobile odin if I have trouble (I have assumed mobile odin works in cm).
My original question remains however - why not use temporary cwm?
Mobile odin will work on cm. And yes you can flash with temp cwm. Get you're modem from here on xda. Makes no odds how you flash philz Use odin or recovery its up to you.
andrewwright said:
Mobile odin will work on cm. And yes you can flash with temp cwm. Get you're modem from here on xda. Makes no odds how you flash philz Use odin or recovery its up to you.
Click to expand...
Click to collapse
If I can flash with temp cwm, there is no need to flash philz at all - or have I missed something?
If you flash with temp there's no guarantee. Philz then flash is a safer way of doing things.
andrewwright said:
If you flash with temp there's no guarantee. Philz then flash is a safer way of doing things.
Click to expand...
Click to collapse
Presumably the latest Siyah kernel will also do?
Yes that's ok
It's simply a matter of preference.....temporary CWM is as it 'says on the tin'........temporary....
You have to reflash it every time you want to use it.
PhilZ is permanent....once it's flashed, it's there, no further action needed, plus it has a touch interface unlike regular CWM......
If you intend to stay with stock, but want to have the advantages of CWM, then I'd advise go with PhilZ...purely because a few steps less are necessary to be able to use it.......
(Enter stock recovery, flash CWM then use CWM to flash whatever..... every time with temporary CWM)
If you intend to flash a custom ROM, it'll come with its own permanent CWM anyway (which will overwrite the PhilZ kernel and/or remove the need to continuously reflash the temporary CWM)
Sent from my GT-I9100 using xda app-developers app
Thanks for the advice folks. I flashed Siyah then installed cm 10.1.3 and the associated gapps. All went without a hitch. I was actually surprised how quickly the process completed. I had the rotating cm boot image less than 2 minutes after starting the install from first zip.
Off topic, but I am totally impressed with the cm ROM. I find my frustration at constantly waiting for phone manufacturers to catch up with vanilla android releases has completely melted away.
Glad it's sorted :thumbup:
Add solved to name of thread pls