Voodoo questions-Which Version - Vibrant Q&A, Help & Troubleshooting

I had simplyhoney 2.8 rom and when i tried to upgrade to 5.1 got a voice telling me to convert data partitions and not enough room. Doing a search lead me to voodoo being the cause, maybe. I have unbricked my phone with odin flashed stock rom, flashed simplyhoney 5.1 same error. Reflashed back to stock cleared cache and data, wipe data and factory reset still 5.1 wont load, still i have voodoo files.
From what i have been reading there are different ways to uninstall voodoo based on your voodoo version. I dont remember installing it so i dont know what version i am on. I do have a voodoo folder and in my base directory and i have like 4 voodoo files some really big.
I have tried the disable_voodoo file trick but i want voodoo gone! I dont understand how to do this? When i flash back to stock guides say to clear your files i thought i selected that but my voodoo folders and files remain. Does anyone have any idea how to remove voodoo.
Can they tell me what needs to be selected in CWM???? Which options the exact wording?
I am pulling my hair out!!!

Just get into recovery and disable voodoo. Reboot the phone and it will boot right up. Then if you want, let it sit for few minutes and get back into recovery and enable voodoo and reboot. This time it should convert your partition properly.
You have red recovery right? Disable voodoo option should be in o lagfix options. You can also make a blank file named disable-lagfix and put it in voodoo folder on your sdcard and reboot. That would also disable voodoo. File should have no extension of course.

red recovery right? Whats that?
I looked in CWM in there boot menu and i see the Voodoo section, it is set to disable and not to turn on at next boot. If its disabled then it wont effect flashing ROMs right?

dpelletier said:
red recovery right? Whats that?
I looked in CWM in there boot menu and i see the Voodoo section, it is set to disable and not to turn on at next boot. If its disabled then it wont effect flashing ROMs right?
Click to expand...
Click to collapse
Red Recovery is Voodoo
Blue is Stock
Green is CWR
Turquoise is CM7/ICS flavors
Also the large files on your SD card that are something like .tar.lzo or whatever they are named, you can delete those. That is a backup created when the lag fix was initiated. They take up unneccessary space on your SD card and aren't needed for anything.

Related

[Q] voodoo removal scenario

i just wanted to make a scenario just so i can get this proper procedure down.
lets say, i just installed bionix 1.4 with JAC kernel and the voodoo lag fix.
a month or so later bionix 1.6 has just been released, and i want to upgrade
first thing i do is jump on my file manager and go to the voodoo folder and rename the "disablelagfix" file to "disable lagfix" , this way i can undo voodoo temporarily
then i go into recovery and flash the new rom
after it completely boots i go back to the file manager and rename that "disable lagfix" file to something else
reboot to get new voodoo, and done?
right? or am i missing a few steps?
That's about it. Just make sure you reboot after creating the "disable lagfix" and before flashing. It'll be a long boot while Voodoo is disabled. Then you can upgrade.
Saiboogu said:
That's about it. Just make sure you reboot after creating the "disable lagfix" and before flashing. It'll be a long boot while Voodoo is disabled. Then you can upgrade.
Click to expand...
Click to collapse
Ok thanks
Ready to flash now I appreciate the help

[Q] Help a noob Vibrant hacker with some questions

My girlfriend has a Vibrant which is not hardware locked. I rooted and installed Bionix w/voodoo on Sept 28. I can't tell in her 'about phone' which version of Bionix she's running, but I believe it's 1.3, as the zip file I downloaded has 1_3 in the filename.
The first big problem I have is that nandroid does not work. If I try to restore to her stock backup I made, it gets an error when trying to mount data. Same error if I try to make a backup of the Bionix ROM. What am I doing wrong? Until I have her phone properly hacked I was just going to keep a backup of her phone and let her use that in the meantime, but can't do that now.
I am familiar with Android and clockwork as I've owned a Droid for half a year and flash new ROMs frequently but I've never encountered that error before. I want to install the new Bionix but without being able to make a backup I don't want to. I don't think it will install properly without being able to mount data anyway. Can someone tell me what I'm doing wrong?
You have to remove voodoo in order to use clockwork.
Ok, I think I can handle that. Can someone explain to me why data can't be mounted with voodoo? Can I just delete the folder and flash the new ROM that includes voodoo?
Yeah in the bionix thread it says nandroid doesn't work with voodoo and shows how to disable it.
Sent from my SGH-T959 using XDA App
velocity92c said:
Ok, I think I can handle that. Can someone explain to me why data can't be mounted with voodoo? Can I just delete the folder and flash the new ROM that includes voodoo?
Click to expand...
Click to collapse
It takes the data, and moves it to a virtual ext4 that it creates, so when nandroid is trying to backup or restore it is looking for the data folders in the wrong place, so it does not work.
You need to follow the voodoo thread, you need to place the file in the voodoo folder, if you delete the folder it may cause you allot more issues, you must install it the way they say in the thread or you can softbrick the phone. And you cannot flash a new ROM with it installed or you again will mess up the phone. The only thing you can do is create the file, put it in your folder and restart the phone, let it do its thing, once it reboots then nandroid will work again.
Thread moved to Q&A.
Noob and hacker in the same sentence...interesting
Sent from my SGH-T959 using XDA App
Pasted in from the Bionix thread:
How-to Disable the Voodoo Lagfix:
1. Once again, you MUST disable the Voodoo lag fix in order to flash any other rom, kernel, or perform a nandroid backup. If you don't...well....lets just say I warned you.
2. Its simple. Create a folder on the root of your sdcard called 'Voodoo'.
3. Now, open notepad or something similar and save the blank file. Name it 'disable-lagfix'. This file cannot have any file extension, so remove it if it does.
4. Place your blank file into the 'Voodoo' folder you made on your sdcard.
5. In order to disable, simply power down your phone and power it back up.
6. FINISHED! You can now flash anything you'd like!
How-to Confirm Voodoo Lagfix is Disabled:
1. In adb shell or terminal type 'mount'
2. If it is disabled is should read '/dev/block/mmcblk0p2'.
3. If it is not disabled, it will read '/dev/block/mmcblk0p4'.
There is also a flashable .zip file that does this for you, if you care to search around and find it. Otherwise, the above will work fine. Once you disable Voodoo and confirm that it's disabled, you'll be able to backup/restore nandroid backups again.

HOW TO: Flash Voodoo Kernels and more... <LOOK HERE FIRST

Ok...I know this can be a complicated process if you run into issues...so here is a detailed how to...Make sure and READ thru the WHOLE post!!!!!
INSTALLATION INSTRUCTIONS:
1. ROOT, Flash CWM Recovery
2. Create a FULL nandroid backup
3. Download a kernel of choice - links below
4. Put the kernel on root of sd, or you can leave it in download folder, but DON'T rename the file
5. Boot into Clockwork MOD recovery (either from ROM Manager or manually- hold volume up and down at same time and press power button, then select "apply sdcard: update.zip"
6. In recovery select "Install zip from sd card"
7. Select "Choose zip from sd card"
8. Navigate to the kernel file and select it
9. Let it install, it will take a few minutes...screen will go weird (black with big blue letters) then take you back to recovery.
10. Reboot phone
IMPORTANT: THIS BOOT WILL TAKE A LONG TIME...MAY BE 5-25 MINUTES...WAIT IT OUT. DO NOT PULL BATTERY. EVEN IF IT IS AT A BLACK SCREEN WITH SOFT KEYS LIT UP, DO NOT TOUCH IT. YOU WILL HEAR FEMALE VOICE. THIS IS NORMAL.
11. Once phone boots, download SetCPU from market and set the slider to desired Max. Do not select "Set on boot" and use Conservative mode.
ENJOY!!!!!
KERNEL LINKS:
- jt1134 - [RELEASE] Voodoo (v0.2) ext4 lagfix for Fascinate! Now with AOSP boot animations!
- Dirrk - [KERNEL] Dirrk v01 Voodoo lagfix OC/UV - For Dirrk OC kernels, use the D012 kernels, not D01: D012 - Dirrk > Open the link>select my folder>the samsung and you will see the D012 kernels...
***If you are using jt1134 kernels with boot animation ability, here is how to add it. Find the boot animation you like, download it to your phone. Do not unzip it. Use Root Explorer or Astro File Manager and copy the bootanimation.zip file into either system/media or data/local. Reboot phone to test out.
HOW TO DISABLE VOODOO LAGFIX
1. Use Astro File Manager or Root Explorer app...open the app
2. Navigate to sdcard/Voodoo folder
3. Create a new blank FILE named disable_lagfix....NOT A FOLDER
4. Reboot phone
IMPROTANT: THIS BOOT WILL TAKE EVEN LONGER THAN THE INSTALLATION OF VOODOO KERNEL BOOT...AGAIN, WAIT IT OUT!!!!! DO NOT PULL BATTERY.
NOTE: IF YOU ARE RUNNING ANY OF VOODOO KERNELS, VERSION 0.2+, YOU CAN FLASH ANY OF THE VOODOO OC KERNELS OVER...INCLUDING JT'S OVER DIRRK'S AND VICE VERSA...IF YOU WANT TO GO BACK TO A REGULAR KERNEL, YOU MUST DISABLE VOODOO FIRST...ALSO IF YOU WANT TO CREATE A FULL NANDROID BACKUP AS WELL, YOU MUST DISABLE VOODOO LAGFIX. IF YOU BACKUP WITH VOODOO ENABLED, YOUR DATA WILL NOT BACKUP. IF YOU RESTORE YOUR NANDROID BACKUP, THE KERNELS ARE NOT RESTORED.
If you ran into trouble, start HERE:
- Adrynalyne - How to completely remove Voodoo Lagfix
- Odin Files to get you back to stock
VERY IMPORTANT:
-Battery issue can be because your phone is too hot...pull battery and let it cool down for 5-10 minutes...then boot up and see if its there.
-IF uninstalling v0.1, create a FILE in sdcard/voodoo and NOT a folder...
-Once uninstalled v0.1, DELETE the disable_lagfix file, before flashing v0.2...
-Boots take may FOREVER in between changes, especially after uninstalling.....WAIT it out. It may be 5 minutes, may be 15. Don't start pulling batteries and using Odin just yet.
-READ all instructions carefully and FULLY....
-And lastly, ALWAYS do a nandroid backup.
Wow. Great write up. Thanks a ton for this
Sent from my SCH-I500 using XDA App
I really hope this eliminates 99% of issues that people run into.
Nicely done. Concise and accurate
awwww man, if only this was posted this morning I wouldn't have called for a doa swap.. lol i thought my phone was fubar-ed earlier b/c of the oc kernel.. i finally got everything fixed the hard way by wiping and loading stock kernels.. that didn't work too well either.. long story short i got everything working but after i called for a swap and before this posted lol.. great post!
wish this was in place before i started flashing. lol. i had to learn the hard way. many flashes later i have learned what to do but this definately deserves a sticky so others dont have to go thru what luckly only took me a day to figure out but could have taken longer.
I've been running the 1200 kernal for a few days with no problems. I do have setcpu set to load on boot.....just curious if I should change it? And why? All seems OK.
Nice post, tats.
Kudos for a great, concise write up!
suzook said:
I've been running the 1200 kernal for a few days with no problems. I do have setcpu set to load on boot.....just curious if I should change it? And why? All seems OK.
Click to expand...
Click to collapse
Once you confirm that its completely stable even Dirrks says its OK to set on boot. You just wanna be 100% sure it is before you get caught in an endless boot loop. But yeah a couple days is long enough to ensure stability; go ahead and lock it in if you want
Is this rom and kernel really that much better than stock?
I guess I'm asking is battery life better and is the speed of the phone better with the lag fix??
I have Voodoo .2, and I set the bootanimation in both folders, both in system/media, and data/local, and the standard animation keeps playing anyway.
Anyone have any ideas ????
Bull174
Yes this kernel with voodoo is that much better. Voodoo isn't that BS one click lag fix. Its a real permanent solution." Basically" the same filesystem all other phones come with.quadrant can do 17-1800 which isn't inflated. Its what the galaxy can actiually do. And that just with eclair(2.1) battery life is the same. The phone will likely never lag on u again. And actually with a normal filesystem its prolly the fastest smoothest running phone out there. Would easily put the second generation snapdragons to Shame. If u try it u will be hooked. It is *VERY IMPORTANT* that before u flash any other kernels that u disable ur lagfix first. This can also be done easily with the app "voodoo toggle" in the market. If you like your phone now you will love it now. Take the plunge. You wont regret it. Just do your reading and follow instructions on how to install and remove voodoo to a T and you will be fine.
Sent from my SCH-I500 using XDA App
Wound up having to restore an old voodoo, the v. 0.2 standard clocking one, from a jt's 1.2 OC kernel. The restore worked fine, but I'm currently trying to disable in order to flash stock kernel and a clean ROM and then get voodoo back. The boot up has been going on for about an hour, heard to voice at the beginning and about 20 minutes in. How much longer will it take? I'm getting kinda nervous as I really don't want to have a bricked phone on my hands.
EDIT: It was about 2 hours and I pulled and went to go do an odin restore. The phone flashed PIT, system, kernel and recovery all successfully, I wiped everything from both clockwork and the blue 2e recovery screen, but now I can't access clockwork nor does the phone boot, however it does appear in adb. Does anybody know what I should do?
EDIT2: Reflashed all the files from Odin, got it to boot both into clockwork and pure stock. Gonna go flash a nandroid and get my setup back.
You can use the disable_lagfix as a folder, I have tried it and it works. Voodoo is looking for anything disable*lagfix so it works even with a dash, space, numbers...
I followed each and every direction to the last word, however I can't seem to overclock my phone. I installed the jt1334 kernel, but the max i can go is 1ghz (1000000mhz). help?
EDIT: In addition, I did both a linpack and Quadrant Standard test. my linpack score was "MFLOPS:8.142" and my Quadrant
Standard score is "950".... i don't understand what I did wrong as I see others have QS scores of 1600+ at least 1200+...
xsalientx said:
I followed each and every direction to the last word, however I can't seem to overclock my phone. I installed the jt1334 kernel, but the max i can go is 1ghz (1000000mhz). help?
EDIT: In addition, I did both a linpack and Quadrant Standard test. my linpack score was "MFLOPS:8.142" and my Quadrant
Standard score is "950".... i don't understand what I did wrong as I see others have QS scores of 1600+ at least 1200+...
Click to expand...
Click to collapse
Have you downloaded SetCPU? What are you using to overclock?
mexiken said:
I have Voodoo .2, and I set the bootanimation in both folders, both in system/media, and data/local, and the standard animation keeps playing anyway.
Anyone have any ideas ????
Click to expand...
Click to collapse
I have the same issue. I thought it was originally because I extracted the bootanimation.zip out of the downloaded file but renaming the original file didn't work either.
kupdegrove said:
I have the same issue. I thought it was originally because I extracted the bootanimation.zip out of the downloaded file but renaming the original file didn't work either.
Click to expand...
Click to collapse
If its just the voodoo 0.2 file, then boot animation wont work. It has to be the 1000_bootabimation kernel or the 1200_bootanimation one.
I actually fixed it somehow... I don't necessarily know what I did though. But thank you for your help!
Sent from my SCH-I500 using XDA App

[Q] Ghost of ROMs past haunts my Vibrant

I've been stuck in a weird place for some time with my phone. After I installed clockwork mod, backed up, installed some flavour of FroYo, and made the mistake of trying to flash back my old back up without properly wiping things have been getting weird. I can use ODIN to flash fresh ROMs, but I always get a bunch of FCs at startup, and most apps don't work. I tried to do all kinds of tricks to completely wipe the internal SD, but there is always some remnants of old fun hanging about causing cascading errors and FCs. No matter what I try to do, MyBackupPro and Rommanager is always present, but not working.
How I can completely rid myself of anything not stock ROM?
I've finally gotten back to root ADB, after a long and hard battle. I believe this may hold the key to salvation for my Vibrant.
Any and all suggestions are much appreciated!
Things I've already tried:
EUGENE373_SamsungS_Froyo_PDA -> Stock 2.1 T959UVJFD
EUGENE373_SamsungS_Froyo_PDA -> battery pull -> Stock 2.1 T959UVJFD
Stock 2.1 T959UVJFD -> EUGENE373_SamsungS_Froyo_PDA
Bionix1.9.zip - would not install due to some error I can't recall right now. Will update.
Factory wipe - from Settings menu
Wipe in Clockworkmod menu
Wipe all in adb shell
The weird *2767*3855#* factory wipe
UPDATE:
Strangest thing happened: I flashed an old ROM back onto the phone with Odin 1.52, then the Updated Stock 2.1 also via Odin the usual FC-ing was still there. Then I rebooted into recovery, reinstalled the Clockworkmod recovery menu, installed the root-update.zip in order to have root shell access. Then I pushed VibrantDeodexed1_2.zip and Vibrantfroyo_R3.zip on to the sd card. I tried to apply the VibrantDeodexed1_2.zip, but it aborted due to some catalog not present. However, I did notice that the installation erased /system and deleted some files, and I had the notion to try and install the VibrantFroyo_R3.zip. The installation succeeded, and Lo and Behold!
the phone has returned to the land of the living! Wohoo!!
I do not fully understand how this can be, but there is no Force Closing of programs any longer. What a relief!
Thanks to everybody who contributed ideas!
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Yea, when in doubt I thank the deities for Eugene and flash his "Froyo that doesn't brick" followed by the stock JFD firmware.
Sent from my SGH-T959 using XDA App
brnagndan said:
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Click to expand...
Click to collapse
Sorry to say, that trying this solved nothing. Just the same as before.
ullrotta said:
Sorry to say, that trying this solved nothing. Just the same as before.
Click to expand...
Click to collapse
You clicked the "repartition" option? That should format your internal sd...
I7oobie said:
You clicked the "repartition" option? That should format your internal sd...
Click to expand...
Click to collapse
Yeah, that's the weird part.. It doesn't really delete anything. Files are still there, and so are the un-wanted system files, too.
Does anyone know if I can manually partition the sdcard?
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
same thing happened to me >.> I just formatted the SD card on the phone. then flashed whatever rom I wanted.
Br1cK'd said:
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
When I boot into recovery, I always have to reinstall packages to get to the CWM recovery menu. I tried to clear everything from the mounts and storage submenu; I cleared system, cache and data, then flashed stock eclair. STILL the same applications and files sit on the internal SD.
When performing the wiping, all looks normal. It does take a little time, and the system reports that all is going according to plan, yet no files are deleted.
What can possibly make the phone act this way? Are there no super secret samsung-technician codes that allow me to completely wipe clean the face of the sdcard?
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
this has to be one of the most useful threads. just last night i was messing with rom manager and enabled advanced settings, BEEFORE reading this thread. I've done so much monkeying, but didn't keep a journal or log, so ive got **** from so many hacks and tweaks (mods and themes)...
thanks, im gonna wipe this ****er clean.
Good Info..but moved to Q&A
Br1cK'd said:
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
ullrotta said:
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
Click to expand...
Click to collapse
I was hoping that would help you friend, that process wiped mine clean of all remnants. Good luck in getting her back into a functional state.
After reading som more, contacting Samsung Service, I've decided to send the phone in for service. [sigh]
I've learnt a lot about ADB, pushing and pulling files, rooting, unrooting, swapping ROMS and whatnot. Still, the phone is stuck in that weird place where I cannot delete files.
Hopefully the service team can fix this poor, misguided phone

[Q] Ok..so I grew a pair and I'm rooted and backed up. (( update.zip question ))

I was in Clockwork Recovery after backing up my stock system (this is my first time) it gave me the options in green text: Reboot, reinstall update.zip, etc.
I chose reboot and everything loaded up fine and after checking in Rom Manager I have a backup of my system. I just want to know if that was the right choice. or should I have reinstalled update.zip
I guess my question revolves around update.zip.
What is that file? I know I originally used it to gain root access but do I need to reinstall it from clockwork recovery everytime before rebooting? and when should I delete it? and are there any negative consequences for not doing either?
As you can tell I'm a noob....but hey I can't believe I'm rooted and backed up at the moment. I'm gonna stop here before flashing any custonm roms and get this question answered first.
I think you are fine. I would not worry so much, i have deleted the update.zip, but since you booted up into ClockWork Recovery you are most likely fine.
I am booted back up completely and the stock os is running and I'm still rooted. I just want to know what that option inside of clockwork recovery means. What is the reason to reinstall update.zip from clockwork recovery and what is the reason to reboot? And once I'm booted back up and running when/why do I go into my files and delete update.zip?
It's not that I'm worried...I just want to know why I'm doing what I'm doing.
I would keep the file. Less chance of failure.
You are only going to use cwr for this:
Backup/restore system
Wipe cache, factory wipe, etc
Flashing rom's (install from sd card)
Don't worry about the other stuff.
I'm confused by the op, not sure how you made a backup from how it reads.
I think I made the backup by flashing into clockwork recovery from rom manager. It started with the purple text recovery mode and I hit reinstall packets. Then it went into the green text clockwork recovery....I think. I've only done it once.
So in clockwork recovery I choose the backup/restore option and then the backup option. So then the phone I assume began the backup process and displayed many lines of white text. At the very end it said something about not being able to mount my ext sd card (which) had me worried.....but then it brought up the menu again. The top option was reboot, the second was reinstall update.zip and I didn't pay attention to the rest because I was pretty sure I needed one of the first two....I just didn't know which one. I selected reboot and the phone then booted into the stock os and was still rooted. Is the fact that it wasn't able to mount my ext sd card at the end of the backup process an issue? I'm able to find a backup in rom manager. Also, if the backup process works correctly should the phone reboot by itself?
What I'm asking is what am I booting from when I choose "reboot" from clockwork recovery and what does it mean to choose "reinstall (packet?) update.zip"? I thought update.zip was what I needed to root.
This last step wasn't in your tutorial (purple text menu) so maybe something didn't go as it should have.
I'm not sure.
Thanks s15274n for the tutorial btw. Its by far the most helpful concise instructions I've found and is really appreciated.
Sent from my SGH-T959 using XDA App
The update.zip in the root of the internal SD card is clockwork recovery (CR). When you install CR it does not overwrite your phone's recovery. What it does is install that update.zip in the root of the SD card. When you want to use CR, you need to "update packages" which will flash that update.zip which contains the CR package. That will load CR into memory only and still does not overwrite the original recovery on the phone. When you reboot into recovery from ROM Manager, it automatically reboots and applies the update.zip and places you into CR. If you enter recovery manually (via buttons on boot), you will need to "re-install packages" from the stock recovery to get CR.
So if you want to use CR, keep that update.zip in the root of the SD card. If you erase it, you will need to re-install it (using ROM Manager) before you can use CR instead of the stock recovery. I hope that makes sense. If not, here is the explanation straight from Koush on how it works.
http://forum.xda-developers.com/showthread.php?t=734164&highlight=clockwork
^^ You are all good then.
The SD-EXT is not going to backup, because you do not have a partiotion on your external SD card (no need for one, like some other phones require). This is normal from what you described.
You will never use the apply update.zip option in CWR... just dont pay any mind to it.
When you select reboot system now, that is all it is.... you are basically saying "Cool, I did everything I needed to do (backup/flash a rom/wipe, etc)... and now I am ready to reboot my phone... ie, you are basically cutting your phone on.
Positive you did, but you can open rom manager, click on manage backups and you should see a file there that has a format kinda like YYYYMMDDTIME, that is the backup you made... no action needed, just an easy way to verify you made a backup of your system.
s15274n said:
I would keep the file. Less chance of failure.
You are only going to use cwr for this:
Backup/restore system
Wipe cache, factory wipe, etc
Flashing rom's (install from sd card)
Don't worry about the other stuff.
I'm confused by the op, not sure how you made a backup from how it reads.
Click to expand...
Click to collapse
Thanks s15274n
i have been wondering the same thing about the update.zip file whether to keep it or not.
Thanks s15274n for the tutorial btw. Its by far the most helpful concise instructions I've found and is really appreciated.
Click to expand...
Click to collapse
Also wanted to say i feel the same way. Appreciate the guide so much!
Thanks guys. I'm glad to have that cleared up so I understand it. Gives me more confidence to do the other things I want to do.
I got confused with the fact that I need to delete the update.zip file after rooting and the fact thats its there again after flashing cw and backing up.
Sometimes I need things spelled out for me. Makes complete sense now.
Sent from my SGH-T959 using XDA App

Categories

Resources