Develop Bugs

Help! Sensors turned off!

Hello everyone. I was with Android 7 on my ZS570KL and returned to 6 for a tutorial found on the internet and worked, but all the sensors of the device were disabled (screen rotation, gyroscope, approximation, fingerprint [only registers up to 93% and gives error], and all the others). How do I reactivate? I came back to Android 7, formatted the device several times, and nothing solves!

What tutorial and why?
No information = no help

{
"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 do not remember where I found the tutorial and the files, but the process is this:
1. Download http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-4.12.40.1698-user.zip
2. Download https://mega.nz/#!tp9DSQ4b!3wdDLsh3BBtPju8G74xlDjLJ9QywFaoLs1T11mMt3QQ
3. Unzip FlashTools64_20161125.zip
4. Unzip UL-Z016-WW-4.12.40.1698-user.zip and move out files under firmware-update to FlashTools folder
5. Put downgrade.bat, boot.img, recovery.img to FlashTools folder
6. Reboot phone to bootloader and click downgrade.bat
The reason was to swap the conventional root SU through the Magisk. I tried to reinstall 7 just by replacing the original recovery available here in XDA, but the process was not going to restart, so I followed that one to try to return and reinstall everything. It worked, I got back to 6, but I did not know everything. It looks like a computer without the drivers installed.

I'd downgrade again, if it was me, this time I'd install a stock Rom (MM) from ASUS. Then test everything again. If everything is good to go then I'd root and upgrade.
Changing the OS in the middle doesn't help if you have a problem.
Especially if it just builds upon the foundations of the previous OS...
Did you flash a complete N rom or do an update?

The ROMs I try are exactly those of the Asus site. I tried the downgrade again to version 4.12.40.1698 and realized something when I flash in recovery mode. The following error messages appear:
Unmount of /firmware failed: no such volume
Mount: failed to mount /dev/block/bootdevice/by-name/mdtp at /firmware: No such file or directory
Unmount of /firmware failed, no such volume
What is it? How to solve?

I need the original kernel and recovery of the latest firmware released, can anyone make it available?

AndreSantoro84 said:
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
Click to expand...
Click to collapse
These recovery images are from nenebear59, thanks to him !
Z016-WW-5.14.44.2212_recovery :
For 2.15GHz CPU
For 2.4GHz CPU

Thank you very much! Now I need the "persist.img" file, of the same rom, can you make it available? I thank you!

I downloaded the source code kernel from the Asus site, and the compressed file has a sensor folder. I downloaded the kernel zip file to my memory card and tried to install via recovery, however the following message appears: E: footer is wrong / E: signature verification failed. How do I get install by recovery or via flash in cmd?

I followed this tutorial (https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061) and managed to recover the fingerprint reader, but the others are still turned off. I really need the correct file! Somebody help me, please!

I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!

Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!

equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Really??

Ryder. said:
Really??
Click to expand...
Click to collapse
sorry from nougat to marshmallow

There isn't android lollipop for the asus zenfone 3 series. They came out with marshmallow.

AndreSantoro84 said:
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Click to expand...
Click to collapse
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build

equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Come on. To downgrade, you need to download the official rom from the Asus website (version WW-4.12.40.1698 - do not forget to check if your device is 2.15 or 2.4 ghz). Downloaded, need to put the rom inside a micro sd card (can not be internal storage, need to be in sd). In addition, it must be with the original recovery (the version is indifferent), if it is in TWRP it will not work. Once you have done this, you will have access to recovery mode, go to the "install zip from sd card" option, locate the zip file of the rom and install it, and just wait. Having problems, report here.

cazadormoron said:
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
Click to expand...
Click to collapse
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.

Solved!
AndreSantoro84 said:
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Click to expand...
Click to collapse
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!

cazadormoron said:
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
Click to expand...
Click to collapse
If you want to root, flash the twrp and then supersu zip from twrp

Mi A2 lite suddenly damaged???

Hello,
I have a very big problem which i'm not able to solve. So here is my story (i have already tried a lot). First of all, my device worked fine for the first month.
First I installed several gsis. At first I didn't know how to do it but now i know. So I flashed my device a lot…
Then, I installed a gsi and wanted to install gapps. Because of the fact, that twrp isn't really able to install zips yet I tried to unpack the zip and run the sh script with root and fx file explorer.
After that the whole s*** began.
My device freezes so I needed to force a reboot. But then it didn't boot anymore. So I flashed the stock rom again with MiFlash.
After a reboot the device freezes at Bootanimation and reboots. the second boot it reboots correctly and the start screen with "Hi there" pops up. But after a few clicks my device freezes again and reboots again.
After that I decided to install a GSI with Android 9 which worked before this Problem without ones. But same issue here: freezes and reboots.
I thought it is an emmc Problem so I tried something and the Phone was completely Bricked. Only EDL mode worked. Flashing back to stock rom with Miflash wasn't possible in edl mode. Idon't know why. So I decided to download qualcomm's flash tool and reflash the whole emmc in edl mode (nothing else was possible). After flash was completed and the phone rebooted successfully I put it into fastboot and flashed the normal images (stock os) again. Now Miflash worked again.
BUT:
The same problem described before happens again and again:
First boot after flashing stock: reboot in Boot Animation
Second boot: Boot to welcome screen, after around 10 seconds phone freezes and reboots
Following boots are same as second boot.
Can anyone please help me?

That doesn't sound good.. have you tried factory reset in recovery? I would try that after a fresh install with miflash.
Hope you get it sorted

Thank for the reply,
I also did an factory reset.
I have news (I think that they are not really good):
I installed PHH's AOSP 8.1 GSI without gapps to prevent the whole setup stuff.
Now I can use the phone for around ten seconds.
Here is everything I noticed:
Wifi not working -> freeze and reboot if I want to activate it
BT not working -> same here (freeze and reboot if I want to activate it)
Camera not working -> also same
Seems like all devices won't work.
Some other advices?
Edit: after reflashing vendor.img problem is still there.

Ok, now I have another problem:
I cannot enter edl mode again.
How can I do that?
Bootloader is locked and i cannot unlock anymore
it just sys:
Code:
FAILED (remote: oem unlock is not allowed)
and entering edl over fastboot also does not work. I only get:
Code:
FAILED (remote: device is locked! no edl)
But i cannot unlock the bootloader.
Is there an other way to enter EDL Mode?
EDIT:
Ok I think the only way to enter edl mode is to open the device and short the two test points.
I will write if I have news.

Seems like there are other Posts with different problems at the beginning which are now facing the same problem as we do, after some flashing:
https://forum.xda-developers.com/mi-a2-lite/how-to/xiaomi-mi-a2-lite-hard-brick-t3861576
https://forum.xda-developers.com/mi-a2-lite/help/destroyed-t3860080

TJ1999 said:
Hello,
I have a very big problem which i'm not able to solve. So here is my story (i have already tried a lot). First of all, my device worked fine for the first month.
First I installed several gsis. At first I didn't know how to do it but now i know. So I flashed my device a lot…
Then, I installed a gsi and wanted to install gapps. Because of the fact, that twrp isn't really able to install zips yet I tried to unpack the zip and run the sh script with root and fx file explorer.
After that the whole s*** began.
My device freezes so I needed to force a reboot. But then it didn't boot anymore. So I flashed the stock rom again with MiFlash.
After a reboot the device freezes at Bootanimation and reboots. the second boot it reboots correctly and the start screen with "Hi there" pops up. But after a few clicks my device freezes again and reboots again.
After that I decided to install a GSI with Android 9 which worked before this Problem without ones. But same issue here: freezes and reboots.
I thought it is an emmc Problem so I tried something and the Phone was completely Bricked. Only EDL mode worked. Flashing back to stock rom with Miflash wasn't possible in edl mode. Idon't know why. So I decided to download qualcomm's flash tool and reflash the whole emmc in edl mode (nothing else was possible). After flash was completed and the phone rebooted successfully I put it into fastboot and flashed the normal images (stock os) again. Now Miflash worked again.
BUT:
The same problem described before happens again and again:
First boot after flashing stock: reboot in Boot Animation
Second boot: Boot to welcome screen, after around 10 seconds phone freezes and reboots
Following boots are same as second boot.
Can anyone please help me?
Click to expand...
Click to collapse
Hello, the solution is VERY simple, however it requires a certain knowledge of mobile maintenance (I believe that almost everyone has knowledge in opening and storing certain things in a mobile device) go for me ...
Download the latest version of MiFlashTool, and download the V9.6.4.0.ODLMIFF version, open the device, and with CAUTION place a tweezers or something like this in the image and place the USB cable in the phone after the procedure. pin the device and put the USB cable, click Refresh, and the device will appear in EDL mode, flash the system and in 5 minutes the system opens, worked for me !!
But proceed with care, I do not take responsibility for people without knowledge of disassembling of devices to cause some damage in the own device.
{
"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"
}

OK I was able to enter edl mode with the testpoint Methode.
I erased the whole flash storage with QFIL from Qualcomm and also reflashed the emmc.
But it did not work.
After that I entered edl mode again and tried to flash via miflash. ( I also downloaded the New Version available now from the miui site).
BUT:
Linke it was with QFIL, after exit edl mode the phone tries to Boot, but it get stuck in bootanimation. It seems Like it boots to infinity. No Matter what I do. I also tried to change partition with fastboot set active x.
BUT Still No Success

no ideas?

Redmi note 8 wipe all partitions since twrp got bricked

Bien...
I was trying to flash the EU rom on my Redmi Note 8, but I did wype to all the partitions, until that moment I had informed myself about how to flash, how to root and use twrp, but the issue of the partitions still did not know, I selected all the partitions except data and sd and I did wype, in the end my cell phone was completely bricked, I try to turn it on and for a period of less than half a second, I get the Redmi logo, below it says Powred by Android and above I get a padlock open indicating that the bootloader is unlocked, then I get a screen with the message "System has been destroyed" and then it turns off, unless I put it to load, in that case it enters the bootloop state, I cannot enter the recovery but yes I can enter fastboot, I tried to flash it through My Flash Tool and ADB, the problem is that the computer recognizes that the bootloader is unlocked, but when flashing it, a message appears that the bootloader It is locked, so flashing it is not an option, for that reason, I assume that the testpoint method for flashing by EDL would not work either.
That happened three weeks ago, at first I did not know the reason for the problem, later I learned more, I will not make that mistake again, but I am interested in knowing if there is a software solution; I would be interested in being able to download all the partitions and install them on my cell phone using the computer, I don't know if any of those who read this have the opportunity to find the partitions and share them here, I don't know if it is a realistic option, but I have hope, I saw that That solution worked with a OnePlus 3 and that's why I'm looking for information about my cell phone. The only other option I can think of is to change the motherboard, but it's very expensive and with that money, I'd better buy another cell phone.
By the way, my cell phone was in very good condition despite having used it for a year, it was very well cared for and I had no problems with both software and hardware, the reason why I was trying to change to the EU rom is because the Global version was to be a decaf version of the update.
I hope that someone can help to find a solution. Thanks for your understanding.

Diego_Arturo said:
Bien...
I was trying to flash the EU ...
Click to expand...
Click to collapse
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended

loopypalm said:
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
Click to expand...
Click to collapse
I understand what you are saying, the problem is that I deleted all the partitions (/ boot, / system, / misk, and several others that I do not remember), the only ones that I did not delete were sd and data. I read that if you delete the boot partition, you should not restart the cell phone, you must flash a rom with the boot partition, if you don't, the cell phone will not start the operating system
Another thing: I didn't flash any ROMs, twrp didn't read my storage well and couldn't find the .zip file of the EU rom, I just wipe and reboot without flashing anything. I do not know why the cell phone still detects the system for a very brief moment before showing that the system has been destroyed, the problem is that it does not start. And when I try to flash the original ROM, the computer detects that the bootloader is unlocked, but when flashing I get an error saying that it is locked, it occurs to me that possibly the bootloader was one of the first things to be erased, but it was not completely erased Maybe the kernel or ramdisk was deleted and after that everything stopped and the cell phone just bricked, I don't know if I'm correct.

Diego_Arturo said:
I understand what you say, the problem is that I did wipe to all partitions, (/ boot, / system, / recovery, / cache, / misc and several others that I do not remember), I just did not wipe to SD and data partitions. I understand that if you delete the boot partition you must have a ROM ready that comes with a boot partition, or else you would be left with a hardbrick. What I don't know is if I can force the installation of all partitions.
Click to expand...
Click to collapse
-how did you wipe recovery ? did you use flashtool or something ?
-all roms now comes with boot img (boot partition is where the kernel files are stored) , so no problem wiping it (same for dalvik/cache/system/vendor/data)
yes, you can flash img files of partitions using fastboot (if that what you mean with force install a partition)
-what you should try now is reinstalling twrp 1st

nteresting ... It reassures me to know that I don't need to search for the partitions separately and only need to flash the ROM, although I am concerned about the same problem when flashing. I tried to flash using Mi Flash Tool, ADB and XiaoMi Tool V2, but it is always the same problem, it detects the unlocked bootloader, but when flashing it gives me an error.
I deleted all the partitions from TWRP, it was weird, because the videos didn't show many of the partitions that came out for me, that's why I don't remember them. Before doing wipe I made a copy of everything in case something went wrong, but in the end everything went wrong ...
Now that I remember, I deleted the partitions because when I tried to do anything, I got red letters and TWRP wouldn't let me do anything, when I deleted them the letters turned blue.
It seems to me that I tried to install TWRP from XiaoMi Tool v2 although I don't remember correctly, I will try and write again.

I HAVE ADVANCES!
I flashed the partitions one by one because Flash Tool still does not let me flash the ROM, on one occasion I flashed the system, but in the end it did not finish flashing, I still got the error "System has ben destroyed", I kept flashing partitions but there was no Result, in the end I flashed the system again and when it finished flashing, the error system has ben destroyed no longer appeared, now my cell phone is in a permanent bootloop state with the redmi logo, but it already lets me enter TWRP, I can't flash it from the computer, I'm going to try to get an SD card and flash it from recovery, I'm going to try to flash the EU ROM, but it's already a breakthrough, I don't have a hard brick anymore.

Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
I thank you very much for helping me find a solution, I hope this helps someone else and this serves me as my experience, I managed to solve a serious problem that I made and you helped me ... Thank you very much.

Diego_Arturo said:
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
Click to expand...
Click to collapse
Glad it work for you ^........^ !
all sensors are working fine ?
Diego_Arturo said:
Thank you very much.
Click to expand...
Click to collapse
you know what to do
{
"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"
}

For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.

Diego_Arturo said:
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Click to expand...
Click to collapse
Miui roms are resource hungry and lag is not their only problem , battery and performance are also affected ...
i think you should try custom roms

First, I didn't want to, I preferred to wait, but seeing how slow the cell phone was and how fast the battery was draining, I felt that the best in the long run would be to install a ROM that did not consume so many resources, so I installed the latest version of Pixel Experience. I have to say that I did not expect anything from this ROM, I just expected fluidity and more battery, but in the end I liked it. I personally like MIUI, but I think that Pixel Experience could extend the life of my cell phone. I will continue using it and possibly in the future I will return to MIUI to see how it goes.

Question [URGENT] Failed to mount '/system_ext' '/product' '/vendor' '/odm' (Invalid argument)

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.

Question Red Warning and UnWorking Lockscreen. HELP

{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)

Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...

redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?

Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely

i have this error also what should i do?
the phone not boot up
the red warning are stuck

yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.

[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!

yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.

[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!

turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"

izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.