NOTE:
DO NOT FOLLOW ANYTHING i have posted below
AS the steps I took maybe out of order
I'll Update these steps with advice people gave soon
.......................................................................
ORIGINAL POST BELOW
........................................................................
This is to help all people on how to do a "Full Wipe." Before you engage in, installing a ROM, kernel, MOD, returning your Phone to TM, or any other reason
you need a full wipe for!
Reason for this post is. I personally did not know how to do a Proper "Full Wipe." Hence I thought this was needed to help others! This is the step I took,
if there is a different, or easier way, or if i missed a step, please, make a post here so I can update this and learn something
Please Note the steps you do, CAN NOT BE UNDONE! also I'm am NOT responsible nor is XDA responsible, if your Phone breaks, bricks, or misbehaves for following,
not following, or Doing anything you see (or read) here!
NOTE as ALWAYS it is best to do a Backup!
NOTES on abbreviations i use here
PB --> Power Button
SDB --> Sound down button
NOTE these steps assume you have ClockworkMod and have installed it VIA "One-Click ClockworkMod Recovery NvFlasher for Windows"
found here
http://forum.xda-developers.com/showthread.php?t=1056847
failure to use this MOD may result in undesirable results. But I'm not sure. So use your own judgment!
The steps I took for doing a proper Full Wipe
1) press and hold PB + SDB until you see the Yellow (Orange ?) "Android" then release these buttons.
1a) you may have to unplug your USB cable if pressing and holding the PB + SDB, results in you only getting the green battery Icon.
2) SDB till "Advanced" is highlighted, then press the PB
3) SDB till "Wipe Delvik Cash" is selected, then press the PB
4) SDB to "Yes - wipe Delvik cash", then press the PB
Now follow steps 1 to 4 except doing it for
"Wipe Battery stats" and "Fix Permissions"
Now using SDB select "Go Back" and then press the PB
1) SDB till "Wipe cash partition" is selected, then press the PB
2) SDB to "Yes - Wipe cache", then press the PB
3) SDB till "Wipe data/factory reset" is selected, then press the PB
4) SDB to "Yes - delete all user data" then press the PB
Now I don't know, if this last step is needed or not. so maybe someone can tell me, to help me do it right and complete this guide properly.
last step) I Think you have to reboot into the OS at least once ? all the way to the initial log-in/setup screen ?
Now reboot going back into ClockworkMod and do what you did a "Full Wipe" for, IE: installing a ROM
then your done
Peace
.
yes a reply to my own post
going through the options of ClockworkMod i noticed the option
"Mounts and storage"
under this option is
format
/cache
/data
/sdcard
/system
when doing a full and proper wipe do you need to do these things ?
If "Yes" do you, do them before or after the above guide ?
if "No" when do you use format on the above options ?
thanks!
.
I usually stick to "wipe data/factory reset" then "wipe /system" then flash.
And once you've wiped, you've wiped. No need to boot the phone and head back to recovery. Just do whatever you need to do while you're still in recovery.
r4d14n7 said:
I usually stick to "wipe data/factory reset" then "wipe /system" then flash.
And once you've wiped, you've wiped. No need to boot the phone and head back to recovery. Just do whatever you need to do while you're still in recovery.
Click to expand...
Click to collapse
I was told in the Vibrant section to do the following when you are flashing a rom:
Go into CWM recovery
select wipe data/factory restore
select Install zip from sd card
select choice zip from sd card
Select zip to be installed
select yes to install zip selected
After flash is completed
wipe cache
Select yes to wipe cache
Use power button to cursor down to Advanced
In advanced select wipe davlik cache
Select yes to wipe davlik cache
Use power button to cursor down to Fix permissions
Select yes to Fix permissions
Select Go back
Select Reboot system now
Let it sit for at least 10 minutes(do nothing)
Reboot and then sign in with Google
Enjoy
a1yet said:
going through the options of ClockworkMod i noticed the option
"Mounts and storage"
under this option is
format
/cache
/data
/sdcard
/system
when doing a full and proper wipe do you need to do these things ?
If "Yes" do you, do them before or after the above guide ?
if "No" when do you use format on the above options ?
thanks!
.
Click to expand...
Click to collapse
These steps may be required in some cases. I developed persistent problems getting Titanium Backup to run properly (either FC or complete failure to load any app data from backup or from the system) on any non-CM7 ROM. I performed these steps after backing up my external card and before re-installing a non-CM7 ROM, after which my persistent TiBu problem went away. I'm not sure what part of the "nuclear wipe" process did the trick (or whether some independent factor was at work). But if I develop persistent cross-ROM problems in the future, I will be re-doing the "wipe and format everything" process.
Thanks a1yet for posting this. Don't let the negatives affect you. There are always those who want to bring you down out there. (They try to do it to me all of the time and I just ignore it). If you helped one person (which looking through your thread you have) you have done a service.
Alot of people like to judge and bash with out themselves every really contributing.
XDA Needs more people like yourself who are willing to help others.
TGA_Gunnman said:
Thanks a1yet for posting this. Don't let the negatives affect you. There are always those who want to prove they know it all. If you helped one person (which looking through your thread you have) you have done a service.
Alot of people like to judge and bash with out themselves every really contributing.
XDA Needs more people like yourself who are willing to help others.
Click to expand...
Click to collapse
oh sh*t you got meatloaf to back you!
(just kidding TGA)
i wasnt trying to be a "fracker" i was just stating it doesnt need to be in dev section.. then you get all butt hurt and im trying to quit smoking cigs so im ready to troll... sorry A1... didnt try to offend you... or make my self look like a ass
but then again its just a web site =)
nate420 said:
oh sh*t you got meatloaf to back you!
(just kidding TGA)
i wasnt trying to be a "fracker" i was just stating it doesnt need to be in dev section.. then you get all butt hurt and im trying to quit smoking cigs so im ready to troll... sorry A1... didnt try to offend you... or make my self look like a ass
but then again its just a web site =)
Click to expand...
Click to collapse
I wasn't speaking about anyone in particular as know it alls, I edited my post and reworded it. Wasn't meaning you at all just giving the young padawan some advise.
I just quit smoking too. 3rd week off 1st week off patches. I'm a freaking bear sometimes I know it. All I want right now is a shot of Whiskey and a smoke!!!
lol Naughty Nate! Have you seen Half Baked? lol
aquariumdrinker said:
I agree it should be in General (not that my opinion on that matters), but I don't think this thread is useless. I read in another thread that CWM is not properly wiping the Dalvik cache. I don't know for what versions that is true, or whether it's true at all, but it seems like the kind of thing that would come out in this thread. And OPs don't always include details when they say "wipe before flashing". This thread gives people a place to go with questions like "does it matter what order I perform wipe steps in?".
Click to expand...
Click to collapse
I believe that this is a very helpful post for many. Just to state again I have been told that it the order in which you wipe does matter. I have been told(and this is what I do each and everytime) to wipe data/factory reset than flash rom than while still in recovery before rebooting wipe cache and then wipe davlik cache and than fix permissions. After rebooting let it sit at opening screen for at least 10-15 minutes and than reboot. It seems to work well that way.
tenbeau said:
I believe that this is a very helpful post for many. Just to state again I have been told that it the order in which you wipe does matter. I have been told(and this is what I do each and everytime) to wipe data/factory reset than flash rom than while still in recovery before rebooting wipe cache and then wipe davlik cache and than fix permissions. After rebooting let it sit at opening screen for at least 10-15 minutes and than reboot. It seems to work well that way.
Click to expand...
Click to collapse
Can't I just take an Electro-Magnet put it to my phone and turn it on?
TGA_Gunnman said:
Can't I just take an Electro-Magnet put it to my phone and turn it on?
Click to expand...
Click to collapse
I have tried this on TGA's advice, and can confirm that it performs and effective wipe. TGA, please PM me with instructions on what to do next.
I thought it was a useful guide... For the noobs out there. Didn't do me any good, but I'm sure it would have made a difference for those just starting out with android.
Anyways, I didn't feel obligated to post before, but now I feel like it's kinda necessary because this is getting funnay
To the OP, ignore the trolls. They didn't know what to do at first either. I'm sure there's people who appreciate what you've done here, including me. Your effort is seen, your effort is noted, ignore the trolls and don't get caught up in this nonsense
Full wipe - two options
It is usually unclear what may are reaaly advising when they say "full wipe". In any case, here are two options:
1. Good most of the time. Done with only Recovery. If you dn't have recovery, you can't flash - so no need for a wipe:
Wipe cache and dalvek
Format /system
This works for me 95% of the time. I even went from froyo to 2.3 without any issues. You can do a factory reset and wipe all data, but I find it is so much easier to leave data intact. Note - a factory reset does not clear the /system, and this is where a lot of the post=flashing issues come from.
If you are stuck with some problems, like WiFi, Bluetooth, etc. on a ROM that others are having no issues with, then you may need a realyl full Wipe:
This assumes you have SDK tools installed and driveer also:
Connect to computer (with USB Debug on).
Go to SDK tools and enter fastboot device. If you are connected OK, this will confirm it,
Then type - fastboot erase /system -w and hit return
If this is successful, then disconnect and get into Recovery.
Do a factory reset (this will re-establish some partition that the above deleted).
You now have a really clean device (you could also format /boot - but do not think it is necessary). Now do a clean install of the ROM (and Gapps if ROM does not include them) and boot it up.
Make sure all is working OK before you go to the trouble of restoring all your apps and data. I usually first check network connections, WiFi, Bluetooth, and GPS.
Note - have not had to do this in a while - but think the fastbook command is correct. you could first type fastboot only, and it would generate a list of commands. i do this first to check the syntax before i enter the actual command.
This is very useful. That is evident by the fact that there are so many replies of people showing different steps they take. So there doesn't seem to be a clear consensus what are the necessary steps for a "full wipe".
Don't list to those who say this is useless and shouldn't be in dev section. It's as useful in development as all the other treads in development that explain things such as how to install nvflash or how to flash CWMR. I say it belongs in development as a "guide" or "howto".
Many people forget what it was like when they started out with their first Android phone.
I know it's frustrating when you see a need, put in the effort to try and fill that need, and someone comes along and pisses on your leg. But that's life...gotta man up.
The people who don't need the information will see it as useless. The people who do will, in most cases, not voice their appreciation. It is what it is. If you provide a service for the appreciation you will most likely be disappointed. But if you do it knowing what you are doing is furthering progress...well, that's its own reward...and probably the only one you'll get.
Ok, enough preaching...and thank you. I got something from this thread and I appreciate your effort. Please, don't stop contributing just because you feel unappreciated...welcome to the world. And , man up.
Dear a1yet
You make a very valid point that whenever someone has an issue, someone always says - Did you do a full wipe first? I have been watching these forums and this is a very common theme.. and people should be informed. I was one who did not know this until recently, again, by reading these responses.. and then your guide.
With that said, don't let their responses of which forum it should be in distract you from your goal. Your goal is to get it into the dev section, and I agree it should be in there.. But why not roll with this and make an all encompassing guide on how to do a nandroid backup, backup your apps, do the full wipe, push the new rom, how to remove the rom, get a nandorid backup restored, etc.
Then, once the guide is done.. Submit it. Look at TGA_gunnman's guides and maybe see if they can be a resource? There are many helpful people that will go over it with ya and tweak it with ya. Then, submit the entire guide as a post. You can first link to the how to root guide, then how to do NVflash guide, etc..etc. It will cover many different areas.
Lastly, if such a guide is rejected and they allow others.. then ya.. the mods are just being jerks. But.. even if so, you can ask TGA to update the other guides and link to your post in general.
You see.. there are ways to work this in. There is always a solution.. but we focus so much on a roadblock that we just give up. Bust through...
TGA_Gunnman said:
Can't I just take an Electro-Magnet put it to my phone and turn it on?
Click to expand...
Click to collapse
What I do not understand is why my previous post referencing what I took to be sarcasm in the above quote was just deleted. There were two post after it that also are missing. I come back to this thread and it is just gone. Anyone know why???? Did the moderator just decide to delete them? Have never had any replies just deleted before, there was no profanity only questioning about sarcasm. Are there sacred cows we cannot question? I have donated to TGA and am very grateful for all the one click roots and nvflash etc. I am able to do things i could not do without these apps. My only question is once again why was my comment deleted when others which were much more inflammatory are still posted.
mapin0518 said:
This is very useful. That is evident by the fact that there are so many replies of people showing different steps they take. So there doesn't seem to be a clear consensus what are the necessary steps for a "full wipe".
Click to expand...
Click to collapse
The only Android phones I've owned are the G1 and the G2x. With the G1, the factory reset only wiped the /data partition, so people figured out that wiping /data was not enough as you still held the old /cache and /dalvik-cache from the old ROM, so wiping all three was coined a "full wipe." I'm not an expert at the interweb or anything so if I'm wrong, be nice.
Anyway, it appears that in the G2x recovery, the factory reset wipes both /data and /cache. And Dalvik cache is actually located in the /data partition, so using this ONE command in CWM "Wipe Data/Factory Reset" should take care of all of your "full wiping" needs.
I just like wiping /system because it gives me a warm fuzzy feeling. And it's not puberty. That was like... 12 years ago.
schmit said:
You make a very valid point that whenever someone has an issue, someone always says - Did you do a full wipe first? I have been watching these forums and this is a very common theme.. and people should be informed. I was one who did not know this until recently, again, by reading these responses.. and then your guide.
With that said, don't let their responses of which forum it should be in distract you from your goal. Your goal is to get it into the dev section, and I agree it should be in there.. But why not roll with this and make an all encompassing guide on how to do a nandroid backup, backup your apps, do the full wipe, push the new rom, how to remove the rom, get a nandorid backup restored, etc.
Then, once the guide is done.. Submit it. Look at TGA_gunnman's guides and maybe see if they can be a resource? There are many helpful people that will go over it with ya and tweak it with ya. Then, submit the entire guide as a post. You can first link to the how to root guide, then how to do NVflash guide, etc..etc. It will cover many different areas.
Lastly, if such a guide is rejected and they allow others.. then ya.. the mods are just being jerks. But.. even if so, you can ask TGA to update the other guides and link to your post in general.
You see.. there are ways to work this in. There is always a solution.. but we focus so much on a roadblock that we just give up. Bust through...
Click to expand...
Click to collapse
+1
Very well said.
r4d14n7 said:
The only Android phones I've owned are the G1 and the G2x. With the G1, the factory reset only wiped the /data partition, so people figured out that wiping /data was not enough as you still held the old /cache and /dalvik-cache from the old ROM, so wiping all three was coined a "full wipe." I'm not an expert at the interweb or anything so if I'm wrong, be nice.
Anyway, it appears that in the G2x recovery, the factory reset wipes both /data and /cache. And Dalvik cache is actually located in the /data partition, so using this ONE command in CWM "Wipe Data/Factory Reset" should take care of all of your "full wiping" needs.
I just like wiping /system because it gives me a warm fuzzy feeling. And it's not puberty. That was like... 12 years ago.
Click to expand...
Click to collapse
Agreed. Since the G2X has no need for "Apps to EXT", a simple "Wipe Data/Factory Reset" should take care of all aspects of /data and /cache.
Related
THIS IS FOR A2SD ONLY!
THIS METHOD HAS BEEN VERIFIED 6 TIMES!
We all have been there at one time or another. We just finished upgrading our G1's or MT3G's to the next awesome version of CYANOGEN rom or we have wiped and installed a fresh CYANOGEN rom and then when the phone boots all of these FC's come up. Normally the next steps are to go in the market and unistall and reinstall the problem apks. Well those days are over, I don't know if anyone here has discovered this method but you will no longer have to install each Protected APK one by one.
Procedure:
Step 1: Make sure you have the latest version of RA-dream-v1.2.3 installed on your device. Now assuming you have just finished flashing the latest update to your phone then follow the next step.
Step 2: Reboot into recovery by holding down the HOME key
Step 3: Select the option in the list for "Wipe Dalvik-Cache on SD", select this option and then hit the HOME key to confirm.
Step 4: Once that completes reboot the phone (it may take 5 or 6 minutes as it is re-Odexing) until it loads as normal, open up your Terminal Emulator. Type in "su" and enter. Then type in "fix_permissions" (depending on how many apps you have this may take a couple of minutes, so do something to stay occupied..) Once this completes proceed to step 5
Step 5: Now while in Terminal Emulator type in "reboot recovery" and hit enter. This will force the phone into recovery without holding the HOME key.
Step 6: Once recovery has loaded, chose the option for "fix mismatched apk uids" and hit HOME key to confirm. Let this run for a little bit, its usually quicker than fix_permissions while the phone is on completely.
Step 7: Once complete reboot your device.
Final Step: Assuming all steps were followed, attempt to open a protected app such as Power Manager or watch it load. If you have any issues please let me know here or PM me.
-flak0
Reserved
Reserved for future SPACE... Just in case
Reserved
Reserved again..... really just in case... Screenshots possibly..
What script? This should be common knowledge by everyone who flashes a rom. This will help with questions and it should be linked whenever someone asks about the flashing procedure.
~~Tito~~ said:
What script? This should be common knowledge by everyone who flashes a rom. This will help with questions and it should be linked whenever someone asks about the flashing procedure.
Click to expand...
Click to collapse
Hmm I was hoping theres some new magical method that he created, instead its just a how-to tutorial on what most people usually do (well almost..why run fix permissions twice?)
You might as well suggest a WIPE to never have a single FC issue!
My procedure before flashing any rom is:
Repartition *manually, meaning removing the ext partition and the linux-swap partition, then recreating them
Wipe
Repair ext
Wipe
Never get a issue, or FC, and once you get the procedure down it takes about a 1 minute and a half. Then I flash and I only get the issues that are issues with the rom I flashed(If there's any) and not an issue on my end. Everyone should do that and no one will have problems
*using Gparted in console of course
Oh and when I flash a theme for cyanogen I usually boot into the fresh flash then I reboot into recovery and nandroid back up then flash the theme, then I only get the problems that occur with a theme(If there's any).
THANKS for this bit of info. What people fail to realize is that EVERYONE is NOT a root specialist like some of us so things that are "easy" to us are difficult and frustrating to others with less skills. That's like me and my IT friends expecting a new graduate to know all the tricks and trade of fixing and maintaining servers across the world. Common knowledge is knowing HOW to root, HOW to find roms/themes and how to wipe and flash new roms. Everything else may get a little sticky for the "common" android users. Afters hours of helping people with tasks who seriously have no clue, i can tell you...its TRUE lol
can anyone please update RA-dream-v1.2.3 link in the first post or post here this is my last hope trying out
phone2175 said:
can anyone please update RA-dream-v1.2.3 link in the first post or post here this is my last hope trying out
Click to expand...
Click to collapse
Here ya go, just had to remove the double "http://"
Ra-dream-v1.2.3
~~Tito~~ said:
My procedure before flashing any rom is:
Repartition *manually, meaning removing the ext partition and the linux-swap partition, then recreating them
Wipe
Repair ext
Wipe
Never get a issue, or FC, and once you get the procedure down it takes about a 1 minute and a half. Then I flash and I only get the issues that are issues with the rom I flashed(If there's any) and not an issue on my end. Everyone should do that and no one will have problems
*using Gparted in console of course
Oh and when I flash a theme for cyanogen I usually boot into the fresh flash then I reboot into recovery and nandroid back up then flash the theme, then I only get the problems that occur with a theme(If there's any).
Click to expand...
Click to collapse
So you like going through and having to install everything again and setting up all your settings again? or do you use some type of back up?
I think he came out with this "guide" to help reduce FCs for those that don't want to wipe every time, because really, it's unnecessary and quite a hassle.
This is brilliant. I just tried it going from a themed cyan 4.2.3.1 to plain 4.2.4 and I had just one force close (which is a protected app that I had a widget for on my home screen so I suspect that is why) instead of at least 8 apps that normally need to be reinstalled taking time and losing settings.
Awesome work sir!
Ummmm doesn't the option of "fixing mismatched uid" mean fix_permissions
don kiedic said:
Ummmm doesn't the option of "fixing mismatched uid" mean fix_permissions
Click to expand...
Click to collapse
Seems you are correct there:
http://forum.xda-developers.com/showpost.php?p=4727115&postcount=377
So I guess we can skip either the fix_permissions step or running 'fix uid mismatches' then? Does it make a difference running in the booted system as opposed to from recovery?
Hmm, this isn't working for me anymore. Do themes have some affect on this?
****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary
Hi! I'm a placeholder.
garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.
Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.
Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary
link posted for testing.
thanks again gary loving it.
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.
chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary
thank you. Gary tried not to get Banned OK? we need you buddy. lol
chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary
not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.
chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.
it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary
worked like a charm...backup and restore works perfectly...
thanks gary !!!
Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk
jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).
***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers
Ah yes i get random freeze screen with some ROM installer
why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?
Very nice guide. Extremely helpful for beginners
Sent from my GT-N7100 using xda premium
And please have to say that use a wipe script it's such a kind of blasfemy ...
Alienator9191 said:
why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?
Click to expand...
Click to collapse
agreed
since nand ram has its life time of cycle. wiping the nand for more than needed is some kind of suicide mission to your droid....
I disagree. If you are the type that flashes a ROM 5 times a day then yes that might be a factor.... might be. Each android device I have owned I have flashed a ROM/kernel to it literally thousands of times and nothing was ever damaged because of scrubbing the disk too much and flashing to it too much. Sorry, but misinformed about just how robust these disks are.
It needs to a must read for noobs
Sent from my GT-N7100 using xda premium
Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.
First of all thz for this step-by-step guide, for newbie is useful.
Phistachio said:
Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.
Click to expand...
Click to collapse
I agree, why repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND...
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:
zenzip said:
First of all thz for this step-by-step guide, for newbie is useful.
I agree, why to repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND ?
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:
Click to expand...
Click to collapse
1 wipe is more than enough
plus this thread should be in general section
I never face any problem with these steps (surely more then 100 flashing)
1.Downoad and flash ROM with Odin (odin doesn't check md5??)
2.Reboot, nevermind if stuck
3.Reboot to recovery, wipe cache and data.
Thats it.
If your counter is already raised, first make sure you have stock kernel and recovery
Reset counter
Start from step 1 above.
**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard
BullHorn7 said:
**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard
Click to expand...
Click to collapse
Lol... this is Sheldon wiping style...
Inviato dal mio GT-N7100 con Tapatalk 2
My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.
Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.
WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.
I've TWRP 2.7 and Crombi-KK. V11.0-20140402-Crombi-kk4.4.2.tf700t. All my apps are "not responding". Would like to clear everything out and reboot in a raw Crombi (don't want to reflash it if possible). Also heard that formatting to fs2f is a screamer, which WOULD mean a reflash, but THAT would be alright if the bennies out-weigh me doing it.
What do I wipe (I HAVE read many other posts, but if I don't ask, I'll **** it up - I have)?
Thanks.
I'm assuming that I factory wipe, wipe cache, then flash cm-11.0-20140921-tf700t-crombi-kk-R1_signed - which will start me over.
Your reluctance to reflash the rom doesn't really make sense to me. All your apps are not responding, you want to "clear everything out" but not reflash? Why?
You could try to just wipe cache and Dalvik and see if that clears out whatever is going on (assuming you are not that well versed in reading a logcat which would be the analytic way to go about this....). That would not touch anything of your current setup.
If that doesn't do it you would have to at least wipe data and then all your apps are gone anyway - why not reflash the rom at the same time????
But you are on a rom that is no longer supported, no further development will happen here, so I would recommend you grab this chance to give your tablet a facelift and switch to where the action is
To do that do these steps in order:
1. Copy anything worth a damn off the tablet
2. fastboot flash lj50036's Kang TWRP 2.8.6 from the Development section (or use his flashable zip in your current recovery). Reboot
3. download ZOMBi-POP and put it onto a fat32 formatted microSD
4. boot into TWRP, go to Wipe > Advanced and format data. This will take up to 90 minutes - do not interrupt it, deep cleaning is going on.
5. Under the Wipe menu find the change/repair file system option and change data (and only data) to f2fs (I have a guide on how to do it in the General section)
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
6. Flash ZOMBI-POP
7. go through basic setup, then leave it alone for 30 minutes to settle in
8. prepare to be amazed
berndblb said:
Your reluctance to reflash the rom doesn't really make sense to me. All your apps are not responding, you want to "clear everything out" but not reflash? Why?
You could try to just wipe cache and Dalvik and see if that clears out whatever is going on (assuming you are not that well versed in reading a logcat which would be the analytic way to go about this....). That would not touch anything of your current setup.
If that doesn't do it you would have to at least wipe data and then all your apps are gone anyway - why not reflash the rom at the same time????
But you are on a rom that is no longer supported, no further development will happen here, so I would recommend you grab this chance to give your tablet a facelift and switch to where the action is
To do that do these steps in order:
1. Copy anything worth a damn off the tablet
2. fastboot flash lj50036's Kang TWRP 2.8.6 from the Development section (or use his flashable zip in your current recovery). Reboot
3. download ZOMBi-POP and put it onto a fat32 formatted microSD
4. boot into TWRP, go to Wipe > Advanced and format data. This will take up to 90 minutes - do not interrupt it, deep cleaning is going on.
5. Under the Wipe menu find the change/repair file system option and change data (and only data) to f2fs (I have a guide on how to do it in the General section)
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
6. Flash ZOMBI-POP
7. go through basic setup, then leave it alone for 30 minutes to settle in
8. prepare to be amazed
Click to expand...
Click to collapse
Thank for your extensive reply. I had already (after re-reading what I had posted) decided to do as you have described. Am installing TWRP today, tomorrow the rest.
I'm using the TWRP Manager having informed it that this is a tf700t, and I'd like to "flash" 2.8.6, it is asking me if /dev/block/mmcblk0p4 && reboot is correct to write to. As I DO NOT profess to be anything other then a 2* newbie with android - I ask, on a T700 is this correct?
AND may I ask a few more questions should I need to? Although the rest is straight forward.
I would not use TWRP manager for anything - even if it happens to identify the correct partition in this case. p4 is the staging partition and that is ok, but still - I have seen TWRP manager do bad stuff - don't use it.
And you don't have to. lj's kang twrp comes in a flashable zip. Just download it, enter your current recovery, flash it and reboot. Bingo - you are now on TWRP 2.8.6
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Post 2, second link
Ask as much as you like. I don't HAVE to answer, right?
Except for that itch I seem to have to keep scratching :silly:
berndblb said:
I would not use TWRP manager for anything - even if it happens to identify the correct partition in this case. p4 is the staging partition and that is ok, but still - I have seen TWRP manager do bad stuff - don't use it.
And you don't have to. lj's kang twrp comes in a flashable zip. Just download it, enter your current recovery, flash it and reboot. Bingo - you are now on TWRP 2.8.6
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Post 2, second link
Ask as much as you like. I don't HAVE to answer, right?
Except for that itch I seem to have to keep scratching :silly:
Click to expand...
Click to collapse
The more I read the more I was disinclined to use the Manager, but couldn't find - and I DID look, the blob, or flashable zip to use!?!?!
So I'm formatting extfs4, THEN changing to f2fs? I changed it to f2fs, which took 10 seconds, then realized I had reversed it. No harm no foul I assume as it is formatting now - and finished in about 30 minutes?
Is this th eversion you suggest: ZOMBi-POP-5.1_B6_omni_tf700t-KANG_signed.zip
Well, I do not have any hard data on this and my knowledge of block devices is more than rudimentary, but the background is this:
Since about TWRP 2.7.x this recovery does a "secure erase" if you format your data partition ext4. All the blocks get wiped before the new file system is created. Just changing the file system to f2fs does not do that and my thinking is: Can't hurt to really, totally wipe your data partition after a couple of years of use, so why not do it once in a while.
Here's what the master said about that:
http://forum.xda-developers.com/showpost.php?p=60189650&postcount=1806
Is it necessary to format ext4, then switch to f2fs? I doubt it. Is it better? I have no idea, but that's what I did
Yes, the b6 is the latest version of ZOMBi-POP. Flash it
berndblb said:
Well, I do not have any hard data on this and my knowledge of block devices is more than rudimentary, but the background is this:
Since about TWRP 2.7.x this recovery does a "secure erase" if you format your data partition ext4. All the blocks get wiped before the new file system is created. Just changing the file system to f2fs does not do that and my thinking is: Can't hurt to really, totally wipe your data partition after a couple of years of use, so why not do it once in a while.
Here's what the master said about that:
http://forum.xda-developers.com/showpost.php?p=60189650&postcount=1806
Is it necessary to format ext4, then switch to f2fs? I doubt it. Is it better? I have no idea, but that's what I did
Yes, the b6 is the latest version of ZOMBi-POP. Flash it
Click to expand...
Click to collapse
I agree, wiping -I assume the format "checks the disc" is not a bad idea. What I'm a little confused about is that everything I've read - including your thread (which started this whole thing - see what you did?) - states it's a 90 minute or so process. When I change the data partition to f2fs, it's a coupla seconds, and when I format it (which defaults to ext4) it only took 30 minutes or so for the 32 gig.
AND I don't see anywhere where I can "check" the disc for stats and condition, so I'd know what it was/is before I install - unless of course it's staring me in the face - I have problems with things that stare at me.
RBraverman said:
I agree, wiping -I assume the format "checks the disc" is not a bad idea. What I'm a little confused about is that everything I've read - including your thread (which started this whole thing - see what you did?) - states it's a 90 minute or so process. When I change the data partition to f2fs, it's a coupla seconds, and when I format it (which defaults to ext4) it only took 30 minutes or so for the 32 gig.
AND I don't see anywhere where I can "check" the disc for stats and condition, so I'd know what it was/is before I install - unless of course it's staring me in the face - I have problems with things that stare at me.
Click to expand...
Click to collapse
I - and others - say 90 minutes so that people leave it alone, I guess. A few months back, when TWRP first implemented the secure erase, we had lots of people who thought the tablet was stuck and they interrupted the format which led to lots of "help - can't mount anything" posts...
90 minutes is on the extreme outside, but better safe than sorry....
berndblb said:
I - and others - say 90 minutes so that people leave it alone, I guess. A few months back, when TWRP first implemented the secure erase, we had lots of people who thought the tablet was stuck and they interrupted the format which led to lots of "help - can't mount anything" posts...
90 minutes is on the extreme outside, but better safe than sorry....
Click to expand...
Click to collapse
Understood. Been a week of amazement . . . . . . .
It was a WHOLE lot faster when first installed, but slowed a bit now BUT still now actually useable.
MANY MANY thanks for "walking" me through this - I've been in IT since large building, that were VERY cold, but now-a-days need to bounce stuff off someone to know I'm thinking correctly.
I've a coupla questions about the setup, but I'll run them through in the correct thread.