Phone is not encrypted but Android and TWRP say it is. [Solved] - ZTE Axon 7 Questions & Answers

SOLVED:
In TWRP I went WIPE > FORMAT DATA
The format failed with error 255 (with many more errors relating to encryption and mounting of /data) and /data would no longer mount
Noticed that the failed format had changed the file system of /data from ext4 to f2fs
Used WIPE > ADVANCED WIPE > REPAIR OR CHANGE FILE SYSTEM to change /data back to ext4
Bob's your uncle
Original issue:
Currently my device is fully functional except that in Android settings under "Security" it indicates that my phone is encrypted. When booting TWRP the console says:
Code:
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Here's how I got here:
-Device arrived yesterday with B29 installed
-Took official OTA to B15
-Unlocked bootloader using the Axon7Toolkit (flashes the unlock EDL file via MiFlash and issues a "fastboot oem unlock" command)
-Flashed TWRP 3.1.1-0 via "fastboot flash" command
-Flashed B19 bootstack and system from post #4 of this thread: https://forum.xda-developers.com/axon-7/development/bad-boyz-zte-axon-7-rom-m-magisk-root-t3543201 (in preparation for Bad Boyz ROM)
-TWRP reported that no OS was installed when attempting to reboot system. Tried to boot system anyways. No boot. Reflashed the above mentioned B19 system. Same as before, no boot.
-Flashed stock recovery
-Used the update.zip file provided by ZTE to flash B19 in stock recovery
-Tried to reboot to fastboot so I could flash TWRP. It just rebooted after selecting the fastboot option.
-Used the test adb and fastboot option in Axon7Toolkit. Toolkit told me that access to fastboot may be locked out due to an incorrect partition flag. It suggested that I use the bootloader unlock option. I followed the prompts again and used MiFlash to flash that EDL file that enables certain fastboot commands. Instead of continuing the bootloader unlock process in the Toolkit (which would have issued a 'fastboot oem unlock' command) I exited the toolkit after flashing the EDL file.
-Flashing that EDL file did enable me to boot to fastboot. However when I booted the system I was asked for a PIN to decrypt data. When I rebooted to TWRP I was asked for a PIN as well.
-Used the "Restore to stock" option in Axon7Toolkit (flashed the full B19 EDL via MiFlash)
-Device now boots both recovery and the system without asking for a PIN. However, as mentioned above, both Android and TWRP say the device is encrypted. (this is the current state of the device)
I'm not sure that this adversely effects me beyond not being able to actually encrypt my phone but I would still like to fix it. I'm might be returning this phone and I'd like to send it back the way I got it. Even if I keep it, leaving it pseudo-encrypted would bug me. How do I fix this please? I made sure that before I started installing things via recovery that I removed my fingerprint and PIN.

Doc Ames said:
Currently my device is fully functional except that in Android settings under "Security" it indicates that my phone is encrypted.
Click to expand...
Click to collapse
You could do a full backup in TWRP and wipe the data partition. After that you can restore the backup. If you have no PIN or gesture unlock enabled, then it should boot fine. Otherwise you should delete the locksettings.db* files in /system/data in TWRP.
Sent from my ZTE A2017U using Tapatalk

DaCashFlow said:
You could do a full backup in TWRP and wipe the data partition. After that you can restore the backup. If you have no PIN or gesture unlock enabled, then it should boot fine. Otherwise you should delete the locksettings.db* files in /system/data in TWRP.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I ended up having to format /data in TWRP. See above.

Related

I think I am bricked

So at one point, I accidentally deleted the OS off of my phone, but I still had TWRP installed. The only solution was to flash a rom through ADB, but TWRP didn't have ADB for whatever reason for me, so I flashed CWM which did have ADB. I was able to flash CWM after I pushed a rom through ADB and install Android 4.3 w/ root from nexus4root.com. It worked correctly, but I noticed that I only had 5.66gb of storage on my phone. I have the 16gb variant which would have about 12gb usable. So I followed a guide here in xda to get back my 16gb. I was told to wipe my phone step by step and flash a factory image. But ere are my errors not
- When I try to flash the factory image, it says 'missing boot.sig, system.sig, and something else.sig'
- I have no recovery on my phone
- When I try using fastboot commands, it says FAILED (command write failed (unknown error))
I am pretty stuck here. And I did redownload the root files.
EDIT: I was able to fix fastboot and flashed TWRP, but my devices is encrypted and requires a password
You should be able to clean your encrypted user storage by using "fastboot erase userdata", and you can do it for /data /system and /cache partition as well.
Or go into TWRP, if it ask for password, just press cancel. Then go to Wipe -> Advance -> Select "Format Data" and it will do a full wipe and cleaning out the encrypted partition.
As for using fastboot to restore to stock, shouldn't be any problem as long as you have the correct drivers and latest ADT package from Google.
I did something similar and had encryption on. My fix was "fastboot flash" the stock system, boot and recovery (4.3 for me). After getting back in my phone and verifying everything was there I re-flash CWM and re-rooted.

[GUIDE] No Deep Sh!t Guide To UPGRADE BOOTLOADER

NO DEEP SH!T GUIDE TO UPGRADE BOOTLOADER​--Yes this is what it says!​
A short, Simple, No Questions ask guide to Upgrade bootloader without using fastboot or a PC and without losing your Internal Storage Data.
Steps:
Assuming that you are on OLD bootloader right now, already using OFFICIAL TWRP (compatible with old bootloader only).
Flash a rom which supports Block Based OTA or Stock ROM(oos 2.X.X). (I used PURITY ROM as i was having that only with me)
Explaination: Make sure that you are already running a rom which was using a block based OTA to install (those which have files compressed in a system.img/dat file, roms compiled by me (DU/Tesla/AICP/Broken) doesnt have it as i wanted all files to be easily extractable. Stock Oxygen OS zip scans for block size etc so its recommended you use a rom with block based ota installation)
Make sure you are having "OEM unlock" and "ADB/USB debugging" enabled in Developer options (if not, enable them first!)
Reboot to recovery > Go to MOUNT section and make sure all partitions are mounted) > Go to INSTALL and flash THIS STOCK ROM ZIP > when flashing is completed, Click on Back Button and Go to the main menu of TWRP and click on INSTALL > Click on Install/Flash image option and flash this NEW TWRP > Then click on REBOOT TO RECOVERY > Then click on REBOOT SYSTEM.
Let Stock rom boot first then enable "ADB/USB Debugging" and "oem unlock" in Developer Options
Reboot to Recovery and Flash This SuperSu Zip > Then Reboot System.
And You are done!
Now you are free to flash Any ROM or Kernel (which supports New Bootloader).
Side note:
If you are already in Trouble - unable to boot recovery/fastboot etc. then follow this Mega Unbrick Guide to Unbrick your device, (this guide will restore your device back to old LP Bootloader then follow the above guide to upgrade to New Bootloader.
I could boot into the stock os but couldn't get twrp to install...
After installing twrp and rebooting to recovery, I got a glimpse of the twrp interface, the screen flashed and then rebooted, I am back to stock recovery
So yeah went back and did the blu_spark install from PC
three0s said:
I could boot into the stock os but couldn't get twrp to install...
After installing twrp and rebooting to recovery, I got a glimpse of the twrp interface, the screen flashed and then rebooted, I am back to stock recovery
So yeah went back and did the blu_spark install from PC
Click to expand...
Click to collapse
Follow the steps properly and it will work as expected
These steps are tried and tested by many peeps and works.
Back to old!
Well this works good enough,
But can u provide a zip for going back to old bootloder, i know that flashing the whole oos 2.x.x rom does the trick but flashing a small file would be better and would save some memory and some seconds while flashing.
I'm on step 4, trying to flash the latest stock rom (OOS 3.1.4 which download from Oneplus site) and constantly gives me an error 7 during the installation. I tried to full wipe all sections, re-flash but the same error. I tried to change the "updater-script" erasing the commands, re-flash but the same error. I tried the mega unbrick guide and next your steps but again the same error. I can't understand what is going on. Everytime I manage to return to OOS 2.2.1 or a ROM with 6.0.1 version but I can't update the bootloader succesfully.
Any suggestion?
Good afternoon,
@CheckYourScreen You wrote "enable ADB/USB debugging". Why should I enable adb/usb if I have no contact with the PC? If I'm wrong so correct me please.
@three0s Maybee my Note helps you. Your OPX is oem unlockt, adb / usb driver installed so reboot in fastboot. With "fastboot devices" is your OPX hopefully detected from your PC. Now write "fastboot oem unlock". "fastboot erase recovery" will erase the Stock-Recovery. With "fastboot flash recovery your-twrp.img" the new one is installed. When you write now "fastboot reboot" so is the new Recovery installed and your System started but when you write "fastboot boot your-twrp.img" you make a reboot directly in the twrp-Recovery and you can install supersu and so on. Good Luck and, yes, my english is poor. Sorry.
mahalo

Looking for thorough flashing guide

Hi,
Does a thorough guide exist on how to flash custom ROM on this phone?
I have done quite a lot of flashing in my life but can't a ROM flashed for the love of God.
Got TWRP installed, ADB works, cables are good.
Thanks!
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Waancho said:
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Click to expand...
Click to collapse
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
AndroidDevices said:
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
Click to expand...
Click to collapse
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Waancho said:
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Click to expand...
Click to collapse
It does have Magisk installed, it should if its one of the newer builds and all you need to do is install Magisk Manager which in turn activates Magisk
Installing Magisk manager was one of the first things I did, but unfortunately, the latest version A/B Havoc at the aforementioned link did not have Magisk.
There's about 6 or 7 and probably a bunch of YouTube's
Sent from my PH-1 using XDA Labs

[guide] [root] [oreo&pie] [jeter/aljeter] [twrp, decrypt, magisk] [stock firmware]

* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
THIS GUIDE APPLIES TO JETER AND ALJETER DEVICES
FOR ALJETER DEVICE OWNERS ONLY.
there are ALOT of different variants of the aljeter so please before beginning this root method go to settings, system, about phone. look for either sw version or software channel verison and either remember what it says or write it down. me or anyone else will need this to help troubleshoot which aljeter variant you have. this will also be important to know incase you mess up and need to reflash stock firmware which those instructions are at the bottom of this guide.
The following devices have been confirmed to work on devices with Android 8 (Oreo)
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile/ Virgin Mobile
XT1922-9 Motorola Retail
The following devices have been confirmed to work with Android 9 (pie)
XT1922-7 (Jeter) boost Mobile/ Virgin Mobile.
XT1922-3 (Aljeter)
XT1922-5 (Aljeter retbr)
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware FOR JETER can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/ and here FOR ALJETER https://mirrors.lolinet.com/firmware/moto/aljeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisite:
Unlocked bootloader.
FOR LINUX USERS. If you're using a linux distro then congrats this is all you should have to run. open command prompt and run this. "sudo apt-get install adb" without quotation marks. then follow Motorolas bootloader guide in provided link. continue to step 1 after.
FOR WINDOWS USERS.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
DECRYPTION AND BACKUP.
NOTICE
IF YOU YOU ARE USING THE 32GB MODEL OR THE 16GB MODEL AND ARE ON ANDROID 9 (PIE) PLEASE USE THE ANDROID 9 (PIE) MODEL TWRP. USERS WITH THE 16GB MODEL AND THE 32GB MODEL ON ANDROID 8 (OREO) WILL STILL NEED TO USE SEPERATE TWRPS
MAKE SURE TO SWIPE RIGHT IN TWRP TO ALLOW SYSTEM MODIFICATIONS.
Step 1.) Download and extract twrp image to the ADB/Fastboot folder on your computer.
FOR ANDROID 8 (OREO)
16gb model twrp: https://www.androidfilehost.com/?fid=6006931924117921836
32gb model twrp: https://www.androidfilehost.com/?fid=6006931924117927211
FOR ANDROID 9 (PIE)
https://www.androidfilehost.com/?fid=6006931924117921849
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding the power button and volume down button at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel)
Step 5.) time to backup your stock recovery and stock boot. use these commands one at a time.
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you need to revert to stock later.
Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader
CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.
ROOT PROCESS.
Step 1.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery twrp.img
Step 2.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. swipe right to allow modifications. IT SHOULD NOT ASK YOU FOR A PASSWORD THIS TIME IF IT DOES YOU MESSED UP DURING THE DECRYPT PROCESS
Step 3.) Follow this link to the creators site to download the disabler zip. https://zackptg5.com/android.php#disverfe download it to your ADB/Fastboot folder.
Step 4.) Download the Magisk Beta v20.0 and or the latest zip file from https://github.com/topjohnwu/Magisk/releases to your ADB/Fastboot folder. (I personally use beta so I use beta in this guide but you don't have to)
Step 5.) Run the following command to push the dm_verity force encrypt disabler and magisk zip to your device
Code:
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /tmp
adb push Magisk-v20.0.zip /tmp
This will push the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v20.0.zip to your /tmp folder
Step 6.) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 7.) Flash Magisk-v20.0.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 8.) Reboot your device
Step 9.) Just wait for the device to boot up. might take a bit and it might seem its in a bootloop but if you followed this guide exactly as is just wait it out it took about 5-10 minutes before i got to the "lets get started" screen after updating to pie (android 9)
Step 10.) Verify Magisk Manager is installed and the root functionality works. sometimes the manager apk wont be installed so download the magisk manager apk from the provide links. click advanced to see if the boxes are unchecked. (2022 edit) If you see magisk app and magisk needs updated you can do it but I can't confirm if it's safe and what works and doesnt after
CONGRATS! IF YOU DIDNT SKIM MY GUIDE YOU SHOULD HAVE A SUCCESSFULLY ROOTED AND ENCRYPTION DISABLED DEVICE, HAVE FUN.
IF YOU MESSED UP, DIDNT PUT A COMMAND IN CORRECTLY, SKIMMED, OR ARE INA GENUINE BOOTLOOP/BRICK THIS SECTION IS FOR YOU
Step 1.) DOWNLOAD STOCK FIRMWARE HERE FOR JETER AND CERTAIN ALJETER DEVICES (from what i can tell usa variant aljeter devices are consided jeter) https://mirrors.lolinet.com/firmware/moto/jeter/official/ IF YOU REMEMBER OR WROTE DOWN YOUR SW CHANNEL VERSION THEN DOWNLOAD STOCK FIRMWARE FOR BASICALLY EVERY OTHER ALJETER DEVICE HERE. https://mirrors.lolinet.com/firmware/moto/aljeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastbot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Credits: @kwiksi1ver for making the original guide. @topjohnwu for magisk. @shimp208 for minimal adb/fastboot. @Spaceminer for providing the new twrps for 16gb and 32 gb devices, and @Zackptg5 for making the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers.
QUICK NOTE/EDIT: SINCE I DO NOT OWN THIS DEVICE ANYMORE I CANNOT CONFIRM IT BUT YOU SHOULD BE ABLE TO UPDATE TO THE LATEST MAGISK 24.3 FROM THE MAGISK APP AFTER YOU INSTALL V20, AGAIN I AM NOT ABLE CONFIRM IF IT WORKS, CAUSES BOOTLOOPS, OR ANYTHING SO KEEP THAT IN MIND, but hopefully it does work for yall I've also updated the ADB commands for the disabler to reflect its latest version and I've updated the magisk link to topjohnwus GitHub as that's where all updates happen/ go first
RESERVED
In order to update the confirmed working models for this guide, if anyone that has this device with a unlocked bootloader and does root and decrypt successfully using my guide and it's not on the confirmed device list. PLEASE JUST PM ME and let me know. Please include device model number, name, and if on aljeter your software channel version.( For example. Xt1922-5 aljeter, sw channel: retbr)
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
blowingoff said:
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
Click to expand...
Click to collapse
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Kuntitled said:
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Click to expand...
Click to collapse
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Spaceminer said:
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Click to expand...
Click to collapse
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
blowingoff said:
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
Click to expand...
Click to collapse
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Spaceminer said:
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes"no to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Click to expand...
Click to collapse
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Kuntitled said:
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Click to expand...
Click to collapse
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
Click to expand...
Click to collapse
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
Click to expand...
Click to collapse
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Starkiller2 said:
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Click to expand...
Click to collapse
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Kuntitled said:
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Click to expand...
Click to collapse
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Kuntitled said:
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Click to expand...
Click to collapse
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Starkiller2 said:
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Click to expand...
Click to collapse
Do i check the file system for data at any point?
Kuntitled said:
Do i check the file system for data at any point?
Click to expand...
Click to collapse
Only if it won't mount
Starkiller2 said:
Only if it won't mount
Click to expand...
Click to collapse
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Kuntitled said:
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Click to expand...
Click to collapse
No that's fine
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues
Click to expand...
Click to collapse
But data won't work as ext4, hence the boot loop
Try going to fastboot and typing
Fastboot -w
Then boot to recovery
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Click to expand...
Click to collapse
I honestly don't see how, especially if stock is working

Find device storage corrupted your device is unsafe now.

So I unlocked bootloader on my redmi note 7.
Then I flashed twrp and rooted my device.
Then I flashed pixel experience but it stuck on the Google logo after reboot. I tried factory reset in twrp but it didn't work.
So I restored the backup I did before flashing pixel experience.
And then my phone stuck on bootloop.
So I booted into fastboot mode and flashed the fastboot rom and it worked. I have successfully unbricked my device.
But now it shows "find device storage corrupted your device is unsafe now"
Everything works fine except I can't turn on find device and also can't install miui ota updates via twrp.
(And also when flashing twrp for the first time when I reboot it showed the stock recovery because I hadn't flashed disable dm-verify because when I am in twrp and try to mount my system to my computer my phone doesn't show up in the computer. So first I copied the disable dm-verify file then again flashed twrp then booted into twrp and then flashed disable dm-verify. I don't know if it is necessary to format data when flashing twrp. Maybe that's why the problem occured. I don't know.)
Please help.
Thank you.
Extract persist.img from official fastboot rom and replace the existing persist in Orangefox.
At least it helped me.
Persist.img flash through recovery gonna fix the problem but forget about Netflix and L1!!
Personally speaking had that problem with corrupted message pop up every time i reboot my device and when i flashed the persist.img through OrangeFox recovery i lost L1 forever (and there is no turning back).
If you wanna try that method i highly suggest you to Backup your Persist Partition first.
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Lucky-thirteen said:
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Click to expand...
Click to collapse
I tried may hours to define the problem's source but i think that's unclear in every situation. Others say that's a persist.img corruption while others had that problem with Mi Account corruption, etc.
Mine corrupted message came when i tried to flash Global Official MIUI in a EU variant device through normal process that doesn't engage any kind of Persist partition rewrite.
I had a backup of persist.img and flashed original from EU fastboot file and finally after that I repatch my old persist.img. The first time i did that process my device and L1 worked properly (even that spam message disappeared) but after a long time that I tried same process for same problem i completely lost my L1 [strange af!].
So, a safe process to try now is to flash back the official fastboot image of your variant (Erase + Lock [for L1]) through MiFlash tool and check that corruption message if it goes away (be careful to flash the correct fastboot image or you will get a a bricked device).
In conclusion it's Extremely advisable to keep a full backup of your partitions and especially Persist partition if you wanna flash Roms and generally unlock bootloader!
I use twrp recovery
I don't know about orange fox recovery
Strange51 said:
I use twrp recovery
I don't know about orange fox recovery
Click to expand...
Click to collapse
Always use OrangeFox for Lavender here is the link (download and test with latest R10.1_02-Stable)

Categories

Resources