Related
---US Cellular / CDMA Desire--- not GSM!
I'm officially sick of waiting for USCC's 2.2 update, and I'm going to hope they release a RUU sometime in the future, so I can send in for warranty if I have to.
But I'll take that chance. Getting ready for my jump, so far I understand.
1) unrEVOked is the best way to get custom recovery (CWR), root, and S-OFF.
2) From the CWR, I perform a nandroid backup of my stock USCC rom.
3) From the CWR, I perform a wipe.
4) From the CWR, I apply the Cyanogen .zip
5) From the CWR, I apply the gapps .zip
And then I'll at least have 2.2 and app2sd+
So far so good?
In the future I would like to learn cMTD, and look at Phoenix or FTRapid roms that let me resize partitions for even more space, but one thing at a time.
Bonus question : If I want to modify the Cyanogen .zip file before I apply them, to like remove ADW and add a different launcher, I simply have to change the zip and then re-sign it using the SDK, right?
Really? 50 views and no one can tell me if I'm on the right track or missing something? I don't want to mess this up, and xda I was told is the only place to trust for real good info.
I never rooted a CDMA version Desire, but your steps seems to be OK.
But you forgot something. If you want to use the a2sd+, you must create an ext partition on your SD card.
Modifying the .zip? You can remove the apks by simply deleting from the zip file and copy over the new ones (does not know if you have to modify something else).
Also you don't need to sign it, just click on Toggle signature verification in CWR and you should be fine (at least it's working for me with unsigned .zips)
yes that is pretty much it, just make sure the rom file you downloaded is compatible withcdma desire
And when using cwm there is no need to resign zips, as it should not check the signature by default. Also instead of editing the rom file, you could always just remove the apps afterwards
Yep, looks good, although I would add cmtd and vork kernel.
Edit: Here is a walkthrough for everything. CMTD instructions courtesy of TheUltimateDroid.com
You can download firerat's CMTD files on MIUI: http://miui-dev.com/forums/showthre...ns-for-MIUI-in-4-Simple-Steps!&highlight=cmtd (download the files marked a,b,c,d)
Here is the 11/29 compile of Vork kernel. It's not the newest, but I found it to be the fastest. Courtesy of Navalynt: http://www.4shared.com/file/d8v4Ztz2/vorkKernel_bravoc_1129.html
Boot into recovery (you should already be rooted with clockwordmod recovery and s-off before you get to this point)
PERFORM A NANDROID BACKUP! (Under Backup and Restore select Backup) - you should have done this earlier
Select Install zip from sdcard
Select Choose zip from sdcard and select recovery-v1.5.6-CustomMTD_S.zip
Press the physical back arrow twice to make sure you are at the main menu of the recovery
Select Advanced then Reboot Recovery
Once you are back in recovery you need to select Wipe data/factory reset
Scroll down to Mounts and Storage then select to format /boot and /system
** At this point the recovery has been patched with the cMTD and all of the partitions have been correctly formatted so you can install your ROM
Now go to choose zip from SD card, select the CM version you downloaded and install
after that's complete, select the google addon (gapps) and install
after that's complete, select vork kernel and install
after that's complete, select the boot-v1.5.6-CustomMTD_S.zip and reboot.
You should be up and running after this with about 290mb of internal storage, CM6/2.2 and everything that entails and pulling down around 1900 in quadrant (on a clean install).
Awesome, thanks so much guys! Time to break some warranty~
fyi, you need SetCPU to take full advantage of that overclock kernel.
Akilldema: Thanks for the info on cMTD and the kernel. Seems very straightforward and I think I will try that right away too.
I love it when the thousands of threads and searches come up with 5 different ways to do 1 thing grrr......
Good thing XDA has a forum community willing to help a starter.
Thanks again!
tufkal said:
Akilldema: Thanks for the info on cMTD and the kernel. Seems very straightforward and I think I will try that right away too.
I love it when the thousands of threads and searches come up with 5 different ways to do 1 thing grrr......
Good thing XDA has a forum community willing to help a starter.
Thanks again!
Click to expand...
Click to collapse
If you're planning on doing cmtd, just follow those steps above exactly, it's everything you need to get the rom/kernel/cmtd installed. It's better to do cmtd when you initially flash the rom IMO, I've had trouble applying it later.
Success! Everything suggest here worked great, and everything is fabulous!
One quick followup, I noticed that Cyanogen doesnt actually use APP2SD+, they use their own modified version of the official FroYo APP2SD, which doesnt require a ext partition. (I think? Is that right?)
I have no problem making a ext partition and going the APP2SD+ route, but....how?
Can I do APP2SD+ with Cyanogen? Is the Cyanogen mod w/ the 290mb of space I have gonna be fine?
tufkal said:
Success! Everything suggest here worked great, and everything is fabulous!
One quick followup, I noticed that Cyanogen doesnt actually use APP2SD+, they use their own modified version of the official FroYo APP2SD, which doesnt require a ext partition. (I think? Is that right?)
I have no problem making a ext partition and going the APP2SD+ route, but....how?
Can I do APP2SD+ with Cyanogen? Is the Cyanogen mod w/ the 290mb of space I have gonna be fine?
Click to expand...
Click to collapse
You are right. For me personally, 290mb and the ability to move most of the app to SD is plenty of space. I have a ton of apps (everything I see that I want) and still only have 1 or 2 moved to sd. I never did the official apps2sd, it does cause slightly more strain on the card and I never neeeded it. However, here are instructions on how to do DarkTremor's apps2sd. http://www.theultimatedroid.com/forum/index.php?/topic/333-running-low-on-space/
You have to register there to see it, but link includes all files and instructions on how to do it all. Again, for me, it was unneeded.
I'm currently running DINC2HD, and was wondering how boot manager works exactly. I'm going to be camping on the 10th, and I'm not sure if I'll have a reliable charging source. I was planning on running MIUI while I was gone. I don't wanna have to restore a backup and take the extra time for that. Can someone please tell me exactly how boot manager works??
Sent from my DINC2HD
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
digitalsynner85 said:
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
Click to expand...
Click to collapse
I usually do too, but like I said, I'm gonna be camping, and I'm not sure when/where I'll be able to charge, so I was gonna use a ROM I KNOW has amazing battery life.
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
tylerlawhon said:
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
Click to expand...
Click to collapse
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, etc. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flashable backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
ChrisDDD said:
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, etc. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flashable backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
tylerlawhon said:
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
Click to expand...
Click to collapse
I think it's recommended that you wipe all three images when you initially install a rom, but that's the 3 images Boot Manger creates. I was just making the point that you don't need to wipe anything on your phone's currently installed rom.
But yea, after that, Miui should install and run just fine. You will need to install GApps to get the market on MIUI, since Boot Manager needs to install itself on each new rom you instal. This is so you can manage and reboot to other roms from roms installed through it. After that, you should be able to reboot back and forth at will.
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
tylerlawhon said:
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
Click to expand...
Click to collapse
Sorry, I was thinking about CM7, which doesn't include with the market app.
I've always installed as Ext2... never had much luck with 4.
I tried Boot manager while running CM7 and I was able to install it but got a force close when I open the app, I also try it with MIK's Inc2 HD 3D rom and didn't work either.
I tried searching didnt get specific answer I am needing. I have been flashing roms for about 1 year. Its possible I have been messing it up, although my phone has always worked correctly (CM of different flavors). I usually use the following:
hboot/recovery
wipe dav/factory reset/wipe battery stats
install rom
now I am trying very hard not to make things more difficult for another user. I am trying to flash a sense rom Stock Plus v2.1.
In the install instructions it states:
Full Wipe and Flash Instructions:
Make a Nandroid Backup of your current rom
Reboot into ClockworkMod
Choose "wipe data/factory reset"
Go into "mounts and storage" menu and choose "format /boot" and confirm
Choose "format /system" and confirm
Go back to main menu and choose "install zip from sdcard"
Browse your sdcard for the rom zip and flash!
**Note: I know there are a million methods that folks say to follow for a full wipe, including: wiping dalvik, wiping cache, etc. Let me explain why that's unnecessary. The "wipe data/factory reset" option erases your /data, /cache and /data/data partitions, so doing the "wipe cache" option would be redundant. Dalvik-cache is just a folder that resides on the /data partition (Already cleared, remember, so redundant again). The ONLY 2 partitions, that effect the wipe, and were not already cleared are /boot and /system. I've changed roms quite a bit and this method is fast and works everytime.
I read the note but am confused. I have not heard of the things in red above. Could someone explain what I have been doing wrong, or why that would need to be done for rom to function properly? Thanks
Aerysana said:
I tried searching didnt get specific answer I am needing. I have been flashing roms for about 1 year. Its possible I have been messing it up, although my phone has always worked correctly (CM of different flavors). I usually use the following:
hboot/recovery
wipe dav/factory reset/wipe battery stats
install rom
now I am trying very hard not to make things more difficult for another user. I am trying to flash a sense rom Stock Plus v2.1.
In the install instructions it states:
Full Wipe and Flash Instructions:
Make a Nandroid Backup of your current rom
Reboot into ClockworkMod
Choose "wipe data/factory reset"
Go into "mounts and storage" menu and choose "format /boot" and confirm
Choose "format /system" and confirm
Go back to main menu and choose "install zip from sdcard"
Browse your sdcard for the rom zip and flash!
**Note: I know there are a million methods that folks say to follow for a full wipe, including: wiping dalvik, wiping cache, etc. Let me explain why that's unnecessary. The "wipe data/factory reset" option erases your /data, /cache and /data/data partitions, so doing the "wipe cache" option would be redundant. Dalvik-cache is just a folder that resides on the /data partition (Already cleared, remember, so redundant again). The ONLY 2 partitions, that effect the wipe, and were not already cleared are /boot and /system. I've changed roms quite a bit and this method is fast and works everytime.
I read the note but am confused. I have not heard of the things in red above. Could someone explain what I have been doing wrong, or why that would need to be done for rom to function properly? Thanks
Click to expand...
Click to collapse
Assuming you are talking about formatting system and boot? If so, cm is different than sense roms, and this data needs to be wiped. The fact that you have been using cm for so long, explains why you haven't had issues with your wipe method. The data has just been overwriting itself, which doesn't work when going from aosp to sense, or vice versa.
Sent from my ADR6300 using xda premium
actually I have 2 different phones. both are htc inc orig, 2 different users. my personal phone has cm. I do not format boot or system and never have. however, when reading about flashing stock plus v2.1 on the other dinc that is freshly rooted with nothing ever having been flashed, it said to do what was highlighted in red (format boot and system). I had never heard of that.
okay, so format boot and system are needed if you are going from asop to sense (did not know that guess I got lucky). So is it still necessary to format boot and system before flashing on a dinc that was just rooted last night and nothing has been done other than rooting? stock is sense, the rom i would like to flash to the newly rooted phone is sense, so it is or is not needed?
I guess it comes down to what is exactly being wiped/formatted in the following:
data wipe/factory reset
format boot
format system
Yeah I guess thats what im trying to ask. Maybe if I understand what those areas are, then I can better understand why they would need to be wiped/formatted.
Oh and thank you for your reply, I do appreciate the help, and maybe im a bit slow in my thinking today. So please bear with me.
The boot and system files/data take on different characteristics and can be stored differently, depending on the base of the Rom. Base being froyo, gingerbread, Dinc2, Evo, aosp, etc. Things are stored in different places, which means new roms need these areas cleared before flashing in order to work properly.
Edit: Most of these roms have been ported from other devices. If flash instructions are provided, it is best to follow them for best results.
Sent from my ADR6300 using xda premium
okay i think i understand. will do it. thanks for taking the time to help. sometimes it takes me a few to get it sorted out.
What Is ClockworkMod Recovery And How To Use It On Android [Tutorial]
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. In what follows, we will cover all that this recovery is capable of doing, and how to do it. We do not discuss Touch recovery (and you shouldn’t use it on the ET4G) or Rogue recovery here. Those are different tuts…
All About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.
Introduction to ClockworkMod
ClockworkMod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices. It is the needed recovery for AOKP, AOSP, CM7 and 9. ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager.
Booting into ClockworkMod
On most Android devices including ones by Samsung, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device (volume up for our phones). This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery.
Tour
1. reboot system now
This one is self-explanatory.
2. apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses. This is what we are talking about:
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
1. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
2. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card.
3. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
4. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (we don’t), it’s best not to change this option.
5. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
1. Backup
Takes a Nandroid backup, as explained above.
2. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
3. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
1. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
2. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
3. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations.
1. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
2. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
3. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
5. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
6. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
7. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Using ClockworkMod for ROM, kernel, apps, theme or mod installation
While in the complete feature tour we have already shown you how to install a ROM, kernel, app, theme or any similar mod from a recovery-flashable zip file using the recovery options, those of you who jumped straight to this section expecting to get just this information quickly are at the right place!
This guide is primary focused on a full feature tour of ClockworkMod recovery but in our previously written guide on how to flash a ROM or app from a zip to an Android device file from recovery, we have already covered in detail how to use ClockworkMod for installing any ROM, kernel, app, theme or mod using a recovery-flashable zip file. While that guide is based on an older version of ClockworkMod recovery, everything in it still applies to the latest versions and should work flawlessly.
How To Install A ROM Or App From Zip File To Android Device From Recovery
Please note that the terms ‘installing’ and ‘flashing’ can be used interchangeably here and will mean the same thing.
Disclaimer: Although I have done my best to make the following procedure as safe as possible, you should still follow this guide at your own risk.
Rooting your device renders its warranty void.
ALWAYS take backups before rooting or flashing a custom ROM or app to your phone.
Flashing a defective ROM or app to your phone might brick it so choose the ROMs and software that you flash wisely and never install a ROM or application from an untrusted source.
AddictiveTips will not be liable if your device gets damaged or bricked during the process.
Official ROM updates from device manufacturers or carriers are released in conveniently packaged installation files that you can run on your computer while your Android device is connected to it, and they automatically take care of updating your phone’s system. Similarly, most applications are available directly in the Android Market for easy installation, or come packaged as convenient ‘.apk’ files that you can just run on your Android phone to install. The case is not the same with most custom ROMs and several custom applications, which come in .zip files rather than PC installers or .apk files.
The idea of installing a customized operating system to their smartphone can be quite intimidating for inexperienced users. Though once they get used to it, some of them end up trying out different ROMs for their devices several times a day. While I don’t exactly recommend that you flash every new ROM that is made available for your Android phone, we are here to help you get over the fear of flashing a ROM that enhances the capabilities of your device so that you can use it to its fullest potential.
Here is a quick look at what we will be covering in this guide. Feel free to skip to the real deal if you already meet the prerequisites.
• Before We Begin: Battery Check
• Before We Begin: Unlocking the Bootloader (Stock Android Devices Only)
• Before We Begin: Rooting
• Before We Proceed: Installing a Custom Recovery
• The Real Deal: Installing a Custom ROM to your Phone
• The Real Deal: Installing an App From a Zip File to your Phone
There are certain steps that you might not require, and we shall be mentioning them in each section.
Before We Begin: Battery Check
Before you proceed with any of the following steps, make sure your phone’s battery level is not too low. It is recommended to have it at 50% or more. Do NOT take this lightly. If your phone’s battery runs out while you are attempting to flash a custom ROM, there is a significant chance of your phone getting bricked and becoming unusable PERMANENTLY.
Before We Begin:Unlocking the Bootloader (Stock Android Devices Only)
Note: This step applies only to Android devices with stock version of Android installed. At the moment, Google Nexus One and Nexus S are the only two such devices available. You may skip this step if you are using any other Android device.
Users of stock Android devices such as the Google Nexus One or Nexus S also need to unlock its bootloader before they can proceed. Once you have done this, you may proceed to the next step.
Before We Begin: Rooting
Note: You may skip this step if your device is already rooted, or if you already know how to root it.
Before you can install a custom ROM to your device, your phone needs to be rooted. Rooting is basically administrator or root level access required to perform administrative tasks on your Android device. Once you are done with the rooting process, you may proceed to the next step.
Before We Proceed: Installing A Custom Recovery
Note: You may skip this step if you already have a custom recovery installed on your device.
Rooting grants you the necessary access level to execute administrative tasks on your Android device but it is the recovery that provides the tools necessary to actually perform those tasks. While every Android device ships with a recovery, the stock recovery is quite limited in what it lets you do, and you need a custom recovery image to perform advanced operations on your device. Once you have a custom recovery installed on your phone, you will be ready to proceed to the next step.
The Real Deal: Installing a Custom ROM to your Phone
Now that you have a custom recovery installed on your phone, you can perform all sorts of wonderful advanced operations on your device and this includes the ability to flash a ROM or application from a zip file. The procedure is pretty standard for most ROMs, though there are certain ROMs which require additional steps for their installation. Since those steps differ from ROM to ROM, pay attention to instructions and this includes only the standard instructions here.
• Manually
1. Download the ROM from the link given in the article featuring that ROM. It should be a zip file.
2. Connect your phone to your computer via USB and mount its storage card.
3. Copy the downloaded ROM to the root of the storage card.
4. Power your phone off and reboot it into recovery. This will involve using a combination of your device’s hardware keys. Once in recovery, you can navigate its menu using the volume up and volume down hardware keys or your phone’s trackball / optical track pad if it comes equipped with one.
5. Use the ‘backup and restore’ feature of recovery to backup your existing ROM installation, software and data. This step is known as performing a nandroid backup. ALWAYS perform a backup before flashing a custom ROM, UNLESS you can afford to lose everything that’s on your phone at the moment.
Note: ALWAYS choose to perform the following steps 6, 7 and 8 UNLESS the ROM you are attempting to flash is an updated version of the same ROM that you are currently using, and is compatible with the current installation’s data. It is usually mentioned with the update whether you can install it over a previous version without wiping its data or not.
6. Get back to the main recovery menu and use the option ‘wipe data/factory reset’. You will be prompted to confirm this action. Select “Yes – Delete all user data”.
7. From the main recovery menu, select ‘wipe cache partition’. You will be prompted to confirm this action. Select ‘Yes – Wipe Cache’.
8. From the main recovery menu, enter the ‘advanced’ menu. From this menu, select ‘Wipe Dalvik Cache’. You will be prompted to confirm this action. Select ‘Yes – Format/System’.
9. From the main recovery menu, enter the ‘Mounts and Storage’ menu. From this menu, select ‘Format/System’. You will be prompted to confirm this action. Select ‘Yes – Wipe Dalvik Cache’.
10. Go back to the main recovery menu by pressing the back button and select the ‘Install zip from SD card’ option.
11. Select ‘choose zip from sdcard’ to get a list of the files and folders on your SD card. Scroll to the ROM’s file that you copied there in step 3, and select it. You will be prompted to confirm this action. Select ‘Yes – Install file_name.zip’ where file_name.zip is the name of the zip file that you are trying to install.
12. Wait patiently while the ROM is flashed to your phone via recovery.
13. Once the installation is complete, head back to the main recovery menu if you aren’t there, and select ‘reboot system now’. Your phone will now boot into the newly installed ROM.
The Real Deal: Installing an App From a Zip File to your Phone
While most apps for Android devices are available at the app store for direct download and installation or as .apk files for direct installation, there are certain apps which are only available as zip files installable from recovery. Their installation procedure is the same as installing a custom ROM that we just featured above. However, there are a few minute differences.
• When installing an app from a zip file, you do NOT need to perform the ‘wipe data/factory reset’ or ‘wipe/system’ step so NEVER do that unless you know what you are doing, have a complete backup and want to start using your ROM as a fresh installation with the new app added.
• You might or might not need to wipe the cache and the dalvik cache for installing apps from zip file. This varies from app to app and the developers of such apps as well as many reviewers including us mention when featuring an app whether it requires a cache and dalvik cache wipe or not. However, it never hurts to wipe these caches anyway, and it does not effect the data on your device or its storage card.
There you go, this concludes the guide on how to flash a ROM or app from a zip file to your Android device using a custom recovery. To try out the skills that you just learned, search our site for custom ROMs for your phone and start flashing, always remembering to take backups first!
Edit- for Nandroid Backup Tut go HERE
By Haroon Q. Raja found (original link HERE), with additions and corrections by VeNuM
Very nice tutorial/guide!
EDIT : First!
Wow this will really help me when i decide to root
Sent from my SPH-D710 using Tapatalk
fghjfhjfghjfghjfgjh
10 char
Nice tutorial bro.
Great Guide!!! Wished we had this kind of guide on the fascinate when I started : )
Sent from my SPH-D710 using Tapatalk
jUgGsY said:
Very nice tutorial/guide!
EDIT : First!
Click to expand...
Click to collapse
Thank you
Me likes it, tank u berry mush
iSaint said:
Wow this will really help me when i decide to root
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Thank You
iSaint said:
Wow this will really help me when i decide to root
Click to expand...
Click to collapse
LOL!
10char
iSaint said:
Wow this will really help me when i decide to root
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Who are you rooting for?... Lol.
Thank you Venum for your time putting this together. Hopefully it will answer allot of questions before they are asked in dev thread. I'm sure it will be very helpful to allot of people.
Sent from my SPH-D710 using xda premium
blackcanopy said:
Who are you rooting for?... Lol.
Thank you Venum for your time putting this together. Hopefully it will answer allot of questions before they are asked in dev thread. I'm sure it will be very helpful to allot of people.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
myself I'm to scared not very edumacated with all this phone stuff
Sent from my SPH-D710 using Tapatalk
iSaint said:
myself I'm to scared not very edumacated with all this phone stuff
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
This coming from someone with over 800 thanks. Lol
Thank you for this!
iSaint said:
Wow this will really help me when i decide to root
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hahahahhaha I was thinking something like that lol
First time user here I wanted to say thank you for this, I found it very easy to read and understand, perfect for helping get threw my first root, recovery, and rom
Could someone please direct me to the version of CWM that is safest for our phones?
Thanks
NM: read the thread again and found it.
Nice Guide.
thanks great guide on installing CWM! will come in handy not just for this device but others
Thanks
Thanks for guide. Defiantly the best CWM guide out there....
Good morning. I registered in this forum some months back (don't remember when) when I was searching for some good ROMs for my GIO S5660.
I ultimately gave up because I couldn't find enough information about flashing (I think it was because the threads gave bad links to odin, or I could only find that specific odin version if I googled because the link's version were outdated/updated). Either way I gave up because smartphones and flashing were (and are) very new to me and I didn't want to risk bricking the phone (although I'm finishing my degree in Computer Science, so some concepts aren't alien to me).
I came back now, decided to find a STABLE and GOOD ROM, with the best battery life I can get. I usually check the screenshots thread and choose the ones that I like the most, normally CM9 or better. Problem is, I spent these past few hours on several of GIO sub-forums (http://forum.xda-developers.com/forumdisplay.php?f=1404), searching and scavenging for something I could use or like. It's been very hard, almost all of them have some kind of major problem, like in-call microphone, wireless, deep sleep, something like that.
Am I chasing wild gooses here? Should I be looking instead at CM7 and earlier versions?
On a closing note, I still have 2.3.3 Portuguese version that came with the phone. Can I update safely through the phone's preferences? Main reason I am looking to flash is because of its battery life: if i charge it to 100%, then proceed to use any kind of program/game with the lowest light settings, it can drop to 50% in a matter of minutes. Its speed isn't that great as well.
Thank you for your time, would be great if anyone could help me.
Flame86 said:
Good morning. I registered in this forum some months back (don't remember when) when I was searching for some good ROMs for my GIO S5660.
I ultimately gave up because I couldn't find enough information about flashing (I think it was because the threads gave bad links to odin, or I could only find that specific odin version if I googled because the link's version were outdated/updated). Either way I gave up because smartphones and flashing were (and are) very new to me and I didn't want to risk bricking the phone (although I'm finishing my degree in Computer Science, so some concepts aren't alien to me).
I came back now, decided to find a STABLE and GOOD ROM, with the best battery life I can get. I usually check the screenshots thread and choose the ones that I like the most, normally CM9 or better. Problem is, I spent these past few hours on several of GIO sub-forums (http://forum.xda-developers.com/forumdisplay.php?f=1404), searching and scavenging for something I could use or like. It's been very hard, almost all of them have some kind of major problem, like in-call microphone, wireless, deep sleep, something like that.
Am I chasing wild gooses here? Should I be looking instead at CM7 and earlier versions?
On a closing note, I still have 2.3.3 Portuguese version that came with the phone. Can I update safely through the phone's preferences? Main reason I am looking to flash is because of its battery life: if i charge it to 100%, then proceed to use any kind of program/game with the lowest light settings, it can drop to 50% in a matter of minutes. Its speed isn't that great as well.
Thank you for your time, would be great if anyone could help me.
Click to expand...
Click to collapse
Buy a new battery and try AOSP GINGERBREAD 2.3.7 :highfive:
Flame86 said:
Good morning. I registered in this forum some months back (don't remember when) when I was searching for some good ROMs for my GIO S5660.
I ultimately gave up because I couldn't find enough information about flashing (I think it was because the threads gave bad links to odin, or I could only find that specific odin version if I googled because the link's version were outdated/updated). Either way I gave up because smartphones and flashing were (and are) very new to me and I didn't want to risk bricking the phone (although I'm finishing my degree in Computer Science, so some concepts aren't alien to me).
I came back now, decided to find a STABLE and GOOD ROM, with the best battery life I can get. I usually check the screenshots thread and choose the ones that I like the most, normally CM9 or better. Problem is, I spent these past few hours on several of GIO sub-forums (http://forum.xda-developers.com/forumdisplay.php?f=1404), searching and scavenging for something I could use or like. It's been very hard, almost all of them have some kind of major problem, like in-call microphone, wireless, deep sleep, something like that.
Am I chasing wild gooses here? Should I be looking instead at CM7 and earlier versions?
On a closing note, I still have 2.3.3 Portuguese version that came with the phone. Can I update safely through the phone's preferences? Main reason I am looking to flash is because of its battery life: if i charge it to 100%, then proceed to use any kind of program/game with the lowest light settings, it can drop to 50% in a matter of minutes. Its speed isn't that great as well.
Thank you for your time, would be great if anyone could help me.
Click to expand...
Click to collapse
The most stable rom currently for our gio is the Enhanced236. I really recommend you reading as much as you can before doing anything, both about android and flashing, but also basic XDA stuff. Read these "threads", and you're good to go! 1. 2. 3. 4. 5. 6.
Phuuu.. All done? Let's flash that ROM! Wohoooooo.. :victory:
Wait! You need a backup before continuing. :good: Since you doesn't have root or custom recovery, you can't use CWM to make a nandroid. One way to backup your stuff is to use a program called Ultimate Backup Tool. This program doesn't need root or custom recovery. It works on Windows, Mac and Linux. :highfive:
Now we can flash the custom rom! :laugh:
If you wanna install Enhanced236 (the most bugfree one), you need to install install cwm, Clock Work Mod, first. How to:
1. Make sure that you have fully charged your battery.
2. You need to download the ext4only 5.0.2.7 cwm version, here http://forum.xda-developers.com/showthread.php?t=1421650.
3. After you have downloaded the zip, you go into recovery mode, in this case stock recovering. You do that by holding The Home Button + Power Button until the recovery gets visible.
4. Then you do click on the Apply update from sdcard, and select the cwm zip.
5. After you have flashed the zip, you should reboot your device. Here's a YouTube video on the installation process: www.youtube.com/watch?v=hxjxB8P9rSU
6. After you have done that, I recommend you to take a nandroid backup. The backup will be stored on your sdcard, so you can copy the backup to your computer if you want to, just in case.
Now you have installed CWM. Let's install the ROM!
7. Download the enhanced236 from this thread. Copy the zip to the root of your sd-card, and then go into CWM. Wipe data/factory reset. After that, wipe the cache partition. NOTE! This will erase everything you have done on your phone, so make sure that you have a backup ready! After that, click on the install zip from sd-card, choose the enhanced236_06.08.2012.zip and flash it. Just follow the instructions that pops up, and then restart your phone. Leave it booting/waiting for like 5 min, and then start touching/configure the device. After doing the necessary configuring, wait another minute. And reboot. And then it's done! :victory:
And if you have any questions, just ask! I'm glad to help! :laugh:
Regards,
X-Zone
Thank you guys! At the moment I can't, but later at home I will pay closer attention to X-zone's post (I'm @ work).
From what I've read, I'll need the USB cable, or some kind of microSD USB drive, right? I actually rooted the phone almost a year ago, since I found very good info in its thread
@PanDeGengibre
Do I really need a new battery? ;n;
Flame86 said:
Thank you guys! At the moment I can't, but later at home I will pay closer attention to X-zone's post (I'm @ work).
From what I've read, I'll need the USB cable, or some kind of microSD USB drive, right? I actually rooted the phone almost a year ago, since I found very good info in its thread
@PanDeGengibre
Do I really need a new battery? ;n;
Click to expand...
Click to collapse
I think yeah your battery drains very fast!
Flame86 said:
Thank you guys! At the moment I can't, but later at home I will pay closer attention to X-zone's post (I'm @ work).
From what I've read, I'll need the USB cable, or some kind of microSD USB drive, right? I actually rooted the phone almost a year ago, since I found very good info in its thread
@PanDeGengibre
Do I really need a new battery? ;n;
Click to expand...
Click to collapse
You need a usb cable to transfer the roms and that kind of stuff. You can also use a micro SD reader if you want.
BTW I don't think you need to buy a new battery, you must calibrate it once a month or so. Calibrate it and see if that works!
Sent from my GT-S5660
X-zone said:
The most stable rom currently for our gio is the Enhanced236. I really recommend you reading as much as you can before doing anything, both about android and flashing, but also basic XDA stuff. Read these "threads", and you're good to go! 1. 2. 3. 4. 5. 6.
Phuuu.. All done? Let's flash that ROM! Wohoooooo.. :victory:
Wait! You need a backup before continuing. :good: Since you doesn't have root or custom recovery, you can't use CWM to make a nandroid. One way to backup your stuff is to use a program called Ultimate Backup Tool. This program doesn't need root or custom recovery. It works on Windows, Mac and Linux. :highfive:
Now we can flash the custom rom! :laugh:
If you wanna install Enhanced236 (the most bugfree one), you need to install install cwm, Clock Work Mod, first. How to:
1. Make sure that you have fully charged your battery.
2. You need to download the ext4only 5.0.2.0 cwm version, here http://forum.xda-developers.com/showthread.php?t=1421650.
3. After you have downloaded the zip, you go into recovery mode, in this case stock recovering. You do that by holding The Home Button + Power Button until the recovery gets visible.
4. Then you do click on the Apply update from sdcard, and select the cwm zip.
5. After you have flashed the zip, you should reboot your device. Here's a YouTube video on the installation process: www.youtube.com/watch?v=hxjxB8P9rSU
6. After you have done that, I recommend you to take a nandroid backup. The backup will be stored on your sdcard, so you can copy the backup to your computer if you want to, just in case.
Now you have installed CWM. Let's install the ROM!
7. Download the enhanced236 from this thread. Copy the zip to the root of your sd-card, and then go into CWM. Wipe data/factory reset. After that, wipe the cache partition. NOTE! This will erase everything you have done on your phone, so make sure that you have a backup ready! After that, click on the install zip from sd-card, choose the enhanced236_06.08.2012.zip and flash it. Just follow the instructions that pops up, and then restart your phone. Leave it booting/waiting for like 5 min, and then start touching/configure the device. After doing the necessary configuring, wait another minute. And reboot. And then it's done! :victory:
And if you have any questions, just ask! I'm glad to help! :laugh:
Regards,
X-Zone
Click to expand...
Click to collapse
Great tutorial,
Followed but flashed 5.0.2.7 (didn't find 5.0.2.0), and now the recovery seems to be only partially working.
I can boot to it, but if I press "flash zip" it only appears the cwm logo, any idea?
skinniezinho said:
Great tutorial,
Followed but flashed 5.0.2.7 (didn't find 5.0.2.0), and now the recovery seems to be only partially working.
I can boot to it, but if I press "flash zip" it only appears the cwm logo, any idea?
Click to expand...
Click to collapse
Tap the menu button on gio
skinniezinho said:
Great tutorial,
Followed but flashed 5.0.2.7 (didn't find 5.0.2.0), and now the recovery seems to be only partially working.
I can boot to it, but if I press "flash zip" it only appears the cwm logo, any idea?
Click to expand...
Click to collapse
Sorry, typo. Meant 5.0.2.7. Fixed that now. When you click on something in cwm, like flash a zip, press the home button. Navigate up and down with the volume buttons.
Finally have the time to check it out.
X-zone said:
Wait! You need a backup before continuing. :good: Since you doesn't have root or custom recovery, you can't use CWM to make a nandroid. One way to backup your stuff is to use a program called Ultimate Backup Tool. This program doesn't need root or custom recovery. It works on Windows, Mac and Linux. :highfive:
Regards,
X-Zone
Click to expand...
Click to collapse
I have it rooted, but I don't have my USB cable, just a microSD adapter. Any other way to do the backup? maybe some application in Play Store that backups into the sdCard?
Flame86 said:
Finally have the time to check it out.
I have it rooted, but I don't have my USB cable, just a microSD adapter. Any other way to do the backup? maybe some application in Play Store that backups into the sdCard?
Click to expand...
Click to collapse
Titanium backup is a very powerful program on the google play store. The pro version (I recommend you buying it, it's worth it) backup things like your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card.
After you have installed CWM you can do a nandroid on your untouched system. You can always restore the nandroid if you don't like your new costum rom or if the installation crashes and "lite" bricks your phone.
X-zone said:
Titanium backup is a very powerful program on the google play store. The pro version (I recommend you buying it, it's worth it) backup things like your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card.
After you have installed CWM you can do a nandroid on your untouched system. You can always restore the nandroid if you don't like your new costum rom or if the installation crashes and "lite" bricks your phone.
Click to expand...
Click to collapse
Let me see if I understood:
1) Backup
This can be made before everything else, through Titanium backup (backs up my data into the sd card (probably in just one file that can be read after)), Ultimate Backup Tool (is installed in the computer, needs USB cable) or other similar programs
OR
Can also be made after CWM is installed, through something called "nandroid" <-(I read the pages you linked in this thread and didn't notice this name/concept, so I was confused)
2) Download ext4only 5.0.2.7 Clock Work Mod that is on page 1
3) Reach recovery mode, select apply update from sdcard, select the cwm.zip. This is "flashing" the phone
This here is where it started to get confusing to me; until I read several times your post, I thought that "apply update from sdcard" would actively install that zip, erasing everything else. What must happen instead is that, that zip installs the app inside, that will allow me to backup and format next.
4) Restart phone, run cwm.
This is where I can make the nandroid backup (as said previously, this got me confused because I thought that at this point the phone was already "empty", formatted)
5) Download the ROM I need/want/wtv, go to CWM then:
a) Wipe data/factory reset.
b) Wipe the cache partition. (note: this is the actual format)
c) Install zip from sd-card, choosing the ROM. (This is also flashing)
*easy part:*
6) Follow the instructions on screen and then restart phone
7) Wait some time for the boot then configure it. After that, wait a minute more then restart again. DONE!
Did I miss anything? If not and this is it, where is the risk in softbricking or hardbricking the phone? (yes, I'm actually scared, since this is my first time and I'm a noob at it, and I can't really risk screwing my smartphone, only in three months will I be able to replace it if anything happens)
Thank you for helping a (scared) noob!
Flame86 said:
Let me see if I understood:
1) Backup
This can be made before everything else, through Titanium backup (backs up my data into the sd card (probably in just one file that can be read after)), Ultimate Backup Tool (is installed in the computer, needs USB cable) or other similar programs
OR
Can also be made after CWM is installed, through something called "nandroid" <-(I read the pages you linked in this thread and didn't notice this name/concept, so I was confused)
2) Download ext4only 5.0.2.7 Clock Work Mod that is on page 1
3) Reach recovery mode, select apply update from sdcard, select the cwm.zip. This is "flashing" the phone
This here is where it started to get confusing to me; until I read several times your post, I thought that "apply update from sdcard" would actively install that zip, erasing everything else. What must happen instead is that, that zip installs the app inside, that will allow me to backup and format next.
4) Restart phone, run cwm.
This is where I can make the nandroid backup (as said previously, this got me confused because I thought that at this point the phone was already "empty", formatted)
5) Download the ROM I need/want/wtv, go to CWM then:
a) Wipe data/factory reset.
b) Wipe the cache partition. (note: this is the actual format)
c) Install zip from sd-card, choosing the ROM. (This is also flashing)
*easy part:*
6) Follow the instructions on screen and then restart phone
7) Wait some time for the boot then configure it. After that, wait a minute more then restart again. DONE!
Did I miss anything? If not and this is it, where is the risk in softbricking or hardbricking the phone? (yes, I'm actually scared, since this is my first time and I'm a noob at it, and I can't really risk screwing my smartphone, only in three months will I be able to replace it if anything happens)
Thank you for helping a (scared) noob!
Click to expand...
Click to collapse
When you install CWM your phone will not be completely wiped. Only the recovery "partition" will be replaced with CWM instead of the almost useless stock recovery. Here's some info about nandroid. 1.. The Ultimate Backup Tool/Titanium backup was just if the cwm installation goes wrong and and "soft" bricks your phone. This will most likely not happen. Note that there is several methods to unbrick the gio if this happens, so be calm! lol
X-zone said:
When you install CWM your phone will not be completely wiped. Only the recovery "partition" will be replaced with CWM instead of the almost useless stock recovery. Here's some info about nandroid. 1.. The Ultimate Backup Tool/Titanium backup was just if the cwm installation goes wrong and and "soft" bricks your phone. This will most likely not happen. Note that there is several methods to unbrick the gio if this happens, so be calm! lol
Click to expand...
Click to collapse
Yeah, hehe.
About titanium backup, how does it work exactly? Does it need a working ROM (preferably the same type as the backup was made on) so it can restore what was previously backed up? Or is like nandroid, it can be restored via CWM?
I read your link about nandroid; it seems pretty easy to grasp: recovery mode and restore backup. What about Titanium backup? It seems to me it is unable to backup the entire phone (it would also make sense since it runs on Android)
I've read about Titanium backup here: http://www.addictivetips.com/mobile/how-to-use-titanium-backup-for-android-complete-guide/
Flame86 said:
Yeah, hehe.
About titanium backup, it is the same as nandroid?
I read the link and it turns out I understand very well the concept; my question here, is then, what is the difference between the two? How can I use Titanium backup in case something goes wrong?
Nandroid seems pretty easy to grasp: recovery mode and restore backup. What about Titanium backup? It seems to me it is unable to backup the entire phone (it would also make sense since it runs on Android)
I've read about Titanium backup here: http://www.addictivetips.com/mobile/how-to-use-titanium-backup-for-android-complete-guide/
Click to expand...
Click to collapse
Titanium backup only backups your user-data, which means that it doesn't backup your kernel, libs and stuff like that. If something happens while you install cwm (you accidentally drops your phone and the battery flies away and soft bricks your phone) you still have your contacts, levels cleard on angrybrids and stuff like that.
CWM nandroid it is then
So, while trying to make a nandroid, CWM "backup" option gives this error:
SD Card space free: 1707 MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Can't mount /system!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is this normal? :|
Erase cache partition? Or unselect cache in advanced?
Flame86 said:
So, while trying to make a nandroid, CWM "backup" option gives this error:
SD Card space free: 1707 MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Can't mount /system!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is this normal? :|
Erase cache partition? Or unselect cache in advanced?
Click to expand...
Click to collapse
Ohh... Sorry. You have installed the ext4only version. The stock rom uses rfs. Try install CWM signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip and then do a bakcup and then install ext4only, the costum rom uses ext4. And no, ext4 + rfs doesn't work that good with ext4.
X-zone said:
Ohh... Sorry. You have installed the ext4only version. The stock rom uses rfs. Try install CWM signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip and then do a bakcup and then install ext4only, the costum rom uses ext4. And no, ext4 + rfs doesn't work that good with ext4.
Click to expand...
Click to collapse
So... when I'm at the cwm ext4only recovery mode and select apply update from the sdcard, it shows me a buttload of "no" options and only one "Yes - Install /sdcard/update.zip."
Like this
confirm install?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes - Install /sdcard/update.zip.
No
No
No
What the hell do I do?
Flame86 said:
So... when I'm at the cwm ext4only recovery mode and select apply update from the sdcard, it shows me a buttload of "no" options and only one "Yes - Install /sdcard/update.zip."
Like this
confirm install?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes - Install /sdcard/update.zip.
No
No
No
What the hell do I do?
Click to expand...
Click to collapse
Navigate with your volume buttons down to Yes - Install Bla bla and press the home button to confirm.