Related
Basically, as the title say, I have problem with it. Before that, I have a custom install (Archidroid 3.1.5), root and bootloader is unlocked. At one point, the phone hang....then I reboot it and that why I got the problem. Thus, I tried many ways to restore back my phone. I tried...
1. Try wipe data, cache, dalvik, system, factory reset, format data using TWRP - failed (except format data)
1. Try install back the custom ROM (ArchiDroid) - it said symlink: some symlinks failed
2. Try install another custom ROM (cm13) - it said error: 7
3. Try flash stock ROM ftf file using flashtool - it said Processing of kernel.sin finished with errors
Edit 1:
1. Try wipe data, cache, dalvik, system, factory reset, format data using TWRP
2. Try install back the custom ROM (ArchiDroid)
3. Try install another custom ROM (example: cm13)
4. Try flash stock ROM ftf file using flashtool
None of the above help. For 1, 2, and 3 I think is because the /data. It said "unable to mount /data {invalid argument}. As for flashtool, I try version 0.9.19.10 and 0.9.18.6 both got error about the process of kernel.sin finished with error. So, my phone only can do boot to recovery (TWRP), and normal boot (back to problem as in title).
Please help me :crying:
I have same problem. Try to flash/install anything at recovery ---> ( Failed to mount data ).
U 've done with that ?
Dickysuryanata said:
I have same problem. Try to flash/install anything at recovery ---> ( Failed to mount data ).
U 've done with that ?
Click to expand...
Click to collapse
mee to
Your phone gets Ebola now. It's now time to change the motherboard.
Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?
Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.
mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!
Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read
wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!
i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.
i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course
what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!
Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work
i tryed it, i get the same error :/
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?
colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!
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'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.