how to wipe data when changing nighties? - Defy Q&A, Help & Troubleshooting

Is it necessary to wipe data when changing nightly builds?
i was using defy_safewipe.zip from here http://forum.xda-developers.com/showpost.php?p=47856069&postcount=569 after being reffered to it a long time ago. It was working fine until now.
Is it still functional/relevant after changing the partition size (NewBuild - since OCT/2014)?
Is there a better/updated/newer tool for doing this?
Do i need an external wipe tool, or can i just use the one in TWRP?
Thanks,
Roy.

anyone?

Related

What exactly does moving dalvik cache to /cache do?

It is in my spare parts.
Thanks
Use the search feature... there are quite a few thread with this question answered...
In short, it move the dalvik vm cache from /data to /cache, giving you 40MB+ extra free space in /data to install apps...
What is dalvik cache -> http://wiki.cyanogenmod.com/index.php/Dalvik-cache
What is dalvik cahce relocation -> http://wiki.cyanogenmod.com/index.php/Dalvik-cache-relocation
I actually saw that after I posted. What are the negatives then? Just less room for cache from other programs?
Well, so far, no one's complained abt any problems cause by this, but yeah, essentially, this reduces your cache size. It could cause problems with OTA updates which can be large, but if you're using a custom ROM, you wouldn't be using OTAs anyway...
Ok thanks for the help. So if I do a data wipe to a new ROM, does this operation get undone and it goes back to normal?
Odd.
I'm running Cyanogen 5.0.3.1 and I don't have this in my spare parts?
@hah2110... no a data wipe does not move the dalvik cache back to the data partition. Don't know if you can uncheck it in SpareParts to revert, but if not moving it back has to be done by modifying/removing the init script which does it. Though keep in mind, if it cannot be unchecked in Spart Parts, it probably means it's not safe to revert...
@Amdathlonuk, CM automatically has this hook enabled. Enomthers 1.7.1+ has this as an option in Spare Parts
craigacgomez said:
@hah2110... no a data wipe does not move the dalvik cache back to the data partition. Don't know if you can uncheck it in SpareParts to revert, but if not moving it back has to be done by modifying/removing the init script which does it. Though keep in mind, if it cannot be unchecked in Spart Parts, it probably means it's not safe to revert...
@Amdathlonuk, CM automatically has this hook enabled. Enomthers 1.7.1+ has this as an option in Spare Parts
Click to expand...
Click to collapse
Thanks man.
Go away for a week and you lose all knowledge of what's going on!!
So many roms, so little time....
It actually is an option in Spare Parts, but it says you need to do a factory reset it you revert back.
hah2110 said:
It actually is an option in Spare Parts, but it says you need to do a factory reset it you revert back.
Click to expand...
Click to collapse
Yep, expected that... didn't run Enom's for long so I wasn't sure... but from what I've read and understood, moving dalvik-cache to /cache is permanent... if u revert u have to clear everything via recovery and re-install everything!!
My suggestion, go with this... been using it for a while... no problems...

Car Home installed twice

For some reason every time I format (wipe data/factory reset and wipe dalvik) then install a new ROM. there will be TWO car home apps! I didn't even use the first one. long story short, how can I remove at least one?
absolutelygrim said:
For some reason every time I format (wipe data/factory reset and wipe dalvik) then install a new ROM. there will be TWO car home apps! I didn't even use the first one. long story short, how can I remove at least one?
Click to expand...
Click to collapse
1. Look for "alternative method to removing bloatware" thread in the development section. It's going to be the same method.
2. Before you flash a new rom, try removing the car home apk from the zip. that should keep you from having two.
absolutelygrim said:
For some reason every time I format (wipe data/factory reset and wipe dalvik) then install a new ROM. there will be TWO car home apps! I didn't even use the first one. long story short, how can I remove at least one?
Click to expand...
Click to collapse
This means there are files left over on your system partition that are not being cleared when you flash the new ROM. In addition to the regular steps, you should also format the system partition (from the partitions menu) before flashing the new ROM. The extra app(s) should disappear.
Personally I always format system and boot partitions before a new ROM because this happens consistently with some ROMs, in particular CM7.

Help with flashing anything to my nook

I have tried to flash my nook several times. First with deeperblues honeycomb and then with cm7. On the honeycomb flash it just hangs on the android_ screen and with the CM7 it hangs on the cyanogen splash screen.
Have tried with different versions of CWR and different SD cards. have tried formatting boot and without for the Honeycomb. Always formatting cache, data and system for both cm7 and honeycomb.
Each time, i flash back to 1.0.1 stock, then root, then try to flash the mod again.
It always works returning to the stock 1.0.1 using the cwr complete restore found on the nook color portal. And the autonooter always works as well.
This is frustrating me as im not amble to install any cool mod on the nook. Does anyone have any ideas as to why my NC is resisting any change i make to it other than root stock 1.0.1?
It sounds like a symptom of not wiping data, but you said you're doing that...
Just to be clear, before flashing, you're doing "wipe data/factory reset", then "wipe cache", then "wipe dalvik cache"? Formatting /system shouldn't be necessary but I guess it wouldn't hurt.
STaria said:
It sounds like a symptom of not wiping data, but you said you're doing that...
Just to be clear, before flashing, you're doing "wipe data/factory reset", then "wipe cache", then "wipe dalvik cache"? Formatting /system shouldn't be necessary but I guess it wouldn't hurt.
Click to expand...
Click to collapse
I have tried the wife data/factory reset option once when trying to flash honey comb. Still gave me the same issue. All of the how to's i read had me formatting the data, cache and system, and depending on the how to sometimes the boot partition as well. Have been following those to the letters. This is the first time i have heard of wiping the dalvik cache, is that different than wiping cache under the mounts and storage?
Was there a color sticker on the box of your Nook?
Also, have you tried doing an SD only install rather than flashing the internal?
fuul4nook said:
Was there a color sticker on the box of your Nook?
Also, have you tried doing an SD only install rather than flashing the internal?
Click to expand...
Click to collapse
Not sure about the color sticker on the box when i bought it. It was right after it came out so going on a year ago. I have tried the SD only install, that works with honeycomb at least, thats the only one i have tried, all be it laggy because i only have a class 2 card at best.
jonwymore said:
Not sure about the color sticker on the box when i bought it. It was right after it came out so going on a year ago. I have tried the SD only install, that works with honeycomb at least, thats the only one i have tried, all be it laggy because i only have a class 2 card at best.
Click to expand...
Click to collapse
I did some searching and i think what your eluding to is maybe my partition is the new style(although like i said i bought it within about a week or two of it originally being released)? would running the repartition in CWR make a difference do you think?
The option to wipe dalvik cache is under "advanced" in CWR. Try that in conjunction with a data and cache wipe.
As for the partitions, I don't think it should make a difference. It also sounds like you're on the old partitioning scheme which is the better one to have. You could try flashing the repartition/reformat zips just for the hell of it. Personally I went with the custom 2/4 setup.
STaria said:
The option to wipe dalvik cache is under "advanced" in CWR. Try that in conjunction with a data and cache wipe.
As for the partitions, I don't think it should make a difference. It also sounds like you're on the old partitioning scheme which is the better one to have. You could try flashing the repartition/reformat zips just for the hell of it. Personally I went with the custom 2/4 setup.
Click to expand...
Click to collapse
Will try once with wiping the delvik cache, data, and cache. I wont wipe the system or the boot. If that doesnt work, il try the repartition and start from scratch. If anyone can think of anything else please let me know.

If anyone Soft-Bricks their Nexus 7

If you did Soft-Brick your new Nexus 7 2013 and you cannot access your Nexus 7 from your computer or a Factory Reset does not help please follow this guide. :crying:
(This is way different than the 0 Internal Storage bug. Go here: http://forum.xda-developers.com/showthread.php?t=2380913 )
Step 1: Download and install Wugs toolkit from here: http://www.wugfresh.com/nrt/
Step 2: Let it download the files it needs and choose what device your have EXACTLY what you have.
Step 3: Install the universal drivers by finding the Initial Setup part which is the big bar at the top. Go to the Step 2 tab and install the Universal Drivers and then let that install. It installs ADB so you can access ADB even in recovery if you could not before.
Step 4: Launch the Advanced Utilities in the bottom left and you will need a new ROM. Go here to get one: http://forum.xda-developers.com/forumdisplay.php?f=2411
gApps: http://goo.im/gapps
Step 5: Once you have those two things go to Flash Zips at the top right and tell it that the file is on the computer. Go to add files and add the ROM then GAPPS and enable to the left that it is a ROM but disable the nandroid backup because you really don't need it at the moment. Also have Wipe Dalvik, Cache, and Data on at the bottom.
Step 6: Confirm it and let it flash. Done! It will take about 5 minutes. Go eat or do something while waiting. It might take less but if you want to be on the safe side just let it run until your device powers on. :victory:
I AM NOT RESPONSIBLE FOR ANYTHING THAT YOU DO WRONG.
If you have any questions or comments please leave some.:good:
So, use a toolkit to install a ROM. How is this some magical fix?
khaytsus said:
So, use a toolkit to install a ROM. How is this some magical fix?
Click to expand...
Click to collapse
I never meant for it to be a "magical" fix. It is just a fix for a soft-bricked Nexus which had a rogue ROM and a Factory Reset would not fix nor was ADB working. Maybe someone has this happen and if you have a Backup from lets say Titanium Backup you kind of don't want to Format Data. So if you could just appreciate if I made a tutorial for the less fortunate in Android I am sorry. Skip the thread next time please
WeRSpecialPeople said:
Also have Wipe Dalvik, Cache, and Data on at the bottom.
Click to expand...
Click to collapse
You say here to wipe data.
WeRSpecialPeople said:
Maybe someone has this happen and if you have a Backup from lets say Titanium Backup you kind of don't want to Format Data.
Click to expand...
Click to collapse
And here not to format data. Though wipe and format are not the same, the end result to the user is still that the data is gone. So I'm not sure whether you mean for the data gone or not.
WeRSpecialPeople said:
If you have any questions or comments please leave some.:good:
Click to expand...
Click to collapse
1. Usually, the better option is to find the most similar ROM to the one that the data partition was populated with, so there will be a smaller likelihood of problems. For example, an older working nightly of the same ROM. Dirty flashing a random ROM is less likely to be problem-free.
2. Out of curiosity, why a toolkit, especially when flashing a ROM zip from recovery (not even ADB or fastboot) would work just as well?
bananagranola said:
You say here to wipe data.
And here not to format data. Though wipe and format are not the same, the end result to the user is still that the data is gone. So I'm not sure whether you mean for the data gone or not.
1. Usually, the better option is to find the most similar ROM to the one that the data partition was populated with, so there will be a smaller likelihood of problems. For example, an older working nightly of the same ROM. Dirty flashing a random ROM is less likely to be problem-free.
2. Out of curiosity, why a toolkit, especially when flashing a ROM zip from recovery (not even ADB or fastboot) would work just as well?
Click to expand...
Click to collapse
Alright Formatting Data wipes the whole device usually. Wiping the data gets rid of the users apps. Lets say you have a backup in storage/emulated/legacy. It will still be there after you wipe the data.
1. Yes but that is the users choice. I couldn't find a definite stock ROM to the device so I will just let them pick.
2. If you want me too I could make a tutorial using ADB if you really want me too. This was just a 5 minute tutorial on a toolkit and I understand that most people here do not like toolkits but it is a really easy way. Just tell me if you do want me to add ADB tutorial as well and I will. :silly:
WeRSpecialPeople said:
Alright Formatting Data wipes the whole device usually. Wiping the data gets rid of the users apps. Lets say you have a backup in storage/emulated/legacy. It will still be there after you wipe the data.
...
Just tell me if you do want me to add ADB tutorial as well and I will. :silly:
Click to expand...
Click to collapse
I don't think formatting data wipes the whole device...just the data partition. Same as wiping data. The kernel and ROM in the boot and system partitions respectively stay. Wiping data wipes all user data as well, not just apps. In either case, I don't think sdcard gets wiped.
Since I won't be using it, I personally don't mind what you do with the toolkit, but users need to be aware that it's not the most problem-free method.
bananagranola said:
I don't think formatting data wipes the whole device...just the data partition. Same as wiping data. The kernel and ROM in the boot and system partitions respectively stay. Wiping data wipes all user data as well, not just apps. In either case, I don't think sdcard gets wiped.
Since I won't be using it, I personally don't mind what you do with the toolkit, but users need to be aware that it's not the most problem-free method.
Click to expand...
Click to collapse
Sdcard is on /data so if you wipe data (including factory reset) the sdcard is 'formatted'.
khaytsus said:
Sdcard is on /data so if you wipe data (including factory reset) the sdcard is 'formatted'.
Click to expand...
Click to collapse
Does it now...how odd. Has it always worked like that on every device? On my Galaxy Nexus, TWRP specifically ignores the sdcard mount point.
EDIT: okay, I think I understand the confusion. I meant that wiping data/factory resetting from recovery doesn't wipe sdcard. I know that doing so from Android does.

Samsung Galaxy Core Prime too laggy

please anyone help
every time i flashing a rom it going to be too laggy even after a full wipe !
even after changing the recovery the proplem not resolved !!
No solutions. All of us have this lag problem. Maybe it has something to do with our device from production.
Try wiping the whole device 3-4 times without -rf option enabled. It works. If it isn't working the use dreamstar's recovery and wipe the device
me too have the lag issue now
---------- Post added at 08:23 PM ---------- Previous post was at 07:35 PM ----------
SupulEdirisinghe said:
Try wiping the whole device 3-4 times without -rf option enabled. It works. If it isn't working the use dreamstar's recovery and wipe the device
Click to expand...
Click to collapse
Tried wiping 3 times also used dreamstar's cwm recovery but found no use
still the device is too much laggy
until now no solution is found
ashish1989 said:
me too have the lag issue now
Tried wiping 3 times also used dreamstar's cwm recovery but found no use
still the device is too much laggy
until now no solution is found
Click to expand...
Click to collapse
Did you wiped the whole device? I meant system + data + internal + dalvik + cache.. whenever I exclude internal the lags continue..
BTW i meant dreamstar's TWRP recovery
SupulEdirisinghe said:
Did you wiped the whole device? I meant system + data + internal + dalvik + cache.. whenever I exclude internal the lags continue..
BTW i meant dreamstar's TWRP recovery
Click to expand...
Click to collapse
I m sorry I mean TWRP recovery and yes after going to advanced wipe I wiped everything excluding external sd card and flashed stock rom
Tried this many times but getting huge lags
Any suggestions????
You have to format data buddy. Instead of going to advanced wipe choose "wipe data"
Then flash Stock and then you can flash any rom afterwards. No lags guaranteed
SupulEdirisinghe said:
You have to format data buddy. Instead of going to advanced wipe choose "wipe data"
Then flash Stock and then you can flash any rom afterwards. No lags guaranteed
Click to expand...
Click to collapse
There are only three options in twrp i.e. advanced wipe, format data and swipe to factory reset
Which one to choose
My mistake I meant format data there. Choose format data. It'll take a while but does the job
SupulEdirisinghe said:
My mistake I meant format data there. Choose format data. It'll take a while but does the job
Click to expand...
Click to collapse
Ok let me try
Will reply shortly
SupulEdirisinghe said:
My mistake I meant format data there. Choose format data. It'll take a while but does the job
Click to expand...
Click to collapse
I have done format data but still getting lags
Any other solution
Now I'm facing something like that..
SupulEdirisinghe said:
Now I'm facing something like that..
Click to expand...
Click to collapse
I have done format data and after that going to advanced wipe I have done wipe system and cache
Done these steps many times but still facing lags
Guys anybody have solution for these lags
Using TWRP 3.0.0 and 3.1.1 from Dreamstar bro
ashish1989 said:
I have done format data and after that going to advanced wipe I have done wipe system and cache
Done these steps many times but still facing lags
Guys anybody have solution for these lags
Using TWRP 3.0.0 and 3.1.1 from Dreamstar bro
Click to expand...
Click to collapse
Use 3.0.1 from dreamstar..
And format data for 2-3 times and format system for 20+ times???.. keep a stopwatch and measure the time it takes to finish one wipe of system. once all the **** is removed it should be like 10mins some said that it goes like 14mins.. easiest way is wipe for more than 20 times and reflash ROM download A1 SD bench app. Do a benchmark of internal storage. If Write speed is 20MB/s or more then your problem is fixed if not go back to wiping ???
SupulEdirisinghe said:
Use 3.0.1 from dreamstar..
And format data for 2-3 times and format system for 20+ times???.. keep a stopwatch and measure the time it takes to finish one wipe of system. once all the **** is removed it should be like 10mins some said that it goes like 14mins.. easiest way is wipe for more than 20 times and reflash ROM download A1 SD bench app. Do a benchmark of internal storage. If Write speed is 20MB/s or more then your problem is fixed if not go back to wiping ???
Click to expand...
Click to collapse
Bro can You provide download link for 3.0.1 from dreamstar
ashish1989 said:
Bro can You provide download link for 3.0.1 from dreamstar
Click to expand...
Click to collapse
Too lazy to find the link so I uploaded by my self
https://drive.google.com/file/d/0BxUVy1MbGMPKUVhDQkxsT3JmYW8/view?usp=sharing
SupulEdirisinghe said:
Too lazy to find the link so I uploaded by my self
https://drive.google.com/file/d/0BxUVy1MbGMPKUVhDQkxsT3JmYW8/view?usp=sharing
Click to expand...
Click to collapse
[emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23]
Sent from my SM-G532F using Tapatalk
One of the easiest solution
Hello Everyone,
As all of us (G360H users) know, no matter what we do, lagness comes back after few days of smoothness. I am going to share what I do as a fix.
After flashing any ROM cleanly, lagness bothers after few days. So what to do?
>After you feel your phone is lagging, restart your phone to Recovery (TWRP 3.0.0 and above)
>Backup your system only (to internal storage or SD card doesn't matter, it's normally 600 to 700 MB)
>After Backup is completed, go to wipe section and then advanced wipe then wipe only system (at least 4 times without -rf option enabled, wiping takes some time)
>After wiping system few times, restore the system Backup from 2nd step, once completed restart your phone to system.
>Smoothness can be felt again but it's gonna come back again after few days (normally in around 15 days) REPEAT above steps again.
There's nothing new but this saves time in backing up and wiping up everything or the hassle of setting up a newly installed ROM. All your installed apps and data will stay safe and as they were.
Regards,
S
SupulEdirisinghe said:
Use 3.0.1 from dreamstar..
And format data for 2-3 times and format system for 20+ times.. keep a stopwatch and measure the time it takes to finish one wipe of system. once all the **** is removed it should be like 10mins some said that it goes like 14mins.. easiest way is wipe for more than 20 times and reflash ROM download A1 SD bench app. Do a benchmark of internal storage. If Write speed is 20MB/s or more then your problem is fixed if not go back to wiping
Click to expand...
Click to collapse
Bro done all the steps and used dreamstar's 3.0.1 twrp recovery
Formatted data for 3 times, formatted system for 20+ times
But still getting lags, but they are least now as compared before
any more solutions???
ashish1989 said:
Bro done all the steps and used dreamstar's 3.0.1 twrp recovery
Formatted data for 3 times, formatted system for 20+ times
But still getting lags, but they are least now as compared before
any more solutions???
Click to expand...
Click to collapse
Well you just have to do that for a little longer . When we use a storage we write and delete data continuously.. So our eMMC acts like a SSD when we write data they store in blocks and when we delete them usually the indexes are deleted ad data remains. so when we write something again those data in blocks are replaced by new data. So when lot of I/O precesses are going on it eventually remains filled blocks and they acts like fragments in HHDs, o remove them we need the process called trimming. Due to our eMMC's bug that wouldn't finish completely. So we have to wipe the storage manually until all blocks are completely wiped out and clean. Unless R/W speed will get low like 8mbps and that causes lags. Be patient and wipe until it's all gone

Categories

Resources