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
Related
So I tried installing the new ASOP rom, and was getting a bunch of force closes. I tried using CWM to revert to a previous backup, unfortunately the force closes continued in the backup. So I want into ODIN to get back to stock. I loading the stock files, did a factory reset, and everything seemed to be fine. However when I went into the market to reinstall appbrain and get my programs back, I kept getting an Out of Space error. I checked the internal memory and sure enough it says 0.00.
I've never installed Voodoo on my phone, because I was trying to avoid issues just like this one. I read over the a similar thread on this issue, but that fix isn't working for me. I tried to reroot, but the SU apk's don't have any place to go, since the phone says there is 0 internal memory.
Luckily I can still use my phone, but every time it turns off it resets, and I can't load my apps back on. Anyone got any suggestions?
The fix should still work for you. I would suggest flashing stock rom, kernel, pit, and cwmrecovery thru odin. After that you can follow the instructions posted on how to completely remove voodoo. Main thing is you need to get the original mbr to your phone.
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
ckochinsky125 said:
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hmm I read that part too, but if he follows adrynalyne instructions he should be fine. It is taking care of the same problem. Corrupted rfs. The op just achieved it in a different way. If that does not work for him then maybe some dev will be able to figure out another way to fix the problem.
I'd be curious to see mount results.
Run it from adb shell.
So the short story is I fixed my phone, from force close and zero memory hell.
I noticed when booting into recovery I was getting an error related to /dev/block/mmcblk0. I used the adb code to install the MBR file. Went in CWM and flashed the stock.zip kernel, restarted and got a ton of force closes. Went to the "How to escape the force close loop of hell" thread over at androidcentral, flashed the stock nandroid image, and someway, somehow the android gods took pity on my poor soul and my internal memory partition was restored.
I don't understand exactly how I fixed my phone, and I'm relatively new to this so I'm a little concerned. I'd like to learn from these mistakes, so does anyone understand what I did to fix my phone?
Sounds like it was the nandroid image that did it.
It is, effectively, the same issue the voodoo users have seen.
My "easy" fix was almost exactly the same as yours.
replace mbr, flash stock, revert to backup (which is basically what nandroid is).
I used my original CWM backup instead, and that worked for me. (I now have this stored on several drives/devices)
I also went back in to Root Explorer and nuked the "databases" folder in /dbdata and then wiped cache/data (CWM, then "settings"). Pretty much fixed it all for me.
Couldn't update to D101 for some reason after that, but the unsigned apk for that did the trick nicely. I suppose I'll have to retry the "odin to stock" bit if the 2.2 update fails the same way on me. Not looking forward to that one...
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?
For all those saying that my instructions are redundant.
Please follow all instructions!
I understand that Nero v3 wipes your data and caches for you, but there has been many cases where it has not done that, and users have really messed up their phones. Please take the extra 30 seconds and wipe it manually to be safe.
As far as the Voodoo step. I undertand that when deleting the "disable-voodoo" file, that it will automatically enable Voodoo for you on the next reboot. However, there are also cases where this didn't happen. Please check to ensure.
My instructions may seem redundant to users who have done this a lot.....but this isn't for those users. Please follow the steps exactly to help avoid ANY problems, don't just assume everything works automatically like it's supposed to. Might as well take the extra 2 minutes to do all of my steps, then 2 hours arguing with T-Mobile as to why they won't exchange your bricked/modded phone.
STOCK 2.1 to NERO V3....SIMPLE AND SAFE!
First of all, thank you Team Whiskey for Nero v3. To everyone wanting Nero v3, but are tired of seeing all the confusing and long tutorials:
1. Ensure your phone is rooted (Google z4root if your not).
2. Download ROM Manager
3. Flash the 2.5.1.2 ClockworkMod Recovery
4. Download Nero v3 from a computer, and Drag-n-Drop the .zip file onto your Vibrant SD card.
5. Restart your phone in CWM Recovery via ROM Manager
6. Click "clear cache", and "wipe data", click Advanced, click "clear Davlik cache", click "install from SD", click "install a .zip from SD", then install the Nero v3 .zip
7. Reboot, WAIT 15 MINUTES WITHOUT TOUCHING YOUR PHONE...REBOOT AGAIN... and you should be good.
8. To enable voodoo, open SD card from phone, delete "disable_voodoo" under the voodoo folder, reboot to recovery (NOT FROM ROM MANAGER, BUT FROM THE HOME SCREEN USING THE POWER BUTTON, THEN SELECTING RECOVERY) (SHOULD BE A RED RECOVERY), goto voodoo lagfix, press enable, then reboot....REBOOT WILL TAKE AROUND 10 MINUTES, DO NOT TOUCH YOUR PHONE!
FOLLOW STEPS CLOSELY
P.S. Don't Forget the THANKS button.
Looks nice, concise, & noob friendly (I should know).
Kudos.
Nero 4 using XDA app (j/k)
thanks!
this video helped me too
http://www.youtube.com/watch?v=33I-aNCypVM
troby86 said:
6. Click "clear cache", and "wipe data", click Advanced, click "clear Davlik cache"
Click to expand...
Click to collapse
I didn't do this part when I flashed NeroV3 because the instructions I read didn't mention that. Did I cause myself a problem that I just don't know about yet?
trunkstar1 said:
I didn't do this part when I flashed NeroV3 because the instructions I read didn't mention that. Did I cause myself a problem that I just don't know about yet?
Click to expand...
Click to collapse
If the install worked you should be fine. This is just a good precaution.
troby86 said:
If the install worked you should be fine. This is just a good precaution.
Click to expand...
Click to collapse
Should I do that now? What does that even do?
troby86 said:
First of all, thank you Team Whiskey for Nero v3. To everyone wanting Nero v3, but are tired of seeing all the confusing and long tutorials:
1. Ensure your phone is rooted (Google z4root if your not).
2. Download ROM Manager
3. Flash the 2.5.1.2 ClockworkMod Recovery
4. Download Nero v3 from a computer, and Drag-n-Drop the .zip file onto your Vibrant SD card.
5. Restart your phone in CWM Recovery via ROM Manager
6. Click "clear cache", and "wipe data", click Advanced, click "clear Davlik cache", click "install from SD", click "install a .zip from SD", then install the Nero v3 .zip
7. Reboot, WAIT 15 MINUTES WITHOUT TOUCHING YOUR PHONE...REBOOT AGAIN... and you should be good.
8. To enable voodoo, open SD card from phone, delete "disable_voodoo" under the voodoo folder, reboot to recovery (NOT FROM ROM MANAGER, BUT FROM LAUNCHER) (SHOULD BE A RED RECOVERY), goto voodoo lagfix, press enable, then reboot....REBOOT WILL TAKE AROUND 10 MINUTES, DO NOT TOUCH YOUR PHONE!
FOLLOW STEPS CLOSELY
P.S. Don't Forget the THANKS button.
Click to expand...
Click to collapse
Boot to recovery from power button/phone options,to get to red recovery.
amandadam said:
Boot to recovery from power button,to get to red recovery.
Click to expand...
Click to collapse
Glad you mentioned that, I need to ask, what's the difference between the green recovery and the red recovery?
trunkstar1 said:
Glad you mentioned that, I need to ask, what's the difference between the green recovery and the red recovery?
Click to expand...
Click to collapse
The green is the default CWM recovery, the red includes the Voodoo lag fix options
Just removing the file turned on voodoo for me.
Sent from my SGH-T959 using XDA App
So glad this thread was made. Its retard easy to flash this rom and get voodoo to work (it was my first and I have this opinion, which should speak volumes), I really can't believe the amount of people in the thread that just couldnt figure it out.
What do you recommend for backup/restore of apps and data? Will EVERYTHING get restored? I spent a lot of time configuring my home screen with folders and apps. Can that be restored?
Lastly, if I decide to go back to stock JI6 and my original setup, is there a relatively easy way to do that?
Thanks.
Titanium backup will backup all your apps and such, but to get your home screen back I'm pretty sure you just have to do it manually. I know that sgs tools lets you backup your home screens but I'm not sure if it will work across roms or not, you could try it, at worse it will give you an error message and just make your home screens all blank (well really at worse you have to reflash).
Titanium managed to back up my homescreen settings, both for TouchWiz and for Launcher Pro.
EVERYTHING (all my text messages, internet history, bookmarks, etc.) was exactly like before, but in Nero instead of stock.
trunkstar1 said:
Should I do that now? What does that even do?
Click to expand...
Click to collapse
Nero v3 already forces wiping data and cache. The instructions are redundant, no need to worry about it.
cyberbillp said:
Just removing the file turned on voodoo for me.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That's really all "enable Voodoo" in green CWM recovery does. The step is redundant as well.
The fastest way is after you flash the Nero V3.zip and reboot, hold down the volume and power buttons to go back into the recovery menu before anything even loads. Enable voodoo here, as theres little data it will need to convert to voodoo. Then once you boot into android, everything it writes from here on out will be ext4. If you load up android first, it'll have to go back and rewrite all the data you just created to the new file system, taking longer.
For all those saying that my instructions are redundant.
Please follow all instructions!
I understand that Nero v3 wipes your data and caches for you, but there has been many cases where it has not done that, and users have really messed up their phones. Please take the extra 30 seconds and wipe it manually to be safe.
As far as the Voodoo step. I undertand that when deleting the "disable-voodoo" file, that it will automatically enable Voodoo for you on the next reboot. However, there are also cases where this didn't happen. Please check to ensure.
My instructions may seem redundant to users who have done this a lot.....but this isn't for those users. Please follow the steps exactly to help avoid ANY problems, don't just assume everything works automatically like it's supposed to. Might as well take the extra 2 minutes to do all of my steps, then 2 hours arguing with T-Mobile as to why they won't exchange your bricked/modded phone.
everything was easy and i did it no problem EXCEPT when i'm in cwm recovery trying to install zip, nero doesn't appear which is weird especially since i know its on the root of sd card. even when i use phone to check files nero appears, just not in recovery. any ideas how to find a solution?
erhan82 said:
everything was easy and i did it no problem EXCEPT when i'm in cwm recovery trying to install zip, nero doesn't appear which is weird especially since i know its on the root of sd card. even when i use phone to check files nero appears, just not in recovery. any ideas how to find a solution?
Click to expand...
Click to collapse
If you have a lot of stuff in the root then you'll need to scroll pasted the bottom. Like just keep scrolling down and once you see the ++go back++ then you're at the bottom. I just had this issue flashing nero v4.1.
Hi, well i've had this phone little over a week and have only just got into the whole process of rooting so in some terms i'm a bit of a noob.
I'm not going to lie, the satisfying feeling of rooting my phone and learning ADB and using SDK manager was pretty good, and I've successfully rooted my phone and overclocked it,
However now i'd like to install a more update custom rom and this seems to be the right one, the Virtuous Sense as its basically the most recent update without the crap i feel. Link
My question is however on how to install this custom rom and the process of it, at the moment i'm running a rooted 1.34 stock rom i think on the htc desire z and i'd like to update it, I've made a Nandroid backup using astro file manager and backed up my apps and contacts are backed up online,
is the process of flashing a new rom as simple as downloading the zip file, placing it on my sd card and using the recovery bootloader and installing it from that?
I'd just like to ask if i'm missing out any crucial steps here or if there's any tips you guys would like to share or any other custom roms you feel are better than the one i've chosen.
On a final note, i'd like to say this forum has amazing help and guides which have helped me so far,
Thanks!
If you don't already have it, download ROM Manager from the Market.
Astro just backs up app data right? That's not a nandroid. A nandroid is a full backup of the whole OS and all your data. You can do this wtih Clockworkmod, which is included with ROM Manager. Open ROM Manager, and pick the option to flash Clockworkmod.
I haven't used Astro to backup my apps, many people use Titanium Backup. But I assume the backup in Astro is similar. You should also backup SMS and email (other than Gmail) if you want to keep those, as those will also be wiped.
Flashing a ROM is a a breeze with ROM Manager. You can get Virtuous right on the ROM Manager app itself, and just flash from there. Really, rooting is 95% of the work, flashing a custom ROM is a breeze.
When you go to flash a ROM in ROM Manager, it will give you the option to backup your ROM (nandroid), so select that. It will also give you the option to wipe, which you should also select. Then ROM Manager will just do the rest.
If a certain custom ROM you want is not included in ROM Manager, just copy the zip for the ROM to your SD card. Pick the option in ROM Manager to install a ROM from SD card. Then select the zip, and the rest is same as the paragraph above.
You MIGHT be able to get away with not wiping your data, since stock DZ ROM and Virtuous are very similar ROMs. But it may also cause some random bugs, requiring you to wipe data and re-flash. In general, follow the instructions in the thread for the custom ROM you want, regarding whether a data wipe is needed. Usually, you can avoid a data wipe if you are staying on the same custom ROM, but a newer version. But a full wipe is the safest bet. You should always wipe cache and dalvik (you can wipe those in Hboot).
redpoint73 said:
If you don't already have it, download ROM Manager from the Market.
Astro just backs up app data right? That's not a nandroid. A nandroid is a full backup of the whole OS and all your data. You can do this wtih Clockworkmod, which is included with ROM Manager. Open ROM Manager, and pick the option to flash Clockworkmod.
I haven't used Astro to backup my apps, many people use Titanium Backup. But I assume the backup in Astro is similar. You should also backup SMS and email (other than Gmail) if you want to keep those, as those will also be wiped.
Flashing a ROM is a a breeze with ROM Manager. You can get Virtuous right on the ROM Manager app itself, and just flash from there. Really, rooting is 95% of the work, flashing a custom ROM is a breeze.
When you go to flash a ROM in ROM Manager, it will give you the option to backup your ROM (nandroid), so select that. It will also give you the option to wipe, which you should also select. Then ROM Manager will just do the rest.
If a certain custom ROM you want is not included in ROM Manager, just copy the zip for the ROM to your SD card. Pick the option in ROM Manager to install a ROM from SD card. Then select the zip, and the rest is same as the paragraph above.
You MIGHT be able to get away with not wiping your data, since stock DZ ROM and Virtuous are very similar ROMs. But it may also cause some random bugs, requiring you to wipe data and re-flash. In general, follow the instructions in the thread for the custom ROM you want, regarding whether a data wipe is needed. Usually, you can avoid a data wipe if you are staying on the same custom ROM, but a newer version. But a full wipe is the safest bet. You should always wipe cache and dalvik (you can wipe those in Hboot).
Click to expand...
Click to collapse
thanks for the help, one quick question though, i've overclocked and used set cpu on the rom with the kernel they specified, though when my phone's display is off, and i click the power button, the buttons at the bottom of the screen turn on but the display stays off, is there a fix for this?
edit: redpoints advice sounds a lot more competent to me, so I would go with that.
(This sounds like a common issue that occurs when you specified a screen off profile in set cpu. If you have it set up so that the cpu is underclocked while the screen is off, it won't wake up since it doesn't have enough power.
Even though this hasn't happened to me before, I've read that the issue will disappear if you raise the clock from say 245mHz to 368mHz.
Hope this will help.)
That is a known issue with the Virtuous Advanced kernel. So I assume this is the kernel you flashed. The Advanced kernel is only needed if you want to overclock greater than 1 GHz. The kernel that is included with the Virtuous ROM is already OCed to 1 GHz by default (no kernel flashing required).
But since you have already flashed the Advanced kernel, the fix is to use screen-off profiles in SetCPU. I believe the fix is to make a screen off profile with "interactive" as the governor, and that's it. But its well covered under the Virtuous kernel thread, so you can check there.
http://forum.xda-developers.com/showthread.php?t=967153
From what I recall, what is happening is the CPU is scaling up too fast when you wake the phone, and using up too much voltage, preventing the screen from waking.
thomas_wlc said:
This sounds like a common issue that occurs when you specified a screen off profile in set cpu. If you have it set up so that the cpu is underclocked while the screen is off, it won't wake up since it doesn't have enough power.
Even though this hasn't happened to me before, I've read that the issue will disappear if you raise the clock from say 245mHz to 368mHz.
Hope this will help.
Click to expand...
Click to collapse
This might work too. A few different possible solutions were given in the Virtuous kernel thread. The one I think worked for me (when I was on Virtuous) was a screen off profile with interactive governor, and that's all.
Underclocking the CPU while the screen is off is unnecessary. The CPU does that automatically, anyway.
Just got a GTab 2 7.0 a few days ago. A P3113, so only 8GB of storage, about half of which is the ROM and crap apps. I've rooted before (had a KF 1st gen when it came out), and just wondering about a few things with the GTab:
Right now, I don't mind the stock ROM so much. There are problem things that would be "nice to have", but right now, would like to generally stay as "stock" as possible. That being said, I'd still like to "de-crap" the ROM to free up some storage space, and I assume that might lead to it running a bit better, since so much seems to just pop-in while running other apps. So:
I know I need to root first, so my first question - how reliable is that? I'm on a Mac, but have access to a netbook running Win7, so could run Odin to "get things done". I'd hate to brick the thing, still having 51 weeks of warranty left. (I also understand that I might want to install something else to keep the flash count from showing it's been flashed).
Once root'ed, is it better to use one of the "de-crapped" ROMs floating around? And if so, which seems "best" (yeah, I know the moderators hate the "which is best" - I'm looking for stock - and STABLE)
Or, is it better to eliminate the apps myself? (Not sure if this is a wholesale "rm" to remove certain apps from a terminal app, using adb, or if they have some uninstallers embedded somewhere, or...) - so better to use one of the ROMs floating around?
Is the GTab 2 "stable", so even if you trash a ROM, you can still get into the ROM manager to restore a previously working, or stock, ROM?
I'll probably come up with a couple more questions, especially depending on the replies... TIA
Hi..
I can answer some of your questions. I hope that helps!
1- Rooting is easy and reliable. you may use "CF-Auto-Root" tool (search for it in XDA forum).
But you need to remember that rooting and custom ROMs void your warranty.
2- If you just need to free some storage space, you may use an app such as "Clean Master" to uninstall system apps and get rid of temp and junk files.
3- If you opt to use a custom ROM make sure it is very well supported and maintained.
aisais said:
Hi..
I can answer some of your questions. I hope that helps!
1- Rooting is easy and reliable. you may use "CF-Auto-Root" tool (search for it in XDA forum).
But you need to remember that rooting and custom ROMs void your warranty.
2- If you just need to free some storage space, you may use an app such as "Clean Master" to uninstall system apps and get rid of temp and junk files.
3- If you opt to use a custom ROM make sure it is very well supported and maintained.
Click to expand...
Click to collapse
Thanks - but prior to using Clean Master I assume I better either get a stock image to reload, or use CWM so I can make a backup of the ROM before messing something up?
tundrwd said:
Thanks - but prior to using Clean Master I assume I better either get a stock image to reload, or use CWM so I can make a backup of the ROM before messing something up?
Click to expand...
Click to collapse
Taking a backup is always good thing to do. I suggest you try clean master to know how it works and what does it do.
aisais said:
Taking a backup is always good thing to do. I suggest you try clean master to know how it works and what does it do.
Click to expand...
Click to collapse
Thanks - I plan to use Clean Master. Allows me to be selective about what I remove/move, instead of getting a ROM from someone and they removed the ONE THING I really wanted.
Ok, got it rooted and CWM installed.
HOWEVER, when I boot into CWM, I DON'T see an option to backup my ROM (I've used TWRP before on my KF, so the menu is different).
What I've got on my screen in CWM:
Android system recover <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
That's it. Where's the option to do a ROM backup? Oh, used file P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip Had CWM and Root all in one. I do have GT-P3113_ClockworkMod-Recovery_6.0.1.0.tar as well. Should I just go through procedure again to flash this CWM? Will it still retain SU?
nandroid backup ok to use? Seems it's just a wrapper for a backup script...
Ok - I'll reply to myself.
I don't know what was wrong with the CWM I installed via the aforementioned file (P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip), but I went to the CWM site, D/L'ed the latest touch enabled CWM for the P3113 (6.0.2.3, I believe), and installed it over the existing recovery image on the device (I had to create my own .tar.md5 - easy with *nix).
Anyway, I now have access to the backup options by scrolling down. The image from P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip, simply wouldn't scroll beyond what I listed earlier. Now can scroll down, make backups, etc.
Haven't tried yet to re-install the image I made with nandroid - I'm a bit leery of that - so I'll just get the stock 4.1.1 ROM from sammobile, and keep it around....
tundrwd said:
Ok - I'll reply to myself.
I don't know what was wrong with the CWM I installed via the aforementioned file (P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip), but I went to the CWM site, D/L'ed the latest touch enabled CWM for the P3113 (6.0.2.3, I believe), and installed it over the existing recovery image on the device (I had to create my own .tar.md5 - easy with *nix).
Anyway, I now have access to the backup options by scrolling down. The image from P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip, simply wouldn't scroll beyond what I listed earlier. Now can scroll down, make backups, etc.
Haven't tried yet to re-install the image I made with nandroid - I'm a bit leery of that - so I'll just get the stock 4.1.1 ROM from sammobile, and keep it around....
Click to expand...
Click to collapse
That's exactly what I did today, grabbed the stock image for a backup, rooted with Odin and CWM then flashed a CM based 4.3 ROM. Piece of cake.