Hi i have a problem with my poco f1
Status : UBL , NO OS , Orangefox recovery
Tried : flashing many roms and changed from twrp to orangefox but the problem persists. While trying to install the roms i wiped everything before.
Problem : Whenever i try installing a custom rom i get an error 7 message that says : xiaomi.verify_vendor() failed to read current vendor UTC build date: -2
I am not able to flash any custom rom and when i try i get this error.
The problem occurred when i tried to boot on my installed rom from multirom recovery. I had backed up everything but when i restore the backup (except the multiRom recovery) the phone is stuck on the pocophone logo.
If you need any more info i can provide please ask for it.
try clean flashing global stable fastboot rom using mi flash tool then flash twrp and flash any rom you want
https://mirror.akhilnarang.me/MIUI/beryllium/
take the latest vendor image 9.3.28 (dated 29-03-2019 17:11)
flash this via twrp and then flash rom
it should work
YasuHamed said:
https://mirror.akhilnarang.me/MIUI/beryllium/
take the latest vendor image 9.3.28 (dated 29-03-2019 17:11)
flash this via twrp and then flash rom
it should work
Click to expand...
Click to collapse
I will try this method first due to the smaller download size. I hope it works so i do not have to flash the stock rom again and go though the whole process.
It worked. I am now flashing a custom rom. My question is why did this happen ?
jackaros said:
It worked. I am now flashing a custom rom. My question is why did this happen ?
Click to expand...
Click to collapse
BRO WHENEVER you are trying to flash new rom be on latest vendor , firmware and vendor can be found on leanage os xda page 1 , updated rom requires latest vendor
jackaros said:
It worked. I am now flashing a custom rom. My question is why did this happen ?
Click to expand...
Click to collapse
I think you came from MIUI10.2.x
since, miui10 on android9, Xiaomi has started using MODIFIED version of VENDOR image*
so when you flash custom rom which works on standard vendor image, it gives your either error7 or hangs on splash screen
*android has following partitions /boot /recovery /system, /data, /internalstorage /persist /OEM
oem or VENDOR partition translates android
using modified oem (vendor) image in android 9, its xiaomi's attempt for speedy android updates (CGI) (treble)
YasuHamed said:
I think you came from MIUI10.2.x
since, miui10 on android9, Xiaomi has started using MODIFIED version of VENDOR image*
so when you flash custom rom which works on standard vendor image, it gives your either error7 or hangs on splash screen
*android has following partitions /boot /recovery /system, /data, /internalstorage /persist /OEM
oem or VENDOR partition translates android
using modified oem (vendor) image in android 9, its xiaomi's attempt for speedy android updates (CGI) (treble)
Click to expand...
Click to collapse
Just a follow up question..
So what will happen to my phone.. if its on miui 10.2.3.0 then i flashed the latest vendor img?? Will it cause bootloop?? Will it have a better performance?? Will it make games much smoother???
santiagoruel13 said:
Just a follow up question..
So what will happen to my phone.. if its on miui 10.2.3.0 then i flashed the latest vendor img?? Will it cause bootloop?? Will it have a better performance?? Will it make games much smoother???
Click to expand...
Click to collapse
miui10.2.x has its own modified vendor image,
to comeback on standard image, you must flash the image (which you did)
Related
So i am on the new miui using the oficial flash thing (unlocked bootloader oficialy).
The thing is i always wanted to get root and use a kernel on xda here that gives more available memory and solves some of the heating problems when charging (but i know need TWRP ofc) .
So i went to here and checked a few guides however there are many twrp's versions some of them i can't flash miui oficial roms, some of them i need installl boot.img every single time or when i want to restore backup is not just select the backup and done, i need to do something else (is a bit confusing)... so instead i decided to ask you guys directly
The question is:
- If i wanted to use oficial miui but have root and install a kernel and in future just flash the new miui rom again without any stress (just twrp -> flash-> select rom and gapps and done), no boot.img bull****, no flash another twrp etc is it possible??
(before this phone i had moto g(1st gen) and was easy as to put ONE twrp and then would be always flash rom + gapps every single time, no boot.img no firmware, worked for CM12, 12.1 and 13)
Install Alka recovery and back up all the partitions before doing anything.
tigax said:
- If i wanted to use oficial miui but have root and install a kernel and in future just flash the new miui rom again without any stress (just twrp -> flash-> select rom and gapps and done), no boot.img bull****, no flash another twrp etc is it possible??
Click to expand...
Click to collapse
Although I haven't tried it personally, the TWRP explanation guide here says the Cofface TWRP (linked on that page) automatically patches the boot.img when you flash a new ROM, which I believe solves your problem.
harishmenace said:
Install Alka recovery and back up all the partitions before doing anything.
Click to expand...
Click to collapse
so this one allows me to flash new roms from Miui? without any boot.img and stuff?
tigax said:
so this one allows me to flash new roms from Miui? without any boot.img and stuff?
Click to expand...
Click to collapse
Yes, I was doing it all the time.
Sent from my Redmi Note 3 using Tapatalk
timberwolf60 said:
Yes, I was doing it all the time.
Click to expand...
Click to collapse
Thank you will use then
as far as I know, the coffec twrp is based on 3.0.0. which is an old twrp. I want to know, is there a twrp with auto miui image patching and all partition backup capability alongside f2fs support based on latest twrp 3.0.2-2??? if so, please provide a link. sorry for mh bad English
Only way is to use the Alka TWRP first, backup all partitions. Then flash F2FS TWRP for converting into F2FS filesystem.
Then return to Alka TWRP to restore your backup of all partitions.
You must have a PC(with all drivers installed) which is available to you whenever needed to flash the recoveries using fastboot command.
superboy123 said:
Only way is to use the Alka TWRP first, backup all partitions. Then flash F2FS TWRP for converting into F2FS filesystem.
Then return to Alka TWRP to restore your backup of all partitions.
You must have a PC(with all drivers installed) which is available to you whenever needed to flash the recoveries using fastboot command.
Click to expand...
Click to collapse
Read it here on XDA that Alka TWRP has some bug.. like errors in restoring firmware. true?
candiesdoodle said:
Read it here on XDA that Alka TWRP has some bug.. like errors in restoring firmware. true?
Click to expand...
Click to collapse
Yes, it gives some sort tarfork error in firmware partition as the firmware partition is read only.
You should uncheck the firmware partition while restoring.
Example: Assume that you have taken a backup of MIUI 8 Global stable (yes, all partition backup). After backup, you went to CM13 or any custom ROM and assume that you flashed the CM 13 radios/firmware zip. Now you want to go back to MIUI and you restored it. Now you will face issues in MIUI like no sound in calls where neither you nor the person on the other side will be able to hear any sound.
The above issues are caused due to firmware. MIUI's firmware and CM's firmware are not the same.
If you want to revert from CM or any custom ROM to MIUI, you must use MiFlash (EDL).
superboy123 said:
Yes, it gives some sort tarfork error in firmware partition as the firmware partition is read only.
You should uncheck the firmware partition while restoring.
Example: Assume that you have taken a backup of MIUI 8 Global stable (yes, all partition backup). After backup, you went to CM13 or any custom ROM and assume that you flashed the CM 13 radios/firmware zip. Now you want to go back to MIUI and you restored it. Now you will face issues in MIUI like no sound in calls where neither you nor the person on the other side will be able to hear any sound.
The above issues are caused due to firmware. MIUI's firmware and CM's firmware are not the same.
If you want to revert from CM or any custom ROM to MIUI, you must use MiFlash (EDL).
Click to expand...
Click to collapse
Thanks!! So a safe way to revert from CM to MIUI would be to:
- restore partitions, and assuming firmware gives error
- flash via EDL over this
Maybe i could directly flash through EDL..will that work? will the radios/modem get overwritten by the MIUI radios/modem?
candiesdoodle said:
Thanks!! So a safe way to revert from CM to MIUI would be to:
- restore partitions, and assuming firmware gives error
- flash via EDL over this
Maybe i could directly flash through EDL..will that work? will the radios/modem get overwritten by the MIUI radios/modem?
Click to expand...
Click to collapse
Yes, the radios/modem will get over-written.
No need to restore partitions. All the partitions will get flashed by the MiFlash.
I almost backup only the Boot, Data, Cache and System partitions leaving others.
If you want your Internal SD card, select Flash all except data and storage option at the bottom.
Enjoy with your device!:good::good:
I am using MIUI 8.0.1.0 and maybe someday I will try CM13/14. About twrp, what is the recommended twrp for our phone ?
Read this http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
---------- Post added at 12:57 PM ---------- Previous post was at 12:57 PM ----------
Sohan_Saymum said:
as far as I know, the coffec twrp is based on 3.0.0. which is an old twrp. I want to know, is there a twrp with auto miui image patching and all partition backup capability alongside f2fs support based on latest twrp 3.0.2-2??? if so, please provide a link. sorry for mh bad English
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Apcoolboy said:
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Click to expand...
Click to collapse
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
There is flashable zip file which is extracted from miui rom only. So both way will be good as flash latest stable miui rom and then twrp > rom zip > gapps. Or twr0 > firmware zip (search in any custom rom thread you will get one) > custom rom zip > gapps.
Only benefit of flashing firmware zip is less time consuming and less file size (around 50mb) compare to full miui rom.
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
unlock your bootloader again it will run without problem..
With this modded version of TWRP you can now install A1 roms into the 5X.
How to install A1 roms using this TWRP:
https://forum.xda-developers.com/mi-5x/how-to/guide-how-to-install-a1-rom-5x-t3777139
Oreo Modded TWRP 3.2.1-0 Download:
Google Drive
Nougat Modded TWRP 3.2.1-0 Download:
Google Drive
How to install:
- Unlock bootloader
- Enter in Fastboot Mode (Power Button + Vol Down)
- Flash using "fastboot flash recovery twrp.img"
- Enter in Recovery Mode (Power Button + Vol Up)
Which one should I download?
You should install the correspondent version according to your currently installed Android version. If your current system is Nougat, you should flash Nougat TWRP. Same for Oreo. It doesn't matter which version of Android are you going to install, but the one that you already have installed. If you are in Nougat and want to flash Oreo rom, after flashing it, be sure to flash Oreo TWRP. If you dont do it, recovery may not work.
How can I use the port feature?
First, download an A1 fastboot ROM. You can do so here. Then, flash system and boot partitions using fastboot.
After you flashed it, go to "Advanced" then tap on "Terminal". Write "a1to5x" and press Enter. Wait until it finishes. Make proper wipes and reboot.
Are there any other features?
I have enabled system.img and modem.img flashing, so people without a pc can flash A1 fastboot roms. But be careful, system.img can't be a sparse image (this are the images included on the a1 official fastboot rom), it should be a raw ext4 image. You can use simg2img to convert them. Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you. I know it is not a very easy process, but at least people without pc now have a chance to update their phones.
In what roms does it works?
I have only tested it with official Android One Oreo rom, however, it should work with Nougat Android One and with custom roms. Try it and let me know in what roms does it work.
How do you port A1 roms to the 5X?
I have been asked this question a lot of times. I can't give a step by step guide since I don't have enough spare time to make a decent guide. If you are interested on the porting process, take a look at /sbin/a1to5x (inside twrp ramdisk), it is the script which takes cares of the automatic porting process. Inside it you will find how the ports are made.
Where is the changelog?
You can check it here
Donations:
If you like my work and want to contribute, you can donate via paypal.me/aex12
Device Tree: https://github.com/Aex12/android_device_xiaomi_tiffany
Manifest used: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
XDA:DevDB Information
Modded TWRP 3.2.1, Tool/Utility for the Xiaomi Mi 5X
Contributors
Aex12
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Stable
Current Stable Version: 3.2.1
Created 2018-03-07
Last Updated 2018-03-08
Reserved
Love Man... You Are Love Brother
is it normal that the external memory is not shown?
@Aex12
Thanks for your great work. I have some question.
Should we install an whole A1 fastboot rom or only install system.img and boot.img like the old one?
vangame said:
@Aex12
Thanks for your great work. I have some question.
Should we install an whole A1 fastboot rom or only install system.img and boot.img like the old one?
Click to expand...
Click to collapse
Forgot to mention it on the thread. Thanks for reminding, I am updating it right now. You should only flash system and boot. Modem and other firmware partitions can be flashed too, but they are not mandatory.
And have someone test LineageOS 15.1 for Mi A1 with this recovery?
Awesome work @Aex12. Thanks a lot
Hello can I use it at tissot bootloader?
eurekaseven said:
is it normal that the external memory is not shown?
Click to expand...
Click to collapse
That was somthing I also have noticed.. without sd memory being shown I can't do a backup to SD Card.
Instead I'll have to do a local backup and connect to PC and copy files over, Early stages I guess we are lucky we can even see the Internal Memory right?
Alright so I was curious and thought I'd see what happens if I flash recovery Nougat Modded TWRP 3.2.1-0 ( While currently running Oreo )
I booted into recovery and instantly discovered that you no longer even have access to internal memory 0b shown.. Don't waste your time !
I flashed recovery Oreo Modded TWRP 3.2.1-0 using fast boot as you won't be able to flash a recovery rom using TWRP in this state..
https://www.xda-developers.com/how-to-install-twrp/
Shows an easy guide if you aren't sure howto do this
Can not get back to MIUI Nougat or even get old recovery to work
When i try to install back xiaomi.eu's miui rom after installing zip and do all the proper wipes, it reboot to system but says that encryption was interrupted and can't complete. So I tried to install back the nougat 3.2.1 recovery and try again, with the same result. again i tried to install the rom again with 3.1.1 recovery and same happens. With nougat recovery it can't mount any partition, so it can not opperate properly, only the oreo recovery works. the only rom that works and gets installed good is the oreo one that you submitted so what can i do to get back to my normal twrp recovery (no oreo) and to a miui rom? thanks
P.D: I also tried to flash with fastboot a a1 nougat rom and with the 3.1.1 twrp port it but no succes as it can no longer mount anything, only oreo twrp is working but still not get to work properly any other rom, via fastboot or via recovery. Bootloader is unlocked.
What phone and model is this 4? It states nothing
hi,
i tried to flash system.img from official MiA1 fastboot ROMs today but i got these message " target reported max download size of 536870912 bytes, is this a normal message? will the flash resume?
vangame said:
And have someone test LineageOS 15.1 for Mi A1 with this recovery?
Click to expand...
Click to collapse
I want to know this too!
Aex12 said:
Aex12, Brother Please Fix SD issue... Cant flash files from my SD Card.
Click to expand...
Click to collapse
Comparing fstab with stock recovery / sd supported recovery might fix this issue...
This recovery doesn't read my SD card. Only the internal storage.
>Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you
Yeah, anyone willing to do it for me?
udaan said:
>Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you
Yeah, anyone willing to do it for me?
Click to expand...
Click to collapse
Make sure to make a backup of your current modem, just in case.
It's from v9.5.9.0: https://mega.nz/#!UAhwAQLY!-8np_yuZnJscEUFh9bJuCkkqDkPuZrr8Aa6o0kkBq5Q
My 5x does not go to recovery mode. My ROM is AOSPE. I am using OREO twrp. The device is not ROOTED
I can boot twrp using
Code:
fastboot boot twrp.img
but after using
Code:
fastboot flash recovery twrp.img
the phone does not go to recovery using Volume up + Power
tuhi009 said:
My 5x does not go to recovery mode. My ROM is AOSPE. I am using OREO twrp. The device is not ROOTED
I can boot twrp using
Code:
fastboot boot twrp.img
but after using
Code:
fastboot flash recovery twrp.img
the phone does not go to recovery using Volume up + Power
Click to expand...
Click to collapse
I think you need to fastboot flash boot image first, then go to twrp and flash it again from it.
---------- Post added at 08:14 AM ---------- Previous post was at 08:06 AM ----------
@Aex12 please update TWRP. I can't format /data /system etc from twrp made for MiA1(MohanCM's) but I cannot do it with yours. I have mi5x and it is ****ing stuck on boot. If I flash MiA1's fastboot rom I can get to fastboot and flash TWRP (since the bootloader is locked) but I can't do anything with your TWRP. But I can also flash MohanCM's twrp and I can do all that stuffs except for installing ROms and booting to it. im ****ing confused myself.
Hi,this is my first time installing a custom rom and recovery and rooting and all.
I am on MIUI 10 8.11.22 beta on RN3 2gb.
And have unlocked bootloader using official method.
Currently following
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
Planning to
flash official twrp-3.3.1-0-kenzo
Install Havoc 9.0 OS https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
Install Magisk
but twrp site is showing
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
I think it is about boot.img but I do not have patched boot.img of my miui version and also (from above guide) to patch boot.img i need fastboot rom but linkhttps://en.miui.com/a-234.html only takes me to Chinese miui website.
Can any one share link to boot.img of fastboot rom for MIUI 10 8.11.22 beta?
And in Havoc OS post
https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
do I need custom kernel for 9.0?
In Magisk Post
Prerequisite
If you plan to install custom kernels, flash the zip AFTER installing Magisk
Make sure to remove any ‘boot image mods’ such as other root solutions. The easiest way is to restore the boot image from factory images, or reflash a non-prerooted custom ROM
Click to expand...
Click to collapse
does that mean i do not need to flash boot.img or do i need to flash it afterwards?
Qustions
1) Do I need boot.img file of my version or any will do?
2)Do I need custom kernel for havoc os 9.0?
3) how to proceed after flashing twrp(need help)?
here what i think i have to do after flasing twrp(correct me If i am wrong)
(do not flash boot .img as installing magisk) -> flash havoc os -> flash magisk->flash custom kernel(which one?)-> (flash boot.img) ->reboot
ARY-Pyran said:
Hi,this is my first time installing a custom rom and recovery and rooting and all.
I am on MIUI 10 8.11.22 beta on RN3 2gb.
And have unlocked bootloader using official method.
Currently following
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
Planning to
flash official twrp-3.3.1-0-kenzo
Install Havoc 9.0 OS https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
Install Magisk
but twrp site is showing
I think it is about boot.img but I do not have patched boot.img of my miui version and also (from above guide) to patch boot.img i need fastboot rom but linkhttps://en.miui.com/a-234.html only takes me to Chinese miui website.
Can any one share link to boot.img of fastboot rom for MIUI 10 8.11.22 beta?
And in Havoc OS post
https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
do I need custom kernel for 9.0?
In Magisk Post
does that mean i do not need to flash boot.img or do i need to flash it afterwards?
Qustions
1) Do I need boot.img file of my version or any will do?
2)Do I need custom kernel for havoc os 9.0?
3) how to proceed after flashing twrp(need help)?
here what i think i have to do after flasing twrp(correct me If i am wrong)
(do not flash boot .img as installing magisk) -> flash havoc os -> flash magisk->flash custom kernel(which one?)-> (flash boot.img) ->reboot
Click to expand...
Click to collapse
If u official unlocked using miunlock tool then u dont need any patched boot.img.
Flash latest twrp 3.3.1 kenzo
Download ur favourite rom and nano gapps zip to external sd card.
First go to wipe and do format data.
You must do it or rom wont boot.
So click Format data
Type Yes to format
This will decrypt and erase internal sd.
Then Swipe to "factory reset"
Then Go to install
Flash rom zip
Flash nano gapps.zip
Then Reboot and enjoy
Black_Stark said:
...
Click to expand...
Click to collapse
I know this is off topic but do you know something about "Red Light Blinking" and "init Storage:Fail" ?
Thanks for the tip. Currently on havoc os . Installation went smoothly