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.
Related
So I have a lineageOS on my redmi 4x and a twrp recovery, but whenever I try to flash something new from TWRP (I tried magisk and some other thing) it completely deleted my OS, I had a backup so its not a problem, but how could I flash something new again? Should I wipe something or what?
Use Latest 3.1.1/3.2.0 TWRP from official TWRP page. It's a Recovery Problem.. if you're On N go for latest 3.2.0 and Also check if you're Device is not encrypted (like you can't see Internal storage In TWRP) Clean Flash ROM, If anything Doesn't work... This is strange, I heard this issue the first time. Maybe Recovery Problem, Try and Reply.
SleepyWeeb said:
So I have a lineageOS on my redmi 4x and a twrp recovery, but whenever I try to flash something new from TWRP (I tried magisk and some other thing) it completely deleted my OS, I had a backup so its not a problem, but how could I flash something new again? Should I wipe something or what?
Click to expand...
Click to collapse
If your Problem solved report back
Dear xda members,
I recently installed the Oxygen stable 9.0.2 on OnePlus3T
The phone was unlocked, rooted and with twrp 3.3.0-1 installed
During first boot after installation, I received this error:
Decryption unsuccessfull
The password you entered is correct, but unfortunately your data is corrupt
The only way to continue is a factory reset (but I would like another way, if possible).
I was able to revert to Oxygen stable 5.0.8, but the error persist.
Is there any procedure to access the encrypted data partition and recover files stored in it, before wiping all?
Thank you.
Kind regards
you need to do a factory reset from the recovery menu.You will lose all your data but its the only way.
You should totally flash the 5.0.8 fw after flashing the offical pie OOS. It has been discussed in the official thread here at XDA.
Check this:
https://forum.xda-developers.com/showpost.php?p=79542744&postcount=517
Tagtag123 said:
You should totally flash the 5.0.8 fw after flashing the offical pie OOS. It has been discussed in the official thread here at XDA.
Check this:
https://forum.xda-developers.com/showpost.php?p=79542744&postcount=517
Click to expand...
Click to collapse
Thank you very much for the information!
This is what I did
1 Boot recovery and press cancel when it asks for password
2 Adb push needed files in /mnt
3 Flash the rom (OnePlus3TOxygen_9.0.2_28_OTA_082_all_1905110010_f09a2bfe8e361d.zip)
4 Flash the firmware package (oxygenos-9.0.2-bl-km-5.0.8-firmware-3T.zip)
5 Flash twrp 3.3.0-1 again in the recovery partition
6 Flash Magisk 19.2
7 Wipe cache / dalvik-art (with errors related to mount storage)
But I found the same error of the first post. Which is my mistake in the procedure?
Darksp1der said:
Thank you very much for the information!
This is what I did
1 Boot recovery and press cancel when it asks for password
2 Adb push needed files in /mnt
3 Flash the rom (OnePlus3TOxygen_9.0.2_28_OTA_082_all_1905110010_f09a2bfe8e361d.zip)
4 Flash the firmware package (oxygenos-9.0.2-bl-km-5.0.8-firmware-3T.zip)
5 Flash twrp 3.3.0-1 again in the recovery partition
6 Flash Magisk 19.2
7 Wipe cache / dalvik-art (with errors related to mount storage)
But I found the same error of the first post. Which is my mistake in the procedure?
Click to expand...
Click to collapse
You could have flashed the firmware first, ROM second, but I don't think it would have changed anything.
We used to have this problem with the closed beta and with the open betas as well.
Once you wipe your storage, flash Pie, boot it, it doesn't happen again. I've been to Nougat, then back to Pie, no issues.
Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.
have you taken any recent OTA updates?
mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere
I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.
tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit
mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally without deleting any of my data, but does not enter twrp either. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition' and some other errors. I think that version is too old for my rom, so I'm afraid to use it for backup/flash. My phone is LG G6 H870, Android 9, software version V30b. The phone is not rooted, the bootloader is unlocked. Tried to erase cache partition and install twrp 3.4.01 again, didn't work. I can't install Skyhawk or Orangefox becuase I can't use twrp.
Is anybody facing this problem too?
Thanks!
Bootloader unlocked?
Mendoo said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yes
Thelock1 said:
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition', I think that version is too old for my rom. My phone is LG G6 H870, Android 9, software version V30b. My phone is not rooted.
Is anybody facing this problem too?
Thanks!
Click to expand...
Click to collapse
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
jis251 said:
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
Click to expand...
Click to collapse
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Thelock1 said:
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Click to expand...
Click to collapse
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
jis251 said:
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
Click to expand...
Click to collapse
Ok, thanks, I'll try to find a solution, or maybe I'll just wait for the next version of twrp.
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
AlejandroMota said:
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
Click to expand...
Click to collapse
Yes, I know I have to install twrp again every time I let the stock rom boot, but the only version of twrp working is 3.2.3 and I think that was released before the G6 received official Android 9 update, so that's why I'm not very confident using it. I've tried to enter recovery immediately after I've installed it, so I don't think that's the problem.
I have the same problem on the LG G6 H870. I won't get to TWRP. I tried several versions of TWRP and nothing.
Edit.
This twrp is functional:
https://androidfilehost.com/?w=files&flid=289997
After installation using fastboot, restart directly to twrp using power+vol. down.
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Update TWRP 3.1 to 3.4 problem
Thelock1 said:
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Click to expand...
Click to collapse
Hi, I don't know if this goes here, I hope you can help me, I update twrp from version 3.1 to 3.4 and now I can't access twrp, how can I fix it?
Hello again, I answer myself, and if it helps someone else, using adb fastboot with twrp 3.2 Melina solves it and twrp works perfectly again.
I installed lineage os 18.1 on my redmi 8, whenever I try to boot into the system it redirects me to twrp. What do I do?
ArthurNobody said:
I installed lineage os 18.1 on my redmi 8, whenever I try to boot into the system it redirects me to twrp. What do I do?
Click to expand...
Click to collapse
which los did you install? usually when it redirects to twrp something was skipped. did you format data? was the flashing successful?
fonzacus said:
which los did you install? usually when it redirects to twrp something was skipped. did you format data? was the flashing successful?
Click to expand...
Click to collapse
I have the same problem, i did format data and the flash was successful, also internal storage has just a bunch of folders with corrupted names after the flashing
aale01 said:
I have the same problem, i did format data and the flash was successful, also internal storage has just a bunch of folders with corrupted names after the flashing
Click to expand...
Click to collapse
id suggest not installing any a9 or a10 roms (aside from miui mods) as their trees are unstable, a11 has good support most of the time. los a11 was also very buggy from the start
[ROM][11.0][UNOFFICIAL][LineageOS 18.1] for Redmi 8(olive)
would like to share my device tree from scratch from 0 to hero for redmi 8 olive i left developing that phone for a while 2day sharing my device tree for lineage 18.1 along with the rom . rom based on latest miui vendor prebuilt Your warranty...
forum.xda-developers.com
there are plenty more stable alternatives now
encrypted (random names) are usually due to an unsupported
recovery on a12. in a normal boot they should work just fine
Xiaomi protect their device from custom rom or custom recovery and some time device go to hardbrick and stock on fastboot mode
So every time you want to install a custom rom after successful to install(dirty flash better) the rom first go beck to twrp menu and format system and dalvik cache then go to install>install image>select twrp img file>install
Then go to reboot>reboot to recovery
Then reboot to system
Hi,
I got the same problem with my samsung S9.
lineage allready worked fine. But then i decided to install the gapps and therefore i had to swipe the rom (according to a video). Whatever. So afterall i had nothing on the phone and had to install lineage again.
The first time then in odin i forgot to click away the check at "automatic recovery". I don´t know if that was my mistake.
Anyway, i repeated Odin, twrp and the installing of lineage. And allways when i reboot it after installing, lineage shows its surface and i can type in my pin. 1 or two seconds. And then a window "reboot into fabrique settings" appears and its rebooting back into twrp again.
What could that be?