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
Related
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.
Note:
Please take full twrp backup of your phone before you proceed with the below steps
Steps to Flash GSI:
You can follow one of the two methods to flash GSI in Realme 3
Fastboot Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2a. Commands to execute in fastboot mode:
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
fastboot reboot
TWRP Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2. Copy system.img file to your sdcard.
3. Boot your phone to TWRP.
4. Press Install - > Install Image button -> Select the System.img file -> Select System Image-> Swipe to Flash
5. Format Data and then Wipe Cache, Dalvik Cache
6. Reboot, Done.
I used gsi from here (use aosp_arm64, download aosp_arm64-img.zip from artifacts tab and extract and flash system.img only):
https://ci.android.com/builds/branches/aosp-pie-gsi/grid
{
"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"
}
Incase you want to go back to stock follow the same process and flash stock system.img instead of gsi system.img
stock system image: https://www.androidfilehost.com/?fid=1395089523397966778
GSI List(use ARM64 AB or A/B images):
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
ADB Installer tool: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
what Custom rom did you user sir ?
jeffalaiza said:
what Custom rom did you user sir ?
Click to expand...
Click to collapse
AOSP
fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i flash the gsi rom in gsi list of a-only partition ?
jeffalaiza said:
can i flash the gsi rom in gsi list of a-only partition ?
Click to expand...
Click to collapse
You have to use ab gsi for realme 3 phone, but if you are downloading from ci.android.com, use aosp_arm64
fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i use this rom for daily driver that less of bugs ?
myeganz said:
can i use this rom for daily driver that less of bugs ?
Click to expand...
Click to collapse
I have not used that aosp gsi for much time, so not sure whether it is good for daily usage or not.
You can give it a try and see
What the meaning of veritydecrypt?
jeffalaiza said:
What the meaning of veritydecrypt?
Click to expand...
Click to collapse
Its a file ,link is there in the OP,
https://www.androidfilehost.com/?fid=6006931924117905745
How can i know my device use A,B, or AB ?
Link A.14 .ozip
@fawazahmed0 please link a.14 ozip file? thanks
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
Click to expand...
Click to collapse
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
After flashing any rom i lost my cellular network did not showed sim card, i tried to flash stock back, but it was same,
I tried doing fastboot erase nvdata and nvram, now it recognises sim but no network coverage. Is there something I'm missing?
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
Click to expand...
Click to collapse
android Q ba yung GSI na to bro?
(This problem is solved now, it's just for future reference)
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
fawazahmed0 said:
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
Click to expand...
Click to collapse
Is magisk root now stable?
yametekudasai said:
Is magisk root now stable?
Click to expand...
Click to collapse
yeah
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
my realme 3 1821 is only black screen .. can you tell me why?
Tấn Ho said:
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
Click to expand...
Click to collapse
I tried many GSI ROMs, but VoLTE and Fingerprint works in none of them, execept for these two, everything else seems to work, in Havoc OS atleast
When downloading a GSI, the required variant for Poco M3 is ARM64, A/B (perhaps referred to as "SAR"). Download and extract if necessary, the accepted image formats are sparse and EXT4. To install:
Code:
#Restart on bootloader fastboot
adb reboot bootloader
#Install the vbmeta image provided by Google to disable AVB and allow GSIs to boot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
#Format userdata to avoid possible encryption problems. Back up your files first
fastboot -w
#Restart on recovery (userspace) fastbootd
fastboot reboot fastboot
#Install GSI
fastboot flash system system.img
#Finally restart on it
fastboot reboot
Downloads:
Google vbmeta: image
Updated adb and fastboot: Windows | Linux | Mac
Tested GSIs and issues:
(will be edited later)
I have tested some GSIs. Here are some bugs.
- (happens to almost all variants) Google voice typing / Google Assistant are not functioning. Seems like the microphone does not pick up our voice. I have tried chaning permision, clearing data etc but to no avail.
- (happens to Caos 11 and some modded AOSP 11) The device will be listed as uncertified trebble device, so I cannot install Google apps nor login with Google account.
That's all for now.
hi guys can you help me,
i tried to instal gsi but the files size too big so i decided to restore but apprantly my sd card formated to by mistake,
then now i tried to flash eu rom and this happen anything i can do to fix this ? thanks
{
"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"
}
gasleak08 said:
hi guys can you help me,
i tried to instal gsi but the files size too big so i decided to restore but apprantly my sd card formated to by mistake,
then now i tried to flash eu rom and this happen anything i can do to fix this ? thanks
View attachment 5215101
Click to expand...
Click to collapse
Have you tried to install the stock ROM?
KaMyKaSii said:
Have you tried to install the stock ROM?
Click to expand...
Click to collapse
not working, when i do this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that cannot flash any,
sad news i got my phone bricked
gasleak08 said:
not working, when i do this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that cannot flash any,
sad news i got my phone bricked
Click to expand...
Click to collapse
What commands do you use to flash the GSI?
KaMyKaSii said:
What commands do you use to flash the GSI?
Click to expand...
Click to collapse
i ff the steps then
fastboot flash system (gsi i downloaded).img
but before that when i do this
#Format userdata to avoid possible encryption problems. Back up your files first
i also wipe dalvik and cache
gasleak08 said:
i ff the steps then
fastboot flash system (gsi i downloaded).img
but before that when i do this
#Format userdata to avoid possible encryption problems. Back up your files first
i also wipe dalvik and cache
Click to expand...
Click to collapse
Let's talk in private, I think it's better than flood the topic. Try installing xiaomi.eu again and then copy the /tmp/recovery.log and send it to me. And your device is not completely dead, at most reflashing the super partition will solve this
KaMyKaSii said:
Let's talk in private, I think it's better than flood the topic. Try installing xiaomi.eu again and then copy the /tmp/recovery.log and send it to me. And your device is not completely dead, at most reflashing the super partition will solve this
Click to expand...
Click to collapse
i dunno if i still can do that, last night my phone automatically turned off and i cannot turn it on. can you still help
gasleak08 said:
i dunno if i still can do that, last night my phone automatically turned off and i cannot turn it on. can you still help
Click to expand...
Click to collapse
Can't you get into fastboot anymore? Power + volume down
KaMyKaSii said:
Can't you get into fastboot anymore? Power + volume down
Click to expand...
Click to collapse
yes i can not get to onto fastboot, but my pc can still recognize my phone.
Did you try with XiaoMiTool V2 ?
Noru29 said:
Did you try with XiaoMiTool V2 ?
Click to expand...
Click to collapse
my phone wont boot to fastboot
deleted
KaMyKaSii said:
Tested GSIs and issues:
(will be edited later)
Click to expand...
Click to collapse
Any updates on GSI's you've tested?
Rama Himura said:
I have tested some GSIs. Here are some bugs.
- (happens to almost all variants) Google voice typing / Google Assistant are not functioning. Seems like the microphone does not pick up our voice. I have tried chaning permision, clearing data etc but to no avail.
- (happens to Caos 11 and some modded AOSP 11) The device will be listed as uncertified trebble device, so I cannot install Google apps nor login with Google account.
That's all for now.
Click to expand...
Click to collapse
Did you test AOSP 10 GSI not AOSP 11? If there are not many bugs on AOSP 10 GSI, I would like to try it.
When will be custom ROM awailable ?
sparrow1121 said:
When will be custom ROM awailable ?
Click to expand...
Click to collapse
February 29th
Hello, has someone tested AOSP 11 GSI? Could someone tell about his experience? Thanks.
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.
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.