Failed to mount /persist (invalid argoument) - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!

Youshouldsmile said:
Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!
Click to expand...
Click to collapse
You can extract the persist.img file from the MIUI Q beta fastboot ROM

i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !

sar78mad said:
i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !
Click to expand...
Click to collapse
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.

i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..

sar78mad said:
i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..
Click to expand...
Click to collapse
Bro could please tell us step by step ? i am getting mad. please

Eng.Raman said:
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.
Click to expand...
Click to collapse
perfect
I read my computer partitions. After finding the number of the block that corresponds to my team, copy the persist of the rom stock to my internal memory in twrp and then flash with your command and add my block.
in my case note 10 pro (sweet)
dd if=/sdcard/persist.img of=/dev/block/sdf7
VERY CAREFUL NOT TO USE THIS COMMAND ON ANOTHER computer. each person must read the exact block that corresponds to your mobile reference.

I guess your problem is more of hardware issue ,but have to test to know.
I come to this conclusion because magisk does not modify partitions nor system files , I would start with a clean fastboot flash of the phone (be careful of the lock checkbox).
Then judge from there , if phone still presents anomalies then my first assumption is true.

Related

Help System does not mount

I tried the repartition method manually and did all the steps carefully without doing it wrong everything was right until i tried to reboot i get a error node not found
i can reboot my phone to recovery and fastboot but whenever i try to flash a rom i get a error during the process saying failed to mount the system1 at system!
btw i have cwm r11
please help i need my phone to work again
quick help would be highly appreciated
thanks
guys should i use the mi flashtool and flash the fastboot stock rom ?
The miflash only works with the original partitions. Try to change the partitions to original and late try use the fast boot. If you cant acces to the storage, use adb to push your zip.
This tutorial can help you:
http://forum.xda-developers.com/showthread.php?t=1667929
thats the problem i cant flash any roms on the phone whenever i try to there is an error in the middle of the process saying cant mount system and mounting system error
and can i not use the miflash right away cause the main problem here is my system partition not working properly
thank you so much guys i solved the problem if anyone finds himself in this situation contact me through pm i would help you

Mİ3 Brick or Dead Im very sadly

Guys. I installed mm miui beta. after I want go back miui kk. and I flashed stock partition with cwm. now I cant flash any zip with twrp, cwm or orj miui recovery. I cant flash fastboot rom. I can only flash recovery with fast boot. in twrp menu internal stroge looking 0 mb. SDcard working but recovery cant flash any zip bec. internal stroge looking 0 mb. And I cant flash rom with adb.
mi flash error: 0x80004005:FAILED (remote: partition table doesnt exist ) Im very sad guys. I love my phone pls help me. with out battery cant give me 9008 port. I cant try testpoints.
Sorry for my bad lang. Who can help me?
in my partition table cant see rm 25 and 26
my partition table = i.imgur.com/XxyPuVA.png
I solved my problem with qpst guys. dont need thread thanks. firstly ı removed partition table with adb. after my pc connected with port10. with qpts ı write blocks. and install with mi flash my offical rom
en.miui.com/thread-138246-1-1
use http and html in end and . wherever necessary cant post link
There is a solution to unbrick using miflash here http://en.miui.com/thread-59891-1-1.html
Flash partition first then try I'm even faced the problem
Flash partition first then try I'm even faced the problem after upgrading to mm
Try to flash partition ill post u the link in next reply
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
This guide is for you
What you will need:*
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)*
2. Windows
3. The device defined somehow Device Manager*
4. The latest version of*MiFlash*
5. MIUI firmware developer for fastboot*here
6. Adb and fastboot installer*here
Connect your phone in fastboot mode*
Enter this
Fastboot flash partition gpt_both0.bin
This file is in fastboot rom.*
This will restore stock partitions, then flash all the kitkat rom.
"Fastboot flash partition gpt_both0.bin"

[CLOSED]Vivo XL2 TWRP 3.0 and Root

I must note: I use linux. I only used Windows because SPFT Linux version gave me a chip mismatch error I couldn't fix easily.
1: Please read. It explains what problems might arise. Especially post #6 and #13.
2: There are 2 versions of the scatter file. The MT6735 version is what I used successfully. The MT6737Tmod version is what comes from post #6 & #13.
3: Please use each scatter file to Readback your boot and recovery partitions first, renaming as fit, so you can have a backup BEFORE ANYTHING. Then test unpacking them to see if everything went correctly. Then readback every partition in the scatter file so you don't have to depend on the stock ROM for a backup. I didn't and it led me to take this route.
3: Seem to be a difference in the naming of the scatter file and sizes of system, cache, and userdata inside from the stock ROM and what works..
4: DO NOT choose Format+Download until you know which scatter file works, unless you want to chance a Hard Brick.
5: Wiping the dalvik and cache in stock recovery before flashing TWRP seems to be the best thing to do to avoid boot loops or a hung boot.
THIS ROOT PROCESS WAS DONE OVER THREE DAYS OF CAR WORK, DRIVING, FAMILY, AND COMPUTER WORK. MOST OF THE TIME SPENT WAS THIS MORNING TRYING TO GO TO SLEEP. DIDN'T HAVE TIME TO DOCUMENT AND TAKE PICTURES. THIS WRITE-UP IS FROM WHAT I REMEMBER DURING THIS PROCESS. IF I CAN REMEMBER SOME VAGUE DETAIL THAT YOU NEED, GOOD. IF NOT, DON'T STRESS ME. THE HARD PART IS DONE. A GOOGLE SEARCH OF SOME OF THESE PROGRAMS WILL GET QUICKER RESULTS IF YOU DON'T HAVE THEM. THE MAIN THING NEEDED FROM MY RESEARCH WAS THE SCATTER FILE. LINKS FOR SCATTER FILE AND RECOVERY IMAGE ARE BELOW.
Looking for a way to root first day getting this phone in February. Read this post last Tuesday about MT67xx rooting, thanks lsemprini. Spent two days finding which versions of the programs work with this phone, already had the ROMs, drivers, and tools. Dove right in.
I downloaded the ROM from needrom. Scatter file was unusable. Wrong chip error. Phone reads MT6735 scatter file read MT6737. Did a manual diff. Used SP Flash Tool v5.1524 to flash, formatted instead of downloading by mistake, cord got pulled, Hard brick. Fought with Windows7 to get drivers to recognize a hard brick. Still don't know how I did it but it read then flashed. Looked like another hard brick but SPFT would recognize it for the Memory Test. I just held power+vol_down with just charging block power to get it to come on. Sometimes just one of the buttons was enough to get it to power on and start a bootloop. Took two minutes sometimes. Flashing the wrong recovery led to bootloops. Starting SP Flash Tool and plugging in the USB to the phone as soon as it powers off during a loop will let the preloader "register" and the images to be flashed. Flashing from a stock ROM will lead to IMEI being erased. Used SN Write Tool v1.1716 to write the IMEI numbers. Got them from the side of the box. The MD1_DB and AP_DB files needed are in the stock rom.
Ported TWRP, credit to jemmini for the post https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601. Used that recovery as a base. Ported according to the myriad of guides that I have been reading over the past few days. None of them worked as instructed, had to modify trial and error style. Finally got TWRP to read the internal partitions AND remain after a reboot. A lot was going on when I did this. Not sure if I formatted before, I remember flashing a lot of because of something. I mounted the system just in case & flashed SuperSu from chainfire's website, no formatting afterwards. Rebooted and installed SuperUser and BusyBox. I tried adb and fastboot. They work but not for everything. Hooked phone up to computer with debugging enabled.
Code:
adb root
gives a shell, no errors unlike before. Edit: ADB won't let me start as root anymore.
Needed files
Blu Vivo XL2 TWRP 3 Recovery
MT6735 Scatter File
MT6737T Scatter File
BLU Vivo XL2 V0070UU Stock ROM if you don't have a backup of your partition images.
Step 1
Install Minimal ADB and Fastboot and USB VCOM drivers.
Download SP Flash Tool, SN Write Tool, scatter file, and twrp3.0 to a working folder.
Download SuperSu zip & SuperUser apk then put them on your SD Card.
Install SD card into phone.
Step 1.A For Full ROM Flash and IMEI Write
Download Stock ROM and extract to working folder.
Move twrp3.0 to ROM folder.
Step 2
Install SP Flash Tool and SN Write Tool and run.
Step 3 To flash TWRP only
Reboot phone to recovery then wipe cache and dalvik. Can't remember if it is a dalvik option in the stock recovery now.
Power off phone. Make sure it is not plugged up to the computer.
IN SP Flash Tool:
Load scatter file that works from working folder.
Make sure download only is selected in drop down menu.
Check only the recovery partition box and click the name of the recovery file on the same line.
Browse to TWRP recovery image and select.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success.
Step 3.B OPTIONAL
Select format and flash all using stock ROM or images backed up from your phone.
Stock ROM must be extracted and custom recover put into same folder and renamed to "recovery.img" to make
everything automatically load.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success
Step 4 Only needed when formating+downloading ROM
With phone still powered off and unplugged, write IMEI numbers using SN Write Tool.
Step 4.A
Click System Config.
Select IMEI in Write Option Area.
Make sure IMEI Checksum and Dual IMEI are checked.
Load MD1_DB and AP_DB files from ROM folder.
Click Load Modem DB from DUT box.
Click Save.
Step 4.B
Click Start.
Input your IMEI numbers from box.
Click OK. Success
Step 5
Boot to recovery.
Swipe to make permanent.
Wipe dalvik and cache.
Flash SuperSu..
Reboot.
Install SuperUser apk and BusyBox of your choice.
Step 5.A
If SuperUser apk or any app that ask for root permission cannot get it, reboot to recovery.
Mount system partition: Shouldn't matter but it worked for me.
Flash SuperSu zip again.
Reboot.
Install SuperUser apk and BusyBox of your choice.
ENJOY
When i connect the device after clicking download, it says "CHIP TYPE NOT match!"
mind you the device is off, i tried to troubleshoot but still getting the same error.
any help would be appreciated
UPDATE: Im thinking it has to be the scatter file, but im not sure.
UPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
[QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.[/QUOTE]
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.
=smith901;72841007][QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
Click to expand...
Click to collapse
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.[/QUOTE]
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
ANJIII said:
chip type not match. pls help
Click to expand...
Click to collapse
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
ANJIII said:
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
Click to expand...
Click to collapse
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
ANJIII said:
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
Click to expand...
Click to collapse
Good. I had to name it that because of the chip mismatch error. It was from the V7 ROM. The other two are updates. I also messed up big time along the way. My phone always read MT6735 but it does have MT6737T in different files. I always wondered about that. I got it to work without buying another phone.
It seem that the phone boot logo never goes away. What should I do now?
Alexis96312 said:
It seem that the phone boot logo never goes away. What should I do now?
Click to expand...
Click to collapse
Hope you Readback your original recovery and other partitions. I didn't and worked hard to get it back. When I just flashed the recovery and something went wrong, it reverted back to the stock recovery.
Try doing this:
1. Start SPFT with the reçovery you want to flash.
2. Hold down the power button. AS SOON AS IT VIBRATES, PLUG THE USB CORD IN.
3. Hopefully you timed it right and it will flash and boot.
Sometimes it took 15 minutes to get past the boot logo.
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Alexis96312 said:
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Click to expand...
Click to collapse
Try flashing stock ROM, wipe data in stock recovery, then flashing TWRP, wipe dalvik.
If that don't work, wipe data then flash stock ROM with TWRP recovery, wipe dalvik.
The scatter file from the stock ROM gave me problems. Had to modify mine.
Don't forget to restore your IMEI afterwards since you formatted+flashed.
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Alexis96312 said:
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Click to expand...
Click to collapse
The one I attatched on the first post #1 is my modified scatter file. The mods included changing the size to the system, cache, and userdata. Just compared all three. The stock MT6737T scatter file and the V12 ota scatter are the same. The one I changed, MT6735, have the file name, platform name, and partition changes. I don't know why I had to modify it., especially the size parts. It all worked when I did that. I basically gave up on it because of a hard brick. Then I remembered reading MT6735 in some file a few months back while roaming the file system. Made the changes and was back in business. Maybe you need the stock scatter file, here it is.
It's what the end result of this post @ANJIII did minus the size changes..
He just did the name changes and it worked for him. Ya'll seem 180° from where I was.
The second one is from the V12 OTA update. It is very minimal, must be all that is needed for a scatter file. Not really sure tho. Hope it is just scatter file issues.
As long as SPFT is reading your phone, it's still a chance on it all working out. That is how I viewed it.
@andromedaXVIII Don't know if you got it working. This might be a potential solution.
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Alexis96312 said:
Unable to find partition for path '/sdcard'
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
I take it TWRP flashed successfully, it is having a problem reading those four partitons. Possibly encryption is stopping you. Try flashing this in TWRP before anything else to remove the encryption.
I didn't get any errors. I know the userdata partition was different in the scatter files. That could be the reason for /sdcard not being recognized. Must be a difference in the layout of phones, not really sure. My protect_s, protect_f, and nvdata partitions and /sdcard all mount fine, pictures attached. I am able to do a backup in TWRP. I have been playing around with porting different ROMs and came across an issue similar to this. Had to change some lines in updater-script.
I checked fstab.mt6735 file in the stock recovery, the modded twrp3 recovery, and stock boot recovery to make sure I didn't make any typos or leave anything out. They all have the same lines. Had to do this:
Code:
("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system")
in the updater-script I was working on. I got ahead of myself flashing a ROM and was stuck on the 1st logo screen. Held power+vol_down to get it unstuck. Yes I was all calling myself kind of names like I'm sure some people have done following this guide.
Which scatter file you used? Did you do a readback in SPFT with the WORKING scatter file and mount one of those images to check if you can read and write the files. I mounted system.img from the stock ROM to make sure I could read and write the files before I started with flashing. I'm thinking there is are internal differences in the XL2s. You might have to reflash using the stock ROM with TWRP as the recovery with the Format+Download option since you got TWRP installed.
Once I get through playing around with trying to flash this ROM, I will restore and try to find all the partition mappings and update TWRP to work with the format from the updater-script and see if that work. Will let you know what happened.
Alexis96312 said:
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Here is all the information I have pulled so far from the phone. Have a screenshot attached from About device in settings. The attached zip file is all the information I could think to pull using adb . The attached file is my partitionlayout. I just ran cat against every file to see what it would give me and redirected the output. Using adb while the phone is in recovery let me pull and read the files I couldn't while the phone was booted.
@Alexis96312, try to run this command in terminal to get your partition map:
Code:
adb shell "su -c 'ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/'" > someFileName.txt
I have mine listed in the zip file as partitionLayout.txt It will list which names go to what device in /dev and save it in your current directory. The file can be used to get the correct partition layout on your phone. Post the results and I will repack the recovery to see if it will work for you. You can do it also with Carliv Image Kitchen, it has a menu :good:. You will have to modify the fstab files in the ramdisk folder of the extracted image to what the partition map specifies. I went thru all of them to be sure when I first ported TWRP.
@ANJIII is correct about the different versions, nice catch. I forgot about that. I assumed you had the V0070UU version like mine, fault on me for not asking. Mine specifically says BLU_V0070UU_V07_GENERIC 25-11-2016 09:46. I'm thinking the GENERIC part comes from me having to flash the stock ROM. I think it had BLU_V0070UU_V07 with user/keys before I bricked it and had to flash the stock ROM. Got three extra apps that I instantly removed. Seems like the stock ROM function the same as before bricking flashing stock.
ScreenShot
ANJIII said:
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Click to expand...
Click to collapse
Answer in pictures
ADB USB
It seem that the computer can't find it what now
Do I need to install the ADB driver again?
I'm trying to do it on stock recovery
Do I have to do it on TWRP recovery?
Alexis96312 said:
It seem that the computer can't find it what now
Do I need to install the ADB driver again
Click to expand...
Click to collapse
It look like the pid:vid aren't recognized correctly. Usually a reboot will help.
Are you connect using adb while in recovery? If so, see if Windows will install new drivers for you. My Linux box read mine as a Samsung at one point. Try running the ls part of the command in TWRP terminal.
This is where I fought with windows when the cord got pulled during flashing. I never got an error like the 2 at the top, always like the bottom one. I kept adding legacy hardware in device manager until one of them worked. The Linux version of SPFT always give a chip mismatch error. Wish it worked so I won't have to boot to Windows.
I kept doing format+download and and plugging the phone in until Windows recognized it because it was in a bootloop when that happened. You need the preloader to be recognized.
Both stock ROMs are on needrom.com. I downloaded the UU version, the EE version is what you might need. I'll pm you a link to my backups from TWRP to see if they will work for you. Same thing happened to me playing with the new ROM. Restoring my boot and system got it back working.

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

Bricked realme x2 pro (TWRP - unlocked) partition problem?

Hi. This afternoon I tried to install the dirty unicorn rom. Unlock bootloader and flashed TWRP successfully. Then I tried to flash "Pie Firmware & Vendor" because it had realmeUI no ColorOs. The problem is that now I can not do anything with the mobile. It starts directly in TWRP. I have tried to flash a stock rom (CN) but it doesn't work. I think it is a problem with the partitions, for example if I try to clean cache / dalvik etc I receive these messages.
- Failed to mount '/data'
-Falied to wipe dalvik.
I have read many threads, but I cannot find a solution.
I saw this video,- [FIXED] Unable to mount /data or /system error- on youtube (sorry, i cant post URL yet) where even if it is another phone, it presents the same problem as me, but when I try to repair data I receive a failure (Error 8, unable to repair data) and I don't know what else I can do.
I hope you can help me .
Thank you!
in twrp to return to stock:
flash realme ozip
flash vbmeta.img to vbmeta
format data
reboot
perisman said:
in twrp to return to stock:
flash realme ozip
flash vbmeta.img to vbmeta
format data
reboot
Click to expand...
Click to collapse
Hi,I cannot pass files from my pc to the device, when I connect it, it is detected but it does not allow me to insert any rom.
Any other way to pass it?
Hi. I have managed to solve the problem that I had when wipe. I have changed "Data" format first to FAT and then back to EXT4.
But I still can't get past TWRP. Now if I try to start the TWRP system, it says that there is no OS installed.
Tried to flash ozip using SIDELOAD, but it gives me an error. I can flash dirty unicorns this way (for example), which also doesn't fix anything.
perisman said:
in twrp to return to stock:
flash realme ozip
flash vbmeta.img to vbmeta
format data
reboot
Click to expand...
Click to collapse
Hi. ok, after a whole afternoon struggling, i have found that i cannot flash .ozip from twrp, so i have transformed a rom .ozip into .zip. I have tried to flash using SIDELOAD but it gives me an error. I have tried to flash D.U rom the same way and there has been no error but it still gets caught on the loading screen. I don't know how to flash the realme rom, I can't fix anything, I'm really desperate
THANKS
What twrp are you using?
mauronofrio's last version -13 , orangefox R 10.1 and skyhawk 2.2 can decrypt and flash ozips.
Try also to put files to flash in a usb memory, change storage in twrp mount option and try to flash from usb.
If you flash aosp rom, try aosip 10, and used it and works well. and after flash it format data.
---------- Post added at 11:26 PM ---------- Previous post was at 11:10 PM ----------
you can try also to flash aoisp with whole process
firmware and vendor zip first
rom
volte fix
gapps
format data
reboot
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
If you can go to fastboot from twrp reboot menu
try this
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
perisman said:
What twrp are you using?
mauronofrio's last version -13 , orangefox R 10.1 and skyhawk 2.2 can decrypt and flash ozips.
Try also to put files to flash in a usb memory, change storage in twrp mount option and try to flash from usb.
If you flash aosp rom, try aosip 10, and used it and works well. and after flash it format data.
---------- Post added at 11:26 PM ---------- Previous post was at 11:10 PM ----------
you can try also to flash aoisp with whole process
firmware and vendor zip first
rom
volte fix
gapps
format data
reboot
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
If you can go to fastboot from twrp reboot menu
try this
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
Click to expand...
Click to collapse
Hello, I just installed TWRP v13 and wipe everything (data, system, vendor ...).
I have tried to install rom stock by fastboot but still it doesn't fix anything.
I have also tried to install AOSP by slideload and nothing is solved either. I have to buy a usb adapter this afternoon, to connect and test it this way, but for the moment, I still have no solution. Thank you, I will keep reporting!
I definitely don't know what to do. Change TWRP for Orange fox, and I have tried to install a stock rom, I have tried downloading the latest official rom from here (Realme UI), https://www.realme.com/cn/support/software-update, but when flashing it gives me an error "Update process ended with error: 7. Are you installing onto the correct device?" (I'm sure I'm downloading the proper CN version).
I have tried to flash a previous rom that I downloaded from here (color OS 6.1) https://www.xda-developers.com/andr...2-pro-android-software-update-download-links/ and it seems to be successful, but it gives two failures at the end
1. Failed to mount / dev / block / bootdevice / by-name / userdata at / data: Device or resource busy.
2.Failed to unmount / data: device or resource busy.
The phone is locked in the startup image.
i am facing the same problem
twrp 3.4 is no longer able to unlock partition,
is there any solution
what to do ?
i have the same problem. i bricked my device and stuck at twrp.. every time i try to flash the latest official update from realme i get this error : Failed to mount / dev / block / bootdevice / by-name / userdata at / data: Device or resource busy."
i dont know how to fix it.. my bootloader is unlock.
i am stuck on bootloop and twrp.. any ideas how to fix it?
I have two ways that probably will fix your issues .
The first one is much more faster and I recommend you to try it first .
Boot into bootloder mode (fastboot mode)
Open cmd and type fastboot -w .(THIS WILL WIPE YOU INTERNAL STORAGE )
boot to recovery .
Wipe cache, dalvik-cache,system,data .
Format data .
Reboot to recovery (Use the recovery boot option, choose recovery) it will ask you if you sure to reboot as no rom is installed ,swipe yes,or something similar.
Flash ozip if you are on OrangeFox or unofficial twrp ,if you on official twrp that does not support ozip , you must use a zip stock rom .
Format data .(if have a error reboot into recovery and then format data again)
Boot to the rom .
If it does not solve you issue I recommend to flash stock rom with fastboot commends .
You can find the files needed in this thread https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107 .
Choose the files for you phone version EU,IN,CN .
This is a color os and not realme ui . You can make your own realme ui version but this will work just fine .You can flash after a realme ui version ozip on recovery .
Open cmd on the folder of the download files .
Write without the quote mark and press enter "fastboot -w && fastboot erase system && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot"
After this your phone should boot into color os version.
If you need help please write and I try to help you .
JUST DO NOT TRY TO RELOCK YOUR BOOTLODER, THIS WILL BRICK YOU PHONE .
unknownart said:
i have the same problem. i bricked my device and stuck at twrp.. every time i try to flash the latest official update from realme i get this error : Failed to mount / dev / block / bootdevice / by-name / userdata at / data: Device or resource busy."
i dont know how to fix it.. my bootloader is unlock.
i am stuck on bootloop and twrp.. any ideas how to fix it?
Click to expand...
Click to collapse
I FOUND A WAY
switch off mobile,
after few mins boot in to fastboot
flash orangefox recovery
now boot in to recovery and try format data NOW,
and reboot
remember, update till C25, magisk20.3 works
all custom roms magisk20.3 works
only latest C29, magisk20.4 working
davidscdl said:
Hi. This afternoon I tried to install the dirty unicorn rom. Unlock bootloader and flashed TWRP successfully. Then I tried to flash "Pie Firmware & Vendor" because it had realmeUI no ColorOs. The problem is that now I can not do anything with the mobile. It starts directly in TWRP. I have tried to flash a stock rom (CN) but it doesn't work. I think it is a problem with the partitions, for example if I try to clean cache / dalvik etc I receive these messages.
- Failed to mount '/data'
-Falied to wipe dalvik.
I have read many threads, but I cannot find a solution.
I saw this video,- [FIXED] Unable to mount /data or /system error- on youtube (sorry, i cant post URL yet) where even if it is another phone, it presents the same problem as me, but when I try to repair data I receive a failure (Error 8, unable to repair data) and I don't know what else I can do.
I hope you can help me .
Thank you!
Click to expand...
Click to collapse
Just reboot to twrp .
Directly to format data
Format data by typing Yes
Now try to mount data
It will work
or965 said:
I have two ways that probably will fix your issues .
The first one is much more faster and I recommend you to try it first .
Boot into bootloder mode (fastboot mode)
Open cmd and type fastboot -w .(THIS WILL WIPE YOU INTERNAL STORAGE )
I got this problem
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Click to expand...
Click to collapse
My fastboot -w command not working....its showing
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
help me

Categories

Resources