Related
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?
Hi all,
Long time lurker, first time poster (I think...)
If this is in the wrong location and/or the title is off, I apologise.
I'm having a weird issue with my P3XL. I'm able to properly root it with Magisk (have used 17.3 beta in the past, am now on 18.0), but after "a while", if/when I reboot my phone, it'll simply refuse to boot. Or rather, it will boot, it will show me the Google logo, and then I see my lock screen for about half a second, screen goes black, and then every so often the time (in white) will flash/blink in the top right corner. After a while it will also flash/blink Safe Mode in the bottom left. After a few more blinks, it will reboot and tell me: "Can't load Android system/ Your data may be corrupt."
Now, I have not yet done a full root cause analysis, but it seems to have started after I messed up my first unlock and used the "format data" option in TWRP. I have since flashed (and wiped) the stock factory image, but this issue seems to be reocurring after I root my phone again.
I am currently on the P3XL December update, and am using Magisk 18.0 with TWRP 3.2.3-3-crosshatch, but my first Magisk install after which this happened was on P3XL November, Magisk 17.3 (beta), TWRP 3.2.3-1.
I had hoped it was a Magisk beta issue, but I feel like there's more to this than just Magisk. My gut is telling me it's some kind of encryption thing, that doesn't work well due to the (accidental) full format through TWRP.... But again, gut feel, not based on any true evidence.
The steps to reproduce (for myself) are:
1) flash_all December stock firmware (with -w/wipe option enabled)
* Install my phone, some apps, set up screen lock (pin) and fingerprint
2) download Magisk 18
3) fastboot boot twrp
4) install Magisk 18 through twrp
5) reboot (all looks great, rooted, safetynet, the whole shebang)
6) use my phone for a couple of days
7) decide I need to reboot my phone (for whatever reason, I've run out of battery, I used GPS Joystick and it needed me to reboot to disable location services, I just wanted to reboot)
8) Phone panics and I need to start at 1
When in step 8, I have tried (without success):
* fastboot boot twrp, wipe dalvik/cache
* fastboot boot twrp, install Magisk (with and without dalvik wipe)
* * No issues with Magisk, it happily tells me all is well
* fastboot flash (stock) boot.img
* install twrp (and try to install Magisk)
* use the stock bootloader's factory reset
* use twrp's factory reset
Only the last two will allow me to boot once, but at the end of the setup process stop responding to screen inputs/grind my phone to a halt/flash&blink my screen (although the wifi, phone bars and charging icon remain on/visible)
Has anyone seen this behaviour before, and if so, has found a permanent solution? Because I like having my phone rooted, but I don't like having to wipe and reinstall everything every time my phone restarts
Thanks in advance!
It seems that the phone goes to heck after you reboot? When you flashed the stock boot image did you flash it to both slots? Next time you try to root install the magisk uninstaller zip prior to installing the magisk zip, this of course is all done in twrp. At this point I would start with the factory image, less the -w. Then boot twrp and run the magisk uninstaller then the magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks @jd1639
I have flashed both slots with the factory image. Good call on the Magisk uninstaller. I had assumed that wouldn't be required on a full flash.
*However* I seem to have made some progress with my root cause analysis, and unlike what the title now says, it seems to be the GPS Joystick that I'm using. As soon as I turn on "Disable Location Services" and turn on "A-GPS Reset", it goes to heck. It rebooted perfectly fine the 6 times before I enabled those settings.
I realised in all my repeats, the GPS Joystick's settings were the only other common denominator.
I have just stock flashed my phone (the 3rd time today), both slots, and will try Magisk Uninstall before I install it again... And then I'll repeat my steps up to the GPS Joystick's settings.
I'll try to report back asap.
So far, everything looks alright. I have:
Flashed (and wiped) December stock firmware
Booted TWRP, uninstalled magisk, wiped cache/dalvik, installed Magisk
Installed GPS Joystick (and used private mode)
Installed Systemify Magisk module and installed above as system app
Rebooted multiple times, no issues.
I have yet to enable either A-GPS Reset and/or Disable Location Services, but I have to get to work and don't have time to further tinker right here right now.
hey ho
so i have been reading several guides here and i recently posted in some of the threads but i think maybe it'll be clearer for you if i go through the steps i've taken. My goal is a non MIUI - rom without all the garbage, plus i want the option of expanded display or whatever it's called to hide the statusbar and i also want a rom with built in dark theme for the menus (settings for example)
what i did
redid EVERTYING, from scratch, I.E. (TWRP was erased)Downloaded: nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105
i then flashed it with MiFlashSetup.msi (previously before this whole entire debacle i had miui_MIMAX3Global_V10.2.1.0.PEDMIXM_a9972483fb_9.0.zip)
i installed TWRP with TOOL_ALL_IN_ONE_1.0.9.4-NO-INSTALLER
i booted into TWRP
Chose to flash DotOS-v3.0-arm64_aonly-vanilla-20190310.img and it then proceeded to ask what partition to flash, i chose system.
i then tried installing open_gapps-arm64-9.0-pico-20190327.zip and it said something about insufficient space and or / failed to mount partitions so i mounted vendor and system partitions and tried again, didn't help. so i just rebooted and it is now in the boot animation for DotOS and just.... spinning it's wheels so to speak...
p.s. before i did step 1 as extreme as that was when i tried going into twrp it asked me to decrypt using a password, the password should be the one i chose at setup, in my case i chose PIN and that password was never accepted as the correct password in TWRP so i could never show the system partition, it was listed as 0mb.
premier69 said:
hey ho
so i have been reading several guides here and i recently posted in some of the threads but i think maybe it'll be clearer for you if i go through the steps i've taken. My goal is a non MIUI - rom without all the garbage, plus i want the option of expanded display or whatever it's called to hide the statusbar and i also want a rom with built in dark theme for the menus (settings for example)
what i did
redid EVERTYING, from scratch, I.E. (TWRP was erased)Downloaded: nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105
i then flashed it with MiFlashSetup.msi (previously before this whole entire debacle i had miui_MIMAX3Global_V10.2.1.0.PEDMIXM_a9972483fb_9.0.zip)
i installed TWRP with TOOL_ALL_IN_ONE_1.0.9.4-NO-INSTALLER
i booted into TWRP
Chose to flash DotOS-v3.0-arm64_aonly-vanilla-20190310.img and it then proceeded to ask what partition to flash, i chose system.
i then tried installing open_gapps-arm64-9.0-pico-20190327.zip and it said something about insufficient space and or / failed to mount partitions so i mounted vendor and system partitions and tried again, didn't help. so i just rebooted and it is now in the boot animation for DotOS and just.... spinning it's wheels so to speak...
p.s. before i did step 1 as extreme as that was when i tried going into twrp it asked me to decrypt using a password, the password should be the one i chose at setup, in my case i chose PIN and that password was never accepted as the correct password in TWRP so i could never show the system partition, it was listed as 0mb.
Click to expand...
Click to collapse
To avoid this gapless error when installing gapps, first boot the GSI that you have installed, then go back to twrp and install the gapps. In my opinion, xiaomi.eu roms are better as a basis for GSI's, even because I've never been able to start a GSI using an official xiaomi rom.
The main thing is that your data partition is encrypted and you will need to format the data partition.
This may help you - https://forum.xda-developers.com/mi-max-3/how-to/b-guide-to-fake-rom-unlocked-bootloader-t3846891 (where appears china rom, china dev ... can be replaced by global rom - this process has to be done before installing the GSI of your choice and take care of the ARB.).
Germano1980 said:
To avoid this gapless error when installing gapps, first boot the GSI that you have installed, then go back to twrp and install the gapps. In my opinion, xiaomi.eu roms are better as a basis for GSI's, even because I've never been able to start a GSI using an official xiaomi rom.
The main thing is that your data partition is encrypted and you will need to format the data partition.
This may help you - https://forum.xda-developers.com/mi-max-3/how-to/b-guide-to-fake-rom-unlocked-bootloader-t3846891 (where appears china rom, china dev ... can be replaced by global rom - this process has to be done before installing the GSI of your choice and take care of the ARB.).
Click to expand...
Click to collapse
what do the acronyms GSI and ARB stand for?
premier69 said:
what do the acronyms GSI and ARB stand for?
Click to expand...
Click to collapse
GSI - generic system image (in this case, the rom you download in .img format for installation via twrp - for example, DotOS)
ARB - anti roll back - which is a mechanism to prevent the version rollback of Android.
Always read the topics carefully and follow the step by step without changing anything, not to generate problems.
I was avioding this current MIUI 12 OTA update on my Redmi Note 8 because I went through the same crap already last time. After a while it just installed anyway while the phone was idle (only sure way seems uninstalling the updater via fastboot).
So what did it do (again):
1. It did overwrite TWRP recovery (though it was originally installed with "allow modifications")
Had to flash TWRP again via fastboot and MIUI would still overwrite it (despite directly booting into recovery and doing the swipe) after every boot unless Magisk was installed.
2. It broke TWRP's ability (after being reinstalled) to decrypt the data partition with the pin / swipe matrix. TWRP doesn't even ask for a pin or swipe marix any more.
Just shows garbled folders on the data partition. Decryption worked before the OTA update.
3. It broke Magisk (needs to be reinstalled via TWRP). Had to reinstall it from a USB-stick (since internal storage is encrypted) to at least get root back.
Any ideas to fix the decryption in TWRP and avoid the complete hassle in the future with the next OTA update?
EDIT: Decryption issue fixed by using "Miui HellasTWRP recovery". If that makes me a member of some bot net? Time will tell.
Question remains: Is there a way to have OTA do it's thing while leaving my stuff (recovery and magisk) tf alone?
str_ange said:
I was avioding this current MIUI 12 OTA update on my Redmi Note 8 because I went through the same crap already last time. After a while it just installed anyway while the phone was idle (only sure way seems uninstalling the updater via fastboot).
So what did it do (again):
1. It did overwrite TWRP recovery (though it was originally installed with "allow modifications")
Had to flash TWRP again via fastboot and MIUI would still overwrite it (despite directly booting into recovery and doing the swipe) after every boot unless Magisk was installed.
2. It broke TWRP's ability (after being reinstalled) to decrypt the data partition with the pin / swipe matrix. TWRP doesn't even ask for a pin or swipe marix any more.
Just shows garbled folders on the data partition. Decryption worked before the OTA update.
3. It broke Magisk (needs to be reinstalled via TWRP). Had to reinstall it from a USB-stick (since internal storage is encrypted) to at least get root back.
Any ideas to fix the decryption in TWRP and avoid the complete hassle in the future with the next OTA update?
EDIT: Decryption issue fixed by using "Miui HellasTWRP recovery". If that makes me a member of some bot net? Time will tell.
Question remains: Is there a way to have OTA do it's thing while leaving my stuff (recovery and magisk) tf alone?
Click to expand...
Click to collapse
your best bet is use OrangeFox ,flash DFE and format data and enable "Aggressive stock recovery deactivation"
(i said bet because i'm not sure if it's the reason i kept my recovery while flashing miui12 or not)
note that uninstalling the updater with adb dosn't remove the app completly, it just freez it for user0 ,to remove it use lucky patcher or titanium backup or just delete the apk with recovery file manager
Hey,
I am having a bootloop after a pretty normal Android usage. All I did was:
browsing Internet, moving some photos, deleting file, moving some videos to Shelter (workprofile)
using Instagram inside Shelter, uploading a video
then I rebooted (in order to update my shelter file directory), and I suddenly got a system message that my workprofile was locked and requested my security code, I entered it several times but the workprofile including all shelter apps and files stayed inaccessible, it would keep requesting the code
so I rebooted again and since then the phone gets stuck at the Redmi logo, then boots into twrp recovery
I am running crDroid 9.2 on a Redmi Note 8. I have been running that system for at least two months now, only minor issues (never a bootloop). I was not really messing with any system settings/files.
Booting into TWRP, I am not being asked for decryption of the data, so maybe the system is even corrupt on that level... What can I do
I am running latest twrp 3.7.0-12.1
Do you have any ideas of what could be the least invasive procedure to fix this bootloop (i.e. without losing any data)?
Thanks in advance!