Factory Resetting doesn't work somehow after rooting with Magisk...

Factory Resetting doesn't work somehow after rooting with Magisk... - OnePlus 5T Questions & Answers

Dear Community,
My objective is to install Cerberus (an anti theft app) as a system app.
What I did and worked fine:
*Flash TWRP (latest version)
*Root using Magisk (latest version)
*Install Magisk Manager + Systemizer module
*Use Systemizer to install Cerberus apk in /System-priv apps folder
Now I wanted to test a Factory Reset (as a thief would do obviously):
Settings -> Backup & Reset -> Factory Data Reset
When I do that the phone reboots and TWRP opens and runs some OpenRecoveryScript
Then the phone restarts and nothing seems to have changed? All user installed apps are still there etc.
I'm running the latest available update for the Oneplus 5T.
Anyone has an idea why my phone behaves like this?
And any suggestion on how to make cerberus survive factory resets?
I just installed TWRP to make cerberus a system app, I plan on using custom recovery once everything is in place (cerberus as an unwipable system app)
Greetings,
Down...

Downloading123 said:
Dear Community,
My objective is to install Cerberus (an anti theft app) as a system app.
What I did and worked fine:
*Flash TWRP (latest version)
*Root using Magisk (latest version)
*Install Magisk Manager + Systemizer module
*Use Systemizer to install Cerberus apk in /System-priv apps folder
Now I wanted to test a Factory Reset (as a thief would do obviously):
Settings -> Backup & Reset -> Factory Data Reset
When I do that the phone reboots and TWRP opens and runs some OpenRecoveryScript
Then the phone restarts and nothing seems to have changed? All user installed apps are still there etc.
I'm running the latest available update for the Oneplus 5T.
Anyone has an idea why my phone behaves like this?
And any suggestion on how to make cerberus survive factory resets?
I just installed TWRP to make cerberus a system app, I plan on using custom recovery once everything is in place (cerberus as an unwipable system app)
Greetings,
Down...
Click to expand...
Click to collapse
You already have a custom recovery installed

Dazed No More said:
You already have a custom recovery installed
Click to expand...
Click to collapse
So if I reflash stock recovery I will be able to factory reset from the phone settings menu?
And Cerberus will be kept since it's a system app right?

Factory reset clears up the data partition and it needs the default recovery in order to work. You can flash it back if you don't need the TWRP anymore but if your phone is encrypted the thief would have a hard time getting into the TWRP without a password.

Squabl said:
You can flash it back if you don't need the TWRP anymore but if your phone is encrypted the thief would have a hard time getting into the TWRP without a password.
Click to expand...
Click to collapse
This is not correct, or needs clarification. TWRP, is NOT password protected. When you are encrypted it needs a password to decrypt the data, not a password to enter TWRP. You are free to enter TWRP by hitting cancel at the password screen. From that point the "thief" could wipe the phone and your data. He could not access your data though. If your phone was not encrypted, he could easily remove your pin codes, password, and finger prints, etc, and then boot your phone and use it. This is why encryption is important.
TWRP has stated they will never have password protection as there is no point it's easy to just flash a new recovery. As a thief would do even if you flash a stock recovery.
You can protect your data, but a thief that knows what they are doing is going to wipe the device pretty easily.

OhioYJ said:
This is not correct, or needs clarification. TWRP, is NOT password protected. When you are encrypted it needs a password to decrypt the data, not a password to enter TWRP. You are free to enter TWRP by hitting cancel at the password screen. From that point the "thief" could wipe the phone and your data. He could not access your data though. If your phone was not encrypted, he could easily remove your pin codes, password, and finger prints, etc, and then boot your phone and use it. This is why encryption is important.
TWRP has stated they will never have password protection as there is no point it's easy to just flash a new recovery. As a thief would do even if you flash a stock recovery.
You can protect your data, but a thief that knows what they are doing is going to wipe the device pretty easily.
Click to expand...
Click to collapse
Thanks for the reply because I learned a few thinks, now I know that factory reset doesn't work with a custom recovery!
But will a Factory Reset with Stock Recovery work normally? Will it keep my Cerberus app in System-priv folder?
Because I don't care about my data, I would just want to recover my phone .
An unknowing thief would simply reset the phone without checking if cerberus is present as a system app. That's why my question!
EDIT:
I uninstalled Magisk and restored stock recover. I rebooted and Cerberus was still on the phone (as a System App)
After that I did a Factory Reset (from phone settings) and after the reset Cerberus was gone...
So I suppose Android Oreo (Or OxygenOS) factory reset also resets the system apps?
If that's the case, how would I have an app survive factory reset?
(I remember on previous versions I could keep cerberus even after a factory reset)

By default Cerberus could not, it would not be in the play store if it would survive a factory reset. Things like that essentially get flagged "malware" in googles eyes whether it be for "good" reasons or not. Second for it to be able to do this, it would need to have root privileges which most users would not have. Second what you are after is going to stop dumb thieves, anyone who really flashes the thing, is going to wipe out what ever you have done anyways. Granted I guess most people aren't going to go grab a factory image, or the unbrick tool and reflash it, but perhaps I'm wrong, I'm not a phone thief, so I don't know what goes on in that world.
I take it you are moving it to a system folder using a root browser? I honestly don't know how to accomplish what you are trying to do.

OhioYJ said:
By default Cerberus could not, it would not be in the play store if it would survive a factory reset. Things like that essentially get flagged "malware" in googles eyes whether it be for "good" reasons or not. Second for it to be able to do this, it would need to have root privileges which most users would not have. Second what you are after is going to stop dumb thieves, anyone who really flashes the thing, is going to wipe out what ever you have done anyways. Granted I guess most people aren't going to go grab a factory image, or the unbrick tool and reflash it, but perhaps I'm wrong, I'm not a phone thief, so I don't know what goes on in that world.
I take it you are moving it to a system folder using a root browser? I honestly don't know how to accomplish what you are trying to do.
Click to expand...
Click to collapse
Well, it has been possible because I have done it in the past, I am wondering if it is possible to do it know.
I had Cerberus installed on the Galaxy S5 of my brother (as a system app). His phone got stolen, 3 months later it shows up again.
Phone had been reset but Cerberus was still working. So I went to the police and we recovered the phone (It was like a real police thriller ).
OhioYJ said:
I take it you are moving it to a system folder using a root browser? I honestly don't know how to accomplish what you are trying to do.
Click to expand...
Click to collapse
The way I tried (as stated in OP):
I moved Cerberus to a system folder using 'Systemizer' module from Magisk.
I tried browsing the source of the factory reset code here:
https://android.googlesource.com/platform/bootable/recovery/+/android-8.0.0_r36/recovery.cpp
I can see nothing that points to the /System partition getting reset aswell.
* FACTORY RESET
* 1. user selects "factory reset"
* 2. main system writes "--wipe_data" to /cache/recovery/command
* 3. main system reboots into recovery
* 4. get_args() writes BCB with "boot-recovery" and "--wipe_data"
* -- after this, rebooting will restart the erase --
* 5. erase_volume() reformats /data
* 6. erase_volume() reformats /cache
* 7. finish_recovery() erases BCB
* -- after this, rebooting will restart the main system --
* 8. main() calls reboot() to boot main system
Maybe it's a modification brought in OxygenOS?
This topic is getting interesting

Downloading123 said:
*Install Magisk Manager + Systemizer module
*Use Systemizer to install Cerberus apk in /System-priv apps folder
Click to expand...
Click to collapse
So out of curiosity I tried this on my phone with a different method, and different app. As an experiment, I just used a terminal emulator, and moved the entire folder to the system/app location using a root browser. Then factory reset my phone with TWRP, wiped cache, and dalvik, booted back up, didn't login to anything, and the terminal emulator was still there.

OhioYJ said:
So out of curiosity I tried this on my phone with a different method, and different app. As an experiment, I just used a terminal emulator, and moved the entire folder to the system/app location using a root browser. Then factory reset my phone with TWRP, wiped cache, and dalvik, booted back up, didn't login to anything, and the terminal emulator was still there.
Click to expand...
Click to collapse
Yes, that is what I had too... (read previous posts).
But this will NOT work if you put that app in system while rooted, uninstall magisk(aka unroot) and then put back STOCK RECOVERY (else factory reset won't work from phone settings).
If you reset TWRP then only data and cache are wiped, but if you use STOCK RECOVERY and reset from phone settings, app will be gone.

Related

Is it possible to have a rooted AND encrypted device?

I have tried several ROMs (Genesys, Imperial, RR, CM, stock) and can not seem to be able to encrypt my phone. I have done the
Code:
su
pkill -KILL daemonsu
exit
thing and the phone reboots but does not encrypt. I have even gone as far as installing the unrooted stock ROM and setting it up, then encrypting it, THEN rooting it. However, I get tons of FC's and can not enter in the password to decrypt the device.
Does anyone have any ideas on getting encryption working with a rooted device? And no, running pure unrooted stock is not an option.

It can be tricky. Very tricky. Try disabling/freezing SuperSU. Also try going into safemode, then try. I've done it before, it just took a ton of trying. Hold the power off button until you get to the menu. Then press and hold the off option. You should see an option for safe mode in a second or two.

Since SuperSU is a system app, I believe it still starts in SAFE MODE. Also, I couldn't find SuperSU in Titanium Backup even when "System" apps were checked so I couldn't freeze it.
I think I might have succeeded. Here's how I did it:
Download Genisys 3.8 & Genisys Theme 3.6
Reboot to recovery
Wipe system, data, cache, and dalvik (3 times)
Flash Genisys 3.8
Boot up and sign in
*OPTIONAL* Reboot to recovery and flash Genisys Theme 3.6 and reboot system
Open SuperSU and under Settings ---> Full Unroot (should reboot automatically, if not reboot manually)
Encrypt phone ---> Full encryption ---> set pin (DO NOT set boot up pin/password, only unlock pin/password/knock/pattern)
Verify encryption by going to Settings --> Security ---> Encrypt Phone (Should say "Encrypted")
*OPTIONAL* Encrypt SD Card
Reboot to recovery and flash UPDATE-SuperSU-v2.46.zip.
Reboot System
No guarantees, but this worked for me. Remember, DO NOT set the boot up pin because there are tons of FC's preventing you from entering your pin/password on this screen. Just set the lockscreen pin/password/knock/pattern.

[SCRIPT] (Depreciated) Wipe Encrypted Data Without Wiping Internal Storage

Update: The latest TWRP is already capable of decrypting data. This method is now unnecessary and depreciated. Use factory reset in TWRP menu instead
Disclaimer: This mod will wipe your data. I am not responsible for data loss after using this mod.
I tested on my device several times, it's working for me so internal storage is always preserved, but I cannot guarantee if anything is messed up on your side. Please read the post carefully before using this mod!
Always backup your important data before modifying your phone's software!
To compensate the mistake I have done in the modified SuperSU script (I fixed it eventually though ), I decided to release a mod I consider quite useful for most people.
I've used the 10 for quite some time, and I've been messing with it from day 1.
Since the encryption is required for the phone to have proper radio signal (more info here), we are forced to keep our devices encrypted.
And because HTC uses proprietary encryption method, TWRP is unable to decrypt our data partition, which causes the recovery unable to read anything from data.
This is actually quite a big problem. If you want to full wipe and clean flash your favorite custom rom, the "Factory Reset" option in TWRP is not available, so you are forced to wipe the whole data partition, which will cause all your personal files stored in internal storage to be removed.
If you're a flashaholic like I am, you are forced not to store anything important in the phone storage because it will be wiped every time trying to clean flash a rom.
To breakthrough this inconvenience, I created this flashable zip to accomplish something similar to the "Factory Reset" option in TWRP.
Requirement: You have to use the systemless root of SuperSU to use this mod. If you want to flash the wipe script with SuperSU, flash SuperSU first, then flash the wipe script.
Important: If you have chosen "Require PIN/password/pattern to start device" in the "Secure startup" page during the initial setup, you CANNOT use this mod!
If you have to enter your PIN/password/pattern before your device booted up, this means that you have secure startup enabled. You CANNOT use this mod!
If secure startup is enabled and you flash this zip, your encryption will be messed up and you will have to format the whole data partition eventually to make your phone working again.
After flashing the mod, your data will not be wiped immediately in recovery because we cannot do so. It will wipe the data AFTER you rebooted back to system. It will reboot again after the wipe is done. If you flashed SuperSU at the same time with this mod, you will experience 2 consecutive reboot loops. This is normal behavior, don't panic.
If devs are interested in including this zip into your rom, you can use it in the same way as SuperSU:
Code:
package_extract_dir("wipe", "/tmp/wipe");
run_program("/sbin/busybox", "unzip", "/tmp/wipe/wipe.zip", "META-INF/com/google/android/*", "-d", "/tmp/wipe");
run_program("/sbin/busybox", "sh", "/tmp/wipe/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/wipe/wipe.zip");
For those who are interested in what this zip actually do, here is a brief explanation:
If secure startup is disabled, data will be decrypted as soon as the device booted up. We can only access data after it is decrypted. So our only choice is to wipe data after the device has booted up.
I created a script to wipe all data except SuperSU app, su binary image, and your internal storage.
SuperSU will automatically run scripts inside the directory /su/su.d, so after putting the script into the folder, SuperSU will the wipe script at boot time.
The problem is: su.img is also located in /data, how can we push files into the image? Fortunately, our master Chainfire has thought of this problem. The image /cache/su.img will be merged with /data/su.img during boot. So I just need to place the script into /cache/su.img, then Chainfire's script will do all the rest of the work automatically. If you're interested in the merging process, take a look at launch_daemonsu.sh in the ramdisk of a SuperSU modified boot for more details.

Is this helpful in regards to initial routing and flashing a rom or only afterwards to flash a new one?

topjohnwu said:
Disclaimer: This mod will wipe your data. I am not responsible for data loss after using this mod.
I tested on my device several times, it's working for me so internal storage is always preserved, but I cannot guarantee if anything is messed up on your side. Please read the post carefully before using this mod!
Always backup your important data before modifying your phone's software!
To compensate the mistake I have done in the modified SuperSU script (I fixed it eventually though ), I decided to release a mod I consider quite useful for most people.
I've used the 10 for quite some time, and I've been messing with it from day 1.
Since the encryption is required for the phone to have proper radio signal (more info here), we are forced to keep our devices encrypted.
And because HTC uses proprietary encryption method, TWRP is unable to decrypt our data partition, which causes the recovery unable to read anything from data.
This is actually quite a big problem. If you want to full wipe and clean flash your favorite custom rom, the "Factory Reset" option in TWRP is not available, so you are forced to wipe the whole data partition, which will cause all your personal files stored in internal storage to be removed.
If you're a flashaholic like I am, you are forced not to store anything important in the phone storage because it will be wiped every time trying to clean flash a rom.
To breakthrough this inconvenience, I created this flashable zip to accomplish something similar to the "Factory Reset" option in TWRP.
Requirement: You have to use the systemless root of SuperSU to use this mod. If you want to flash the wipe script with SuperSU, flash SuperSU first, then flash the wipe script.
Important: If you have chosen "Require PIN/password/pattern to start device" in the "Secure startup" page during the initial setup, you CANNOT use this mod!
If you have to enter your PIN/password/pattern before your device booted up, this means that you have secure startup enabled. You CANNOT use this mod!
If secure startup is enabled and you flash this zip, your encryption will be messed up and you will have to format the whole data partition eventually to make your phone working again.
After flashing the mod, your data will not be wiped immediately in recovery because we cannot do so. It will wipe the data AFTER you rebooted back to system. It will reboot again after the wipe is done. If you flashed SuperSU at the same time with this mod, you will experience 2 consecutive reboot loops. This is normal behavior, don't panic.
If devs are interested in including this zip into your rom, you can use it in the same way as SuperSU:
Code:
package_extract_dir("wipe", "/tmp/wipe");
run_program("/sbin/busybox", "unzip", "/tmp/wipe/wipe.zip", "META-INF/com/google/android/*", "-d", "/tmp/wipe");
run_program("/sbin/busybox", "sh", "/tmp/wipe/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/wipe/wipe.zip");
For those who are interested in what this zip actually do, here is a brief explanation:
If secure startup is disabled, data will be decrypted as soon as the device booted up. We can only access data after it is decrypted. So our only choice is to wipe data after the device has booted up.
I created a script to wipe all data except SuperSU app, su binary image, and your internal storage.
SuperSU will automatically run scripts inside the directory /su/su.d, so after putting the script into the folder, SuperSU will the wipe script at boot time.
The problem is: su.img is also located in /data, how can we push files into the image? Fortunately, our master Chainfire has thought of this problem. The image /cache/su.img will be merged with /data/su.img during boot. So I just need to place the script into /cache/su.img, then Chainfire's script will do all the rest of the work automatically. If you're interested in the merging process, take a look at launch_daemonsu.sh in the ramdisk of a SuperSU modified boot for more details.
Click to expand...
Click to collapse
Is the systemless one the one you patched?
Sent from my LG-H830 using XDA-Developers mobile app

stonew5082 said:
Is this helpful in regards to initial routing and flashing a rom or only afterwards to flash a new one?
Click to expand...
Click to collapse
It functions the same as "Factory Reset" in TWRP, which means it will wipe all data, but your personal files stored in internal storage will remain on the device.
StickyEyez said:
Is the systemless one the one you patched?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
Actually you can use the original version. But I suggest you to use my patched one, in case you accidentally wiped your whole data partition (this mod will not do this), you will stay encrypted, and your data signal will be fine

Hi topjohnwu
@ jollywhitefoot suggested you might be able to help to wipe userdata from download mode.
My phone will not get passed message "Your phones is encrypted" "TO DECRYPT YOUR PHONE. ENTER YOUR SCREEN LOCK PASSWORD" I had no screen lock password... i have different passwords to decrypt . Each time i put a password in it resest phone and does factory rest and then reboots straight into Bootloader again.
Phone has no recovery " Failed to boot into recovery mode" red writing on a black screen.
Phoned has OEM Relocked ....cant fastboot or unlock bootloader again
Please can you help

tailor999 said:
Hi topjohnwu
@ jollywhitefoot suggested you might be able to help to wipe userdata from download mode.
My phone will not get passed message "Your phones is encrypted" "TO DECRYPT YOUR PHONE. ENTER YOUR SCREEN LOCK PASSWORD" I had no screen lock password... i have different passwords to decrypt . Each time i put a password in it resest phone and does factory rest and then reboots straight into Bootloader again.
Phone has no recovery " Failed to boot into recovery mode" red writing on a black screen.
Phoned has OEM Relocked ....cant fastboot or unlock bootloader again
Please can you help
Click to expand...
Click to collapse
You can try to unlock your bootloader again.
If you cannot unlock it, then I regret to say that your phone might be doomed.
Never try to relock your phone if it's not in 100% stock condition and perfectly working.

topjohnwu said:
You can try to unlock your bootloader again.
If you cannot unlock it, then I regret to say that your phone might be doomed.
Never try to relock your phone if it's not in 100% stock condition and perfectly working.
Click to expand...
Click to collapse
I have tried unlocking boot loader again. The log shows oem needs to be unlocked.
When a RUU comes out, would that help recover the phone?
Sent from my ONE A2003 using XDA-Developers mobile app

tailor999 said:
Hi topjohnwu
@ jollywhitefoot suggested you might be able to help to wipe userdata from download mode.
My phone will not get passed message "Your phones is encrypted" "TO DECRYPT YOUR PHONE. ENTER YOUR SCREEN LOCK PASSWORD" I had no screen lock password... i have different passwords to decrypt . Each time i put a password in it resest phone and does factory rest and then reboots straight into Bootloader again.
Phone has no recovery " Failed to boot into recovery mode" red writing on a black screen.
Phoned has OEM Relocked ....cant fastboot or unlock bootloader again
Please can you help
Click to expand...
Click to collapse
Assuming you have a stock recovery image..
Boot to bootloader then recovery.
Long press power for a few seconds then tap volume up.
You can then factory reset in stock recovery

LeeDroid said:
Assuming you have a stock recovery image..
Boot to bootloader then recovery.
Long press power for a few seconds then tap volume up.
You can then factory reset in stock recovery
Click to expand...
Click to collapse
Oh dam it, just seen your post a bit late. Car phone warehouse has just collected my handset :silly: - im sure they'll send it back saying ive lost warranty :crying:

tailor999 said:
Oh dam it, just seen your post a bit late. Car phone warehouse has just collected my handset :silly: - im sure they'll send it back saying ive lost warranty :crying:
Click to expand...
Click to collapse
Oh dear....

topjohnwu said:
Requirement: You have to use the systemless root of SuperSU to use this mod. If you want to flash the wipe script with SuperSU, flash SuperSU first, then flash the wipe script.
Important: If you have chosen "Require PIN/password/pattern to start device" in the "Secure startup" page during the initial setup, you CANNOT use this mod!
If you have to enter your PIN/password/pattern before your device booted up, this means that you have secure startup enabled. You CANNOT use this mod!
If secure startup is enabled and you flash this zip, your encryption will be messed up and you will have to format the whole data partition eventually to make your phone working again.
Click to expand...
Click to collapse
the thing is i have selected no for secure boot but whenever i setup a fingerprint and boot then it gets enabled again even if i had disabled it...
any way around or am i missing on something.. currently on lee's rom

SacredDeviL666 said:
the thing is i have selected no for secure boot but whenever i setup a fingerprint and boot then it gets enabled again even if i had disabled it...
any way around or am i missing on something.. currently on lee's rom
Click to expand...
Click to collapse
you're talking about something different that he is. secure boot is a pin before you ever get the system loaded. you are talking about lockscreen pin/password, which, is mandatory if you use fingerprint scanner.

jollywhitefoot said:
you're talking about something different that he is. secure boot is a pin before you ever get the system loaded. you are talking about lockscreen pin/password, which, is mandatory if you use fingerprint scanner.
Click to expand...
Click to collapse
cool thank you...

I'm confused a bit. So every time I want to clean flash a rom, I can flash this script and it will wipe everything (system, data, cache etc.) except internal storage? Would dirty flashing a rom have any affect?

Ndaoud360 said:
I'm confused a bit. So every time I want to clean flash a rom, I can flash this script and it will wipe everything (system, data, cache etc.) except internal storage? Would dirty flashing a rom have any affect?
Click to expand...
Click to collapse
+1

Ndaoud360 said:
I'm confused a bit. So every time I want to clean flash a rom, I can flash this script and it will wipe everything (system, data, cache etc.) except internal storage? Would dirty flashing a rom have any affect?
Click to expand...
Click to collapse
It will only wipe data without internal storage.
You should flash this zip after you flash a rom.
It will wipe data after the device boots up.

topjohnwu said:
It will only wipe data without internal storage.
You should flash this zip after you flash a rom.
It will wipe data after the device boots up.
Click to expand...
Click to collapse
Ok so the process would be wipe system, cache, flash rom, flash data wipe script?

Ndaoud360 said:
Ok so the process would be wipe system, cache, flash rom, flash data wipe script?
Click to expand...
Click to collapse
Why would you wipe system this will be done by the rom installation, just flash the rom then flash the script & job done

LeeDroid said:
Why would you wipe system this will be done by the rom installation, just flash the rom then flash the script & job done
Click to expand...
Click to collapse
huh? Ever since I began rooting phones, I would wipe system, data and cache before a clean flash of a rom. I guess I never knew the rom does it for you. I thought the rom just over wrote the system possibly leaving remnants of the old system which could lead to issues which is why devs advise to full wipe when switching roms.

Ndaoud360 said:
huh? Ever since I began rooting phones, I would wipe system, data and cache before a clean flash of a rom. I guess I never knew the rom does it for you. I thought the rom just over wrote the system possibly leaving remnants of the old system which could lead to issues which is why devs advise to full wipe when switching roms.
Click to expand...
Click to collapse
Ah, a full wipe is only applicable to data buddy, if a rom dev doesn't wipe system before their installation, they need a good slap with a frozen kipper.
Cache is entirely optional

How To re-encrypt my OnePlus 3 ?

Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.

You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.

As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.

abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?

formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.

Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.

Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !

Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?

HTC 10 doesnt show up in Windows explorer apfter TWRP wipe

Hello guys,
I just installed TWRP onto my HTC 10. I unlocked the bootloader and flashed the recovery with TWRP. I backed up the default system and then wiped the Dalvik /ART Cache, the system partition, data partion and internal storage. As I now wanted to install LineageOS my device doesn't show up in the windows explorer. I tried rebooting the phone into recovery mode but it didn't work. So basically I can't accses my phone from my pc.
Can you give me some advice?
################ SOLVED ###################
I booted into TWRP. I chose "wipe" and then selected "format data". The description of "format data" already says "will remove the encryption of your phone". So I formated my phone, insalled LineageOS and GApps and the system is running, no password needed.
################ SOLVED ###################

_JonRyan said:
Hello guys,
I just installed TWRP onto my HTC 10. I unlocked the bootloader and flashed the recovery with TWRP. I backed up the default system and then wiped the Dalvik /ART Cache, the system partition, data partion and internal storage. As I now wanted to install LineageOS my device doesn't show up in the windows explorer. I tried rebooting the phone into recovery mode but it didn't work. So basically I can't accses my phone from my pc.
Can you give me some advice?
Click to expand...
Click to collapse
So basically you wiped everything you could without knowing what you were actually wiping, and what wiping that stuff would actually do to your phone?
When you wipe the system partition you won't have an OS unless you flash a ROM directly after.
Place a ROM onto your extSD and put that into your phone. Boot to recovery and flash the ROM.

I'm aware of what a wipe does, but I wasn't prepared for this case. I flashed a couple Samsung Devices and after flashing them I still had access to the phone via my pc as long I was in recovery mode. But it seems to me, that I found the problem. The device is, as far as I know, encryped by default and a signal loss after wiping/flashing the device is common.
https://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
However, I managed to install LineageOS and GApps, and the system boots. But after the boot is completed I am facing a screen where I have to enter a password to unlock Android. And I dont know which password I have to enter.
Do you know how to continue?
Thanks for your help, I really apprechiate it.

_JonRyan said:
I'm aware of what a wipe does, but I wasn't prepared for this case. I flashed a couple Samsung Devices and after flashing them I still had access to the phone via my pc as long I was in recovery mode. But it seems to me, that I found the problem. The device is, as far as I know, encryped by default and a signal loss after wiping/flashing the device is common.
https://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
However, I managed to install LineageOS and GApps, and the system boots. But after the boot is completed I am facing a screen where I have to enter a password to unlock Android. And I dont know which password I have to enter.
Do you know how to continue?
Thanks for your help, I really apprechiate it.
Click to expand...
Click to collapse
Obviously you didn't exactly know, because if you did you would have known that wiping /system would leave you with no OS.
Not slagging you here. I did the exact same thing when I had just got my 2nd gen Nexus 7 and switched to TWRP from CWM for the first time.
For your password issue:
twrp > advanced > file manager > data > system ~ delete the locksettings.db files and reboot

Thank you for your reply!
Unfortunatley, the folder "data" doesn't contain any subfolder or file. Do you still know how to unlock my device?

################ SOLVED ###################
I booted into TWRP. I chose "wipe" and then selected "format data". The description of "format data" already says "will remove the encryption of your phone". So I formated my phone, insalled LineageOS and GApps and the system is running, no password needed.
################ SOLVED ###################

Question Stuck on "Pixel is starting"

Had to do a factory reset, and all was good. Using LSposed with Magisk and reinstalled several mondules. Upon reboot, the screen hangs at "Pixel is starting." So I rebooted into safe mode, knowing the Magisk modules would be disabled, but the same thing happens, even in safe mode. Booted again. I can access all my settings, and adb works fine. But I'm clueless as to what I should do, even with adb and settings access.
Will appreciate any help. Everything is backed up, I'm just trying to avoid the nuisance of having to factory reset again and all that entails.
Thanks.

You can try Official Google Android Flash Tool and uncheck the wipe data option (and don't force flash all partitions, either, which will also wipe), and don't forget to uncheck the option to re-lock the bootloader.
That official site has solved many weird issues where even manually flashing the full factory image hasn't solved the problem. Good luck, let us know if that's what you do and how it goes.

my old go-to for boot issues was last_kmsg. I recentlky found abou about boot-chart, which logs what happens during boot, and may log an error for you. You will have to run this in recovery if yopu are in a non-booting state
To enable it:
Code:
mkdir -p /data/bootchart;
touch /data/bootchart/enabled;
try a reboot, which fails. Reboot to recovery and retrieve the logs
init/grab-bootchart.sh - platform/system/core - Git at Google
I havent had to use it "in anger" yet, but it will be my tool of choice.

Develop Bugs

welcome