GingerDX CWM 4.0.1.5 Update ZIP - XPERIA X8 Themes and Apps

As the thread title already suggests this is ONLY meant for GingerDX (v014+) and will update ClockworkMod Recovery to 4.0.1.5.
I checked this version to:
...create working backups.
...restore the backups correctly.
However, this version does NOT contain SD card partitioning functionality.
Why GingerDX only?
Simple. Doixanh is using a different approach in GingerDX. /system/bin/recovery.tar is just a symlink pointing to /system/bin/cwm-rec.tar. This script replaces /system/bin/cwm-rec.tar, so chances are pretty good that it does NOT work with other ROMs.
NOTE: NOT needed when you run GingerDX on Alfs as the kernel already contains CWM v5 series - this is only for GingerDX on Stock Kernel!
ClockworkMod Recovery 4.0.1.5 Install ZIP
Flash with ClockworkMod, installs the new CWM version
GingerDX ClockworkMod Restore ZIP
Flash with ClockworkMod, restores the default CWM version
Once we got a working CWM 5.x.x.x stand-alone version I'll create a new update ZIP.
Thanks to puppet13th for the CWM 4.0.1.5 tar.

huge thanks
i'll try it soon
so now we can use one recovery instead of two
B.Jay u r the man

semdxd said:
so now we can use one recovery instead of two
Click to expand...
Click to collapse
You seem to misunderstand the meaning of the update:
GingerDX ships with DualRecovery (xRecovery AND CWM) by default. All this update does is to update (ok, actually replace) the cwm-rec.tar (CWM v3.2.0.0r2) which shipped with GingerDX to a newer cwm-rec.tar that's CWM v4.0.1.5.
The DualRecovery will still be there. It's just an update, it doesn't mod the GingerDX defaults.

B.Jay said:
You seem to misunderstand the meaning of the update:
GingerDX ships with DualRecovery (xRecovery AND CWM) by default. All this update does is to update (ok, actually replace) the cwm-rec.tar (CWM v3.2.0.0r2) which shipped with GingerDX to a newer cwm-rec.tar that's CWM v4.0.1.5.
The DualRecovery will still be there. It's just an update, it doesn't mod the GingerDX defaults.
Click to expand...
Click to collapse
yea i know
i meant that we will not need to use Xrecovery for making backups
so we'll use one instead of two
and thanks i'll try it now(free time)

Related

ClockworkMod for Samsung Galaxy 5

ClockworkMod Recovery for Samsung Galaxy 5
Current release - v0.7 - 6 January 2012 [CWM Ver. 5.0.2.7]
What is ClockworkMod Recovery? From AddictiveTips:
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
Click to expand...
Click to collapse
What does it mean for us Galaxy 5 users? Apart from all the goodies like backup, restore and SD card partitioning, the biggest thing is this: Odin is no longer needed to flash new ROMs!
FAQ:
Will this overwrite my current ROM? No, it only replaces the (horrible) Samsung recovery partition. The rest of your system will remain untouched.
Why don't you support dual filesystems in one package? ClockworkMod doesn't support multiple filesystems properly. I can create a version that can read EXT4 and RFS, but it cannot reformat partitions as RFS.
Can I use this to flash regular .tar files in the same way as Odin? No. ClockworkMod uses a completely different (and better) method to update ROMs. The good news, however, is that with a little bit of work, older ROMs can be re-packed in this new .zip update format.
Which ROM packages can be used with ClockworkMod? So far we have my CyanogenMod port and the Motafoca Froyo 2.0.9 ClockworkMod Edition re-release. However, in the future, all ROMS (custom and stock) be made compatible with a little effort.
Installation - Odin Method (tar):
Use this method if you have never flashed ClockworkMod recovery to your phone before.
Download the latest tar release using the link(s) below. Do not extract any files from the .tar file.
Flash the .tar file via Odin using the regular "One Package" procedure. If you need help, consult the relevant wiki page.
Your phone should now automatically reboot into ClockworkMod. Enjoy!
Installation - ClockworkMod method (zip):
Use this method if you already have ClockworkMod installed, and you wish to update the version that already exists on your phone.
Download the latest zip release using the link(s) below.
Transfer the .zip file to your SD card. Do not extract the .zip file - only copy it.
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes. Reboot and enjoy!
Usage:
ClockworkMod Recovery replaces the old "Samsung Recovery Utils for BML" recovery partition, and you can access it in the same ways as before: either via adb reboot recovery, or in the case of CyanogenMod, by choosing Recovery from the Reboot menu.
Once you've entered ClockworkMod Recovery, you will be presented with several options (some familiar, some not). I won't try to explain all of the options, as there are better guides on the internet (example: the AddictiveTips site above). However, these are the ones you should really know about:
Wipe data/factory reset - same as before
Wipe cache partition - same as before
Install zip from sdcard -> choose zip from sdcard - this is the new method you will be using to flash ROMs and update packages
Backup & restore - this menu lets you perform a full backup or restore of your boot, /cache, /data/ & app2sd partition (which is compatible with mad2sd)
Mounts & storage -> mount USB storage - this lets you enable UMS mode to copy update packages (if you forgot to transfer before rebooting into recovery)
Advanced -> partition SD card - this lets you easily partition your SD card for use with mad2sd or any third-party app2sd solutions. It lets you select the size for the EXT4 partition as well as swap. MAKE SURE TO BACKUP ALL DATA ON YOUR CARD BEFORE USING THIS OPTION.
Important Notes:
If you flash any older ROMs (such as stock, Motafoca 2.0.9.x, DashBlack 2.x, or even my CyanogenMod versions before 0.7) that already contain a recovery.img file, ClockworkMod will be overwritten by the older Samsung Recovery. If this happens, you can simply re-flash ClockworkMod via Odin again. Future ROMs (including v0.7) will not overwrite ClockworkMod in this way.
Changelog:
[CWM Ver. 5.0.2.7] v0.7 tar - 6 January 2012
Updated to version 5.0.2.7
Rebuilt using latest source, and verified to work properly.
Advanced Restore function should now work properly.
[CWM Ver. 5.0.2.6] v0.6 tar - 7 November 2011
Updated to version 5.0.2.6
This is the official ClockworkMod build (compatible with ROM Manager) in tar format. If you have an older version installed, you can install this update via ROM Manager directly.
[CWM Ver. 4.0.1.5] v0.5 tar | v0.5 zip - 21 August 2011
Updated to version 4.0.1.5.
Kernel: rebuilt using gcc 4.3.3 (more reliable).
Improved compatibility with RFS. This version can read and backup RFS partitions, but cannot yet restore backups properly. More work is needed upstream for full RFS support.
[CWM Ver. 4.0.1.4] v0.4 tar | v0.4 zip - 26 July 2011
Updated to version 4.0.1.4.
Kernel: reverted to more stable version. Should fix problems with failed backup/installs.
This update is highly recommended if you are using versions v0.2-v0.3.
[CWM Ver. 4.0.1.0] v0.3 tar | v0.3 zip - 19 July 2011
Updated to version 4.0.1.0.
[CWM Ver. 4.0.0.8] v0.2 tar | v0.2 zip - 10 July 2011
Updated source to .8 release.
Replaced CodeAurora kernel with new Samsung Mini/Ace kernel - fixes USB & general stability problems.
Small improvements to flashing code.
[CWM Ver. 4.0.0.5] v0.1 tar - 2 July 2011
First release. Only supports EXT4 for now. Can be flashed to any ROM version, but you can only backup ROMs which use EXT4 (Cyanogen, recent MadTeam releases).
RFS version (for stock ROMs only, don't expect constant updates): v0.4-RFS tar | v0.4-RFS zip
Note: the 0.4 RFS version is not working fully - it cannot reformat partitions from EXT4 to RFS format. If you only use stock roms, this will not be a problem, but if you switch between custom and stock ROMs, it will cause issues. Please wait for the next release for this to be fixed.
Reserved #1
Reserved #2
Thanks, subsyke, it's good for linux users. I flashed CWM and I used Win the last time!
Sent from my Galaxy5 using Tapatalk
Im thinking about putting this on my friends phone. Since my arc/x10 never had a true recovery, Is there a way to get Stock recovery back?
Thanks!
-luke
mrloltime said:
Im thinking about putting this on my friends phone. Since my arc/x10 never had a true recovery, Is there a way to get Stock recovery back?
Thanks!
-luke
Click to expand...
Click to collapse
I guess you can't. But why would you do that after all?
Warranty? Or would it come back as you flash the stock rom?
Sent from my LT15a using XDA App
mrloltime said:
Warranty? Or would it come back as you flash the stock rom?
Sent from my LT15a using XDA App
Click to expand...
Click to collapse
Flashing stock rom will revert it back
What's the purpose of this mod (respect to di coder) if there's nothing stable to flash?!?
mario06 said:
What's the purpose of this mod (respect to di coder) if there's nothing stable to flash?!?
Click to expand...
Click to collapse
To flash something unstable.
mario06 said:
What's the purpose of this mod (respect to di coder) if there's nothing stable to flash?!?
Click to expand...
Click to collapse
It's funny when people say "with all due respect" but don't really mean it.
CyanogenMod is packaged in zip format. I repackaged Motafoca's Froyo 2.0.9 rom recently, and now that we have a separate RFS version of ClockworkMod, it is now possible to repackage stock ROMs in zip format. It's just a matter of somebody spending 10 minutes to go through the process of converting and then uploading.
This is a quick & dirty way to repackage a ROM: http://www.madteam.co/forum/support-7/how-can-i-convert-a-tar-for-odin-to-a-cwm's-zip/
subpsyke said:
ClockworkMod Recovery for Samsung Galaxy 5
Current release - v0.4 - 26 July 2011 [CWM Ver. 4.0.1.4]
What does it mean for us Galaxy 5 users? Apart from all the goodies like backup, restore and SD card partitioning, the biggest thing is this: Odin is no longer needed to flash new ROMs!
Click to expand...
Click to collapse
Hi Subpyske:
I am running the Froyo 2.2 Samsung version in my Galaxy 5. It was downloaded from the XDA only.
I did try to install the CMW using ODIN, it had prompted me to add the Ops File. For which I used the same "EUROPA_v1.0.ops" that I had used for porting Froyo.
I did get a Pass (blue) status in ODIN, I thought I will check if the CMW is installed properly, started my phone in the Safe mode.
But I am still getting the image of Android man working not the CMW screen.
Can you let me know where I have gone wrong?
Please help
xingamazon said:
Hi Subpyske:
I am running the Froyo 2.2 Samsung version in my Galaxy 5. It was downloaded from the XDA only.
I did try to install the CMW using ODIN, it had prompted me to add the Ops File. For which I used the same "EUROPA_v1.0.ops" that I had used for porting Froyo.
I did get a Pass (blue) status in ODIN, I thought I will check if the CMW is installed properly, started my phone in the Safe mode.
But I am still getting the image of Android man working not the CMW screen.
Can you let me know where I have gone wrong?
Please help
Click to expand...
Click to collapse
Wat do u mean by safe mode....????
After flashing fon should boot into recovery....
Do not do data wipe just after flashing....boot the fon normally then boot to recovery then data wipe....either u will stuck in boot loop.
Sent from my Galaxy5 using Tapatalk
cooladityarai said:
Wat do u mean by safe mode....????
After flashing fon should boot into recovery....
Do not do data wipe just after flashing....boot the fon normally then boot to recovery then data wipe....either u will stuck in boot loop.
Sent from my Galaxy5 using Tapatalk
Click to expand...
Click to collapse
Hi Aditya,
I meant when I start the phone with Vol down+center button+Power button I only get the Android man working image (Mentioning downloading).
I assume when I do this I am actually supposed to get the CWM menus.
xingamazon said:
Hi Aditya,
I meant when I start the phone with Vol down+center button+Power button I only get the Android man working image (Mentioning downloading).
I assume when I do this I am actually supposed to get the CWM menus.
Click to expand...
Click to collapse
That is the bootloader not the recovery partition.
Usage:
ClockworkMod Recovery replaces the old "Samsung Recovery Utils for BML" recovery partition, and you can access it in the same ways as before: either via adb reboot recovery, or in the case of CyanogenMod, by choosing Recovery from the Reboot menu.
Click to expand...
Click to collapse
cooladityarai said:
Wat do u mean by safe mode....????
After flashing fon should boot into recovery....
Do not do data wipe just after flashing....boot the fon normally then boot to recovery then data wipe....either u will stuck in boot loop.
Sent from my Galaxy5 using Tapatalk
Click to expand...
Click to collapse
i was flashing my nephew's phone.
i data wiped his phone and i'm stuck in boot loop as you mentioned.
What should i do?
Also, you said i should boot normally and then to recovery...how to boot in recovery?
Should i reboot the system when i get pass screen or i can do before that(i did before the pass screen)?
ROM - I5500LAROJP2.tar (the folder says I5500LUYJP2)
Clockwork - ClockworkMod-Galaxy5-v0.4-RFS
I followed the procedure by using ODIN and the RFS. It booted into Clockwork recovery and then I rebooted the device. How can I check if it's installed?
I seem to have an issue since I did this. I haven't been able to install or update from the Market. It says "Download starting" then "Download paused" then it just stops.
I'm not sure if it's the recovery or not. I didn't do anything else to the phone during this period.
Any help would be great.
Hello, i am wondering if when i reverted my phone back to stock does it get rid of clockworkmod v4?
Please PM me the answer as i wont be checking this thread reguarly, i will greatly appreciate it.
Thanks
Will does this ClockworkMod work on Samsung Galaxy 551?
downloaded rom manager premium.....
opend it... tapped on download roms...
my phone (galaxy 5) isnt listed der... plz help...

How to update CWM v4.0.1.5 on SGS II?

Can anyone give me a link from where I can download the latest version of CWM which can be used for SGS II? Is CWM Manager v3.0.0.5 the latest version?
I have the latest version of ROM Manager Premium, can that help?
EDIT :
I figured I could download the latest version of CWM using my Rom Manager Premium. But I'm still stuck! I figured that I had to "Flash update" using my existing CWM Manager to flash the file update.zip. Ok, done that. But after rebooting when I again open the CWM app it is still showing as version 2.0!!!! What exactly do I have to do with the update.zip file which is there on my sdcard to make me show the CWM Manager v4..0.1.5??? If only Chainfire had bundled the latest version of CWM with his CF Root kernels rather than the ancient version he has! How unthoughtful on his part!
I have been trying to get answers since yesterday and no knowledgeable developer/senior has come forward to give any proper answer. Do all of them go on a holiday on weekends? I am having to figure out everything myself by hit and trial method, using my own common sense and some well intentioned help from junior members! If this is the way this forum is going......then I'm sorry to say that this forum is going down the drain!!
ClockworkMod recovery or the app?
If you want a kernel with CWM (as in samsung land the recovery and the kernel and linked togethet) and everything else stock try cf root, most kernels come with CWM, but not all will work with rom manager.
Sent from my GT-I9100 using XDA Premium App
I already have a CF rooted kernel which came bundled with a CWM Manager v2.0. But that version seems to be a very old one. It is of no use to me in flashing modded files. Now how do I update the CWM installed in my SGS II with the latest version of CWM? I wonder why Chainfire is not putting the latest version of CWM in his root kernels.....have asked him this question on his CF Root thread also. Meanwhile, can anyone here tell me how to upgrade my current CWM Manager v2.0 to the latest version? Surely, a stand alone file of CWM Manager must also be in existence for installation into our phones? Or do we necessarily have to get it bundled in the CF Root kernels only? I am on CF Root KF3
Oh ok, never mind! I found the file with help from another member, Arhtard, on another thread. And I just figured, I can simply upgrade it by using the Rom Manager that I already have.
TheMegastar said:
I already have a CF rooted kernel which came bundled with a CWM Manager v2.0. But that version seems to be a very old one. It is of no use to me in flashing modded files. Now how do I update the CWM installed in my SGS II with the latest version of CWM? I wonder why Chainfire is not putting the latest version of CWM in his root kernels.....have asked him this question on his CF Root thread also. Meanwhile, can anyone here tell me how to upgrade my current CWM Manager v2.0 to the latest version? Surely, a stand alone file of CWM Manager must also be in existence for installation into our phones? Or do we necessarily have to get it bundled in the CF Root kernels only? I am on CF Root KF3
Click to expand...
Click to collapse
CWM manager is an app like rom manager.
Chainfire includes an upto date version of ClockworkMod recovery in the newer versions of cf root.
Using rom manager to just update CWM without updating the kernel won't stick, and the version will go back down on reboot.
Sent from my GT-I9100 using XDA Premium App
veyka said:
CWM manager is an app like rom manager.
Chainfire includes an upto date version of ClockworkMod recovery in the newer versions of cf root.
Using rom manager to just update CWM without updating the kernel won't stick, and the version will go back down on reboot.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
1. KF3 is hardly one month old! And Chainfire's bundling of version 2.0 with that is just not right. He should have bundled the v4.0XX with it. Now because of that ancient version installed on my phone, I can't install any mods that I make in the UOT Kitchen.
2. I have the latest version of ROM Manager Premium. I used it to download the latest version of CWM v4.0.1.5. I have tried to update my existing CWM v2.0 by flashing the update.zip file......but after reboot I again see the version as 2.0 only! So how do I upgrade my CWM to 4.0.1.5??? And you seem to be right in saying, "Using rom manager to just update CWM without updating the kernel won't stick, and the version will go back down on reboot. "...... so does this mean I cannot get the latest version of CWM installed on my phone if I want to remain with KF3 Stock Kernel? So what is the workaround to this problem?
Do I have to flash again with a later CF Root kernel like say for example, CF Root KG3 and then flash the Stock KF3 Kernel back? I want to remain on KF3 stock kernel for a while till I get the official Firmware update in India via Kies.
3. My whole problem began when I downloaded a modded file from UOT Kitchen to change my Boot Screen, Icons, Windows, Battery Icon, Fonts etc. And while rebooting in the recovery mode of my ANCIENT CWM Manager, I get an error due to "signature verification". Now the developer of UOT Kitchen tells me to "disable signature verification" to be able to flash the UOT .zip file. But he does not tell me how to "disable signature verification". He must have assumed that I have the latest CWM installed. So now in order to use the modded file I created on the UOT Kitchen, I need to have the latest version of CWM installed. But you are telling me that I cannot install the latest version of CWM while still on KF3. So I'm back to square one!
4. And has anyone using the SGS II successfully installed the modded boot animations, fonts, icons etc. from files cooked in the UOT Kitchen??? If after wasting so much time & effort in trying to install the latest CWM Manager I find that the SGS II boot animation, fonts, icons cannot be modded, then I'm going to get really mad!
TheMegastar said:
3. My whole problem began when I downloaded a modded file from UOT Kitchen to change my Boot Screen, Icons, Windows, Battery Icon, Fonts etc. And while rebooting in the recovery mode of my ANCIENT CWM Manager, I get an error due to "signature verification". Now the developer of UOT Kitchen tells me to "disable signature verification" to be able to flash the UOT .zip file. But he does not tell me how to "disable signature verification". He must have assumed that I have the latest CWM installed. So now in order to use the modded file I created on the UOT Kitchen, I need to have the latest version of CWM installed. But you are telling me that I cannot install the latest version of CWM while still on KF3. So I'm back to square one!
Click to expand...
Click to collapse
On my phone I have CWM 4.0.0.2 when in the actual recovery mode but the apk version is 2.0
According to the cf-root thread kf3 had cwm4 so have you tried rebooting into recovery then IN IT choose to install the zip and then you should see a option to toggle the signature verification that isn't in the app.
Even after having flashed the update.zip file (v4.0.1.5 downloaded via Rom Manager) through the CWM app, I get only the following options when I go in recovery mode:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
I choose "apply update from sdcard", then I get to choose the file to install from sdcard. I choose the UOT File, and I get these two lines of errors in RED color
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted
Same errors show up if I choose the update.zip file instead of the UOT .zip file.
"According to the cf-root thread kf3 had cwm4 so have you tried rebooting into recovery then IN IT choose to install the zip and then you should see a option to toggle the signature verification that isn't in the app.".............
That is the reason I'm upset with Chainfire....he has written on his thread that it has CWM v4 but you find out later that it's only v2.0. And YES, I tried rebooting into recovery from the option given inside the CWM manager app only. And I DO NOT see any option to toggle the signature verification when in recovery mode, simply because the ANCIENT version of CWM does not have this option!
And as per Veyka, it is not possible to upgrade the CWM manager without upgrading the Kernel also. And he seems to be right. I have the update.zip file on my sdcard but I am still unable to effectively install it so that the upgraded CWM Manager will show as v4.0.1.5. So as per him, if I want the new CWM then I will be forced to flash a newer stock Rom. This is coercion! I do not want to flash any unoffical Roms at this point of time, I want to stay with KF3 till an official firmware update comes from Kies.
Does someone know what to do with my CWM update.zip file so that it gets installed and the CWM Manager stops showing as v2.0?? I guess no one knows. The only way out is if Chainfire makes amends and recreates a CF Root Kernel for KF3 with the latest version of 4.0.1.5
And one more thing I'd like to know, will Kies update firmware after we install the modded UOT zip file?
try "install zip from sdcard" not apply update
shadowofdarkness said:
try "install zip from sdcard" not apply update
Click to expand...
Click to collapse
Where do I get this option "install zip from sdcard"??? I DON'T HAVE THIS OPTION ANYWHERE! There are only TWO options in the CWM Manager that I have, "flash an update.zip" and "install an APK"
That's what the whole problem is : I have an ANCIENT CWM Manager app (thanks to Chainfire) and I CANNOT UPGRADE TO THE LATEST VERSION OF CWM unless I flash a later kernel.
Don't use the manager just reboot into recovery
shadowofdarkness said:
Don't use the manager just reboot into recovery
Click to expand...
Click to collapse
How to "just reboot into recovery"???
All done!
Ok....finally figured it all out on my own, without any/much help coming from the veterans on this board. Managed to install the CWM latest version via Odin. And got my UOT Kitchen mods to work also (well most of them worked like fonts, notification screen, windows animation, icons.....but boot animation did not work. No worries, am happy with the changes I made in the appearance of my phone.....will try some more later. Cheers!
TheMegastar said:
I have been trying to get answers since yesterday and no knowledgeable developer/senior has come forward to give any proper answer. Do all of them go on a holiday on weekends? I am having to figure out everything myself by hit and trial method, using my own common sense and some well intentioned help from junior members! If this is the way this forum is going......then I'm sorry to say that this forum is going down the drain!!
Click to expand...
Click to collapse
Oddly enough, developers have families/outside interests aswell, which means they aren't sat staring at a pc screen just waiting to help you with your problem. That with a bit of reading you could easily solve.
Sent from my GT-I9100 using XDA Premium App
rom manager isn't compatible with cfroot. it's stated in the cfroot thread. also, stop blaming chainfire. afaik, the latest version of the CWM manager (THE APP) is v2.0, that's what you keep seeing. the version of the CWM (THE RECOVERY) he bundles with his kernels is, iirc, v4.0.0.2. all you need to do is read more thoroughly.
fyre31 said:
rom manager isn't compatible with cfroot. it's stated in the cfroot thread. also, stop blaming chainfire. afaik, the latest version of the CWM manager (THE APP) is v2.0, that's what you keep seeing. the version of the CWM (THE RECOVERY) he bundles with his kernels is, iirc, v4.0.0.2. all you need to do is read more thoroughly.
Click to expand...
Click to collapse
Untrue. He did not bundle v4.0.0.2 with KF3. If he had, then I wouldn't have faced so much trouble. He had bundled some ancient version which showed only 4 options, as compared to the current version which has more than double the options. All I needed to do was to disable one option of CWM Recovery, but was unable to do so because that option was NOT THERE in the version CF had bundled with KF3. As a result, I kept wondering what other people were talking about....as I didn't see those options in the version I had.
Having said that, I do appreciate all the good work CF does for getting us new root kernels everytime and have also pressed the THANK YOU button several times on his profile.
@stoney73 : I do understand and appreciate that people have a life other than sitting in front of their comps, but this is a very very large community of people living in different time zones, and at any given time there are like a 100 people logged into the site. And it was probably sheer bad luck that no one knowing about my problem came forward to help for nearly two full days.
Cheers!
Would you mind sharing, TheMegastar how you flashed the latest CWM via Odin? Perhaps you could provide a link, that would help others who would come and read this thread.
Megastar.please share I have the same issue with kf4
Sent from my GT-I9100T using Tapatalk
tonycfc said:
Would you mind sharing, TheMegastar how you flashed the latest CWM via Odin? Perhaps you could provide a link, that would help others who would come and read this thread.
Click to expand...
Click to collapse
You need to have the CWM file in .tar format to be flashed via Odin. I don't have the link, but I'm sure you will find it somewhere in this forum itself. It should be version 4+ to work. Just do a search for this version and then flash it just like flashing any root kernel, putting it in the PDA space.
xd4d3v said:
Megastar.please share I have the same issue with kf4
Sent from my GT-I9100T using Tapatalk
Click to expand...
Click to collapse
Hi, xd4d3v......I hope my reply to Tonycfc also addresses your issue. If your issue is different then please be specific, so I can give a specific reply.

nAa kernel and rom for x10 mini pro

Hey can we put xrecovery in this
THANKS IN ADVANCE
There is something you need to know before you check with xrec.
xrecovery is the basic and old recovery and backup system. now all of the scripts that custom roms use need CWM recovery. because that is easy and all (majority) of the users use that recovery.
Why do you want to go back to xrecovery? you will/sometimes brick your phone if you try to install a custom rom using xrecovery. so it is better that you move to CWM.
That is much better and advanced then xrec.
Tommylee567 said:
There is something you need to know before you check with xrec.
xrecovery is the basic and old recovery and backup system. now all of the scripts that custom roms use need CWM recovery. because that is easy and all (majority) of the users use that recovery.
Why do you want to go back to xrecovery? you will/sometimes brick your phone if you try to install a custom rom using xrecovery. so it is better that you move to CWM.
That is much better and advanced then xrec.
Click to expand...
Click to collapse
still some update zips use old scripting..
how can we install xrecovery and cwn(dual recovery)
and how to boot into xrecovery

ICS LPQ and Clockwork Recovery

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

CWM flashable zip and root fix for some rom ( locked bootloader)

Hi today i bring you fix for root problem on some rom
(1) Download the files from this thread and put them in your phone memory
(2) Flash the rom and uncheck reboot option at the end so the phone does not reboot it stays in recovery flash the files i have provided CWM.zip and superuser3.1.1.zip then reboot your phone you should have CWM and full root now
CWM http://www.mediafire.com/?nm4txl531uqtapy
superuser 3.1.1 http://www.mediafire.com/?22zetxlmoh2hgj2
Don't forget to hit Thanks if this has helped you
Noob question
Sharaz22 said:
Hi today i bring you fix for root problem on some rom
(1) Download the files from this thread and put them in your phone memory
(2) Flash the rom and uncheck reboot option at the end so the phone does not reboot it stays in recovery flash the files i have provided CWM.zip and superuser3.1.1.zip then reboot your phone you should have CWM and full root now
CWM http://www.mediafire.com/?nm4txl531uqtapy
superuser 3.1.1 http://www.mediafire.com/?22zetxlmoh2hgj2
Don't forget to hit Thanks if this has helped you
Click to expand...
Click to collapse
Sorry for this question but I do not have any customization on my XS. I have copied the CWM.ZIP and ROM.ZIP files on SD card. Could you please suggest how can I flash ROM.ZIP as I do not have any custom recovery installed.
p.s. The bootlocker is also locked.
sozofriend1234 said:
Sorry for this question but I do not have any customization on my XS. I have copied the CWM.ZIP and ROM.ZIP files on SD card. Could you please suggest how can I flash ROM.ZIP as I do not have any custom recovery installed.
p.s. The bootlocker is also locked.
Click to expand...
Click to collapse
This is a fix only for who is installing custom ROMs without custom kernel. To install recovery, search for it.
I have had a problem, after flashing Rom, before flashing your zips I wiped cache, and started this problem in recovery:
Can't mount CACHE/recovery/log
then after flashing your zips phone stuck reboting at logo sony, so I have to start from zero, do you know why have that ocurred, is it because wiping cache?
Can i use this method to flash cm10 without custom kernel?
rumkugel13 said:
Can i use this method to flash cm10 without custom kernel?
Click to expand...
Click to collapse
No, CM10 requires the CM10 kernel, no work arounds, sorry.
fareeed said:
No, CM10 requires the CM10 kernel, no work arounds, sorry.
Click to expand...
Click to collapse
for the xperia sspeed rom for example, you can also use the stock kernel, but why can't i use it for cm10?
That's a stock based rom so you can use the stock kernel. Whereas CM10 is AOSP based so many things in the Kernel are different for example Wi-Fi modules as well as other things
Sharaz22 said:
Hi today i bring you fix for root problem on some rom
(1) Download the files from this thread and put them in your phone memory
(2) Flash the rom and uncheck reboot option at the end so the phone does not reboot it stays in recovery flash the files i have provided CWM.zip and superuser3.1.1.zip then reboot your phone you should have CWM and full root now
CWM http://www.mediafire.com/?nm4txl531uqtapy
superuser 3.1.1 http://www.mediafire.com/?22zetxlmoh2hgj2
Don't forget to hit Thanks if this has helped you
Click to expand...
Click to collapse
HaiI am using Miui 2.9.14 rom in my Xperia S, I dont see CWM, I have installed rom manager and searched to install CWM but rom manager says Unsupported device ( LT26i does not have an officially supported CWN yet.)
What should I do to install CWN...?
dhanasekar_83 said:
HaiI am using Miui 2.9.14 rom in my Xperia S, I dont see CWM, I have installed rom manager and searched to install CWM but rom manager says Unsupported device ( LT26i does not have an officially supported CWN yet.)
What should I do to install CWN...?
Click to expand...
Click to collapse
Back to stock, install CWM again, install MIUI and before reboot, install CWM.

Categories

Resources