As mentioned in the title, fastboot booting a twrp.img to enter a temp TWRP seems to completely wipe everything else on the device, including the current OS. To bypass this I'm using a method in one of the guides using a nonflagged twrp.img to format data, re-fastboot boot into recovery, unmount-remount data. This allows me access to storage again so I can flash a different ROM. If I make the TWRP permanent, booting from new ROM system into recovery also wipes the OS. I'm not sure what other details to provide but I can answer any questions. Help would be appreciated, thank you!
I have never heard of this problem, what TWRP are you using? Firmware? ROM?
Darkaeluz said:
I have never heard of this problem, what TWRP are you using? Firmware? ROM?
Click to expand...
Click to collapse
Started with base MIUI, I believe it was 12, then updated to 12.5, so I got hit with ARB from the start. Switched to custom ROM, I went through crDroid, EvoX, and HavocOS before switching to Descendant 12, which is what I'm on now.
I'm pretty sure the issue began when I was flashing 12 after updating to 12.5 (to make sure all the tail ends were cleaned up I suppose) before flashing crDroid.
edit: I flashed stock through MiFlash so it just didn't work and I moved on, no bricking from ARB with TWRP
I've been using the Nebrassy TWRP, following this guide.
I'm not sure what you mean by firmware. I do not use a custom kernel if that is what you're asking.
FoxTailKitsune said:
Started with base MIUI, I believe it was 12, then updated to 12.5, so I got hit with ARB from the start. Switched to custom ROM, I went through crDroid, EvoX, and HavocOS before switching to Descendant 12, which is what I'm on now.
I'm pretty sure the issue began when I was flashing 12 after updating to 12.5 (to make sure all the tail ends were cleaned up I suppose) before flashing crDroid.
edit: I flashed stock through MiFlash so it just didn't work and I moved on, no bricking from ARB with TWRP
I've been using the Nebrassy TWRP, following this guide.
I'm not sure what you mean by firmware. I do not use a custom kernel if that is what you're asking.
Click to expand...
Click to collapse
Try to flash the latest fastboot original MIUI ROM for your device, that normally gets rid of most conflicts, and I would recommend following the flashing steps from CrDroid 8.1
Darkaeluz said:
Try to flash the latest fastboot original MIUI ROM for your device, that normally gets rid of most conflicts, and I would recommend following the flashing steps from CrDroid 8.1
Click to expand...
Click to collapse
How can I do that when my ARB is higher than stock ROM
Edit: I removed the ARB check in the .bat file and then flashed stock MIUI 12.5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this error after flashing but everything seems fine once booted up.
Edit2: Attempt to flash Descendant 12:
1. Boot into stock ROM, set pin, finish setup
2. Boot into bootloader -> fastboot boot twrp.img
3. Flash descendant.zip -> I get this:
ERROR: failed to mount /system_ext
failed to mount /product
3a. (optionally) make TWRP permanent -> flash current TWRP
same errors
3b. system OS is wiped, sdcard is empty
4. Boot into system. Buggy (most notably audio freezing/cutting out)
4a. fastboot boot twrp.img
4b. OS is wiped, sdcard empty
I tried this twice. First time was 1-3b, second time 1-3, 4-4b.
I will try with the crDroid 8.1 posted TWRP file.
Edit3: using crDroid TWRP file
1. fastboot boot twrp-crdroid.img
2. flash crDroid (auto-flash twrp toggled)
3. reboot recovery
4. flash everything
5. FORMAT VERY IMPORTANT
6. boot system
On further consideration, I made two mistakes. One was getting too fixated on the errors, the other was not formatting after flashing. The twrp file really helped to resolve these issues. Thanks for your help.
FoxTailKitsune said:
How can I do that when my ARB is higher than stock ROM
Edit: I removed the ARB check in the .bat file and then flashed stock MIUI 12.5.
View attachment 5525303
I get this error after flashing but everything seems fine once booted up.
Edit2: Attempt to flash Descendant 12:
1. Boot into stock ROM, set pin, finish setup
2. Boot into bootloader -> fastboot boot twrp.img
3. Flash descendant.zip -> I get this:
ERROR: failed to mount /system_ext
failed to mount /product
3a. (optionally) make TWRP permanent -> flash current TWRP
same errors
3b. system OS is wiped, sdcard is empty
4. Boot into system. Buggy (most notably audio freezing/cutting out)
4a. fastboot boot twrp.img
4b. OS is wiped, sdcard empty
I tried this twice. First time was 1-3b, second time 1-3, 4-4b.
I will try with the crDroid 8.1 posted TWRP file.
Click to expand...
Click to collapse
what MIUI are you trying to flash? what phone do you have? K40?, F3 global? China?
Darkaeluz said:
what MIUI are you trying to flash? what phone do you have? K40?, F3 global? China?
Click to expand...
Click to collapse
12.5.5, the latest official ROM. I have F3 global.
Edit: It seems to be more an issue with Descendant than the other ROMs. PEX and crDroid, although also having mounting errors, did not come with the same ones. /vendor is okay, but it seems to be an error when failing to mount /oem and/or /system(.extensions) -- this would make sense, obviously.
I may try HavocOS and some other ROMS at a later time.
Related
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Lol, dont understand why you typed "revocery" in your pic but it still understood
badrsj said:
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Click to expand...
Click to collapse
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
That's strange, but Orange recovery also reverted
You're right it shouldn't have installed but it did. The Orange recovery also installed, neither stuck tho
Awesome
martin.burgas said:
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
Click to expand...
Click to collapse
Will try
Thanks
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N950U1 using Tapatalk
badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights outView attachment 4591035
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I'm straggling with Chinese like most of us here. There is an android app you can install on your other phone which would use your cam to translate Chinese. Try that see if it helps...
What I am getting from this (cannot read chinese) but phone goes into fastboot - So I have formated, deleted the eu rom I had on the internal - so start again install the fastboot rom, twrp into it reboot twrp, have eu rom on SD Card and go from there.
badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
Click to expand...
Click to collapse
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Sent from my SM-N950U1 using Tapatalk
badrsj said:
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Click to expand...
Click to collapse
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Can I flash this instead
Hi, I'd also flashed miui_MIMAX3Global_V9.6.6.0.OEDMIFD_091e94a919_8.1
Can I flash this rom on top of the above?
Fastboot ROM: http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
Located here
https://xiaomi.eu/community/threads...-and-recovery-rom-9-6-7-0-for-mi-max-3.45198/
Thanks, I'm afraid I'll brick the device?
Also struggled with twrp, switched back to miui's.
Look the twrp official site, find your device and follow step by step the fastboot method till the end. Worked.
I have solved the TWRP issue, the problem now is that when I flash a ROM it does not seem to work and crashes.
I am worried this is going to get bricked in this process. Maybe just wait for the official Global to come out
Which Partitions Change to F2FS
martin.burgas said:
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Click to expand...
Click to collapse
Hi, Which partitions to change to F2FS, If we change the Data Partition that would need to reflash Miui Chinese again?
Many Many Thanks - I am up and running
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Thanks Martin you're very helpful I am now up and running. I am going to list a list of mistakes
1. I should have used CMD, not Powershell (type CMD in the address bar of the folder where your recovery is)
2. I did not know the sequence of flashing (change to F2FS, reboot recovery from within, Wipe Dalvic, Cache, Data) Then flash
3. I did not know how to boot recovery from fastboot (fastboot boot "recovery.img" "name of your recovery")
4. I did not know to change file system for data, (From TWRP Wipe->Advanced wipe->Repair or change file system. Select Data partition, select F2FS) change it then reboot recovery = see step 2 above.
Thanks Very Much
I am listing these for reference, and for those who help others to know what other errors may be committed.
Twrp supposedly installed -- twice -- but i got nothin'
Hi all,
I love this forum -- despite having a bunch of learning disabilities, I've managed to root a half dozen devices over the years thanks to your patience. This time I'm stumped.
Can't install TWRP. It says it is installed successfully with ADB (see screenshot). I used
twrp-3.3.1-0-nitrogen.img and I'm on I'm on Miui Global 10.3.5 Stable (Android 9PKQ1.181007.001).
Command line confirms installation. MM3 reboots when I enter the fastboot reboot to recovery command but it boots into the main system. I can boot into recovery using power/volume up method but it boots to the stock Mi recovery.
Should I try OrangeFox? Does this have anything to do with dm-verity? Is there anything else I can try to get root?
Originally, I wanted to install LineageOS, but what with locked bootloaders, anti-rollback, DM Verity, etc. , I'm guessing that's over my head and would happily settle for rooted stock.
Best,
Amy
Twrp supposedly installed -- twice -- but i got nothin'
EUREKA!!! I found a simple solution to install TWRP no worries about verity etc and I am rooted!
Genius idea came from Youtuber. Here is the link but I will still describe it in case the video gets removed for some reason.
You do it the regular stuff:
adb reboot bootloader
fastboot flash recovery "twrp filename"
But then while you're still in fastboot enter "fastboot recovery" into the command line and before you hit enter, press and hold volume up on the phone.
It boots into TWRP!
Note that you will keep getting Mi Recovery using volume down/power combo until after you use TWRP install (accessing TWRP with above method) to flash magisk.
Then, TWRP seems to stick. (Although just in case it gets unstuck, I installed the official twrp app from the Play store, since it has a 'boot into recovery' option.
Presenting the TWRP Recovery for Asus Zenfone Lite L1 (ZA551KL) (asus_x00r)(Treble Supported)(Encryption Fixed) Disclaimer : I am not responsible for any bricked device, all responsibility bears the user.
First Unlock Boot-loader using official asus ubl tool - Download UBL App
Team Win Recovery Project (TWRP) is the most famous custom recovery used by the people who like to flash custom roms, patches, flashable zips etc. The latest version is TWRP 3.2.3-0.
Flash zips through otg or Micro sd Cards as device is encrypted , if you format data and decry-pt then the Flashlight (torch) and the Camera will not Work.ENCRYPTION IS FIXED NOW
Installation By PC
1. Install fastboot tools - minimal adb and fastboot
2. Download twrp image and rename it as "twrp.img", then copy it to the Minimal ADB and Fastboot folder
3. Boot the device to fastboot mode - press and hold power button and volume down button
4. Connect device to pc
5. Open command prompt from Minimal ADB and Fastboot
6. Run command " fastboot flash recovery twrp.img "
7. Twrp will be flashed immediately
8. To boot in to twrp run " fastboot boot twrp.img " or disconnect device from pc and press and hold power button and volume up button
9. Device will be booted to twrp
NOW LETS DECRY-PT DATA
*Download the data Decrypt patch Zip :- Download
*Put it in otg (pendrive) or microsd card
*Then in twrp , Go to wipe section in twrp and tap on Format data (Important )
*Do not wipe data partiton , you have to format it
*then flash the Decrypt zip from your sdcard or pendrive
*after flashing wipe caches
*then reboot , and see camera and flashlight is working and Storage in Decrypted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Join telegram group for updates
Downloads:-
1. Minimal Fastboot and Adb
2.TWRP_3.2.3.0_asus_lite_l1
3. Decrypt Patch Download
Device tree
Credits:
@Ashish Gupta1999 (me)
Tester - for testing a lot of builds time to time
if you like my work you can donate me also
Dose it support g cam portrait mode
Yes works fantastic(front cam)
Doesn't work for me. Anyone have a working root method for Asus zenfone live L1?
dexx121 said:
Doesn't work for me. Anyone have a working root method for Asus zenfone live L1?
Click to expand...
Click to collapse
Live l1 and lite l1 is a completely different devices
This TWRP actually partially works for Live L1 (ZA550KL, SD425). The problems are 1) it can't decrypt /data, 2) it fails to mount /xrom (which is inexistent on the Go variant) and 3) no ADB/MTP, but for flashing ROMs/addons, backing up and restoring, it works nicely. Just letting y'all know about it.
AndyYan said:
This TWRP actually partially works for Live L1 (ZA550KL, SD425). The problems are 1) it can't decrypt /data, 2) it fails to mount /xrom (which is inexistent on the Go variant) and 3) no ADB/MTP, but for flashing ROMs/addons, backing up and restoring, it works nicely. Just letting y'all know about it.
Click to expand...
Click to collapse
there is a specific twrp for live l1
Ashish Gupta1999 said:
there is a specific twrp for live l1
Click to expand...
Click to collapse
Can you link me to the one you know of? I just found another one from TWRP Builder, and it did fix most problems, but I still can't use decrypted data (shows "encryption unsuccessful" on boot). And it doesn't expose /vendor either which is a small letdown. <- Fixed by unpacking and editing recovery.fstab.
AndyYan said:
Can you link me to the one you know of? I just found another one from TWRP Builder, and it did fix most problems, but I still can't use decrypted data (shows "encryption unsuccessful" on boot). And it doesn't expose /vendor either which is a small letdown. <- Fixed by unpacking and editing recovery.fstab.
Click to expand...
Click to collapse
Contact me on telegram @yoursenpai1 i will provide you there
it works
Ashish Gupta1999 said:
Contact me on telegram @yoursenpai1 i will provide you there
Click to expand...
Click to collapse
Something gone wrong. System in boot loop. Able to load TWRP through PC. Tried to flash a new ROM but only 2 options (Boot & Recovery) available. Please help
Abhicr said:
Something gone wrong. System in boot loop. Able to load TWRP through PC. Tried to flash a new ROM but only 2 options (Boot & Recovery) available. Please help
Click to expand...
Click to collapse
All I know there is no rom for this device as of now , if you flash a gsi , it. Will definitely show system image option , for now flash stock rom using stock recovery to unbrick
Ashish Gupta1999 said:
All I know there is no rom for this device as of now , if you flash a gsi , it. Will definitely show system image option , for now flash stock rom using stock recovery to unbrick
Click to expand...
Click to collapse
I used a GSI to update from Oreo to Pie. But the TWRP has only 2 options (boot & Recovery) to flash the .img file. However, I did a restore & back with the old Oreo. I want to upgrade my Asus Lite 1 to Pie!! Is there any possibility to get the mobile back to the factory state including recovery? So, that I can begin from one.
Abhicr said:
I used a GSI to update from Oreo to Pie. But the TWRP has only 2 options (boot & Recovery) to flash the .img file. However, I did a restore & back with the old Oreo. I want to upgrade my Asus Lite 1 to Pie!! Is there any possibility to get the mobile back to the factory state including recovery? So, that I can begin from one.
Click to expand...
Click to collapse
Well there is a fastboot rom available in my telegram channel of lite l1 check in there
Accidentally deleted the OS and now the mobile isn't even switching on. Any solution for this? Anyway I can install an OS ?
My mobile is ASUS Zenfone Lite L1.
Are there any owners who are sitting on GSI? What is the processor architecture? I really want to get away from OneUI. Judging by the asset, AOSP is not expected soon
Release Pixel Experience 11.0 v312 · ponces/treble_build_pe
Fix Extreme Battery Saver Linux denials Sync with Phh's AOSP v312 Sync with August sources of PE
github.com
UPD: I figured out the architecture of ARM64 A. Now, as I understand it, the vendor is first flashed and only then GSI ? There are generally people who use GSI, why not make an instruction?
Anyone with any GSI?
caffezim said:
Anyone with any GSI?
Click to expand...
Click to collapse
Yes. I have many other GSI.
We have arm64 a or ab, but everyone is talking about ab. The fact is that it will not be possible to simply put it. We have a dynamic section (super). I previously worked only with Vendor and that's it. Here is a completely different situation and I am powerless. I'm just in a stupor.
This phone uses arm64 cpu and a only partiton scheme, but because this phone is android 10+ only a/b GSI working.
Im flashing GSI by using these commands in TWRP:
1. This command sets system block device in r/w mode
Code:
blockdev --setrw /dev/block/dm-0
2. Using this command im flashing raw system.img
Code:
dd if=/external_sd/system.img of=/dev/block/dm-0 bs=256M
Or this command if system image is simg
Code:
simg2img /external_sd/system.img /dev/block/dm-0
3. Wipe data.
4. Reboot to system or flash gapps.
Also because this phone has android 11 only android 11+ GSI works ,excluding google android betas they never booted for me(maybe selinux issue)
I hope TWRP devs will add support for flashing system partition inside super partition like orange fox recovery already does.
map220v said:
Im flashing GSI by using these commands in TWRP
Click to expand...
Click to collapse
But how does it work without a vendor? I don't quite understand. Have you done a full wipe or not?
Realees56 said:
But how does it work without a vendor? I don't quite understand. Have you done a full wipe or not?
Click to expand...
Click to collapse
Android 8+ devices already have vendor partition provided by OEM. This device has VNDK version 30.
Yes i did full wipe (format data) it's should format userdata partition to f2fs (if it's formats to ext4 then use stock recovery to wipe data it's also wipes metadata)
Also it's seems this TWRP doesn't format metadata, use this command to format metadata after "format data":
Code:
mke2fs -t ext4 /dev/block/by-name/metadata
map220v said:
dd if=/external_sd/system.img of=/dev/block/dm-0 bs=256M
Click to expand...
Click to collapse
nothing happens after this command
upd:
I waited a little and the process was completed, I had to wait. I tried to put gaps - 70 error. Yes, and it does not load into the system. It constantly reboots, as if the system is not there. I downloaded this (underlined) Perhaps you need to download from vndklite?
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Realees56 said:
nothing happens after this command
upd:
I waited a little and the process was completed, I had to wait. I tried to put gaps - 70 error. Yes, and it does not load into the system. It constantly reboots, as if the system is not there. I downloaded this (underlined) Perhaps you need to download from vndklite?
Spoiler
View attachment 5405433
Click to expand...
Click to collapse
I think vndklite is for android 8 devices.
Try flashing system.img using this command:
Code:
simg2img /external_sd/system.img /dev/block/dm-0
If it's flashed without errors then system.img was simg.
map220v said:
I think vndklite is for android 8 devices.
Try flashing system.img using this command:
Code:
simg2img /external_sd/system.img /dev/block/dm-0
If it's flashed without errors then system.img was simg.
Click to expand...
Click to collapse
No, it's an error right away. But the fact is that the phone writes the size of 3.3 Gb after the substitution. I'm doing Format data and reboot. But the phone is still an eternal reboot
Realees56 said:
No, it's an error right away. But the fact is that the phone writes the size of 3.3 Gb after the substitution. I'm doing Format data and reboot. But the phone is still an eternal reboot
Click to expand...
Click to collapse
I think TWRP on this device has some problems with formatting data. I used wipe data in stock recovery to make gsi boot(also i had magisk flashed)
Does anyone teach step by step how to install a gsi please?
I am also interested in step-by-step instruction.
@Realees56 @map220v did you finally managed to make it run? I am tempted to try it with instructions above and write it down if I can get any support from you guys
If I will not like it, is it possible to go back to "stock" by flashing all packages with Odin, or TWRP, or there may be some complications?
madseason.live said:
I am also interested in step-by-step instruction.
@Realees56 @map220v did you finally managed to make it run? I am tempted to try it with instructions above and write it down if I can get any support from you guys
If I will not like it, is it possible to go back to "stock" by flashing all packages with Odin, or TWRP, or there may be some complications?
Click to expand...
Click to collapse
I have not been able to launch it, I need a more advanced recovery. And what we have now does not work well with partitions
With a little bit of agony I was able to install the GSI. The speed is impressive.
But not without bugs, a lot depends on the vendor
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Pillow fan said:
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Click to expand...
Click to collapse
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
reg66 said:
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
Click to expand...
Click to collapse
I just controlled and it seems what i did while trying to flash the fastboot rom is completely wrong since i tried to flash the recovery version. I have downloaded the fastboot rom now but i will have to try to install it tomorrow
The rom was flashed succesfully this time but it still goes into the mi recovery when trying to boot. i flashed twrp to see if i could flash the rom from there and now all partitions can be mounted except for /data. When trying to decrypt it using the pin passcode it says Password Failed. is it because i also had the fingerprint and face unlock? When i still couldn't mount the other partitions I always used the pin passcode to decrypt storage. Has the passcode been changed when flashing with the mi flash tool? I don't have a recent system and data backup nor a backup of the internal storage so this issue is devastating to me, i want to save my data at all costs
EDIT: I tried reflashing twrp from fastboot and now I also can't mount the /cust partition with error "Structure needs Cleaning"
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
reg66 said:
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
Click to expand...
Click to collapse
So i have to accept that all my data is gone? No chances of decrypting the data partition? I'll wait and see if someone has something that could work, if nothing else does i guess i'll have to accept the reality. Thank you anyway
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Sauceunny said:
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Click to expand...
Click to collapse
TWRP doesn't display the "OS not installed error" and before flashing the fastboot rom version the data partition could be decrypted normally with the lockscreen passcode. Does this mean that Mi Flash encrypted the data partition with a different key?
Thank you to @reg66 and @Sauceunny , I have decide to wipe the memory of the phone as i have deemed it to be too much work to save some chats and images while the most important files are stored as a backup. I will have to plan the next update or changing rom more thorougly next time.
I have the same problem with my S21 ultra
Error on product, vendor and ODM
So i can't install stock ROM because of this error.
Doesnl anyone have an idea?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i cant mount system
i use poco f3
cant someone help me for fixed
how tp fixed..
please help
I'm facing the same errors except "Odm" I don't know what to do I tried to flash pixel experience rom in my mom's redmi note 10 using "twrp" it's just just in it. Please help me out
Download fastboot rom, use miflash to flash it (select clean all without lock) and dont play with mom's phone again. Watch a miflash tutorial on youtube if you're new to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OrangeFox Recovery
Information
Status: Beta
Version: R12.1_0
Release Date: 2021-07-12
Source Code:
https://gitlab.com/OrangeFox
https://github.com/Iscle/twrp_device_xiaomi_munch
Download:
https://github.com/Iscle/twrp_device_xiaomi_munch/releases
Installation:
https://wiki.orangefox.tech/en/guides/installing_orangefox
Documentation (FAQ):
https://wiki.orangefox.tech/en/guides
Donations:
https://opencollective.com/orangefox/donate
Source changelog:
https://wiki.orangefox.tech/changelog
Telegram channels:
News - https://t.me/OrangeFoxNEWS
Beta testing chat - https://t.me/OrangeFoxBeta
OrangeFox App:
app.orangefox.tech
Thank you very much for maintaining OrangeFox!
Since I'm new on an A/B device, I do have a question concerning installing magisk and keeping custom recovery.
As far as I understand, boot.img is modified by flashing orangefox.zip in recovery. What about magisk? Can I do a backup of the boot.img (hopefully) containing orangefox and flash back in recovery? Or is it best to use magisk addon from inside orangefox or flash magisk.apk from inside orangefox recovery?
Guide @ https://wiki.orangefox.tech/en/guides/flashing says to flash magisk once orangefox.zip is flashed an rebooted into recovery, but also, that:
One thing to note with respect to A/B devices is that, with respect to flashing ROMs, ... you must, immediately after flashing a ROM..., flash the OrangeFox zip again, then change slots, then reboot OrangeFox, before doing anything else. ...
iirc I did that and messed up the data & system_root partition or soemthing, so I reflashed stock rom and tried again. This time I just fastbooted into orangefox recovery and installed the orangefox.zip and it sticsk, flashed a custom rom (e.g. arrow or evolution or xdroid) but didn't slots and neither indstalklked magisk in any way. It works. So what about that slot changing? Better not?
Can you please hint in the right direction and if possible I'd like to understand what's going on, too.
Thanks!
Well done bro!
DidierMoulin said:
Thank you very much for maintaining OrangeFox!
Since I'm new on an A/B device, I do have a question concerning installing magisk and keeping custom recovery.
As far as I understand, boot.img is modified by flashing orangefox.zip in recovery. What about magisk? Can I do a backup of the boot.img (hopefully) containing orangefox and flash back in recovery? Or is it best to use magisk addon from inside orangefox or flash magisk.apk from inside orangefox recovery?
Guide @ https://wiki.orangefox.tech/en/guides/flashing says to flash magisk once orangefox.zip is flashed an rebooted into recovery, but also, that:
One thing to note with respect to A/B devices is that, with respect to flashing ROMs, ... you must, immediately after flashing a ROM..., flash the OrangeFox zip again, then change slots, then reboot OrangeFox, before doing anything else. ...
iirc I did that and messed up the data & system_root partition or soemthing, so I reflashed stock rom and tried again. This time I just fastbooted into orangefox recovery and installed the orangefox.zip and it sticsk, flashed a custom rom (e.g. arrow or evolution or xdroid) but didn't slots and neither indstalklked magisk in any way. It works. So what about that slot changing? Better not?
Can you please hint in the right direction and if possible I'd like to understand what's going on, too.
Thanks!
Click to expand...
Click to collapse
Well, to answer myself: when booting into recovery, just flash magisk or use orangefox magisk installer addon. It modifies the active a/ or B slot. While flashing a new rom is flashing it to the inactive A or B slot. After a reboot the newly flashed slot will become active, therefore install magisk (or any other) after reboot into recovery, when flashed new rom. But then the advice to change slot seems to be wrong :-?
Can you give me more explanation on how to flash this recovery, the guide said to flash orangefox.zip after installation but there's only the .img files
sorry double post
gandaprayoga7 said:
Can you give me more explanation on how to flash this recovery, the guide said to flash orangefox.zip after installation but there's only the .img files
Click to expand...
Click to collapse
We have A/B devices, so just move to the folder where you have that .img and use following command in console while you are in fastboot:
fastboot boot OrangeFox-Unofficial-munch.img
Click to expand...
Click to collapse
I didn't remember any "zip" file. Maybe it appeared later automatically as message to install or not.
Hi. I understood that in file manager TWRP and OrangeFox "Read-only file system". Cant move/delete/chmod files in /system_root folders. Is it problem recovery or stock android 12 ?
gandaprayoga7 said:
Can you give me more explanation on how to flash this recovery, the guide said to flash orangefox.zip after installation but there's only the .img files
Click to expand...
Click to collapse
I see your point.
Op didn't provide zip file, my way to flash it is
1. fastboot boot .img
2. find the option "Flash this recovery" in orange recovery and choose.
psklf said:
I see your point.
Op didn't provide zip file, my way to flash it is
1. fastboot boot .img
2. find the option "Flash this recovery" in orange recovery and choose.
Click to expand...
Click to collapse
thank you!!
There's or was a link to the zip file for munch on telegram via the pco f4 thread, I used that, too.