Is it possible to go straight back to stock using ODIN or do I need to remove voodoo first?
Voodoo must be gone. Or you will have even bigger problems.
There is a sticky on removing voodoo.
good day.
Thanks! I was afraid of that. Oh well, fresh slate...
Voodoo overwrites what's called your MBR with a new partition table. The odin restore files expect the old partition table. You need to remove voodoo first, try the manual method if you're having problems with the automatic uninstaller.
wizang said:
Voodoo overwrites what's called your MBR with a new partition table. The odin restore files expect the old partition table. You need to remove voodoo first, try the manual method if you're having problems with the automatic uninstaller.
Click to expand...
Click to collapse
Thanks for the info!
And from reading the voodoo removal thread, there's no way of removing it without wiping data, correct?
Related
excuse me,i have a problem.
i want flash my galaxy with rom m5 but i must unlag the phone before flashing?
thank you
I think you *should* do it. However i'm not certain about it..
No, you don't have to unlagfix it... you can if you want to, but a full flash will format the internal memory before rewriting
Last time I flashed my phone, I didn't unlagfix it. Works fine. No problem encountered.
I flashed without removing the lagfix by RyanZA. Odin got stuck on the first attempt. Had to remove the battery to switch off the phone and start the process again, then it went fine. Doubt that had anything to do with the lagfix anyway, just Odin having trouble.
I'm guessing that at the second time you selected "repartition" in Odin, right?
That would undo some partition possibly made by lagfixers
Phk said:
I'm guessing that at the second time you selected "repartition" in Odin, right?
That would undo some partition possibly made by lagfixers
Click to expand...
Click to collapse
Lagfixes don't make any partitions. So no.
RyanZA said:
Lagfixes don't make any partitions. So no.
Click to expand...
Click to collapse
Sorry RyanZA, you'd know that better than anyone I'm still confused about some tweaks that lagfixers do.
BTW, your oneclick is great, keep it growing and getting better =)
cheers
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Jeff5886 said:
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Click to expand...
Click to collapse
Jeff,
See this post for returning to stock http://forum.xda-developers.com/showthread.php?t=782204. I would do this as a last resort only.
Good Luck!
that is what got me to this problem. there are multiple files there what one do i use?
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
I was having the same issues with USB cable looking like it was plugged in so I couldn't reboot unless it was plugged. I tried the voodoo uninstall and screwed up my data partition.
I ended up restoring the CWM_Kernel and Di01 Stock update which brought me back to stock with root and OTA update from Verizon BUT my Data partition is screwed and I have no internal app memory. Also, I have an Nandroid backup that I tried to install but that causes the FC issues that you mentioned. My guess is that my nandroid backup will work once I fix the data partition.
Later tonight, I'm going to try to put the stock MBR back onto the phone which I think you need to do as well.
However, it sounds like you didn't complete the whole recovery process and only applied one file. I'm an android newby so you can't take my advice to the bank but I think you need to restore all the files if you're going to flash with Odin per those instructions.
For me, I had CWM loaded so I just wiped the kernel and put back the DI01 ROM which put me back to stock albeit with some work to do to get my data partition back in shape. I hope this helped, for what it's worth.
Since you've already got the original.mbr copied and the stock.zip flashed...
Boot into CWM recovery and wide data/cache.
If you have a CWM backup of your phone in a rooted state, restore that backup through CWM.
Reboot, and go into "settings" if possible at this point, and factory reset.
This got me back from market failure/0.00/fc hell after utterly failing to heed the voodoo warnings and trying to revert to stock without undoing the lagfix.
You'll likely need to use the unsigned d101 apk if your backup/flash is dh12. The OTA update did not work for me at that point.
phispher said:
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
Click to expand...
Click to collapse
My question is do i use the phone. pda or csc buttons for these files?
Ok in Odin use the PDA button for the /system
but what button do i use in odden to load the kernal.tar and recovery.tar
i loaded the pit, and installed all the files using the pda button one after the other. now my phone get no service and it still isnt wiped. what is going on? how do i get the phone back to out of the box condition.
also, now i cant do a factory wipe/reset, im getting the error message Can't mount /dev/block/mmcblk0p1
Gotta do the mbr fix from the 0.00 internal memory topic and then restore nandroid recovery.
Oh, and it is PDA for all three files, not just system.
Sent from my SCH-I500 using XDA App
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
trapstarr56 said:
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
Click to expand...
Click to collapse
Use the uninstaller form Here:
http://forum.xda-developers.com/showthread.php?t=804784
If that does not solve it, follow the steps here:
http://forum.xda-developers.com/showthread.php?t=782204
Read all pages of each topic completely prior to initiating *either* of them.
So I just got my Fascinate and have rooted it, installed clockwork mod and worked on flashing a couple of roms. But here is the thing, when I flashed a ROM on my old Incredible, it was always starting brand new unless I was doing a restore on clockworkmod. Well, the Fascinate seems to be different. When ever I flash a ROM, All of my apps, are still there with out doing a Titanium back up, all the Verizon apps are still there even though the ROM creaitor said they weren't there. I know the rom flashed, because I have the vanilla lock screen. Is this the way the Fascinate is or do I have a funky phone?
do you erase data or have voodoo installed?
bomber889 said:
do you erase data or have voodoo installed?
Click to expand...
Click to collapse
Yes, I do have Voodoo installed via the Kernel I am running. Is Voodoo causing this to be different then my Dinc? I also do a full wipe of everything before flashing a new rom or restoring an old one.
sonar_chris said:
Yes, I do have Voodoo installed via the Kernel I am running. Is Voodoo causing this to be different then my Dinc? I also do a full wipe of everything before flashing a new rom or restoring an old one.
Click to expand...
Click to collapse
You should read up in the voodoo threads. There's some different steps to take when running it.
I know voodoo works great for some, but it has been one of the worst things I've ever done to my phone. Constant freezes, reboots, shutoffs, force closes, etc.
I've decided to remove it. I've read over and over, but I'm still a little scrared. I plan on using the automatic uninstaller found in this thread:
http://forum.xda-developers.com/showthread.php?t=804784
First of all, how do I know if I have voodoo4? I downloaded voodoo from the thread on here (where it says v0.2) about 2 months ago.
Now on to the questions:
1. Do I have to disable voodoo before completely removing it?
2. I don't understand the steps of the auto uninstaller. They seem basic, but I want to make sure I understand correctly. First it says "boot clockwork, apply uninstaller." Does this simply mean go to "install zip from sd card" in clockwork and install it?
3. And what does this mean: "Wipe data from stock recovery. Apply CWM. Wipe data from clockwork." Well, I know what it means, but how do we wipe data from stock recovery and clockwork? And what does it mean "apply CWM."?
Thanks for any help.
jbrdr985 said:
I know voodoo works great for some, but it has been one of the worst things I've ever done to my phone. Constant freezes, reboots, shutoffs, force closes, etc.
I've decided to remove it. I've read over and over, but I'm still a little scrared. I plan on using the automatic uninstaller found in this thread:
http://forum.xda-developers.com/showthread.php?t=804784
First of all, how do I know if I have voodoo4? I downloaded voodoo from the thread on here (where it says v0.2) about 2 months ago.
Now on to the questions:
1. Do I have to disable voodoo before completely removing it?
2. I don't understand the steps of the auto uninstaller. They seem basic, but I want to make sure I understand correctly. First it says "boot clockwork, apply uninstaller." Does this simply mean go to "install zip from sd card" in clockwork and install it?
3. And what does this mean: "Wipe data from stock recovery. Apply CWM. Wipe data from clockwork." Well, I know what it means, but how do we wipe data from stock recovery and clockwork? And what does it mean "apply CWM."?
Thanks for any help.
Click to expand...
Click to collapse
You likely have voodoo4 if you downloaded it from here in the thread with 0.2 in it.
1. You should try to disable voodoo first to get rid of it. Create the disable_lagfix file and reboot. If it disabled properly, you should just be able to flash a non-voodoo kernel and be done. This doesn't always work though, so be sure voodoo is disabled before flashing another kernel.
2. That is what it sounds like you do. I've never used the auto-uninstaller, but that is what I would do based on that instruction.
3. I believe there is an option in both CWM and also stock recovery to wipe the data partition, essentially taking your phone back to it's factory state. What you'd do is perform the wipe in both the stock recovery and within CWM. Prior to the new voodoo and the permanent CWM flash, you would have to boot to stock recovery, and then apply update.zip to get to CWM as CWM is/was a flashable zip file.
Thanks for helping out. I'll go ahead and disable this right now (I have a app that enables/disables voodoo...got it here from xda). I'll wait for other replies before I attempt to completely remove it.
anyone else?
If it disables properly with the disable_lagfix file, all you should have to do to remove it after you're done then is flash a new, non-voodoo kernel and you should be ok. If it doesn't disable, that is where the thread on completely removing voodoo will be needed.
Yes, it is disabled successfully, but I didn't know all we had to do is flash a kernel over it once it's disabled? Can I flash the stock kernel over it?
jbrdr985 said:
Yes, it is disabled successfully, but I didn't know all we had to do is flash a kernel over it once it's disabled? Can I flash the stock kernel over it?
Click to expand...
Click to collapse
Yes, once it is disabled, assuming it disabled properly, you can flash whatever kernel you want over top of it. I would be sure to perform a full backup before doing any flashing though just in case.
But would doing that completely get voodoo out of my phone and not just disabled? I want it out of my phone...hate it.
EDIT: So I guess I'm using the stock kernel now since voodoo is disabled? I guess if it doesn't affect anything on my phone (like when updates come, etc.) then I can leave it in there and just keep is disabled.
Anyone? I want to install DJ05 and it says voodoo needs to be completely removed.
jbrdr985 said:
Anyone? I want to install DJ05 and it says voodoo needs to be completely removed.
Click to expand...
Click to collapse
When I put DJ05 on my phone, I just disabled Voodoo, didn't totally uninstall it.
The OP says to completely remove it though. I don't know if I should take the chance.
jbrdr985 said:
The OP says to completely remove it though. I don't know if I should take the chance.
Click to expand...
Click to collapse
Like I said, I didn't completely remove voodoo, I disabled it, flashed the DJ05 modem, kernel, and rom, and my phone booted fine.
Some things essential to understand before ever putting a voodoo kernel on your phone:
A filesytem is a template for organizing data on a disk, drive, sd card, ram etc. coupled with rules for managing that data [into files]
Samsung installed a dubious file system on Galaxy S phones called RTS (very similar to Microsoft's FAT32).
Stock, custom, and voodoo kernels all recognize RTS, a big advantage, despite its stigma of being laggy.
Voodoo circumvents the RTS lag issue by replacing it with a (fairly simple, but speedy and proven) linux native filesystem (colloquially referred to as 'the lagfix'). Voodoo also provides other speed optimizations.
Only kernels designed to work specifically with voodoo recognize the filesystem it adds. This means that other unaware kernels cannot read the optimized filesytem properly, or worse may corrupt the data stored therein.
-----
This is why if (when!) you switch to a voodoo unaware kernel (always assume unless otherwise stated), you MUST disable the 'lagfix' first!
If you do not, then you need a more advanced understanding of things like the MBR. Expect to lose data either in the transition, or from simple corruption.
Swyped w/ XDA App. BH 2.2 1212nv
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
CalabiYau said:
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
Click to expand...
Click to collapse
You have to do a clean install. With Odin, pit 512, Re-partition and the 3 files. I advise to wipe data and factory reset before flashing.
You should restore the backup titanium applications, but only the applications carefully restored, not the data. JPY to return to the same but now flashing the JPY. If you have any lagfix enabled is recommended to disable it before doing anything. In Spain we say "better safe than sorry."
But then if i go to jvp I'll loose the chance to go back easily to JPY??
I mean that installing cleanly JPY again.,.......
Hello,
went through this today (from JVP back to CWM backup of JSD, never used repartition, flashing tool = heimdall), ran in some problems as I thought that the Gingerbread bootloaders work for Froyo,too (I think I read that somwhere here at XDA).
1) Tried flashing Froyo kernel (speedmod) only and restored CWM-Backup of JSD after factory reset/cleared cache and dalvik cache -> did not work, booting stopped at SGS logo without progress for a really long time (longer than recreating dalvik cache used to last).
2) Flashed a complete self-made JSD-ROM including bootloaders and then installed CWM backup of last running JSD system (again, after factory reset, dalvik & cache clearing) -> worked fine, no problem for hours now.
Maybe I did something wrong at first try, maybe needed the correct bootloaders - don't know.
Hope this helps you a little bit - recreating running system from CWM *full* backup including apps and settings finally worked for me, data on sdcard and external_sd will not be touched (unless you format internal sdcard which is /sdcard directory).
Edit: Be sure to have a copy of your full CWM backup on your harddisk so in case something goes totally wrong you can restore the backup to your SGS recovery, the backups are saved in /sdcard/clockworkmod/backups/)
Yes, I guess this should work. A clean JPY installation, then CWM and then restore...
By the way, we did you go back to JSD??? JVP was faulty??
No, believe me or not, I somehow "feel better" with JSD, JVP made absolutely no problems here, it felt very fast, stable, without (for me) noticable errors, no battery drain.
Maybe I'll try 2.3.4 again in some weeks as I like experimenting with Linux/Android in general but for now JSD is my choice. Only real advantage (again, for me, maybe you don't need this) of Froyo/JSD is that I can reenable logcat using speedmod recovery tweaks.
I use this as a reliable root back to Froyo from custom roms or gingerbread. Not failed me yet. I keep plenty of backups so touch wood, no fowl ups yet.
http://forum.xda-developers.com/showthread.php?t=1100906
are you using the Stock ROM ?