I'm having difficulty flashing ROMs and not sure how to fix it. I've tried several over the last few months and had issues with all of them, sometimes the same issue. These are the ones I've tried in the last couple days:
Syberia
crDroid
Arrow
LineageOS(4MicroG)
It started a few months ago with one of the updates to Syberia. I was running Syberia, and had a notification for an OTA update. The update failed and put me back in the old Syberia partition. I then started trying to flash other things, and after that I couldn't even get the older versions of Syberia to boot.
The install goes fine, however after step 2/2 I get the following errors:
Failed to mount 'system_root' (Invalid argument)
Failed to mount 'system_ext' (Invalid argument)
Failed to mount 'product' (Invalid argument)
Failed to mount 'vendor' (Invalid argument)
Click to expand...
Click to collapse
I've been using MiFlash 2020.3.14.0 to restore back to stock EEA v13.0.7.0, and also flashed firmware EEA v13.0.3.0, however I've also tried some others along the way. Also using SKKK's TWRP V3.4, or whatever each ROM has suggested in its install instructions.
These are the problems I'm having with the ROMs above:
Syberia - bootloops back into recovery
crDroid - bootloops back into recovery
ArrowOS - works, screen flickers sometimes though, not my preferred ROM as no traffic indicators
LineageOS - boots, little bit unstable, USB OTG does not recognise my larger thumbsticks
I get the feeling this isn't a ROM issue, rather something with my device - particularly when multiple ROMs are having the same issue.
One other thing I've noticed, my Fastboot logo has changed. Instead of the little Chinese dude pulling apart an Android, it just says in faint orange text "Fastboot". When I first started tinkering this problem somehow it went back to the old logo but then it changed again on another reboot. I'm concerned that something has tampered with my unlocked bootloader, but maybe that's just paranoia.
Does anyone have any suggestions on what to try?
TWeaKoR said:
I'm having difficulty flashing ROMs and not sure how to fix it. I've tried several over the last few months and had issues with all of them, sometimes the same issue. These are the ones I've tried in the last couple days:
Does anyone have any suggestions on what to try?
Click to expand...
Click to collapse
Try with the latest TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.0_A12
NOSS8 said:
Try with the latest TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.0_A12
Click to expand...
Click to collapse
Thanks, I'd thought there was a new version however I didn't find it before.
No luck though, got the same errors. Took a logcat this time:
Part 1: https://pastebin.com/tkqvZvBe
Part 2: https://pastebin.com/U4q9QKLJ
TWeaKoR said:
Thanks, I'd thought there was a new version however I didn't find it before.
No luck though, got the same errors. Took a logcat this time:
Part 1: https://pastebin.com/tkqvZvBe
Part 2: https://pastebin.com/U4q9QKLJ
Click to expand...
Click to collapse
Twrp/wipe format data write yes /reboot twrp flash rom.
If still the same, install with this tool the rom corresponding to the firmware of the one you want to install.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
TWeaKoR said:
Thanks, I'd thought there was a new version however I didn't find it before.
No luck though, got the same errors. Took a logcat this time:
Part 1: https://pastebin.com/tkqvZvBe
Part 2: https://pastebin.com/U4q9QKLJ
Click to expand...
Click to collapse
1. Format data (with typing "yes")
2. Wipe cache/dalvik
3. Flash ROM
4. Reflash recovery ("Flash current TWRP" / "Flash current OrangeFox" - or, when flashing the ROM, tick "Reflash ... after flashing a ROM")
5. Format data (again)
6. Reboot to Android
PS: the recovery log (/tmp/recovery.log) would provide useful information
Right, so I managed to get it to boot into Syberia, then lost it again.
I forgot to install TWRP after flashing, it bootlooped me into Syberia's AOSP recovery, and I was able to format in here. Rebooting afterwards launched Syberia. However, when I flashed TWRP again (and then Magisk) it broke and just bootlooped over and over (had to manually go into recovery instead of being thrown into it).
NOSS8 said:
Twrp/wipe format data write yes /reboot twrp flash rom.
If still the same, install with this tool the rom corresponding to the firmware of the one you want to install.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
MiFlash20220507 didn't work for me, it throws up errors that it can't access its own log file, both when trying to install drivers or find devices. MiFlash 2020-3-14-0 works fine however. I downloaded and flashed EEA 13.0.8.0 this time.
DarthJabba9 said:
1. Format data (with typing "yes")
2. Wipe cache/dalvik
3. Flash ROM
4. Reflash recovery ("Flash current TWRP" / "Flash current OrangeFox" - or, when flashing the ROM, tick "Reflash ... after flashing a ROM")
5. Format data (again)
6. Reboot to Android
PS: the recovery log (/tmp/recovery.log) would provide useful information
Click to expand...
Click to collapse
In the past I've tried formats both before and after flashing with no luck.
This time, after flashing stock I Fastboot flashed the latest TWRP, then tried to format, but got the errors:
Failed to mount '/data' (Invalid argument)
Unable to format to remove encryption.
Updating partition details...
Failed to mount '/data' (Invalid argument)
Click to expand...
Click to collapse
Doing a factory reset instead of format gave the same errors, without the 'Unable to format' line.
When I then flashed the ROM, I didn't get the 4 errors I had previously, only 1 error for /data. However rebooting to system still bootlooped the same, until an AOSP recovery format.
It seems like the issue is with the TWRP format step? It's strange that TWRP format doesn't work but AOSP recovery's does.
I forgot to get logs the first time, but I ran through it all again (back to stock and flashing in TWRP).
Recovery: https://pastebin.com/sU4LCcZQ
Logcat P1: https://pastebin.com/4pfLJ0pn
Logcat P2: https://pastebin.com/QLnahBjb
TWeaKoR said:
Right, so I managed to get it to boot into Syberia, then lost it again....
Click to expand...
Click to collapse
You might want to try another custom recovery.
DarthJabba9 said:
You might want to try another custom recovery.
Click to expand...
Click to collapse
Anything you can suggest? Most of the others I can find are well out of date, not sure if they'll even work in Android 12.
TWeaKoR said:
Anything you can suggest? Most of the others I can find are well out of date, not sure if they'll even work in Android 12.
Click to expand...
Click to collapse
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
DarthJabba9 said:
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Oh hah that's yours, didn't realise I was speaking to the Don!
DarthJabba9 said:
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Wahey, got there in the end! Flash with Orangefox, then format data (otherwise on the reboot it will be encrypted). I then had a bit of an issue - I bent and borked the only USB OTG adapter I have with me. However I managed to dig out a flash drive with USB-C, it's a little dodgy but it got the files across to flash add-ons.
Orangefox is nice, and it seems a little more robust and better at handling the a/b partitions than the TWRPs I've tried previously.
Now all I need to do is get a working MicroG setup, then I'll be golden.
Related
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
Click to expand...
Click to collapse
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
Click to expand...
Click to collapse
unfortunately no choice other than wiping everything.....
antisoma said:
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
Click to expand...
Click to collapse
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Hw4ng3r said:
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Click to expand...
Click to collapse
So do you think there would be workaround in future?
0xelectron said:
So do you think there would be workaround in future?
Click to expand...
Click to collapse
Hopefully there will be, but it doesn't look promising right now. @eng.stk is the one that was modding the TWRP, but has since stopped doing TWRP dev.
kipue said:
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
Click to expand...
Click to collapse
But I'm on official 3.2.8 with ext4 partition
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
nqk said:
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
Click to expand...
Click to collapse
Fastboot Format system and data
Then fastboot flash stockrecovery
Then boot to system
Sideload rom
Then fastboot boot twrp28
Then wipe data and install superuser in one go
candiesdoodle said:
Fastboot Format system and data
Click to expand...
Click to collapse
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
nqk said:
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
Click to expand...
Click to collapse
Yeah fastboot Format userdata
But since you don't have the dm-verity you can skip the fastboot Format. Boot into the modd twrp and when it asks for password, hit cancel and then format data (you will have to type 'yes').
Then flash SuperSU or superuser in the same session without booting. This will ensure dm-verity doesn't come up again as it will start in enforcing mode, thanks to SuperSU/superuser.
You may be able to flash twrp afterwards but I haven't tried it.
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
prospektus said:
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
Click to expand...
Click to collapse
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
thrustaxehandle said:
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
Click to expand...
Click to collapse
yes.. delete internal memory. rom board. format data.
thrustaxehandle said:
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
Click to expand...
Click to collapse
You need to upgrade to a higher version for twrp. 3.2.2
prospektus said:
yes.. delete internal memory. rom board. format data.
Click to expand...
Click to collapse
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
esiv129 said:
You need to upgrade to a higher version for twrp. 3.2.2
Click to expand...
Click to collapse
I'm already using TWRP version 3.2.3
thrustaxehandle said:
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
I'm already using TWRP version 3.2.3
Click to expand...
Click to collapse
try again unlock
prospektus said:
try again unlock
Click to expand...
Click to collapse
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
thrustaxehandle said:
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
Click to expand...
Click to collapse
When you get the mount error, come to the home page and get to the mount. speak enable all options enable all options. speak restart recovery restart recovery. make format data
Not sure if the link is forbidden? I can't tell you sorry. https://www.youtube.com/watch?v=dzrWkjOfndA&t=501s
I have read replies and everyone is sharing his bit of suggestions, here are mine
1. boot redwolf as FASTBOOT BOOT recovery.img - (if you arent already)
2. change file type of /data partition to-from (xFat to ext4) and wipe all partitions (internal storage can be skipped)
3. instead of linage15.1 same package, try downloading some other custom rom, i recomend DotOS2.5 or Crdroid4.6.2
4. uncheck enforce md5 bla bla while flashing zip.
i hope you will succeed
I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU).
The steps I took to change the ROM:
Formated data (errors started right away) then I did the usual wipes (cache, dalvik, data)
Whenever I try to wipe or format data I get error messages like: Error opening /data/XXX (Operation not permitted).
System is always mounted read-only no matter what I try and after I install any ROM many of these error messages pop up.
Orange Fox gives some error about key.
Flashing of the ROM suceeds, but system cannot boot, loading screen forever.
Can anyone point me some directions?
Thanks in advance and sorry about any possible bad grammar.
[ ]s
;-)
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Pavello said:
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Click to expand...
Click to collapse
Well , i have the same problem..and used pitch black also
Any update on this?
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
i gusse thats a problem in miui12.0.3
i was using pixel experience 10 then i flash miui 12.0.3 in fastboot when i tryd to flash orange fox i had the same problem
so i gusse u can downgred to miui 11 and flash twrp and it will work
I solved this by downgrading to 12.0.1
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
I am having this exact problem.
Under internal storage (sdcard) I see a bunch of hashed folders I cannot open.
Format data returns a multitude of "Error opening '/data/somefolder/asdf/asdf' (Operation not permitted) and marks the wipe as Failed. The attempted formatting also mentions "E:Error making /sdcard/Fox directory: Required key not available." "Failed to unmount '/data' (Device or resource busy)
I can wipe anything except Data. I also tried downgrading to 12.0.1 firmware but it does not fix it for me.
The ROM can be booted into, and magisk managed to be installed, but no google apps were installed.
Dibbo Sarker said:
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
Click to expand...
Click to collapse
I tried this, but no luck on my side.
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
A problem like this was the one I had since TWRP had the device encrypted but it did not inform me and it did not give me any sign that I had to write a password (password that I have no idea what it is).
What I did so that it did not give me an error was to install Orangefox and while there delete everything and install a file of these that I got from google.
I had to try one by one and restart to see if it asked me for a password in orangefox, luckily one worked and it no longer asked me to decrypt the files and I could install the rom and gapps normally
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
Thank youuuuuuuu! You have rescued my phone!
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
THANK YOU!
Why is my orange fox is not showing Vendor, System Etc ? How can i fix this ? I really need to wipe those as well..
Jona'san - sama said:
Why is my orange fox is not showing Vendor, System Etc ? I really need to wipe those as well..
Click to expand...
Click to collapse
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
Jona'san - sama said:
I really need to wipe those as well..
Click to expand...
Click to collapse
if you want to flash a rom = yes
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Can't wipe it still, I already try the Mount > ✓ Vendor ✓ System.. but in formatting it say's "Cant Mount the....blah..blah.."
I try to uncheck the "Mount System vendor, system as read-only" from the settings of mount.. but for some reason, if you go back to Mount options again, you can't check the system, vendor now
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Yes, I need it to flash a ROM
try this it worked
Had the same issue.
1. I installed twrp via ADB
2. Restarted to recovery mode into twrp
3. Installed the latest OrangeFox and restarted into recovery again.
4. It asked me for a password which is the pin I set then proceeded to format data.
5. After formatting data I restarted again to recovery.
Then I was able to install custom roms.
I am using derpfest Android 12 on my Poco x3 pro. I want to install magisk.zip through orange fox recovery installed on my phone. But I am not getting storage data on recovery, only a fox folder is there. Can somebody tell me is it a glitch or any Android 12 restrictions or something.
I need your help please
my phone sometimes reboot automatic, the last get bootloop, and then the phone won't work properly.
Error on /system , /data , / cache, /storage (all of them get message "Invalid argument" but on system "No such file or directory"). Can't take picture of it because that's only my phone.
already doing anything from Google, Youtube, and MI forum. But all of them not work for my phone.
I tried to flash from MI flash and get error "remote: failed to write partition"
what I need to try :
1. Send your TWRP, PBRP, OrangeFox, Batik Recovery . Backup all of them and fresh (just like a new from factory reset) so i just only restore that
2. i need your suggestion what should i do
if all of them doesn't work too, well my last thing is buy a new phone
sorry for my bad English
Which model, what was the ROM installed on the phone before and which ROM were you trying to flash?
edizz0 said:
Which model, what was the ROM installed on the phone before and which ROM were you trying to flash?
Click to expand...
Click to collapse
Redmi 5A (RIVA) Installed CUSROM "Syberia OS 3x" trying to flash Stock ROM via MI FLASH but can't, error like the screenshot
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Renatoskie said:
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Click to expand...
Click to collapse
Are you using TWRP by Vasishoth? Those "Failed to mount" errors are related to his TWRP, no user error. Nebrassy's TWRP doesn't have those errors.
Are you using a Custom ROM or Stock ROM?
You may have accidentally wiped "/metadata". That partitions is crucial and contains the encryption key for /data, and without the encryption key /data cannot be accessed, and therefore the system can't boot.
If that's the case, you might have bad luck and need to format data, in order to boot the system again.
dreamytom said:
Are you using TWRP by Vasishoth? Those "Failed to mount" errors are related to his TWRP, no user error. Nebrassy's TWRP doesn't have those errors.
Are you using a Custom ROM or Stock ROM?
You may have accidentally wiped "/metadata". That partitions is crucial and contains the encryption key for /data, and without the encryption key /data cannot be accessed, and therefore the system can't boot.
If that's the case, you might have bad luck and need to format data, in order to boot the system again.
Click to expand...
Click to collapse
Oh I see. I think it his, it was twrp-aliothin, the unofficial one. I using a stock ROM and decided to move to Pixel Experience through TWRP and I stuck there. Where to format the data? Is it in the TWRP? And what do I do after that, sir?
Renatoskie said:
Oh I see. I think it his, it was twrp-aliothin, the unofficial one. I using a stock ROM and decided to move to Pixel Experience through TWRP and I stuck there. Where to format the data? Is it in the TWRP? And what do I do after that, sir?
Click to expand...
Click to collapse
Yup that's Asishoth's TWRP. Both Nebrassy's and Asishoth's are unofficial tho. No official TWRP yet available for Poco F3.
Did Pixel Experience boot properly once, tho? Or has it never booted?
Yup I meant Format Data inside TWRP. It's in "Wipe". That may fix your problem, but I'm not sure...
Renatoskie said:
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Click to expand...
Click to collapse
Can you start it in fastboot?
Does your pc recognize it in fastboot?
If the answer is yes, try switching back to the stock you previously had using miflash.
Remember to select "clean all" instead of "clean all and block" otherwise the brick is insured...
You can also read this guide which contains a lot of information that may be useful to you.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
dreamytom said:
Yup that's Asishoth's TWRP. Both Nebrassy's and Asishoth's are unofficial tho. No official TWRP yet available for Poco F3.
Did Pixel Experience boot properly once, tho? Or has it never booted?
Yup I meant Format Data inside TWRP. It's in "Wipe". That may fix your problem, but I'm not sure...
Click to expand...
Click to collapse
I tried this and still not working honestly. It's still in the process of loading the Pixel Experience ROM. My bad actually, Pixel Experience ROM also provides a Recovery but it seem sketchy so I decided to use the TWRP one.
RollDload said:
Can you start it in fastboot?
Does your pc recognize it in fastboot?
If the answer is yes, try switching back to the stock you previously had using miflash.
Remember to select "clean all" instead of "clean all and block" otherwise the brick is insured...
You can also read this guide which contains a lot of information that may be useful to you.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
Click to expand...
Click to collapse
Oh yes thank you. Finally it worked. At first I didn't find the menu for Bootloader Fastboot, instead the Fastboot that the TWRP provided, which makes the device undetected with Mi Flash, CMD Fastboot Devices, Xiaomi Szaki Tools, but after I found the right menu which lead me ro Bootloader Fastboot, it can detect my device again, so I properly did what you told and voila, all worked again. Many thanks, Sir!
Renatoskie said:
Oh yes thank you. Finally it worked. At first I didn't find the menu for Bootloader Fastboot, instead the Fastboot that the TWRP provided, which makes the device undetected with Mi Flash, CMD Fastboot Devices, Xiaomi Szaki Tools, but after I found the right menu which lead me ro Bootloader Fastboot, it can detect my device again, so I properly did what you told and voila, all worked again. Many thanks, Sir!
Click to expand...
Click to collapse
I'm glad it worked.
however, if you want to enter fastboot mode easily do this:
1) turn off the phone;
2) hold down the "volume - and power" keys until the word fastboot appears.