Related
So do the old flashable wipe zips for the EVO 4G work for us or are they different? I'd rather flash one wipe zip before I flash a rom instead of going through the settings hitting a bunch of different ones each time I flash.
I tried caulkins format all and it didn't work, it said it was using some old scripting way.
But I too would like a flashable zip to wipe.
Sent from my PG86100 using Tapatalk
Which recovery are you using. I THINK cwm would take it
spencer88 said:
I tried caulkins format all and it didn't work, it said it was using some old scripting way.
But I too would like a flashable zip to wipe.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
coffeehandle said:
Which recovery are you using. I THINK cwm would take it
Click to expand...
Click to collapse
I'm using cwm and it didn't work.
twrp has a "wipe everything" option, or something similar. I used it when flashing and so far, no issues.
erikivy said:
twrp has a "wipe everything" option, or something similar. I used it when flashing and so far, no issues.
Click to expand...
Click to collapse
It doesn't wipe the system partition. You have to do that manually..
Sent from my PG86100 using XDA Premium App
Did devs get too lazy and not put a format system line in the updater script now?
I've never wiped or formatted system.
Anyways.. Link me to the original files. I'll look at them and see what I can come up with
unCoRrUpTeD said:
Did devs get too lazy and not put a format system line in the updater script now?
I've never wiped or formatted system.
Anyways.. Link me to the original files. I'll look at them and see what I can come up with
Click to expand...
Click to collapse
I think this is it: http://www.mediafire.com/?ikylelx99c49133
(You might want to check out the zip first before trying to flash it, just in case)
SH4YD33 said:
It doesn't wipe the system partition. You have to do that manually..
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Might be a stupid question, but just to be clear: manually wiping with TWRP means going into the format menu and "formatting /system"? I'm just getting used to this recovery, still having amon ra flashbacks from my og evo days.
walkingcorpse said:
Might be a stupid question, but just to be clear: manually wiping with TWRP means going into the format menu and "formatting /system"? I'm just getting used to this recovery, still having amon ra flashbacks from my og evo days.
Click to expand...
Click to collapse
Correct
Appreciate my help? Thank me
unCoRrUpTeD said:
Did devs get too lazy and not put a format system line in the updater script now?
I've never wiped or formatted system.
Anyways.. Link me to the original files. I'll look at them and see what I can come up with
Click to expand...
Click to collapse
Not sure what device you are coming from but Evo 4G we have always needed (strongly advised) to properly wipe/reformat before flashing. It wasn't needed in most cases if just updating nightlies but moving from rom to rom it was a basic requirement to prevent any bugs popping up from remnants of the previous rom.
I don't know the guys, any of them, personally but I don't know if it has anything to do with being lazy.
mrrogers1 said:
Not sure what device you are coming from but Evo 4G we have always needed (strongly advised) to properly wipe/reformat before flashing. It wasn't needed in most cases if just updating nightlies but moving from rom to rom it was a basic requirement to prevent any bugs popping up from remnants of the previous rom.
I don't know the guys, any of them, personally but I don't know if it has anything to do with being lazy.
Click to expand...
Click to collapse
This is what I'm talking about in the updater script
format("ext4", "EMMC", "/dev/block/mmcblk0p23");
This should be doing the same thing that happens when you do it through recovery. And yes it is in the updater scripts that i have looked at. I'm looking at the OG EVO script now.
I'm sure most of you know what a super wipe zip is if you've owned other smart phones. It's a CWM flashable file that wipes data/cache and formats /cache, /data, and /system (usually twice or three times).
Is there any file like that for the S3 available yet? If not, if someone knows how, could you possible make one? I don't know how to code or develop but it seems like a pretty easy file to make considering all everything you need is already in CWM.
Thank you in advanced.
Hypercore said:
I'm sure most of you know what a super wipe zip is if you've owned other smart phones. It's a CWM flashable file that wipes data/cache and formats /cache, /data, and /system (usually twice or three times).
Is there any file like that for the S3 available yet? If not, if someone knows how, could you possible make one? I don't know how to code or develop but it seems like a pretty easy file to make considering all everything you need is already in CWM.
Thank you in advanced.
Click to expand...
Click to collapse
Wiping any of those 3 times is no different then wiping them once. Just a fun fact.
task650 said:
Wiping any of those 3 times is no different then wiping them once. Just a fun fact.
Click to expand...
Click to collapse
I know, but its a habit. Its just annoying always having to wipe them one by one. Also, is there any way to make it so theres only one "No" to choose from?
When working with ROMs, it would appear that, to be thorough, the system partition needs to be wiped as well.
What's the best way to do this, and are there any risks I need to be aware of?
For what it's worth, I'm using Romracer's recovery.
Haphim said:
When working with ROMs, it would appear that, to be thorough, the system partition needs to be wiped as well.
What's the best way to do this, and are there any risks I need to be aware of?
For what it's worth, I'm using Romracer's recovery.
Click to expand...
Click to collapse
https://www.dropbox.com/s/1tgt2yax88rp2mi/Moto-Fastboot FULL WIPE.rar
DOWNLOAD THIS! This is deleting everything! I use that all the time before I flash roms. I highly recommend bro.
--connect your phone to your pc in FASTBOOT mode. Run the .bat script in the file. You should press enter I guess, It will do the rest.
Much appreciated, thanks!
Incidentally, does this do anything problematical when working with Cyanogen? It doesn't wipe something Cyanogen expects to be there, does it?
It makes your phone ready for flashing rom. I was having some problems when i switch the roms in my phone, after this script it is like a new born phone don't worry.
Hit thanks if i helped
http://www.jokersax.com/developer-pages/th3bill/809-2/
here is a full wipe app by an active dev. will be able to get support if you need it. it wipes everything, including your data. best to do a nandroid backup before wiping.
I use Th3bill's wiping tools all the time. They work great.
mrphil101 said:
http://www.jokersax.com/developer-pages/th3bill/809-2/
here is a full wipe app by an active dev. will be able to get support if you need it. it wipes everything, including your data. best to do a nandroid backup before wiping.
Click to expand...
Click to collapse
mrphil101 said:
http://www.jokersax.com/developer-pages/th3bill/809-2/
here is a full wipe app by an active dev. will be able to get support if you need it. it wipes everything, including your data. best to do a nandroid backup before wiping.
Click to expand...
Click to collapse
Doesn't wipe everything. This leaves webtop and preinstall intact..............Use either of the following for full or selective wipe:
http://forum.xda-developers.com/showthread.php?t=1421261
http://forum.xda-developers.com/showthread.php?t=1314607
<edit> As an added note, I used to manually wipe fully from fastboot with commands. I now always use the tool in my second link and select options 1, 3, 6, 7, and 8 before rebooting with option 13. This will wipe everything except your sdcard and radio.
is it not clearing cash and doing a factory wipe? does it mean just to flash the zip over the last rom flashed and doing nothing else?
stackz07 said:
is it not clearing cash and doing a factory wipe? does it mean just to flash the zip over the last rom flashed and doing nothing else?
Click to expand...
Click to collapse
Yes dirty flashing means flashing without clearing anything out.
A clean wipe is wiping cache, dalvik cache, doing a factory reset and wiping system.
Sent from my SCH-I605 using xda app-developers app
I'd say this is pretty dirty!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nosympathy said:
Yes dirty flashing means flashing without clearing anything out.
A clean wipe is wiping cache, dalvik cache, doing a factory reset and wiping system.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Thank you. In clockworkmod recovery wiping cashe and factory reset are in the same function right? I don't have to do three different actions, just two (reset dalvik, and reset cash+factory wipe is one action that does two things) right?
stackz07 said:
Thank you. In clockworkmod recovery wiping cashe and factory reset are in the same function right? I don't have to do three different actions, just two (reset dalvik, and reset cash+factory wipe is one action that does two things) right?
Click to expand...
Click to collapse
Yes and then make sure to format /system as that is where the old ROM is installed at.
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
A clean wipe is wiping cache, dalvik cache, doing a factory reset and wiping system.
Click to expand...
Click to collapse
nosympathy said:
Yes and then make sure to format /system as that is where the old ROM is installed at.
Click to expand...
Click to collapse
Performing a factory reset wipes /cache and the dalvik cache as well, so you don't need to wipe those and then perform a factory reset, or the other way around. Doing so is really just wasting time. The same with wiping system before flashing a ROM. If the ROM isn't already doing this as part of the flash process, IMO, you shouldn't use it. If you can't setup the updater-script properly, who knows what else isn't right in the ROM.
imnuts said:
Performing a factory reset wipes /cache and the dalvik cache as well, so you don't need to wipe those and then perform a factory reset, or the other way around. Doing so is really just wasting time. The same with wiping system before flashing a ROM. If the ROM isn't already doing this as part of the flash process, IMO, you shouldn't use it. If you can't setup the updater-script properly, who knows what else isn't right in the ROM.
Click to expand...
Click to collapse
See, believe what you want, but there are still people who believe in wiping 3+ times.
Never hurts to make sure everything wipes correctly. Specially when you have recoveries that don't work right. Plus clockwork mod is well known for having issues with wiping. Maybe not on this phone, but in the past. I refuse to use it. Even TWRP for this phone the latest version is goofy.
Better to play it safe.
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
See, believe what you want, but there are still people who believe in wiping 3+ times.
Never hurts to make sure everything wipes correctly. Specially when you have recoveries that don't work right. Plus clockwork mod is well known for having issues with wiping. Maybe not on this phone, but in the past. I refuse to use it. Even TWRP for this phone the latest version is goofy.
Better to play it safe.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I agree 100% with this.
1) You should never depend on someone else's rom doing this for you. That's not the roms job. Making sure your phone is clean and working well is YOUR job. Do it and quite being lazy.
2) While the 3+ wipe method may be overkill, most people still aren't wiping their phones properly and that's why we are seeing everyone have so many problems with 4g, gps, bootloops, etc. Just like sex, nobody wants to take the time to do it right anymore and then cry when they catch some nasty from doing it dirty.
3) I think of roms as women. If you want a flawless transition from one to another, they must never find out about each other. This means erase all proof of the previous one's existence. Everybody's 4g/gps issues would be non-existent if they would listen to what we are telling them. Going from rom to rom, always wipe internal and external storage as well as after a backup. This is because conflicting data stored on your card from the previous rom can screw with the new one.
4) I would say use common sense, but you kids these days don't seem to have any. So use mine instead. Stay away from the dirty. In life and on your phone.
Yeah ibeoukdnt go so far as wiping internal and external storage....
Sent from my SCH-I605 using xda app-developers app
its like not wiping after ya poop.
Well not exactly true; I don't think anyone wants the residue after a poop; but plenty of folks would like the residue data (contacts et all) after a flash
droidstyle said:
its like not wiping after ya poop.
Click to expand...
Click to collapse
jake21 said:
Well not exactly true; I don't think anyone wants the residue after a poop; but plenty of folks would like the residue data (contacts et all) after a flash
Click to expand...
Click to collapse
if you look at it that way yes, but thats not my point. dirty flashing is ok when upgrading from lets say beans build 7 to build 8, long as the base has not changed. other than that a full wipe is recomended when flashing or your device might develop a stinch and discomfort, causing force closes. apps and contacts can easily be backed up with google or tibu, so there is no reason not to wipe before changing roms.
What exactly is considered the same base? The kernel version or something else? I.e, lets take cleanrom as an example (which is what I currently use). If we look at the files in cleanrom (via unzip -l) at what point can we determine that the 'base' has changed ?
(I understand your point; it still myths me that different versions use different file structures for caches/data; I mean I understand how it could happen but for some reason I thought he root branches were all the same for android which would imply the data files/format would be largely the same; pity there is not some sort of auto versoning of the data on disk so that when the app loads it if the version was inappropriate it could just kick it out).
droidstyle said:
if you look at it that way yes, but thats not my point. dirty flashing is ok when upgrading from lets say beans build 7 to build 8, long as the base has not changed. other than that a full wipe is recomended when flashing or your device might develop a stinch and discomfort, causing force closes. apps and contacts can easily be backed up with google or tibu, so there is no reason not to wipe before changing roms.
Click to expand...
Click to collapse
jake21 said:
What exactly is considered the same base? The kernel version or something else? I.e, lets take cleanrom as an example (which is what I currently use). If we look at the files in cleanrom (via unzip -l) at what point can we determine that the 'base' has changed ?
(I understand your point; it still myths me that different versions use different file structures for caches/data; I mean I understand how it could happen but for some reason I thought he root branches were all the same for android which would imply the data files/format would be largely the same; pity there is not some sort of auto versoning of the data on disk so that when the app loads it if the version was inappropriate it could just kick it out).
Click to expand...
Click to collapse
Read the change log for the ROM you are on. They will put in it rebased to. ....
Sent from the dark on a Note 2
kintwofan said:
Read the change log for the ROM you are on. They will put in it rebased to. ....
Sent from the dark on a Note 2
Click to expand...
Click to collapse
--
You mean this line:
International N7105XXDMA8 Jellybean 4.1.2 Base
or this line
Rebuilt: Complete rebuild from N7105XXDMA8 International Base!
--
4.2.5 is from:
Rebuild: Complete rebuild off the international N7105XXDLL4 Base
but also
International N7105XXDLL7 Jellybean 4.1.2
-
-
So would that imply that 4.5 and 4.2.5 have different bases or same base (since they are both off of 4.1.2) ?
jake21 said:
--
You mean this line:
International N7105XXDMA8 Jellybean 4.1.2 Base
or this line
Rebuilt: Complete rebuild from N7105XXDMA8 International Base!
--
4.2.5 is from:
Rebuild: Complete rebuild off the international N7105XXDLL4 Base
but also
International N7105XXDLL7 Jellybean 4.1.2
-
-
So would that imply that 4.5 and 4.2.5 have different bases or same base (since they are both off of 4.1.2) ?
Click to expand...
Click to collapse
Yes they would be different bases since they have different build numbers. There will be a lot of revisions on the same Android version (in this case 4.1.2) however it is recommend to clean flash in the different builds even if Android version stays the same.
I'll add that I personally always clean flash. With a good backup app, I use titanium backup pro, it literally takes less then 10 minutes to be fully back up after a flash
Sent from the dark on a Note 2
Yes but on Scott board he suggest you should not restore apps from TB backup:
http://www.scottsroms.com/showthread.php?2523-Battery-Drain-issue
(post #8)
(not sure about contacts and accounts)
-
Very confusing.
kintwofan said:
Yes they would be different bases since they have different build numbers. There will be a lot of revisions on the same Android version (in this case 4.1.2) however it is recommend to clean flash in the different builds even if Android version stays the same.
I'll add that I personally always clean flash. With a good backup app, I use titanium backup pro, it literally takes less then 10 minutes to be fully back up after a flash
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Formatting multiple times to make sure it formatted properly? If you go to clean install the OS on your computer, do you format the HDD 3 times as well? Same principle, different device. If it doesn't format properly the first time, what makes you think doing it again will format it? If it doesn't format properly, it's going to give you an error in recovery, and trust me, recovery will complain when there is a problem, even if it is a minor one. Feel free to continue formatting /system before flashing a ROM, and wiping everything 20 times, but I'm trying to prevent people from wasting their time and continuing with the mis-information of needing to "wipe 3 times"
jake21 said:
Yes but on Scott board he suggest you should not restore apps from TB backup:
http://www.scottsroms.com/showthread.php?2523-Battery-Drain-issue
(post #8)
(not sure about contacts and accounts)
-
Very confusing.
Click to expand...
Click to collapse
you can restore apps just not app data....use google to sysnc and restore contacts. its really not that difficult.
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
imnuts said:
Formatting multiple times to make sure it formatted properly? If you go to clean install the OS on your computer, do you format the HDD 3 times as well? Same principle, different device. If it doesn't format properly the first time, what makes you think doing it again will format it? If it doesn't format properly, it's going to give you an error in recovery, and trust me, recovery will complain when there is a problem, even if it is a minor one. Feel free to continue formatting /system before flashing a ROM, and wiping everything 20 times, but I'm trying to prevent people from wasting their time and continuing with the mis-information of needing to "wipe 3 times"
Click to expand...
Click to collapse
agreed! thats why guide simply states to wipe data then flash rom...no extra bs is required. in my gs3 guide i do infact have instructions stating to wipe system but that was just to make a few folks happy that kept insisting it was needed. either way it does no harm, so yea.
I'm always worried when it comes to the sd card.. alot of important info (no not porn).. I cant afford to lose. . Yes it's backed up on my comp. too .. what's the method to use to wipe sd but not lose anything.. if wiping is the same as formatting then yes I know not to do this.. thanks .. apologies if this sounds like nonsense. .
making a note for the 2nd time in Samsungs Galaxy
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running