Titanium Backup Create Flashable Zip of Apps! - Verizon Samsung Galaxy S III

This changes everything! All in all should cut 30 mins. off of ROM Flashing!
What if you could cut that time by a solid 20 or 30 minutes? Thanks to a new feature just incorporated in Titanium Backup, you can. With the newest update to TB Pro, you can now create a flashable zip of all your apps and data. That means that you can flash all your goodies right after a new ROM and fire up a system that's ready to go right out of the box.
http://www.androidpolice.com/2012/11/06/new-in-titanium-backup-create-flashable-zips-of-all-your-apps-and-data/
It'll be interesting how the "data" part works out on new or re-based ROMS though.

I saw this today and got super excited. Hope it works good and is bug free.

Cool! I remember when CWM was supposed to add a feature to create a zip of the Rom you were running but that never came out.

MMag05 said:
I saw this today and got super excited. Hope it works good and is bug free.
Click to expand...
Click to collapse
Just tried it, it makes the update.zip file in the root of the SD0 card, even if you have backups to save to SD1 (external SD card)

sanjsrik said:
Just tried it, it makes the update.zip file in the root of the SD0 card, even if you have backups to save to SD1 (external SD card)
Click to expand...
Click to collapse
Yep. I haven't tried restoring via CWM yet though.

Samsung.Galaxy.S3 said:
Yep. I haven't tried restoring via CWM yet though.
Click to expand...
Click to collapse
I was going to try it since I just downloaded the latest nightly for CM10. I've noticed <off topic> that if I do a dirty upgrade (wiping just dalvik and cache), that my phone answers calls in speakerphone mode</off topic>
---------- Post added at 12:43 PM ---------- Previous post was at 11:56 AM ----------
sanjsrik said:
I was going to try it since I just downloaded the latest nightly for CM10. I've noticed <off topic> that if I do a dirty upgrade (wiping just dalvik and cache), that my phone answers calls in speakerphone mode</off topic>
Click to expand...
Click to collapse
tried the update.zip as the last file to flash after updating on a complete wipe to the latest CM nightly (11/07/2012), flashed GAPPS, then tried to flash update.zip. It "looked" it was flashing, went through about 5 of the 54 applications and then rebooted into CM with none of the applications installed.
Only saving grace was I had the foresight to to a TI backup before I tried the update.zip
I was able to restore all 54 applications from there after downloading TI Backup from the market.
Long and short, it doesn't work yet. Good concept, doesn't work.

An advanced restore in cwm let's you restore all of your apps, data and widgets.

superrelaxx said:
An advanced restore in cwm let's you restore all of your apps, data and widgets.
Click to expand...
Click to collapse
Could you be a little more specific as to what you mean? Which version, how to run it. and so on?

sanjsrik said:
Could you be a little more specific as to what you mean? Which version, how to run it. and so on?
Click to expand...
Click to collapse
This has worked on every version of cwm that I've used (I'm on 6.0.1.2). If you've already made a backup, then flash a new rom:
-go back into recovery
-select backup/restore
-goto advanced restore
-select the rom to get your backup from
-select restore data
-reboot

@sanjsrik
Yeah, not working for me as well. Maybe I'm missing a step here or not doing it in the correct order.
1. Boot to Recovery
2. Wipe/Factory reset
3. Wipe cache
4. Wipe dalvik
5. Install ROM (in this test case, CM10)
6. Install .zip file (created by TI Backup)
7. Boot
8. Nothing restored (it's like a bone stock install of CM10)
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
superrelaxx said:
This has worked on every version of cwm that I've used (I'm on 6.0.1.2). If you've already made a backup, then flash a new rom:
-go back into recovery
-select backup/restore
-goto advanced restore
-select the rom to get your backup from
-select restore data
-reboot
Click to expand...
Click to collapse
If that's the case, we don't need TI Backup, no?

Samsung.Galaxy.S3 said:
@sanjsrik
Yeah, not working for me as well. Maybe I'm missing a step here or not doing it in the correct order.
1. Boot to Recovery
2. Wipe/Factory reset
3. Wipe cache
4. Wipe dalvik
5. Install ROM (in this test case, CM10)
6. Install .zip file (created by TI Backup)
7. Boot
8. Nothing restored (it's like a bone stock install of CM10)
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
If that's the case, we don't need TI Backup, no?
Click to expand...
Click to collapse
Does this restore the applications before the flash update? It doesn't step on any of the system stuff?

sanjsrik said:
Does this restore the applications before the flash update? It doesn't step on any of the system stuff?
Click to expand...
Click to collapse
I flash my new rom, boot up, and let it settle. If by chance the apps don't get installed automatically from the Google restore, then I boot back into recovery and do the advanced restore. This doesn't affect the system (don't want that)

superrelaxx said:
I flash my new rom, boot up, and let it settle. If by chance the apps don't get installed automatically from the Google restore, then I boot back into recovery and do the advanced restore. This doesn't affect the system (don't want that)
Click to expand...
Click to collapse
Next nightly, I'm giving this a shot. Full wipe and restore just the data before rebooting back into ROM.
Thanks for the advice.

to avoid running into system data restore errors should i deselect everything that is red?
---------- Post added at 03:21 PM ---------- Previous post was at 03:01 PM ----------
just tried this and i cant get past boot logo screen..anyone else?

superrelaxx said:
I flash my new rom, boot up, and let it settle. If by chance the apps don't get installed automatically from the Google restore, then I boot back into recovery and do the advanced restore. This doesn't affect the system (don't want that)
Click to expand...
Click to collapse
Is this safe to do if switching ROMs?

TyroneLT said:
Is this safe to do if switching ROMs?
Click to expand...
Click to collapse
I hate letting Google reinstall everything. Takes forever and doesn't restore data
Squirted out of my Samsung's jellybean

TyroneLT said:
Is this safe to do if switching ROMs?
Click to expand...
Click to collapse
I just used a backup of Synergy to restore data into Beans. I did the advanced restore right after flashing the rom without rebooting first. Worked perfect!

superrelaxx said:
I just used a backup of Synergy to restore data into Beans. I did the advanced restore right after flashing the rom without rebooting first. Worked perfect!
Click to expand...
Click to collapse
I tried this process tonight and it worked perfectly!

I flashed rom, gapps n then i hit that install update.zip button after I let the rom boot up n settle. It wouldn't get past the boot animation. I wiped, flashed rom, flashed gapps, let the rom boot up n settle. Then I went back into recovery. I installed the zip as I would a regular zip n I fixed permissions. Then it worked
Sent from my SCH-I535 using Tapatalk 2

superrelaxx said:
This has worked on every version of cwm that I've used (I'm on 6.0.1.2). If you've already made a backup, then flash a new rom:
-go back into recovery
-select backup/restore
-goto advanced restore
-select the rom to get your backup from
-select restore data
-reboot
Click to expand...
Click to collapse
This looks to be a process to try!

Related

Tutorial: How to upgrade Huawei Ascend from Android 2.1 OS to 2.3

Tutorial:
How to get Android 2.3 Operating System(OS) on your Huawei Ascend (For Newbies)
Android 2.3
Z4Root
Google Apps
Metro Backup
Ok, to start things off, You need to move all of the files that you downloaded to your phone’s SD Card, you will also need a Application Installer, You can download one from the android marketplace for free, there’s tons of them. “AppInstaller” is the one that I personally use.
1)First you must root the phone by installing the Z4Root file. Open your application installer and find Z4Root where ever you placed it onto your SD Card, install the Z4Root. The phone will restart on its own. The phone is now rooted.
2)Next you need to download clockwork recovery from the android marketplace. There is a Free version and a Paid version. The free version works just fine . After downloading the app, open it and under the 2nd tab of the app choose the reboot into recovery option.
3)The phone will restart itself and a black screen with blue/green text will appear, it is recommended to create a backup before installing anything new. Next, Choose the “wipe data/factory reset” option and click yes. Then choose the “wipe cache partition” option and click yes again. Lastly, click the “advanced” option then scroll down to “wipe Dalvik Cache” and choose yes again.
4)Once you have wiped the three files, choose the “Install From Zip” option, then the “choose Zip from SD Card” option. (You should have the Android 2.3, gapps and Metro backup Files on your zip already, If not, put the two files onto your SD card then repeat the last step). Then scroll down to the “Cm7-Ascend-05142011” option, the new operating system will now be installed onto your phone.
5)After that, choose the “MetrOFF.v1.1-MMS-[GB]-[CM_AOSP]” option. This fixes a bug that caused users to not send multimedia messages properly.
6)Now choose the “gapps-gb-20110307-signed-1.zip”, this installs all of the google apps onto your phone
6)After installing the Gapps file, choose the “reboot system now” option. Your phone now has Android 2.3 Operating system!
7) Yay!
clockwork recovery is not in market is there another program or someplace else to find it
It's called ROM Manager.
Sent from my Droid using XDA Premium App
would i still be able to send mms (text messages), and recieve service?
Need for Cricket
Do you or any one have the links to the same as above but for a Cricket Huawei Ascend?
Thanks for any help you can give.
Hello
If I got OS 2.2 already on my huawei, have I go through the same steps as update from 2.1 ?
There is no Z4Root file on android market.
---------- Post added at 09:51 PM ---------- Previous post was at 09:47 PM ----------
Do I need to install superuser? Can you tell me for what is it for?
After update to 2.3 OS there is no problem with taking pictures(camera) and mms?
Is there any way to come back to 2.2 OS if I won't like 2.3 ?
what would the benefit be of going from 2.2 up to 2.3 since the major benefits hit at the 2.2 mark in my opinion any ways
trickfitt said:
clockwork recovery is not in market is there another program or someplace else to find it
Click to expand...
Click to collapse
Handy Ascend Download Links
peteisme said:
would i still be able to send mms (text messages), and recieve service?
Click to expand...
Click to collapse
Yes, if you're on Cricket. If you're on Metro, you need to flash the metroff mms fix zip with CWM.
Qeutua said:
Do you or any one have the links to the same as above but for a Cricket Huawei Ascend?
Thanks for any help you can give.
Click to expand...
Click to collapse
Handy Ascend Download Links
samsimon said:
If I got OS 2.2 already on my huawei, have I go through the same steps as update from 2.1 ?
There is no Z4Root file on android market.
Click to expand...
Click to collapse
The same, but use Gingerbreak to root instead.
samsimon said:
Do I need to install superuser? Can you tell me for what is it for?
Click to expand...
Click to collapse
Superuser keeps track of and grants permissions to apps to root access. When you use Z4Root or Gingerbreak, it is installed automatically. And yes, you need it.
samsimon said:
After update to 2.3 OS there is no problem with taking pictures(camera) and mms?
Click to expand...
Click to collapse
The only problems are that with Metro you need the metroff fix flashed, and you can't use the camera with apps. For instance, you can't use a barcode or QR code scanner. If you need a QR scanner, you have to take a pic of the QR code first with just your camera, then open something like QR Droid, and read the code from the pic you took.
samsimon said:
Is there any way to come back to 2.2 OS if I won't like 2.3 ?
Click to expand...
Click to collapse
Sure. Just look at this thread. You'll have to flash back to 2.1, then get the OTA update to 2.2.
wtfdissux said:
what would the benefit be of going from 2.2 up to 2.3 since the major benefits hit at the 2.2 mark in my opinion any ways
Click to expand...
Click to collapse
PlayfulGod has really maximized what the Ascend is capable of. I haven't heard anyone saying that his CM7 ROMs aren't faster and better. His latest overclock to 710 and 748, depending on if you have a lazy Ascend or not, and have a2sd integrated into the ROM. It's faster, beefier, and just plain better. IMO anyway.
AndroJordan said:
Tutorial:
How to get Android 2.3 Operating System(OS) on your Huawei Ascend (For Newbies)
Android 2.3
Z4Root
Google Apps
Metro Backup
Ok, to start things off, You need to move all of the files that you downloaded to your phone’s SD Card, you will also need a Application Installer, You can download one from the android marketplace for free, there’s tons of them. “AppInstaller” is the one that I personally use.
1)First you must root the phone by installing the Z4Root file. Open your application installer and find Z4Root where ever you placed it onto your SD Card, install the Z4Root. The phone will restart on its own. The phone is now rooted.
2)Next you need to download clockwork recovery from the android marketplace. There is a Free version and a Paid version. The free version works just fine . After downloading the app, open it and under the 2nd tab of the app choose the reboot into recovery option.
3)The phone will restart itself and a black screen with blue/green text will appear, it is recommended to create a backup before installing anything new. Next, Choose the “wipe data/factory reset” option and click yes. Then choose the “wipe cache partition” option and click yes again. Lastly, click the “advanced” option then scroll down to “wipe Dalvik Cache” and choose yes again.
4)Once you have wiped the three files, choose the “Install From Zip” option, then the “choose Zip from SD Card” option. (You should have the Android 2.3, gapps and Metro backup Files on your zip already, If not, put the two files onto your SD card then repeat the last step). Then scroll down to the “Cm7-Ascend-05142011” option, the new operating system will now be installed onto your phone.
5)After that, choose the “MetrOFF.v1.1-MMS-[GB]-[CM_AOSP]” option. This fixes a bug that caused users to not send multimedia messages properly.
6)Now choose the “gapps-gb-20110307-signed-1.zip”, this installs all of the google apps onto your phone
6)After installing the Gapps file, choose the “reboot system now” option. Your phone now has Android 2.3 Operating system!
7) Yay!
Click to expand...
Click to collapse
Update this method by using the latest CM7 and gapps 20110613 found in Prepaid Android Wiki. Just know that if you try to flash the ROM with the 748 OC kernel, and your phone won't boot after a couple attempts, you probably have a lazy Ascend and need to flash the ROM with the 710 OC kernel.
If you're on 2.2, it will still work, except root with Gingerbreak instead of Z4Root.
i did all the steps but when i go to install from zip thru the recovery screen it says its unpacking then failed and gets aborted.. Any help?
Derp, wrong info here, deleted...
No rom manager
I have the Huawei Ascend and have been trying to get rom manager but t is now only for 2.2 and up I have 2.1 Please can anyone help out. And just so you know...I tried to load CWM recovery on boot up but it doesn't work. Debugging alow user all that stuff was done. I have been working on this for days now. Everytime I try and boot up CWM it fails...I updated drivers for my phone and all but when it turns on in boot mode it only shows the android 2A boot sceen with 4 options...reboot...load SD card (does absolutely nothing) wipe data and lastly wipe cashe. Long story short rom manager is for 2.2 and up but there are people out there posting 2.1 to 2.3 upgrade soo???? Is it possible? Thanks
Give me an hour and I'll show you how to do what you want to, on the road atm.
Sent from one pimped out DroidX2
---------- Post added at 06:15 PM ---------- Previous post was at 05:30 PM ----------
Spikebob21 said:
i did all the steps but when i go to install from zip thru the recovery screen it says its unpacking then failed and gets aborted.. Any help?
Click to expand...
Click to collapse
You're holding volume up and end call (the rightmost one) instead of volume up and send (leftmost one).
---------- Post added at 06:31 PM ---------- Previous post was at 06:15 PM ----------
experymental said:
I have the Huawei Ascend and have been trying to get rom manager but t is now only for 2.2 and up I have 2.1 Please can anyone help out. And just so you know...I tried to load CWM recovery on boot up but it doesn't work. Debugging alow user all that stuff was done. I have been working on this for days now. Everytime I try and boot up CWM it fails...I updated drivers for my phone and all but when it turns on in boot mode it only shows the android 2A boot sceen with 4 options...reboot...load SD card (does absolutely nothing) wipe data and lastly wipe cashe. Long story short rom manager is for 2.2 and up but there are people out there posting 2.1 to 2.3 upgrade soo???? Is it possible? Thanks
Click to expand...
Click to collapse
To install CWM:
First, make sure Unknown Sources and USB Debugging are both checked.
Make sure you have the Ascend drivers installed.
Then, if you haven't rooted your phone, do a permanent root with Z4Root. If you're going to flash CM7 (Android 2.3.4) grab the CM7 and gapps zip files from Prepaid Android Wiki and put them on your sdcard now.
Plug your phone into your computer via USB.
Then grab Clockwork Mod 3.0.2.8, unzip it, open the folder, and run these files (make sure you use the versions for the OS your computer is running, Windows for instance)
adb
fastboot
install recovery
Unplug the phone, pull the battery for several seconds, put it back in.
Hold volume up and send button (leftmost button along bottom) and hit the power button. Don't let go of the buttons until you see recovery.
To flash CM7:
Make sure to BACKUP APPS AND CONTACTS!
Grab the latest version from Prepaid Wiki along with the gapps zip there
Copy both zips to your sdcard (don't unzip them!)
Boot into Clockwork Mod
Wipe data/factory reset
Wipe cache partition
go into advanced
Wipe dalvik cache
back out to main menu
go into mounts and storage
Format boot
Format system
Format data
Format cache
back out to main menu
Install zip from sdcard
Choose zip from sdcard
select CM7 zip
select gapps zip
back out to main menu
Advanced
Fix permissions
back out to main menu
Reboot system now.
Wait for a little bit. If it gets stuck at the boot screen for more than ten minutes, and you tried the 748 OC kernel, try it all over again with the 710 OC kernel.
Scur827 said:
Wipe data/factory reset
Wipe cache partition
go into advanced
Wipe dalvik cache
back out to main menu
go into mounts and storage
Format boot
Format system
Format data
Format cache
back out to main menu
Install zip from sdcard
Choose zip from sdcard
select CM7 zip
select gapps zip
back out to main menu
Advanced
Fix permissions
back out to main menu
Reboot system now.
Wait for a little bit. If it gets stuck at the boot screen for more than ten minutes, and you tried the 748 OC kernel, try it all over again with the 710 OC kernel.
Click to expand...
Click to collapse
I'm hoping I'm just missing something. I tried these steps earlier but no matter which CM7 ZIP I tried, i get stuck at the "Ascend" screen during boot. I have CWM 3.0.2.8, tried the following MODs:
PlayfulGod CM7.2-Ascend (09122011) (748 OverClock defaulted to 710)
PlayfulGod CM7.2-Ascend (09132011) (710 OverClock defaulted to 710)
PlayfulGod CM7.2-Ascend (09132011) (710 OverClock defaulted to 600)
Always seem to get stuck on the Ascend screen. I'm rooted. Originally had 2.2, rooted via Gingerbreak and when I couldn't get it going, I tried going to Metro PCS stock 2.1, used Z4 to root, then tried the exact steps above, even the extra formats and the permissions fix at the end. Waited 15 mins during each boot and it's stuck on the Ascend screen (before the CM7 boot screen).
Any ideas?
Odd that you keep getting stuck at boot, maybe you have a super-lazy Ascend that doesn't like the kernels. When it's stuck at the screen like that, I could sneak into a too-high-for-my-phone kernel by tapping or holding rhe power button when it seemed stuck.
Personally, I would run this by the guys at androidforums.com. They're still fresh in this phone, and it's probably something obvious that I'm not seeing.
Sent from one pimped out DroidX2
Another thought. When I was flashing my Ascend all the time, there were lots of times I had to reflash with fresh downloads multiple times. I remember at least twice I it took 4 flashes to take. Granted, those were early versions of CM7, but I never called it unsuccessful until I tried to flash a ROM 3 or 4 times.
Sent from one pimped out DroidX2
Thanks Scur. I posted on AndroidForums.com. I tried Bobz's last build and that loaded. Maybe it's just PlayfulGod's mods. I'll do it a few more times and see, but at least I know I have one build that works. Thanks again!
Yeah, so I did litterally EVERYTHING this wanted me to do, and in the end I got black screen with blue letters. I only had 4 options:
Reboot now
Upgrade SD
Wipe factory
Wipe cache
Someone please help? I have the CM7 downloaded into my SD card i think, just someone please try to help.
JonJon927 said:
Yeah, so I did litterally EVERYTHING this wanted me to do, and in the end I got black screen with blue letters. I only had 4 options:
Reboot now
Upgrade SD
Wipe factory
Wipe cache
Someone please help? I have the CM7 downloaded into my SD card i think, just someone please try to help.
Click to expand...
Click to collapse
That's the factory stock recovery. You didn't install ClockworkMod recovery.

[Q] Please Help :(

First off, this is my first post (Woopty doo horraaaay) and I desperately need help.
I have a Wifi-Only Motorola Xoom, it used to be on 3.2.1, and I had it rooted, with only using the Tiamat 2.2.2 Moray root.
I've been wanting to upgrade to ICS for a while, and I finally am. I've had to reset my xoom back to stock 4 or 5 times now, and I'm annoyed and want to do it right. Starting off, my Xoom is starting on ICS, unlocked, unrooted.
I've done many different orders of stuff. First, I flashed the clockwork recovery mod, and then I go into it, and installed the EOS-Wingray-60, but after I did that, when I start up the xoom, it never loads, it stays on the "Team EOS" boot animation. I tested it, and left it on all night, and woke up and it was still on team eos. Next, I tried installing the universal root, (It worked), and THEN I installed the Wingray-60. Same problem, stuck on animation. I've repeated these several times, and am not sure what to do.
Pretty much all I want is to be able to overclock it. What order should I do when installing roots and things?
I have wingray-60, Rogue Kernal 2.0.2 Kuma, Universal root, Clockwork recovery mod, Tiamat 3.0.5 (Not sure what this is, but when I use it, it automatically aborts the install), and I have all of the **** to restore it back to factory + my original 3.2.1 backup rooted is saved.
What order should I use the installs in, and which ones should I use? And is there something I'm doing wrong?
To have ICS with Overclock, all you need is:
- Unlocked Bootloader
- Rooted
- CWM Recovery installed (Rogue)
- TeamEOS Wingray Build 60
- TeamEOS Google Apps V10.5
All the other stuff you listed, you can move to another folder for archive. You don't need it.
Follow these steps.
Use Titanium Backup to backup any applications and data you want to save. If you don't care about the apps/data, you can skip this step.
Boot into Recovery. Power off, when the Moto logo shows for about 1 sec, hold the Vol down. Select Android Recovery.
From CWM, select wipe data/factory reset **Warning - you will blow away all your apps/data *** See note about backing up first.
Follow these steps to ensure a clean first install. Select "wipe cache partition"
Select "Yes - Wipe Cache"
Select "advanced"
Select "Wipe Dalvik Cache"
Select "Yes - Wipe Dalvik Cache"
Select "+++++Go Back+++++"
Select Install from Zip, Select Zip. Navigate to your Team EOS ROM, and install it
IMMEDIATELY after the ROM is installed, install the Google APPS file via Select ZIP.
If you did everything correctly, Reboot. Now Team EOS boot animation should start and ICS will be available to you along with the Market. Restore your apps. Select from Settings to OC to your desired speed and enjoy.
Remember to thank the Devs for all their hard work and donate
al mon said:
To have ICS with Overclock, all you need is:
- Unlocked Bootloader
- Rooted
- CWM Recovery installed (Rogue)
- TeamEOS Wingray Build 60
- TeamEOS Google Apps V10.5
All the other stuff you listed, you can move to another folder for archive. You don't need it.
Follow these steps.
Use Titanium Backup to backup any applications and data you want to save. If you don't care about the apps/data, you can skip this step.
Boot into Recovery. Power off, when the Moto logo shows for about 1 sec, hold the Vol down. Select Android Recovery.
From CWM, select wipe data/factory reset **Warning - you will blow away all your apps/data *** See note about backing up first.
Follow these steps to ensure a clean first install. Select "wipe cache partition"
Select "Yes - Wipe Cache"
Select "advanced"
Select "Wipe Dalvik Cache"
Select "Yes - Wipe Dalvik Cache"
Select "+++++Go Back+++++"
Select Install from Zip, Select Zip. Navigate to your Team EOS ROM, and install it
IMMEDIATELY after the ROM is installed, install the Google APPS file via Select ZIP.
If you did everything correctly, Reboot. Now Team EOS boot animation should start and ICS will be available to you along with the Market. Restore your apps. Select from Settings to OC to your desired speed and enjoy.
Remember to thank the Devs for all their hard work and donate
Click to expand...
Click to collapse
Now, just to be clear, I should root with the universal root?
Do you have Titanium Backup or Rom Manager? Do you also have SU access?
If you do, you most likely have Root, but you can always re-root if you are unsure.
al mon said:
Do you have Titanium Backup or Rom Manager? Do you also have SU access?
If you do, you most likely have Root, but you can always re-root if you are unsure.
Click to expand...
Click to collapse
No, I had just restored my xoom back to factory. I just rerooted, using the universal root, then I wiped all my crap like you said, then I downloaded Eos 60, then I download Gapps and when I download gapps, my xoom says "E:Can't open /sdcard/EOS_GApps_ics_4.0.3_v9.zip (bad) Installation aborted".
Now what :|
You need to flash this version of the CMW Recovery. Without it, you cannot see/mount your SDCard.
http://forum.xda-developers.com/showthread.php?t=1074979
After flashing, reboot into recovery again and it should see the external SDCard which now contains your EOS ROM and EOS GApps. Flash those back to back and you should be good to go.
I CAN see my external SDCard!!!
If I couldn't see it, how could I even be rooted? That's a whole 'nother problem!
Sorry, but yeah, I can't see everything just fine. It's just Gapps is refusing to install, and everytime I install Eos 60, my device won't boot.
Slayergramp said:
I CAN see my external SDCard!!!
If I couldn't see it, how could I even be rooted? That's a whole 'nother problem!
Sorry, but yeah, I can't see everything just fine. It's just Gapps is refusing to install, and everytime I install Eos 60, my device won't boot.
Click to expand...
Click to collapse
Okay... Relax lol
Please answer these questions
1. Have u checked the md5 sums on the gapps and the eos rom? They are provided and a bad installation can mean your files are buggered sooo check the md5 are correct for each file
2. Did you install the rogue recovery or the modded cwm recovery using fastboot? (not using rom manager or whatever)
3. Have you factory wiped before installing the rom?
4. Did you wipe cache and dalvik cache?
5. Did you install the rom then the. Gapps?
6. Did you fix permissions once you finished flashing both files?
Thanks
Sent from my mind control device
joshndroid said:
Okay... Relax lol
Please answer these questions
1. Have u checked the md5 sums on the gapps and the eos rom? They are provided and a bad installation can mean your files are buggered sooo check the md5 are correct for each file
2. Did you install the rogue recovery or the modded cwm recovery using fastboot? (not using rom manager or whatever)
3. Have you factory wiped before installing the rom?
4. Did you wipe cache and dalvik cache?
5. Did you install the rom then the. Gapps?
6. Did you fix permissions once you finished flashing both files?
Thanks
Sent from my mind control device
Click to expand...
Click to collapse
First off, I finally got the EOS rom to work perfectly fine. My problem was that I never wiped the system's cache data or dalvik. And where do I check the Md5 sum for the Gapps? Because they still are a "(bad)" file.
Yes, I use a perfectly fine recovery, not rom manager, what permissions need fixing? Thanks.
Slayergramp said:
First off, I finally got the EOS rom to work perfectly fine. My problem was that I never wiped the system's cache data or dalvik. And where do I check the Md5 sum for the Gapps? Because they still are a "(bad)" file.
Yes, I use a perfectly fine recovery, not rom manager, what permissions need fixing? Thanks.
Click to expand...
Click to collapse
Download a free md5 program...
Look at the md5 when u download the gapps package in the goo in side me link in the eos thread
Sent from my mind control device
joshndroid said:
Download a free md5 program...
Look at the md5 when u download the gapps package in the goo in side me link in the eos thread
Sent from my mind control device
Click to expand...
Click to collapse
What IS md5, what does it need to be, and where do I check it? I don't understand the jibberish in the second half of your sentence.
Slayergramp said:
What IS md5, what does it need to be, and where do I check it? I don't understand the jibberish in the second half of your sentence.
Click to expand...
Click to collapse
Md5 is a unique hash that is calculated depending on the file.. When they match you have exactly what has been uploaded by the developer. When they dont that can be a cause of your problems.. I suggest u know and understand that for future for almost any file you download where one is provided... You can brick your device and it would be your own fault if you didnt check an md5.. So jibberish, hardly..
Now... Google a free md5 program for your computer and download n install it
Go to your relevant eos thread in first post there is a link for latest gapps packages...
Download the latest 10.5v if u havnt
Look at the md5 its displayed when you download the file or on the side of the file in the list...
Put the downloaded file in the md5 program on your computer and compare to the one provided..
Now try to flash this package within recovery...
Be sure to wipe caches, dalvik... Flash gapps.. Go to advanced then fix permissions... Then reboot.. See if it works.. If not try factory reset, wipe cache n dalvik, install rom, then gapps, then fix permissions.. Then reboot
Sent from my mind control device

Need steps for CM9 Build 8

I have few doubts regarding installation and operating CM9. Currently, I'm on JaggyROM 3.
Q1.
- Copy GApps and CM9 ZIPs to your SDCard
Click to expand...
Click to collapse
I need 20120429.zip for CM9 #8, right?
Q2.
- Flash CM9 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
Click to expand...
Click to collapse
Is this actual order of steps? Cause afaik, we have to first do the reset/wipe & then apply update. And in which order should I apply the CM9 & GApps? or any order is OK?
Q3.
- Don't restore data using Titanium Backup! they might cause FC's
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
This is THE most important question. How should I restore data?
Will it be OK if I installed ONLY APPS first with help of an installer and then used Titanium to restore data?
Can't wait to install this wonderful ROM.
Thanks.
I used this steps without a problem.
1. Download and copy rom to sdcard
2. Boot/Reboot into CWM
3. Backup your existing ROM (just in case)
4. Wipe Data/Factory Reset
5. Goto mounts/storage, mount cache, data, system
6. Format boot, cache, data, system, advanced menu dalvik
7. Install zip from sdcard, choose zip from sdcard, choose "cm-9-20121102-UNOFFICIAL-pico.zip"
8. Wait for it to install, when finished reboot, wait until on homescreen, leave to settle for afew minutes then reboot again
9. Flash gapp
Those are instructions for installing a clean stock cyanogen rom.
-from liverpool-fan
and this is the CM9#8 filename cm-9-20121004-UNOFFICIAL-pico.zip
Actually, I am confused about GApp file name.
And should I install apps in two steps? First only apps and then the app data?
BatsDroid said:
Actually, I am confused about GApp file name.
And should I install apps in two steps? First only apps and then the app data?
Click to expand...
Click to collapse
Why are you confused with gapps file name? Just install apps like normal apps
bluerain28 said:
Why are you confused with gapps file name? Just install apps like normal apps
Click to expand...
Click to collapse
because there are so many of them.
BatsDroid said:
because there are so many of them.
Click to expand...
Click to collapse
Ohhh just choose the one in the "table". :silly:
cm9 build 8
bluerain28 said:
Ohhh just choose the one in the "table". :silly:
Click to expand...
Click to collapse
I just want to know did camera works fine on cmp build 8 also video recording? on cm9 mod link2sd does not make 2nd partation. Is link2sd works fine on cm9 build 8 rom?

{TIP] Restoring TWRP backup after complete data wipe

Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Or you could just copy the whole twrp folder to your hdd. thats what I do anyway and restore without a problem.
Yep that would have prevented me ending up in that predicament for sure.
So would not flashing roms. The point of the post is really about what to do if you find yourself in that situation and the value of keeping a cool head and thinking through a solution rationally, using your own resources.
The way I see it is: it's my mess I got into it, how am I going to solve it....
Sent from my HTC One S using xda app-developers app
Lost my Backup
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
matrixmainframe said:
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
Click to expand...
Click to collapse
Do what the op says and do a backup and you will know where to put it.
Sent from my HTC One S using Tapatalk 2
Plz HELP!!!
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
abdullah.imran2158 said:
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
Click to expand...
Click to collapse
1. wrong forum, if you have a one x device
2. calm down
3. relock your bootloader (fastboot oem lock)
4. download and run latest ruu for your phone (search for a suitable one for your cid and carrier if you are branded)
5. you also can flash a custom sense based rom, which gives you sense back (viper one s or trickdroid or android revolution hd)
6. if you want to flash one of these,dont forget to flash the boot.img too
7. before flashing a rom, wipe system, data and cache 3xtimes to be sure you do a clean install
Thanks Man
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
Thanks Man, been stuck in TWRP for about two hours now, thought I soft bricked my Droid Dna forever. I had a backup, and adb pushed it to the /sdcard directory, but it wouldn't show up in the restore section. This empty-backup method worked fine. Thanks, you saved me $400.:good:
Saved my HTC One!
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
I'd just like to say a MASSIVE THANK YOU for this post! I had a major issue and thought I'd lost my 1-day old HTC One (M7). I wasn't so much panicking as I knew i'd find a way, but a cold sweat had started to break!
The biggest lesson I can take from this is simply this... MAKE SURE YOU BACKUP YOUR ORIGINAL ROM BEFORE YOU DO ANYTHING! It's such an obvious thing, but without this simple step, I'd be in trouble right now as HTC haven't an RUU for my specific device yet (plus I'm on a Mac, making running .exe files more painful still)
What had happened was that as a result of a corporate email policy, I had to encrypt my device. I did this after flashing to a new ROM. Unfortunately after I had done so, the new ROM wasn't playing nicely with Exchange (using native HTC Mail app). Of course the issue here is that when you so into TWRP, you can't see the files to restore (because TWRP is opened before the device asks you for the passcode to decrypt... another learning!). To remove the encryption, I had no choice but to do a full format of the device, so I was basically left with a brick
Anyway, once again, thank you for this post, you just saved me AU$700!
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
Click to expand...
Click to collapse
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
:good:
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
Click to expand...
Click to collapse
Deleted comment
Hei guys,
Please help!!!! I tried to install MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 on my HTC One s,i got storage issue. Now my sd card is just 48MB. I have installed TWRP v2.6.3.0 and i did backup before flashing room. I decided to do factory restore by TWRP and wiped OS from MY device.Now when i do backup i get failed error: not enough free space on storage. Total size of all data 203MB, available space 48 MB.I see my sd card on pc through TWRP, but i cannot make backup and even put any new rom into my sd card to flash it because of 48MB...Is it any chance to get back any OS on my HTC One s....?
This post might help
http://forum.xda-developers.com/showthread.php?p=47744972.
Sent from my One S using xda app-developers app
StifflerServices said:
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
Click to expand...
Click to collapse
EDIT: oops, somehow thought this was a recent post. Never mind
Not really.
If you are S-off,
Restore Backup,
Wipe Caches
S-On
Restore Backup
Wipe Caches
(if the rom you were previously on had a different Boot.img you will need to fastboot your boot.img) In the backup
Assumes you are not trying to restore a backup to 2.15 if you were just on 2.16. You will need to RUU + factory reset/clear storage for that.
I'm sry not sure what "RUU" means... Probably will remember once u tell me I'm sure. But Ya I kinda just winged it, didn't flash the Rom to do the NanBU and all went fine, which is odd cause on my S2 w cwm it out me in a boot loop and had to start over, but I think TWRP may be a diff setup when restoring nanbu's. But either way it's always nice to know and find a "step by step" guide to restoring NanBU's from previous / updated / or different ROMs. For noobs that was one of the confusing things to do due to lack of that info in threads or utube vids out there.
Got a question. I've made my backup files but restore shows nothing but storage... No files to chose, no more options to restore. Is it normal?
Sent with my One S C2 Sense 5 using Taptalk
brilliant!
ATSPerson said:
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
metropical said:
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
Click to expand...
Click to collapse
From one Clash fan to another, thanks for the thanks ☺
¡La lucha continua!

cwm update

Hi
I tried to install cm11
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
When I wanted to install
I was registered installtaion aborted
And discovered that it was because that cwm I have his version does not match
So I found this: http://forum.xda-developers.com/showthread.php?t=2564767
This update cwm
Is it safe?
Anyone tried it?
Because I want to try it to install kitkat
Sorry for the english, I'm from Israel
And I used Google Translate
eran32 said:
Hi
I tried to install cm11
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
When I wanted to install
I was registered installtaion aborted
And discovered that it was because that cwm I have his version does not match
So I found this: http://forum.xda-developers.com/showthread.php?t=2564767
This update cwm
Is it safe?
Anyone tried it?
Because I want to try it to install kitkat
Sorry for the english, I'm from Israel
And I used Google Translate
Click to expand...
Click to collapse
שלום
Not bad!
Use the Jan 16 version. As with any playing around, do a backup before flashing cm-11. If you need to do any sdcard partitioning, do it on the old version as these functions are not in this new version.
Dovidhalevi said:
שלום
Not bad!
Use the Jan 16 version. As with any playing around, do a backup before flashing cm-11. If you need to do any sdcard partitioning, do it on the old version as these functions are not in this new version.
Click to expand...
Click to collapse
so, download jan 16 version and flash the update zip in recovery?
and then install cm11?
eran32 said:
so, download jan 16 version and flash the update zip in recovery?
and then install cm11?
Click to expand...
Click to collapse
Yes, you flash the new recovery with the old recovery first. Reboot to new recovery. Remember to wipe user data/factory reset along with wiping Dalvik cache and formatting system from the mounts and storage item. Then install your CM11 ROM.
shinobisoft said:
Yes, you flash the new recovery with the old recovery first. Reboot to new recovery. Remember to wipe user data/factory reset along with wiping Dalvik cache and formatting system from the mounts and storage item. Then install your CM11 ROM.
Click to expand...
Click to collapse
Good
So what I gather, I need to install the update zip in cwm
And if I want to install cm11 steps I need?
eran32 said:
Good
So what I gather, I need to install the update zip in cwm
And if I want to install cm11 steps I need?
Click to expand...
Click to collapse
I would hope that the update.zip you are referring to is a flashable recovery. From the link posted it is. It's the newest recovery with support for KitKat ROMs. Flash this like you would flash anything else. IE; Install zip from sdcard. Then go to 'Advanced' and choose reboot recovery. This will reboot you in to the new recovery you just flashed.
From there do "Wipe data/factory reset" and then go to "Advanced" again and select "Wipe Dalvik cache". Go back to CWM main menu and then select "Mounts and storage". From there only select "Format /system". Back to CWM main menu. Select 'Install zip from sdcard'. If the ROM is on your external SD, which it should be, then choose "install from external sd". Confirm the installation and wait for it to install. Back to CWM main menu and choose reboot system. Voila!
Now I don't wanna seem harsh, but there are countless threads that explain how to flash a ROM/zip. XDA enforces using their search function to help prevent multiple threads of roughly the same content from being created. So in the future, please use the Search function before creating a new thread.
shinobisoft said:
I would hope that the update.zip you are referring to is a flashable recovery. From the link posted it is. It's the newest recovery with support for KitKat ROMs. Flash this like you would flash anything else. IE; Install zip from sdcard. Then go to 'Advanced' and choose reboot recovery. This will reboot you in to the new recovery you just flashed.
From there do "Wipe data/factory reset" and then go to "Advanced" again and select "Wipe Dalvik cache". Go back to CWM main menu and then select "Mounts and storage". From there only select "Format /system". Back to CWM main menu. Select 'Install zip from sdcard'. If the ROM is on your external SD, which it should be, then choose "install from external sd". Confirm the installation and wait for it to install. Back to CWM main menu and choose reboot system. Voila!
Now I don't wanna seem harsh, but there are countless threads that explain how to flash a ROM/zip. XDA enforces using their search function to help prevent multiple threads of roughly the same content from being created. So in the future, please use the Search function before creating a new thread.
Click to expand...
Click to collapse
Good man, I'll try it
But after that I'll update I can install the cm7 if I wanted?
Clockwork 6.0 only flash cm10~cm11. If you like to install anothrer version, like cm9 or cm7 you have to flash first rhe clockwork 5.0. And then rwboot recovery and then flash zip. So, once you have downloaded the flashable zip for clock 5.0 and the wanted rom you have to do
1- Copy clock 5 and rom to sd card.
2- Reboot recovery
3- Flash clock 5
4- Reboot recovery
5- flash wanted rom under the rom instructions.
6- Enjoy
Sent from my LG-P500 using xda app-developers app
The cm11 support Hebrew?
and my cwm is 5.0.2.0
so i can upgrade to 6.0.4.6 cwm?
eran32 said:
The cm11 support Hebrew?
and my cwm is 5.0.2.0
so i can upgrade to 6.0.4.6 cwm?
Click to expand...
Click to collapse
I cannot say if CM11 supports Hebrew or not, sorry. However, in order to install CM11 you need the newest recovery 6.0.4.6 as you've already figured out. That recovery, 6.0.4.6, will allow you to swap between CM10.2 and CM11 with no issues. To go back to older Android versions you will need to revert back to your older CWM first.
Clock 5.0 is capable of flash:
-CM7
-CM9
-CM10
-CM10.1
-CM10.2
Clock 6.0 is capable of flashing:
-CM10
-CM10.1
-CM10.2
-CM11
Hope it helps you.
chalo99 said:
Clock 5.0 is capable of flash:
-CM7
-CM9
-CM10
-CM10.1
-CM10.2
Clock 6.0 is capable of flashing:
-CM10
-CM10.1
-CM10.2
-CM11
Hope it helps you.
Click to expand...
Click to collapse
thanks, but i can update from my version?
and not need to flash gapps?
And how to increase space by a partition, you can put some space want?
Because I saw that choose mb
eran32 said:
thanks, but i can update from my version?
and not need to flash gapps?
And how to increase space by a partition, you can put some space want?
Because I saw that choose mb
Click to expand...
Click to collapse
CWM 5.0.2.0 can NOT flash CM11. You will get Status 7 error. You must upgrade recoveries to install CM11.
If you don't plan on having a GMail account attached to the device, have no need for the Play Store and some others, then no, don't flash GAPPs. Though I suspect you'll find that you will want/need to.
There is no safe way to increase the internal memory, as in change partition sizes, of these devices.
shinobisoft said:
CWM 5.0.2.0 can NOT flash CM11. You will get Status 7 error. You must upgrade recoveries to install CM11.
If you don't plan on having a GMail account attached to the device, have no need for the Play Store and some others, then no, don't flash GAPPs. Though I suspect you'll find that you will want/need to.
There is no safe way to increase the internal memory, as in change partition sizes, of these devices.
Click to expand...
Click to collapse
thanks man, you have skype?
and if i want i can downgrade cwm after update?
eran32 said:
thanks man, you have skype?
and if i want i can downgrade cwm after update?
Click to expand...
Click to collapse
Sorry, no Skype for me. Yes you can downgrade CWM but I wouldn't advise it unless you are going to go back to an older version of Android.
shinobisoft said:
Sorry, no Skype for me. Yes you can downgrade CWM but I wouldn't advise it unless you are going to go back to an older version of Android.
Click to expand...
Click to collapse
thanks man, so if i want to install kitkat i'm need to :
1. Update cwm
2. Reboot Into Recovery
3. Do A Full Wipe (Wipe Data + Wipe Dalvik Cache + Wipe Cache partiton + system format)
4. Flash The Rom
5. Flash gapps
6. Reboot
thats fine to do it?
eran32 said:
thanks man, so if i want to install kitkat i'm need to :
1. Update cwm
2. Reboot Into Recovery
3. Do A Full Wipe (Wipe Data + Wipe Dalvik Cache + Wipe Cache partiton + system format)
4. Flash The Rom
5. Flash gapps
6. Reboot
thats fine to do it?
Click to expand...
Click to collapse
I would make a backup of my current ROM with my current recovery before proceeding. After that it sounds like you've got the steps figured out
shinobisoft said:
I would make a backup of my current ROM with my current recovery before proceeding. After that it sounds like you've got the steps figured out
Click to expand...
Click to collapse
fine, but i have cm7 install on sd card
you say that im can downgrade cwm
and if im got brick im can fix it
and to update i'm need to flash the zip?
eran32 said:
fine, but i have cm7 install on sd card
you say that im can downgrade cwm
and if im got brick im can fix it
and to update i'm need to flash the zip?
Click to expand...
Click to collapse
The backup statement I made was just a precaution. It's better to be safe than sorry.
I don't understand why you want to install CM11 and then downgrade your recovery. That makes no sense to me. Any flashable zips that need installed will also need the same recovery. CM11 added some new and reworked commands to the scripting language used to install flashable zips thru recovery. That's why you need to upgrade recoveries.
shinobisoft said:
The backup statement I made was just a precaution. It's better to be safe than sorry.
I don't understand why you want to install CM11 and then downgrade your recovery. That makes no sense to me. Any flashable zips that need installed will also need the same recovery. CM11 added some new and reworked commands to the scripting language used to install flashable zips thru recovery. That's why you need to upgrade recoveries.
Click to expand...
Click to collapse
im install cm11 and all working
but the Cellular Network not working

Categories

Resources