Hey guys, I unlocked the bootloader, flashed twrp and root. Then I proceeded to do a fastboot format userdata. But after the boot the encryption was still there. Now I am running PureNexus latest build along with ElementalX kernel. I would like to remove encryption when I will be flashing another rom, How do I do that? Do I simply need to do a fastboot format userdata? Will I lose Twrp and root if I do that?
If you format user data and then boot with the stock kernel it will just re encrypt the device.
Only way to stop this to format usersata and then BEFORE booting the device flashing a kernel or custom rom with force encrypt disabled.
Keep in mind the installation instructions that come with your custom ROM or kernel though. Some require you to be on stock before flashing.
I would generally consider dirty flashing a different ROM over purenexus a bad idea, so you best revert to stock, format user data to disable encryption, do a factory reset then install the new custom rom.
You will lose everything though and have to start from scratch. You may get away with using titanium backup for backup and restoring apps if you know what you are doing.
If the ROM has a kernel with force encrypt disabled then you just flash the whole ROM through fastboot and boot it. What ROM are going to try?
Someone told me on reddit to just simply format data using twrp and that it will remove the encryption and wipe my whole internal storage. Is that correct?
I believe it does just that.
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)
IronRoo said:
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)
Click to expand...
Click to collapse
What I ment is before flashing it....Afterwards/during of couse Ill flash gapps
riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^
syednawaz said:
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^
Click to expand...
Click to collapse
checked every file hash matches, did exactly as written, done all of above and it doesn't work
TWRP went on in less than 10 second does that sound normal ? and how do you know if its actually on there?
Nope. Installation take atleast 2 or 3 minutes.
and if its installed properly you would have seen different rom from the stock.
Here is what i use for s4 mini(i9192). Also used it on i9190 model as well.
http://forum.xda-developers.com/galaxy-s4-mini/development/rom-aokp-rom-25-apr-2016-t3366314
and these steps mentioned in the website.
A. Initial install
1. Copy ROM and Gapps to your external SD Card or internal memory
2. Boot into recovery
3. Wipe
4. Install ROM and Gapps
5. Reboot
Its simple. Should have worked.
I hope you have installed your model rom.
A question the system format is required to install the rom ??
juanpabloml said:
A question the system format is required to install the rom ??
Click to expand...
Click to collapse
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.
syednawaz said:
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.
Click to expand...
Click to collapse
Ie that enough only to make WIPE FACTORY RESET AND WIPE DALVIK CACHE is not necessary to the FORMAT SYSTEM, DATA AND CACHE ??
sorry i do not understand.
to install a rom just do a factory reset. nothing else is necessary.
If you do not do factory reset, sometimes you will not be able to install a new version of rom(for example, from kitkat to lollipop).
if you do not do factory reset its called dirty flash.
for example
you are using custom rom cm13. and it has a new update released, you go in twrp recovery and install the updated rom without doing factory reset. this way you can keep all the application and data you have.
i hope i am making some sense. it is hard for me to explain.
well do some flashing and you will understand but always make a backup.
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
SynaTech said:
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
Click to expand...
Click to collapse
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
madsponge26 said:
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
Click to expand...
Click to collapse
_________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
SynaTech said:
__________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
Click to expand...
Click to collapse
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
J_Dutch said:
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
Click to expand...
Click to collapse
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
J_Dutch said:
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
Click to expand...
Click to collapse
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
SynaTech said:
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
Click to expand...
Click to collapse
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
So, I've flashed CM13 Sultans with root, which I haven't done before... It seems stable, I'll know in an hour or so...
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
ghostofcain said:
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
Click to expand...
Click to collapse
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
SynaTech said:
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
Click to expand...
Click to collapse
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
J_Dutch said:
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
Click to expand...
Click to collapse
The ROM still crashed, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
ghostofcain said:
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
Click to expand...
Click to collapse
The ROM ended up crashing, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
ghostofcain said:
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
Click to expand...
Click to collapse
Wipe everything but internal correct? And also should I install gapps right away or wait a bit, then install gapps?
Thanks for all the help!
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
ghostofcain said:
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
Click to expand...
Click to collapse
Even without Gapps, it crashed in around 2-3 minutes
Wow, that is poor. You aren't having this problem with stock OS?
I have not yet received the phone, but when I do I will boot loader unlock/root. (If I don't intend to stay with Oxygen OS at all, should I even root or just flash the new ROM?) Also, is dirty flashing ok with this? Can I just flash it without wiping?
ZVNexus said:
I have not yet received the phone, but when I do I will boot loader unlock/root. (If I don't intend to stay with Oxygen OS at all, should I even root or just flash the new ROM?) Also, is dirty flashing ok with this? Can I just flash it without wiping?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the device so dirty flashing is not in the equation.
If you are flashing CM then you dont need to root first but you will need to root after. (last I knew) Most roms these days dont come with root by default.
zelendel said:
When you unlock the bootloader it will wipe the device so dirty flashing is not in the equation.
If you are flashing CM then you dont need to root first but you will need to root after. (last I knew) Most roms these days dont come with root by default.
Click to expand...
Click to collapse
Yeah it will wipe it, but the system files are still there right? I was watching a video of someone installing a new ROM, and they deleted
Dalvik/ ART Cache
System
Data
Cache
Or am I wrong? Do I not need to wipe all those partitions before flashing? Really sorry for being a bother, fairly new to this.
ZVNexus said:
Yeah it will wipe it, but the system files are still there right? I was watching a video of someone installing a new ROM, and they deleted
Dalvik/ ART Cache
System
Data
Cache
Or am I wrong? Do I not need to wipe all those partitions before flashing? Really sorry for being a bother, fairly new to this.
Click to expand...
Click to collapse
That is what is called a clean flash. (always the best bet when flashing a rom rom and even suggested by all devs. You will be told that you can "dirty" flash (wiping only system and both caches) so your app data and settings stay after the flash but to be honest that is just being lazy as you will have to clean flash before you can post a bug report anyway, so why not do it from the start)
Yes when you unlock the bootloader the system will be fine. What the unlock does is pretty much a factory reset. So make sure to back up any pic, music or what ever.
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
geokilla said:
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
Click to expand...
Click to collapse
wipe dalvik art cache, cache and system
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
geokilla said:
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
Click to expand...
Click to collapse
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
OhioYJ said:
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
Click to expand...
Click to collapse
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
geokilla said:
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
Click to expand...
Click to collapse
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
OhioYJ said:
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
Click to expand...
Click to collapse
I've asked in the Havoc OS thread but the instructions to clean and dirty flash are the same as when I first played with custom ROMs back in the Samsung Galaxy S days. Wipe system, wipe data, wipe the two caches, etc etc.
If you're using a Substratum theme, make sure to disable all overlays before flashing.
Sorry for digging this post, but with android 10 there is no way to decrypt the data partition.
So how do you dirty flash android 10 "properly" ?