I'd like to install lineageOS, on muiu 8 now, twrp and rooted. When i was on muiu 7 twrp said system was encrytped, now it says its succesfully decrypted in twrp with default password. Can i now just flash normally the lineageOS zipfile from twrp or do i need additional steps to install it ?
My TWRP has said "Successfully decrypted" since MIUI 8 (can't remember what it said in MIUI 7)
I flashed Lineage after wiping system and it worked fine for me. Perhaps I got lucky though?
Related
I install latest TWRP 3.1.0 version today.
All the user data, some apps (Waze, Gmail, Gmaps...), SMS were wiped.
I have RR-N-v5.8.2-20170218-oneplus3t-Official currently installed.
I reinstall some apps back.
After system reboot all seemed fine.... But after boot to recovery (TWRP 3.1) and than boot into system all was gone again.
It looks like every boot to recovery wipes user data and some apps...
Flash 3.0.4-1 again
Same problem here with 3.1.0.0.
I flashed 3.1.0.0 img with 3.0.4-1 and do not have the issues OP is describing.
Edit: stock Open Beta 3 rooted.
sossio18 said:
Flash 3.0.4-1 again
Click to expand...
Click to collapse
I did... and restore system from backup BUT some userdata is gone forever...
Apparently, the official TWRP 3.1.0-0 for OnePlus 3T only works with Oxygen OS. So far, only users using custom ROMs have reported issues with partition wipes after flashing the latest TWRP.
Anova's Origin said:
Apparently, the official TWRP 3.1.0-0 for OnePlus 3T only works with Oxygen OS. So far, only users using custom ROMs have reported issues with partition wipes after flashing the latest TWRP.
Click to expand...
Click to collapse
Happened to me on OOS. Went back to 3.0.4-1
Sent from my OnePlus 3T using XDA Labs
It was updated to 3.1.0-1 try that
I suppose this of because of the official TWRP 3.1.0-0 is not using the backported F2FS driver. I'm using EXT4 filesystem on data partition so therefore I'm not experiencing any data loss.
Was on RR 09.03 with OB3 firmware, it completely destroyed my phone. Bootloops, impossible to go back to recovery, when in recovery, impossible to see files to flash them, even going back to 3.0.4.1 did not solve everything, reinstalled Freedom OS but had screen total freezes.... Had to go through the total disaster recovery utility, and I am still re-installing everything...
TWRP 3.1.0.0 ate 4 hours of my flash-addicted life... FML !!!
**STAY AWAY FOR NOW**
Blu_spark 3.1.0 version is not affected by this, only the official.
Stock OOS 4.0.3 and TWRP 3.1.0-1 = ALL GOOD!
Kjaups said:
Stock OOS 4.0.3 and TWRP 3.1.0-1 = ALL GOOD!
Click to expand...
Click to collapse
Can confirm. TWRP 3.1.0-1 works fine. (rooted OOS 4.0.2)
I had at least two serious issues with official TWRP 3.1.0-1 and LineageOS:
1.) After a first flash attempt via fastboot I was no longer able to unlock my phone with my PIN under LineageOS.
2.) When booting into TWRP I got a black screen - unable to do any useful.
3.) After I could no longer unlock my phone under LineageOS I reinstalled LineageOS from TWRP 3.1.0-1. All looked fine until I rebooted from TWRP into LineageOS: TWRP obviously wiped my device and I was offered
the setup wizzard of LineageOS. All my setting were gone.
I had issue 3.) already with TWRP 3.0.3-1. I immediately reflashed TWRP 3.0.4-1 - the currently only working TWRP version.
I would like to add that I had removed any encryption on the phone before I started at 1.). My device is still unencrypted. I once removed stock encryption because I heard about problems with TWRP and encryption.
[ HELP I have researched everywhere on the internet and I'm not sure what to do. I have a REDMI 4A wit AEX ROM OREO8.1 installed, TWRP 3.2.2.0 Official (for Redmi 4A on the twrp website) and tried to flash Magisk v.16. Error 1 mount vendor shows up in twrp. Many YouTubers says I should flash boot.img. I've already flashed the boot.img of the given AEX ROM OREO 8.1, but the same error occurs. I tried to search for answers, and what I found was that apprently aosp oreo ROMs usually are Treble ROMs. Downloaded Termux app and checked if ROM was treble = false = NOT Treble! Then others say I have to flash a modded vendor version of twrp. (Link: (add Https here)//androidfilehost.com/?fid=674106145207489212) Haven't tried it out just wanted to make sure if I should or not, bacuse the last time I tried to flash a different twrp, I had to flash the original one back using ADB...
Btw I had given up at some point and I flashed SuperSU successfully. Why Can I flash SuperSU but not Magisk?? I fully unrooted SuperSU and am ready to try flashing Magisk again. If anyone has any idea how to fix this, pleeeeeease tell me I need Snapchat to work while having root (yes I know I could've used Titanium Backup but that not the point rn)
Thanks in advance!!!
Austin:fingers-crossed:
Yup, you must use TWRP Vendor if you want to use magisk in AEX Oreo.
Han usb Deccan if DHC dry j
Wrong section.
Install TWRP Pitch Black, then install magisk for treble rom
That version may have bugs try the newer versions
Try with Pitch Black recovery or Orange Fox recovery
Same for me and than i using BATIK Recovery for fix it
Solved Magisk error!
I've tried so many Recoveries and after trying more than 5 recoveries and about 7 Different ROM I finally got the answer.
So basically now that Redmi 4A is treble based, hence it has now a new Partitioning vendor based. For that you'll need new Recovery that support vendor mounting. I've tried the other Recoveries mentioned above and all of them are buggy. Go for the official TWRP vendor based Recovery. I found it here :
https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
The steps are explained purely for Redmi 4A.
Use pitchblack recovery and all the problems will fix or install supersu and install magisk apk, grant root and install directly and then you can uninstall supersu with unsu zip
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Did you tried another recovery? Try Batik Recovery!
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Amir_espie said:
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Click to expand...
Click to collapse
Sure,will give it a go
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Solved Magisk Error!
I've been using Pixys OS on my Redmi 4A and it works fine smoothly. I recommended to clean wipe before installing. Android Pie us amazing and I've installed stable version. Do backup before clean wipe.
For Magisk I recommended this: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
It worked for me. Also go through this step before any custom ROM. Do let me know the status
Anirudh15 said:
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Click to expand...
Click to collapse
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
You have two problems.
Anirudh15 said:
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
You need to flash the twrp separated vendor version by my friend Offain https://androidfilehost.com/?fid=962187416754475993
The other problem with the decryption:
You must enter in the twrp press wipe and format data. Type yes and then reboot into twrp again. After that flash the rom and gapps and you will not have the decryption problem again
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
I had the same problem. Its because your phone is encrypted. The only solution I found is to boot the device into fastboot and using command: [fastboot format userdata] on PC. This will wipe all data off your phone so do backup. It removes encryption and now you can install any custom rom.
Decrypt ur phone first then flash, use twrp vendor
athish said:
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
Click to expand...
Click to collapse
Format Data was the only thing that worked for me. First backup everything on your mass storage.
Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson
Try with different recovery. For example with this
Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.
I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.
Hello boys and girls,
So I recently got me a CN Realme x2 pro and after much trouble I unlocked the bootloader. I updated to the latest firmware (RealUI2 F16) and installed TWRP 3.4 and as soon as I booted into recovery I made a full Nandroid backup. Then tried to boot back into system and I got into a bootloop. So I decided to install a custom ROM, since that was the original plan. After wiping the system in TWRP, I got some error about some partition, formated data, repaired it, formated to ext2 and back to ext4.
I tried LOS 17.1 , LOS 18.1 , crDroid 7.2 and AOSiP 11 . crDroid and AOSiP drop back into bootloader/recovery, both LOS are stuck at the boot animation (I waited for over 4 hours).
I also tried TWRP 3.6 (which is currently installed) and OrangeFox 11 (which results in the red error about destroyed boot/recovery). The strange thing is that when connected to PC, the phone mounts /data to PC instead of /storage (is that normal?)
Any idea?