Database Develop

Error mounting data and cache

Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?

devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.

YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.

I belive I have the same probleme, how i could i do it right?

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.

I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!

Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.

devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...

berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.

[RECOVERY][Huawei P7][Unofficial TWRP Recovery 3.0.3-0]

Hi everyone.
Here's my build of TWRP 3.0.3-0 for Huawei P7.
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup/restore of internal storage.
Added feature to make backup/restore of oeminfo partition. This partition contains info about vendor and current installed version. So in case if you want to rollback to 4.4.2, for example, or revert back your previous vendor version, you can just restore oeminfo from backup with 4.4.2 version or other vendor and flash appropriate firmware without flashing transition package, vendor and without getting "cust fail" error.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd party application: will boot in TWRP. In case of local update, OTA-update, factory reset from menu or "force update" (3buttons method): will boot into EMUI recovery. Thus you don't have to flash stock recovery before OTA-update, flashing official firmware or doing factory rest.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSU from build.
Enabled encrypted data support.
Screen lock by power button replaced with screen off.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_P7-3.0.3-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Notes:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data.
Download: TWRP_P7-3.0.3-0.img
For TWRP: TWRP_P7-3.0.3-0.zip
Previous:
Download: TWRP_P7-3.0.2-0.img
For TWRP: TWRP_P7-3.0.2-0.zip
Download: TWRP_P7-3.0.0-0.img
For TWRP: TWRP_P7-3.0.0-0.zip

Thanks for supportion the P7 devices, greate job

Is it possible, to restore 2.8.7.0-backups?

pokko said:
Is it possible, to restore 2.8.7.0-backups?
Click to expand...
Click to collapse
I can't tell you for sure about backups made by araca's 2.8.7.0 - I don't know his partition layouts and backup naming method, but if you were using my build of 2.8.7.0, then yes, you can.
Anyway, it's better to make a new backup, for any case...

Thanks . works great on my p7 especially the factory reset with cust .
can you explain how i can build similar twrp for the mate S . your help will be much appreciated

Hi !
Whenever I use 3buttons method my phone goes to EMUI recovery ,
Whenever I use 3rd party application my phone goes to TWRP recovery !
There is no update file on my storage so in both cases my phone should go to TWRP recovery ! What is the problem ? Please solve this !

andromodgod said:
can you explain how i can build similar twrp for the mate S . your help will be much appreciated
Click to expand...
Click to collapse
What do you mean by similar?
You'll have to make device tree to build TWRP. Mate S is much different from P7, so I think I couldn't help you with it.
mohammadsaa said:
Hi !
Whenever I use 3buttons method my phone goes to EMUI recovery ,
Whenever I use 3rd party application my phone goes to TWRP recovery !
There is no update file on my storage so in both cases my phone should go to TWRP recovery ! What is the problem ? Please solve this !
Click to expand...
Click to collapse
There is not any problem. 3 buttons method is used for "force update". If you want to boot into TWRP, use "power" + "vol+" instead of 3 buttons. Read the first post attentively!

@Kostyan_nsk_one question, why if internal storage is a subfolder of user data in recovery the size of internal storage partition is bigger of data partition?

complicazio said:
@Kostyan_nsk_one question, why if internal storage is a subfolder of user data in recovery the size of internal storage partition is bigger of data partition?
Click to expand...
Click to collapse
TWRP excludes /data/share folder from backup of /data folder. Thus, if you have a lot of photos, music, etc in your internal storage, its backup size will be greater than size of /data backup.

Kostyan_nsk said:
TWRP excludes /data/share folder from backup of /data folder. Thus, if you have a lot of photos, music, etc in your internal storage, its backup size will be greater than size of /data backup.
Click to expand...
Click to collapse
Well, thus if I want to do a nandroid backup I have to check data and internal storage, not only data partition because of default it's not selected internal memory

complicazio said:
Well, thus if I want to do a nandroid backup I have to check data and internal storage, not only data partition because of default it's not selected internal memory
Click to expand...
Click to collapse
It's not mandatoryly for nandroid backup. Depends on what kind of data you want to save. /data contains user applications and system settings; /data/share (i.e. internal storage) contains your personal data (screenshots, photos, music, videos, etc) if you didn't moved them to sd-card. It's up to you, what to backup and what not.

@Kostyan_nsk I appreciate your work. I have already built TWRP for my Huawei device but I am struggling to fix custom.bin and /data/cust symlink being destroyed after factory reset. I have placed the necessary code in partitions.cpp under Wipe partition block. Can you tell me which method you used to fix this?

@Kostyan_nsk When I do a backup in the internal memory then via es file Explorer goes into TWRP folder in sdcard0 (internal memory) it is empty, and if I go into the folder media / share / 0 / TWRP I find the backup. They are not the same thing? While if I do backup in the external sdcard its all ok.
Sent from my Paris using XDA-Developers mobile app

Hi,, I am new here ... i think this very nice .. do you tell me how is instal for my phone p7?

albelushi7 said:
Hi,, I am new here ... i think this very nice .. do you tell me how is instal for my phone p7?
Click to expand...
Click to collapse
Read first post

RangerP7 said:
Read first post
Click to expand...
Click to collapse
What is the first post?
I mean instal twrp!!
How?
If you mean Buckup I do this ?!!
I'm new don't forget this hhh
Think you

albelushi7 said:
What is the first post?
I mean instal twrp!!
How?
If you mean Buckup I do this ?!!
I'm new don't forget this hhh
Think you
Click to expand...
Click to collapse
First post on first page
Kostyan_nsk said:
Hi everyone.
Here's my build of TWRP 3.0.0-0 for Huawei P7.
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup/restore of internal storage.
Added feature to make backup/restore of oeminfo partition. This partition contains info about vendor and current installed version. So in case if you want to rollback to 4.4.2, for example, or revert back your previous vendor version, you can just restore oeminfo from backup with 4.4.2 version or other vendor and flash appropriate firmware without flashing transition package, vendor and without getting "cust fail" error.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd party application: will boot in TWRP. In case of local update, OTA-update, factory reset from menu or "force update" (3buttons method): will boot into EMUI recovery. Thus you don't have to flash stock recovery before OTA-update, flashing official firmware or doing factory rest.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSU from build.
Enabled encrypted data support.
Screen lock by power button replaced with screen off.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_P7-3.0.0-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Known issues:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data. Otherwise you will get error, saying that TWRP can't mount "storage". So don't bother if you'll see this error.
Download: TWRP_P7-3.0.0-0.img
For TWRP: TWRP_P7-3.0.0-0.zip
Click to expand...
Click to collapse
Download ADB/FASTBOOT
Download TWRP_P7-3.0.0-0.img
And put it into the ADB / FASTBOOT folder
Install drivers of your phone
Connect your phone to your computer
Enable USB debugging on your phone
Open ADB and type:
"adb devices" (you should see now your device)
"adb reboot bootloader"
Now you should see at the bottom unlocked or locked. That means if your bootloader is unlocked. You need to unlock your bootloader to install a custom recovery.
If you see unlocked...
"fastboot flash recovery TWRP_P7-3.0.0-0.img"
That's it
Reboot your phone.

RangerP7 said:
First post on first page
Download ADB/FASTBOOT
Download TWRP_P7-3.0.0-0.img
And put it into the ADB / FASTBOOT folder
Install drivers of your phone
Connect your phone to your computer
Enable USB debugging on your phone
Open ADB and type:
"adb devices" (you should see now your device)
"adb reboot bootloader"
Now you should see at the bottom unlocked or locked. That means if your bootloader is unlocked. You need to unlock your bootloader to install a custom recovery.
If you see unlocked...
"fastboot flash recovery TWRP_P7-3.0.0-0.img"
That's it
Reboot your phone.
Click to expand...
Click to collapse
There are some nots ==
Where is ADB or link ADB/Fastboot
Where is folder Fastboot

albelushi7 said:
There are some nots ==
Where is ADB or link ADB/Fastboot
Where is folder Fastboot
Click to expand...
Click to collapse
Use the power of Google, maybe the force will be with you and you will find it
And please! inform you about flashing things on your phone. First learn how it work (your phone, bootloader, recovery, system, adb/fastboot) and after that start work...
If you are just flashing random **** on your phone without knowing what your are doing I will promise you, in less then one week you will ask for help because your phone won't start anymore...

RangerP7 said:
Use the power of Google, maybe the force will be with you and you will find it
And please! inform you about flashing things on your phone. First learn how it work (your phone, bootloader, recovery, system, adb/fastboot) and after that start work...
If you are just flashing random **** on your phone without knowing what your are doing I will promise you, in less then one week you will ask for help because your phone won't start anymore...
Click to expand...
Click to collapse
I know that
But This new for me ?
I want install this twerb ,because I think phone be better..
Just Try ?
Think you ?

Zip files not showing in TWRP??? Can not flash...

I've been able to do the beginning root process, but after entering TWRP I can not see the SuperSU zip file. I went back and transferred again to the internal storage- but my PC (Windows 10) said it was already there (I went ahead and added it which over wrote the original file)!
After I went back into TWRP- it is still not showing there (or the no-verity zip file or the aptX zip file which I ultimately want to install. ) It says also there is 0mb in the folder.
How come my file is not showing in TWRP? I have toggled the image/zip file setting in TWRP so that is not it...
Thank you!

hkdavexda said:
I've been able to do the beginning root process, but after entering TWRP I can not see the SuperSU zip file. I went back and transferred again to the internal storage- but my PC (Windows 10) said it was already there (I went ahead and added it which over wrote the original file)!
After I went back into TWRP- it is still not showing there (or the no-verity zip file or the aptX zip file which I ultimately want to install. ) It says also there is 0mb in the folder.
How come my file is not showing in TWRP? I have toggled the image/zip file setting in TWRP so that is not it...
Thank you!
Click to expand...
Click to collapse
Is it just this one file/folder or in the complete system?
Problem might be because of pin/pattern error. Hence TWRP might not be able to decrypt the data.
One working solution to this is complete factory reset which will erase internal memory ,
I suggest copying your internal memory to PC. Then goto bootloader and type
Code:
fastboot erase userdata
.
Then goto TWRP and advanced option and sideload Oxygen OS Rom.
The above process is highly experimental however I was able to do this successfully once when i had the same problem.
Might search a bit more before proceeding.

MoonBlade said:
Is it just this one file/folder or in the complete system?
Problem might be because of pin/pattern error. Hence TWRP might not be able to decrypt the data.
One working solution to this is complete factory reset which will erase internal memory ,
I suggest copying your internal memory to PC. Then goto bootloader and type
Code:
fastboot erase userdata
.
Then goto TWRP and advanced option and sideload Oxygen OS Rom.
The above process is highly experimental however I was able to do this successfully once when i had the same problem.
Might search a bit more before proceeding.
Click to expand...
Click to collapse
Well, I rebooted and everything worked... I was just hesitant to do anything... not sure what actually happened... but all seems OK now. Thanks for your reply.

Xiaomi.eu Rom & Encrytion

Hi,
is anybody able to get encryption working on MI8 under xiaomi.eu Rom?
I tried several times with "old" Android O and new Android P Roms from Xiaomi.eu, but after "encryption" my data partition was useless and I've to format my phone completely.
I'm on the newest 'unofficial' recovery-TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150.zip and on xiaomi.eu 8.9.20.
Thanks

hi!
you need to edit vendor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont

t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
interesting... next time i've to do a clean flash, 'll try to encrypt the device. Hope it works.

t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
Hi t0mas,
I don't have ventor on the phone but I've found vendor, can you confirm whether it was a typo or not?
As for the file itselft, I found a resemblence named fstab.qcom in /vendor/etc/.
Fyi I'm on Mi 8 8.9.24 Xiaomi.eu ROM. In order to search for the file mentioned in your post, I went through TWRP and mounted Data, Cache, System, Vendor and Persist.
Thanks for your assistance

Hi
Does it work this way?

Gunshin82 said:
Hi t0mas,
I don't have ventor on the phone but I've found vendor, can you confirm whether it was a typo or not?
As for the file itselft, I found a resemblence named fstab.qcom in /vendor/etc/.
Fyi I'm on Mi 8 8.9.24 Xiaomi.eu ROM. In order to search for the file mentioned in your post, I went through TWRP and mounted Data, Cache, System, Vendor and Persist.
Thanks for your assistance
Click to expand...
Click to collapse
oh sorry about that, of course it is a typo. i ment /vendor/etc/fstab.qcom
edit:also roccected my original post to avoid confusion

t0mas_ said:
oh sorry about that, of course it is a typo. i ment /vendor/etc/fstab.qcom
edit:also roccected my original post to avoid confusion
Click to expand...
Click to collapse
SpiderSGS6 said:
Hi
Does it work this way?
Click to expand...
Click to collapse
Thanks, I'll give it a try and let you know if everything worked out fine.
---------- Post added at 01:32 PM ---------- Previous post was at 12:51 PM ----------
t0mas_ said:
hi!
you need to edit vendor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
So in TWRP, I've renamed the fstab.qcom to old_fstab.qcom_old and copied the modified file to /vendor/etc and did a data wipe. I've rebooted the phone to system but it goes to TWRP splash screen and stays there. If I reboot the phone again, it just reboots to TWRP splash screen so my phone is pretty much stuck.

did you set correct permissions? another thing I did is flash magisk. other than that it should work as far as I know...

t0mas_ said:
did you set correct permissions? another thing I did is flash magisk. other than that it should work as far as I know...
Click to expand...
Click to collapse
My phone isn't rooted.
Right now, I can't do anything, even tried to connect it via adb but it doesn't list when I type the command adb devices

Gunshin82 said:
My phone isn't rooted.
Right now, I can't do anything, even tried to connect it via adb but it doesn't list when I type the command adb devices
Click to expand...
Click to collapse
and you did format userdata?
try starting with that. format, not wipe. you have to type in "yes" to confirm. internal sd will be wiped.
flash rom again. adb pull the file, edit it, insert it it attached zip and flash that. download latest magisk and flash that. if that doesnt work, i have no idea, sorry

I can't do any of that because the phone doesn't go in the TWRP menus, it stays at the splash screen.
I've managed to access the phone via adb but I can't access /vendor/etc/. I'm trying to put back the original file in place but when I do adb shell ls /vendor/, the only thing I see is compatibility_matrix.xml, lib64 and manifest.xml.
I'm also looking at the option of flashing the vendor partition with an image file but I can't seem to find the chinese ROM for v8.9.24
---------- Post added at 03:21 PM ---------- Previous post was at 03:07 PM ----------
t0mas_ said:
and you did format userdata?
try starting with that. format, not wipe. you have to type in "yes" to confirm. internal sd will be wiped.
flash rom again. adb pull the file, edit it, insert it it attached zip and flash that. download latest magisk and flash that. if that doesnt work, i have no idea, sorry
Click to expand...
Click to collapse
I can't because it doesn't go into the TWRP menu, I'm stuck at the blue splash screen.
I've managed to connect to the phone via adb but can't seem to access /vendor/etc/. When I do adb shell ls /vendor/ the only thing I see are compatibility_matrix.xml, lib64 and manifest.xml
**double post, sorry for that, I didn't see that my post went to the second page**

Gunshin82 said:
I can't do any of that because the phone doesn't go in the TWRP menus, it stays at the splash screen.
I've managed to access the phone via adb but I can't access /vendor/etc/. I'm trying to put back the original file in place but when I do adb shell ls /vendor/, the only thing I see is compatibility_matrix.xml, lib64 and manifest.xml.
I'm also looking at the option of flashing the vendor partition with an image file but I can't seem to find the chinese ROM for v8.9.24
Click to expand...
Click to collapse
now you lost me a bit. twrp splash or xiaomi splash screen?
if twrp, you are accessing twrp system from adb, which is separate from phone. you can try to boot in fastboot and format cache. still you did you format or wipe data before that happened? that is important.
edit: you can also format userdata from fastboot

t0mas_ said:
now you lost me a bit. twrp splash or xiaomi splash screen?
if twrp, you are accessing twrp system from adb, which is separate from phone. you can try to boot in fastboot and format cache. still you did you format or wipe data before that happened? that is important.
edit: you can also format userdata from fastboot
Click to expand...
Click to collapse
Yes, TWRP and that's where I'm accessing adb.
Not sure how to format cache in fastboot, I'll look it up
Here are the steps that I did:
1-Copy the file fstab.qcom
2-Modify the copy
3-Boot in TWRP
4-Renamed original fstab.qcom in /vendor/etc to old_fstab.qcom_old
5-Copied the modified fstab.qcom file to /vendor/etc
6-Wipe Data
7-Reboot to system
Since then, I can only reboot to TWRP splash screen or fastboot

Gunshin82 said:
Yes, TWRP and that's where I'm accessing adb.
Not sure how to format cache in fastboot, I'll look it up
Here are the steps that I did:
1-Copy the file fstab.qcom
2-Modify the copy
3-Boot in TWRP
4-Renamed original fstab.qcom in /vendor/etc to old_fstab.qcom_old
5-Copied the modified fstab.qcom file to /vendor/etc
6-Wipe Data
7-Reboot to system
Since then, I can only reboot to TWRP splash screen or fastboot
Click to expand...
Click to collapse
as far as i can tell, you did 2 things wrong
1 is you didnt format data
2 didnt set permissions
maybe 3 that backup file.
do this
fastboot format cache
try to reboot into twrp, be sure it doesnt get to booting into system
if this works, backup your sd and format userdata
if that doesnt work, boot into bootloader again
format cache again just to be shure
fastboot format userdata
this should get you to twrp. there you can flash eu again and try to boot. as far as i know eu contains vendor, so you should be fine.
if this doesnt work, the next thing i would try is to fastboot flash stock rom. be sure not to lock bootloader! in this case you might end up with a hard brick.

I'm editing my answer because it crossed your response.
So I'm guessing that Wipe Data isn't the same as format data... As for the permissions, I don't see anything regarding this, can you give me more details?
So I did a format cache and then rebooted and went directly to TWRP but it remains on the splash screen so can't access the menu.
Next step, I'll try to format the userdata as suggested and flash eu rom

maybe reflashing twrp would also help

t0mas_ said:
maybe reflashing twrp would also help
Click to expand...
Click to collapse
I'm able to access the TWRP menu. Right now I'm copying the ROM from Xiaomi.eu. I tried sideloading it but it couldn't read the file for some reason. Transfer just finish, I'll flash the rom via TWRP and get back to you after. Thanks for you help on this!!

Gunshin82 said:
I'm able to access the TWRP menu. Right now I'm copying the ROM from Xiaomi.eu. I tried sideloading it but it couldn't read the file for some reason. Transfer just finish, I'll flash the rom via TWRP and get back to you after. Thanks for you help on this!!
Click to expand...
Click to collapse
no problem, im glad you got it working.

Ok so ROM installation is done and I've pulled the fstab.qcom from vendor/etc and it's back with the encryptable variable. Phone reboots in system without any problems, just need to reconfigure everything, good thing I backed up.
I'll still need to encrypt the phone. You've mentioned the steps that I did wrong. Could we go through the proper steps for this?
Sent from my MI 8 using Tapatalk

Gunshin82 said:
Ok so ROM installation is done and I've pulled the fstab.qcom from vendor/etc and it's back with the encryptable variable. Phone reboots in system without any problems, just need to reconfigure everything, good thing I backed up.
I'll still need to encrypt the phone. You've mentioned the steps that I did wrong. Could we go through the proper steps for this?
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
dont restore the phone yet
edit file
put it in the zip i posted on prevoius page
go in recovery
format userdata->confirm with typing in yes
flash zip
i allways flashed magisk also, not sure if this is necesarry
if you just flash without formatting, you will probably break stuff again

Question I might have bricked my phone, I need help

I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.

Try putting the stock ROM on a SD card or usb (if you have a dongle).

georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem

Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?

Plus, where did you get the ArrowOS image? There are no builds, official or not.

georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp

I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?

raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card？try click on the Install image and change to install zip

can you sideload?

I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now

you should format data and put the arrow build in it, maybe it will work

J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"

raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.

raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.

georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.

Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you

raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error

I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update

raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].

raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?