Guys, there is a VERY good (and very bad, but about it in the end) news, at my request, one good forumchanin under the nickname yurxxl from 4PDA, collected on TWRP for Poco M4 Pro 5G
Decryption / data works, connection to the computer, I installed magisk through it.
**********************
Installation:
in fastboot mode with the command:
fastboot flash boot twrp.img
<><><><><><><><><><><
And now the bad news:I put the Taiwanese firmware on myself in the morning,and first tested the recovery on it,yes,the recovery is put on it,and everything also works,there are no questions to the recovery,BUT I flashed the magisk,rebooted the system,updated the magisk from the application,the program wrote about the need to reboot,the reboot went,but then the system did not boot,and even deleting the adb folder (where the magisk is placed),nor the twrp firmware (which is the boot, if anyone did not know) did not help again,I was able to boot into the system only by making format data. Then I put back the global firmware, and everything is fine on it, magisk works fine.
——————————————————
Well, I will add more, yesterday, after all these installations of gsi firmware, and flashing the drain, this inscription dm-verity corruption appeared on my logo your device is corrupt. it can't be trusted and my not work properly. press enter button to continue. Or, device will power off in 5s. Since the firmware via fastboot is buggy for me, I flash through F.T. Sewed in download mode.Then I decided to still try to flash in firmware upgrade mode, since in this mode the firmware formats the memory, and after the firmware the inscription disappeared. Yes, also, in this mode, the bootloader is blocked, I first flashed the Taiwanese firmware, and through MiUnlock, without waiting, unlocked the bootloader.And when a jamb with a magisk appeared on it, I flashed it to the global one, again through firmware upgrade, respectively, I blocked the bootloader again, but I unblocked it right after. Maybe someone will need it.I updated the recovery, now the smartphone is visible in them by the computer when connected in fastbootd mode, which facilitates the installation of gsi firmware.
Yes, the recovery is already patched in magisk
Spoiler: screenshots
{
"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"
}
Guys, I forgot to add, I have Poco, so the recovery was tested on this modification, on two firmware versions, Global and Taiwan. I do not know if it will work for Redmi.I've disassembled the boot from the firmware for India, there is another core used. And yet, I see they have already downloaded 5 times, they could have written how everything went, it became normal
Hello,
I've tried your twrp, but some partitions are unavailable. By the way, why to flash in boot and not in recovery?
stratonz said:
Hello,
I've tried your twrp, but some partitions are unavailable. By the way, why to flash in boot and not in recovery?
Click to expand...
Click to collapse
Because we do not have a separate recovery, it is located in the boot, so it is practically a stock boot, with a recovery added to it. Which sections are unavailable?
arraki said:
Because we do not have a separate recovery, it is located in the boot, so it is practically a stock boot, with a recovery added to it. Which sections are unavailable?
Click to expand...
Click to collapse
I can't remember now, cos' I have uninstalled twrp and restore original firmware, but it seems to me that was impossible to install GSI in system. A question: have I to install twrp in both the boot partition?
ah, maybe I've tried to do a nandroid backup and in the partition list there wasn't system
stratonz said:
to install GSI in system.
Click to expand...
Click to collapse
For the gsi firmware, it is necessary that the recovery supports this function, few recoveries are able to do this. Backup should be done of the super partition, for normal recovery it is enough to make a backup of two partitions:data and super, I checked. And gsi are normally put through fastbootD. Here I put it on trial
Spoiler: GSI
Thanks, I reinstall twrp, it works, but during backup process createTarFork ended with error code 255, seems dued to (from log):
failed to lookup fscrypt tar policy for '/data/extm' - 'a0e08c6d2252b15091f8e5807863eaa1'
....
I:Error adding file '/data/extm/I581aDAAAAQh4qwuBNkwvrSSE3fUn6RD' to '/data/media/0/TWRP/BACKUPS/CQX899S4BQ8TQWAU/2022-03-04--07-06-12_CUST_evergreen/data.f2fs.win011'
any suggestions? googling, this extm folder seems to be a common problem...
stratonz said:
Thanks, I reinstall twrp, it works, but during backup process createTarFork ended with error code 255, seems dued to (from log):
failed to lookup fscrypt tar policy for '/data/extm' - 'a0e08c6d2252b15091f8e5807863eaa1'
....
I:Error adding file '/data/extm/I581aDAAAAQh4qwuBNkwvrSSE3fUn6RD' to '/data/media/0/TWRP/BACKUPS/CQX899S4BQ8TQWAU/2022-03-04--07-06-12_CUST_evergreen/data.f2fs.win011'
any suggestions? googling, this extm folder seems to be a common problem...
Click to expand...
Click to collapse
Strange, I did a backup data, everything went fine.Although, I didn't do a backup in twrp, I still have a recovery Orange Fox, I did a backup to them, I'll check in twrp later And I've seen this error before on another smartphone, you just need to delete this folder, and everything will be fine.
arraki said:
Strange, I did a backup data, everything went fine.Although, I didn't do a backup in twrp, I still have a recovery Orange Fox, I did a backup to them, I'll check in twrp later And I've seen this error before on another smartphone, you just need to delete this folder, and everything will be fine.
Click to expand...
Click to collapse
Excuse me, have you also a orange fox recovery working on poco m4 pro 5g/redmi etc etc?
stratonz said:
Excuse me, have you also a orange fox recovery working on poco m4 pro 5g/redmi etc etc?
Click to expand...
Click to collapse
Yes, but I also don't know if it will work on Redmi, it works well on Poco, but I really didn't check everything.
I have Poco (evergreen) could I test it?
Just another question: flashing twrp I lost root (magisk). To restore root I have to install magisk from inside twrp, with "install zip"?
stratonz said:
Just another question: flashing twrp I lost root (magisk). To restore root I have to install magisk from inside twrp, with "install zip"?
Click to expand...
Click to collapse
Ok! Done as described and it works
Regarding the TWRP I posted (and orange Fox, which will be below), the MTP works in them, but there is no connection to the computer in fastbootd, the computer does not even react.I wrote about this to the author, I hope he will fix it. Also, when creating a backup /data in twrp, the process ends with an error, the extm folder is to blame for everything.I've seen this error before, on other smartphones, you just need to delete this folder, it won't be a big deal.But there is no such mistake in Orange Fox.
arraki said:
Regarding the TWRP I posted (and orange Fox, which will be below), the MTP works in them, but there is no connection to the computer in fastbootd, the computer does not even react.I wrote about this to the author, I hope he will fix it. Also, when creating a backup /data in twrp, the process ends with an error, the extm folder is to blame for everything.I've seen this error before, on other smartphones, you just need to delete this folder, it won't be a big deal.But there is no such mistake in Orange Fox.
Click to expand...
Click to collapse
Thanks for OF and for working on recoveries!
Twrp available for Note 11T (Evergo) is useless. It can't flash magisk or Gapps. Tested by some users in Telegram, and they failed.
So can anybody help how to flash GApps into Note 11T (evergo) with TWRP?
I mean flashing China MIUI ROM and Flash GApps into that with TWRP.
When i tried to install using "fastboot flash boot OF_boot.img" it gives error
FAILED (remote: This partition doesn't exist)
I also tried "fastboot boot OF_boot.img" then it gives this error
downloading 'boot.img'...
OKAY [ 3.720s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.552s
Please guide me @arraki
Update : It worked , i tried using latest platform tools then it does not give any errors!
Thank you very much for creating this recovery file @arraki
Anmol98 said:
When i tried to install using "fastboot flash boot OF_boot.img" it gives error
FAILED (remote: This partition doesn't exist)
I also tried "fastboot boot OF_boot.img" then it gives this error
downloading 'boot.img'...
OKAY [ 3.720s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.552s
Please guide me @arraki
Click to expand...
Click to collapse
Is your bootloader unlocked?
arraki said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
it is working now , after i used latest platform tools !
Thanks...
Related
Hi everyone, I just bought a P9, nice and shiny I love it. I easily unlock bootloader and I wanted to root but I had some issues with TWRP and ... I deleted System by mistake.
Now I'm tying to repair it without success. I tried with HiSuite, but it says that the phone is not supported. Any ideas ?
thanks
Restore the stock recovery and then you can do a factory reset.
tnhh said:
Restore the stock recovery and then you can do a factory reset.
Click to expand...
Click to collapse
That I tried. I just end up with the big red "!" in the circle. It seems that there's is nothing to reset. Like no system
Any other ideas ? Is there a way to flash a full firmware ? I couldn't find The P9 firmware
for the same mistake i supported another user in a german android forum yesterday.
what model do you have? EVA-09 (single sim) or EVA-19 (dual sim) or any other chinese variant?
if you have EVA-09 you could try my TWRP backup and restore the partitions you deleted.
https://drive.google.com/open?id=0B9gJ44ME0ZkcWFlNdXZKdjdfZmc
paratox said:
for the same mistake i supported another user in a german android forum yesterday.
what model do you have? EVA-09 (single sim) or EVA-19 (dual sim) or any other chinese variant?
if you have EVA-09 you could try my TWRP backup and restore the partitions you deleted.
Click to expand...
Click to collapse
Thank I try that and I get back to you :good:
It seemed to work at first, but i'm in the BootLoop. I wiped dalvik and cache on TWRP and even did a factory reset on stock. I need help getting out of the loop. System seems to be restored anyway. Thank you again for your solutions
tricknaah said:
It seemed to work at first, but i'm in the BootLoop. I wiped dalvik and cache on TWRP and even did a factory reset on stock. I need help getting out of the loop. System seems to be restored anyway. Thank you again for your solutions
Click to expand...
Click to collapse
what model variant do you have? maybe also try to restore the cust partition, but only if you have the EVA-L09.
if i remember correctly the boot.img from my backup is already superSU patched. try to flash superSU 2.65 after restoring the backup. maybe the bootloop is because half installed superSU.
I get a message in log "unable to locate partition by backup name 'cust'
What I did:
1) Restored the backup in TWRP (system + boot)
2) flashed superSU 2.65
3) Wiped Dalvik + cache
4) Wiped Data
5) Reboot
But I'm still stuck in bootlop.
@paratox, I found the german forum, it was a pretty fast success. I'm maybe doing something wrong here.
And Yes I'm on EVA-L09 too
tricknaah said:
I get a message in log "unable to locate partition by backup name 'cust'
What I did:
1) Restored the backup in TWRP (system + boot)
2) flashed superSU 2.65
3) Wiped Dalvik + cache
4) Wiped Data
5) Reboot
But I'm still stuck in bootlop.
@paratox, I found the german forum, it was a pretty fast success. I'm maybe doing something wrong here.
And Yes I'm on EVA-L09 too
Click to expand...
Click to collapse
do you use paulobriens (modaco) TWRP? the other one i think does not support cust partition.
i would try:
1. paulobriens twrp -> restore boot and system
2. flash superSU
3. reboot
4. if bootloop boot into bootloader
5. flash stock recovery
6. boot into stock recovery and do a factory reset
Can You share the twrp recovery img you used ?? paulobriens (modaco) TWRP I found on his website is a test and does not start on my phone after successful flash
this is strange, it should boot. on my EVA-L09 C900 it is working.
maybe do a "fastboot erase cache" before and after twrp fastboot flash. then switch the phone off, remove usb cable and boot into recovery.
paratox said:
this is strange, it should boot. on my EVA-L09 C900 it is working.
maybe do a "fastboot erase cache" before and after twrp fastboot flash. then switch the phone off, remove usb cable and boot into recovery.
Click to expand...
Click to collapse
can you share your recovery img ? "fastboot erase cache" produce a command not allowed. :crying:
{
"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 used both recoveries from this site and both are working on mine.
redownload the modaco one, unzip it and flash it again.
or use the other one and try what i wrote.
paratox said:
i used both recoveries from this site and both are working on mine.
redownload the modaco one, unzip it and flash it again.
or use the other one and try what i wrote.
Click to expand...
Click to collapse
Alright, I try that again
@paratox I tried again. The second TWRP is not working and put me in loop, even though it installs.
I was able to perform the factory reset, but bootloop again. I'm a bit desperate. I've owned multiple devices until this P9, I've never been in that situation. aweful !!
I hope someone bring me a solution. I really like the phone :s
you get a bootloop when trying to boot into recovery?
you have to boot into recovery without usb attached. hold power and vol- until the bootloader warning (yellow font, not as many options like normal booting) appears then release the both buttons. then wait until twrp appears.
Thank you @paratox I finally got it !! You help a lot on this one, and another great help as well I thank him too. :highfive:I won't forget to back up next time. I'll take some time to write about what I did in case someone else find itself in trouble with all this. I guess it might be useful .
Thank you guys !! Long day, I need to sleep:laugh::laugh::laugh::laugh::laugh:
@tricknaah: how to fix it?
I have the same problem with modaco recovery bootloop
freak3000 said:
@tricknaah: how to fix it?
I have the same problem with modaco recovery bootloop
Click to expand...
Click to collapse
Hi,
1) flashed TWRP 3.0.0, the other one wasn't working
2) Wiped everything, cache, data, Dalvik, and even System
3) I was provided a link for EVA-L19_C185B130_Middle_East_Region_Android_6.0_EMUI_4.1
3) extracted system.img, boot.img, cust.img and even userdata that I flashed everything (fastboot) with Huawei Extractor
4) After reboot, I got the update circle I guess , and It just fired up Like WOW, better than the first time
I'm not sure all that was neccessary, but yeah It actually worked
I hope it helps! :highfive:
paratox said:
for the same mistake i supported another user in a german android forum yesterday.
what model do you have? EVA-09 (single sim) or EVA-19 (dual sim) or any other chinese variant?
if you have EVA-09 you could try my TWRP backup and restore the partitions you deleted.
https://drive.google.com/open?id=0B9gJ44ME0ZkcWFlNdXZKdjdfZmc
Click to expand...
Click to collapse
Hi, I have the same problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program hauuk user https://forum.xda-developers.com/p9-plus/development/huawei-p9-p9-plus-firmware-updater-t3435878 I used several options inside the L09 option in the middle Of the installation gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
DEPRECATED because I don't have the watch anymore. Might still work, might also not. Feel free to just try and iterate on my work.
TWRP touch recovery
{
"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"
}
This is TWRP touch recovery for the Asus Zenwatch 3.
Usual disclaimer:
Code:
[I] I take no responsibility for any issues to your watch, your house, your job, your kitten, blah blah.[/I]
DON'T ALLOW TWRP TO MODIFY /SYSTEM IF YOU DIDN'T DISABLE DM-CRYPT! Recovery will then get overwritten on every boot though.
INSTRUCTIONS
It's recommended to boot it via "fastboot boot twrp_swift_*.img".
To flash, use the default "fastboot flash recovery twrp_swift_*.img". To boot into recovery, use adb or hold center and bottom button when off. Everything is tested to work fine.
If you want to return to stock recovery, flash recovery image from here.[/SIZE]
DOWNLOAD
3.1.1-0: View attachment twrp_swift_3.1.1-0.img
3.1.0-0: View attachment recovery_swift-3.1.0-0.img
3.0.2-0: View attachment recovery.img
SOURCES
Device/board config
Recommended platform manifest
Thanks a lot to @joeykrim and @T10NAZ, I used their Zenwatch 2 thread as a guide to compile the kernel and recovery.
This is interesting to see, I don't own a ZenWatch 3, but I'm curious how this would work. Would it be possible to flash custom ROMs on a watch? Maybe even port over Android 2.0 for the ZenWatch 3? Just curious how this would work on a watch.
To see something like this on a watch I must say you guys and everyone involved are truly awesome
Thank you!
I flashed a SuperSU zip file and the flash process worked well. Still root is not working because the SuperSU app crashes everytime something needs root rights...
g4rb4g3 said:
Thank you!
I flashed a SuperSU zip file and the flash process worked well. Still root is not working because the SuperSU app crashes everytime something needs root rights...
Click to expand...
Click to collapse
Which SuperSU.zip did you flash? Remember not every SuperSU.zip are compatible with Android wear. I am a bit out of time ..will try to play with root in my kernel.
janjan said:
Which SuperSU.zip did you flash? Remember not every SuperSU.zip are compatible with Android wear. I am a bit out of time ..will try to play with root in my kernel.
Click to expand...
Click to collapse
Nevermind, I got it working now using this tutorial: https://forum.xda-developers.com/ap...t-squashfs-t3319097/post65428079#post65428079
g4rb4g3 said:
Nevermind, I got it working now using this tutorial: https://forum.xda-developers.com/ap...t-squashfs-t3319097/post65428079#post65428079
Click to expand...
Click to collapse
Did you flash the recovery or also only boot it?
Maxr1998 said:
Did you flash the recovery or also only boot it?
Click to expand...
Click to collapse
Sorry for the late response, I didn`t flash it I just booted it. But I`ve sent the watch back and got a Gear S3 instead now.
g4rb4g3 said:
Sorry for the late response, I didn`t flash it I just booted it. But I`ve sent the watch back and got a Gear S3 instead now.
Click to expand...
Click to collapse
No prob, I already tested myself and flashing worked fine.
Thanks, can't wait to see other development stuff to follow too. Anybody tried to root through the recovery ?
I just updated the recovery to TWRP 3.1.0, grab the image from OP.
Latest TWRP installed and working fine. Thank you!
wokrs well!
Thank you
Now running :
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340
I added TWRP 3.1.1-0 to the OP, built on latest Nougat kernel from git and with latest TWRP sources in 7.1 tree. Enjoy!
is there an repair option for the partitions like there is in a stock TWRP? I do not see it. I am having some issues with my watch, one of which is that I am unable to mount /data, which is normally fixed with the repair option under the advanced wipe menu, but I do not see that option here. Please help.
Here is a link to the full issues I am experiencing.
https://www.reddit.com/r/zenwatch/comments/7de8ax/help_unbricking_zenwatch_3/
re: flashing roms in twrp
Coltonbyu said:
is there an repair option for the partitions like there is in a stock TWRP? I do not see it. I am having some issues with my watch, one of which is that I am unable to mount /data, which is normally fixed with the repair option under the advanced wipe menu, but I do not see that option here. Please help.
Here is a link to the full issues I am experiencing.
https://www.reddit.com/r/zenwatch/comments/7de8ax/help_unbricking_zenwatch_3/
Click to expand...
Click to collapse
Have you tried to "FORMAT DATA" in TWRP?
If not then go to the WIPE option in twrp and
select "format data" then you will be ready
to flash a zip file rom or IMG files.
Most likely your DATA partition is "encrypted"
which means the watch cannot successfully
complete a rom installation because it cannot
write to the data partition.
Wiping DATA is fine if your DATA partition is
not encrypted.
Good luck, have a great day!
Misterjunky said:
Have you tried to "FORMAT DATA" in TWRP?
If not then go to the WIPE option in twrp and
select "format data" then you will be ready
to flash a zip file rom or IMG files.
Most likely your DATA partition is "encrypted"
which means the watch cannot successfully
complete a rom installation because it cannot
write to the data partition.
Wiping DATA is fine if your DATA partition is
not encrypted.
Good luck, have a great day!
Click to expand...
Click to collapse
I do not see a "format data" option under wipe in TWRP on my zenwatch when i go to wipe i have either factory reset, or advanced wipe.
If i go to advanced wipe, and then select data, and slide to wipe, it says "unable to mount storage " "updating partition details..." "Failed to mount '/data' (invalid argument)" "...done" "unable to mount storage"
I have a problem with my ZW3: I unlockt the bootloader and booted into TWRP 3.1.1.0 (via fastboot, did not install it).
I wanted to transfer a ROM on my watch, but did not find a way to do it. So I rebooted the system.
But now everytime I want to boot into (stock) recovery (on the watch) I get the android droid with a exclamation mark. Is there a recovery image I can flash to solve this?
How do I transfer files on my watch? I don't see the device on my pc in the list (adb and fastboot work fine).
EDIT: Found a file here: https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Do I have to flash all three files (system, boot and recovery) in order to get recovery back?
EDIT 2: When I boot the recovery from the file above via fastboot I also get the droid with the exclamation mark.
re: stock firmware
Der-Knuffi said:
I have a problem with my ZW3: I unlockt the bootloader and booted into TWRP 3.1.1.0 (via fastboot, did not install it).
I wanted to transfer a ROM on my watch, but did not find a way to do it. So I rebooted the system.
But now everytime I want to boot into (stock) recovery (on the watch) I get the android droid with a exclamation mark. Is there a recovery image I can flash to solve this?
How do I transfer files on my watch? I don't see the device on my pc in the list (adb and fastboot work fine).
EDIT: Found a file here: https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Do I have to flash all three files (system, boot and recovery) in order to get recovery back?
EDIT 2: When I boot the recovery from the file above via fastboot I also get the droid with the exclamation mark.
Click to expand...
Click to collapse
@Der-Knuffi
Go into fastboot and flash all 3 of the image files (recovery.img, boot.img and system.img)
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot oem lock
When your done flashing reboot the watch.
The watch will boot into official stock Android Wear 1.5, have patience it takes a long time to boot.
Good luck, have a great day!
Misterjunky said:
@Der-Knuffi
Go into fastboot and flash all 3 of the image files (recovery.img, boot.img and system.img)
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot oem lock
When your done flashing reboot the watch.
The watch will boot into official stock Android Wear 1.5, have patience it takes a long time to boot.
Good luck, have a great day!
Click to expand...
Click to collapse
Thanks, I will try it. Isn't there a dump from AW2.0?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
I have a weird issue with TWRP that I cannot seem to resolve.
I have a 4GB Mix on the latest MIUI (China Stable). Bootloader is unlocked and I followed all the steps to got successfully TWRP loaded onto my device and i can come right in to it.
If i restart the device and use volume+ and power TWRP isn't there. Only the stock recovery from MIUI.
I tried the tutorial here on XDA and this one ''en.miui.com/thread-500625-1-1.html"
Is there someone who can help me please?
Many Thanks from the Nederlands!
Dexterd83 said:
I have a weird issue with TWRP that I cannot seem to resolve.
I have a 4GB Mix on the latest MIUI (China Stable). Bootloader is unlocked and I followed all the steps to got successfully TWRP loaded onto my device and i can come right in to it.
If i restart the device and use volume+ and power TWRP isn't there. Only the stock recovery from MIUI.
I tried the tutorial here on XDA and this one ''en.miui.com/thread-500625-1-1.html"
Is there someone who can help me please?
Many Thanks from the Nederlands!
Click to expand...
Click to collapse
I guess you jumped from Samsung, didn't you? Because i remember that you manually have to reboot into recovery at the first time(right after flashing the twrp via odin). So you need to do it from fastboot on Xiaomi(afaik). Just flash the twrp and enter this code in fastboot:
Code:
fastboot boot twrp-blabla.img
Sent from my Xiaomi MIX using XDA Labs
Hi,
i have a package updated for Mix...
I made quick *.bat command to easily flash what i need...
Try OEM unlock tool (bat file) before trying to flash TWRP...
Be sure to have ADB device found in first line and be in fastboot mode !!
http://download.lesscro.com/Mi Mix/TWRP/
Hope help a bit... Cheers !
Konsstantine34 said:
I guess you jumped from Samsung, didn't you? Because i remember that you manually have to reboot into recovery at the first time(right after flashing the twrp via odin). So you need to do it from fastboot on Xiaomi(afaik). Just flash the twrp and enter this code in fastboot:
Code:
fastboot boot twrp-blabla.img
Sent from my Xiaomi MIX using XDA Labs
Click to expand...
Click to collapse
Nope, from the Nexus 6P.
I just tested it and now I'm right in TWRP again. That great! Thanks!!
So every time I want to use TWRP, I need to go into fastboot mode and use that command line?
Nope... power and Vol - or + need make the job or you can install xposed and add a module MIUI Extended Reboot...
Will looks like something like that...
{
"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"
}
Sorry bored to take a picture from my device...
Thanks for your reply.
No, Power and Vol + i get MI-Recovery 3.0 (main menu) and if i use Power and vol - than i get fastboot mode.
So I now have two recovery's on my device. Is that possible? (TWRP and MI Recovery)
I think i have found the problem..
I've installed TWRP in fastboot mode. I've used ''fastboot boot twrpmrraines.img'' to get into TWRP the first time and i have tried to flash TWRP as recovery.
Now I get the following error message ''error opening: / sdcard'' So there seems to be an error with the sd card i think?
Nope Recovery and fastboot mode are different.... Recovery is used to backup, mount and flash ROM, Mod and various ZIP, IMG files...
Fastboot Mode is used to flash, push, IMG, APK, and sometimes ROM if you use Fastboot method...
Anyway, check in recovery if u can repair sdcard... in wipe feature, DO NOT WIPE, choose REPAIR / Advanced/etc......
lesscro said:
Nope Recovery and fastboot mode are different.... Recovery is used to backup, mount and flash ROM, Mod and various ZIP, IMG files...
Fastboot Mode is used to flash, push, IMG, APK, and sometimes ROM if you use Fastboot method...
Anyway, check in recovery if u can repair sdcard... in wipe feature, DO NOT WIPE, choose REPAIR / Advanced/etc......
Click to expand...
Click to collapse
Can not select sdcard if I click on ''Repair or Change File System'' If I go to Wipe-Advanced Wipe I must select: Dalvik, system, data, internal storage, cache or usb otg. There is no sdcard.
On Mix, SDcard is internal storage....
lesscro said:
On Mix, SDcard is internal storage....
Click to expand...
Click to collapse
Invalid partition selection if i click Internal Storage..
then you can't repair internal storage... can u see, when Mix is on Android ROM, your internal storage... with explorer or PC when u mount as MTP... ?
Dexterd83 said:
Invalid partition selection if i click Internal Storage..
Click to expand...
Click to collapse
Try an another version of twrp image. For me twrp by Mr Raines has no issue other than error 7(mount read-only).
Sent from my Xiaomi MIX using XDA Labs
Dexterd83 said:
I guess you jumped from Samsung, didn't you? Because i remember that you manually have to reboot into recovery at the first time(right after flashing the twrp via odin). So you need to do it from fastboot on Xiaomi(afaik). Just flash the twrp and enter this code in fastboot:
Nope, from the Nexus 6P.
I just tested it and now I'm right in TWRP again. That great! Thanks!!
So every time I want to use TWRP, I need to go into fastboot mode and use that command line?
Click to expand...
Click to collapse
Think I said you before only first boot of twrp.
mount read only can be fixed by go to Mounting and check/uncheck read only system and recheck system...
Then u can flash what u want... strange issue but works...
Konsstantine34 said:
Try an another version of twrp image. For me twrp by Mr Raines has no issue other than error 7(mount read-only).
Click to expand...
Click to collapse
Yea that's the same with smarty, other than that never had a problem since 1st day.
lesscro said:
mount read only can be fixed by go to Mounting and check/uncheck read only system and recheck system...
Then u can flash what u want... strange issue but works...
Click to expand...
Click to collapse
If I do that and want to flash twrp i get the same error: Error opening: '/sdcard/twrpmrraines.img/' (not a directory)
If u are on TWRP, why want flash TWRP again ? i m not sure to understand deal here.... whats' problem actually....
1 - you can't flash TWRP ?
2 - u ry to flash TWRP using fastboot ?
3 - u try to flash twrp from TWRP ? (old image from new image)
4 - other ?
Dexterd83 said:
If I do that and want to flash twrp i get the same error: Error opening: '/sdcard/twrpmrraines.img/' (not a directory)
Click to expand...
Click to collapse
Man, my point was your installed twrp may have got an issue. If it has issue, that's normal can't flash something anything. Use fastboot to flash another twrp as usual.
Sent from my Xiaomi MIX using XDA Labs
Konsstantine34 said:
Man, my point was your installed twrp may have got an issue. If it has issue, that's normal can't flash something anything. Use fastboot to flash another twrp as usual.
Sent from my Xiaomi MIX using XDA Labs
Click to expand...
Click to collapse
I flashed 4 different TWRP files. Nothing will works.
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
bump pls
even bad news is appreciated
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Hmm.. does phone in TWRP works like USB storage?
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"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"
}
swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?
vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.
swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?
swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.
redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.
Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?
So,
I have a Mi 9T Pro (Global) 128GB. I upgraded it to the latest MIUI version when I got it (11.something).
I unlocked the bootloader and flashed TWRP. So far so good. But then, when trying to flash LinageOS I must have missed a step.
Long story short: When booting I see the linageOS bootlogo for a good 3 minutes or so, and then it kicks me back into TWRP.
It might also be worth mentioning that I flashed the DisableForceEncrypt before.
Can someone tell me what I screwed up? (Note: I did wipe cache & dalvik before rebooting so that can't be the issue).
KuroRyu said:
So,
I have a Mi 9T Pro (Global) 128GB. I upgraded it to the latest MIUI version when I got it (11.something).
I unlocked the bootloader and flashed TWRP. So far so good. But then, when trying to flash LinageOS I must have missed a step.
Long story short: When booting I see the linageOS bootlogo for a good 3 minutes or so, and then it kicks me back into TWRP.
It might also be worth mentioning that I flashed the DisableForceEncrypt before.
Can someone tell me what I screwed up? (Note: I did wipe cache & dalvik before rebooting so that can't be the issue).
Click to expand...
Click to collapse
You need to format data when flashing over MIUI.
You should have formatted data, then flashed dfe, before flashing LOS.
Did you flash dfe because you think it's needed, or because you want to permanently remove encryption? There is no need to flash dfe if you would prefer to keep encryption.
I want to keep encryption, if possible. I just had problems that TWRP didnt decrypt, and I couldn't transfer files.
Anyway, so what steps do you suggest me from here on, to get a rooted, working LOS?
Right now I have a half broken LOS install that can't boot properly.
KuroRyu said:
I want to keep encryption, if possible. I just had problems that TWRP didnt decrypt, and I couldn't transfer files.
Anyway, so what steps do you suggest me from here on, to get a rooted, working LOS?
Right now I have a half broken LOS install that can't boot properly.
Click to expand...
Click to collapse
Best bet is to start again.
Flash the latest fastboot ROM for the phone, making sure that you change the flash option in the Mi Flash Tool, so you don't lock the bootloader.
Boot into MIUI once to finalise the installation. No need to do the initial setup.
Flash TWRP and boot into it.
Do a factory reset, followed by format data. Format not wipe, need to type yes to continue.
Reboot into TWRP to ensure the formatted data partition is properly mounted.
Flash LOS, plus the extras you want.
Reboot to system and you should be good.
This is the best failsafe method when nothing else seems to work.
Encryption can cause issues in future, so when updating LOS or flashing a new AOSP ROM it is a good idea to remove lockscreen security before updating/flashing and you should be OK.
Robbo.5000 said:
Best bet is to start again.
Flash the latest fastboot ROM for the phone, making sure that you change the flash option in the Mi Flash Tool, so you don't lock the bootloader.
Boot into MIUI once to finalise the installation. No need to do the initial setup.
Flash TWRP and boot into it.
Do a factory reset, followed by format data. Format not wipe, need to type yes to continue.
Reboot into TWRP to ensure the formatted data partition is properly mounted.
Flash LOS, plus the extras you want.
Reboot to system and you should be good.
This is the best failsafe method when nothing else seems to work.
Encryption can cause issues in future, so when updating LOS or flashing a new AOSP ROM it is a good idea to remove lockscreen security before updating/flashing and you should be OK.
Click to expand...
Click to collapse
Yeah, you should change "clean all and lock" to just "clean all" in the bottom right corner of MiFlash
formated data partition (not wipe data partition, not the same thing)
check my guide https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
(how to flash roms, the MIUI to AOSP part)
@Robbo.5000 @PapajOhn420 Which fastboot rom would that be then? And where can I find the MI Unblock tool? Just want to make sure I don't break anything in the process.
EDIT: The one from the xiaomi website is an absolute disaster tool, it throws errors everywhere.
Also I am pretty sure I dotn have the MIUI accoutn anymore that I created for when unlocking that. I just used a disposable email (10minutemail) for it.
Here's the Fastboot tool: https://forum.xda-developers.com/attachment.php?attachmentid=4920077&d=1578342342
Here you can find a suitable fastboot rom: https://xiaomifirmwareupdater.com/miui/
Just make sure you choose the correct version corresponding with your device's region.
EEA is for European devices
PapajOhn420 said:
Here's the Fastboot tool: https://forum.xda-developers.com/attachment.php?attachmentid=4920077&d=1578342342
Here you can find a suitable fastboot rom: https://xiaomifirmwareupdater.com/miui/
Just make sure you choose the correct version corresponding with your device's region.
EEA is for European devices
Click to expand...
Click to collapse
The ROM I downloaded is a zip file which contains multiple files. When selecting an image from the flash tool I can only search for files with .img or .bin extension.
Should I renmae the .zip to .img? Also, what partition do I select when flashing? And this version of the mi flash tool doesnt seem to lock the bootloader by default, or am I missing something?
There is an option OEM Unlocker/locker, but thats about it. As long as I dont touch that I should be fine?
Use this one: https://www.xiaomiflash.com/download/
Remember to check "clean all" in the bottom right corner.
Then you select the extracted folder in the tool.
Make sure it corresponds with your device's region.
PapajOhn420 said:
Use this one: https://www.xiaomiflash.com/download/
Remember to check "clean all" in the bottom right corner.
Then you select the extracted folder in the tool.
Make sure it corresponds with your device's region.
Click to expand...
Click to collapse
This is the one that prompts errors everywhere. Missing log file paths etc.
KuroRyu said:
This is the one that prompts errors everywhere. Missing log file paths etc.
Click to expand...
Click to collapse
Can you post a screenshot?
Just says:
{
"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 specified the folder where I placed the MIUI rom zip file in. And I also selected clean all.
I still dont understand - what is the difference between flashing normally with TWRP and this MIUI tool? Shouldnt that be the same thing?
KuroRyu said:
Just says:
I specified the folder where I placed the MIUI rom zip file in. And I also selected clean all.
I still dont understand - what is the difference between flashing normally with TWRP and this MIUI tool? Shouldnt that be the same thing?
Click to expand...
Click to collapse
You have to extract the zip file and then select the extracted folder in the tool.
KuroRyu said:
Just says:
I specified the folder where I placed the MIUI rom zip file in. And I also selected clean all.
I still dont understand - what is the difference between flashing normally with TWRP and this MIUI tool? Shouldnt that be the same thing?
Click to expand...
Click to collapse
You can get the latest fastboot ROMs from here
https://xiaomifirmwareupdater.com/miui/raphael/
Make sue you choose the region for your phone and you choose a fastboot ROM.
Here's the flashing guide from the official MIUI forums, it also has the link for the official Mi Flash Tool. If it gives lots of errors, make sure you've got the proper drivers for the phone installed and a good quality USB cable.
https://c.mi.com/oc/miuidownload/detail?guide=2
You will need to view the page in desktop mode if viewing on a phone. Make sure you change the flash option in step 5 to 'clean all' before flashing.
Also the fastboot ROM is a *nix compressed tarball. Most Windows apps will need to unzip it twice. First one uncompresses it, it should leave a .tar file. Second time unpacks the tar file, leaving the ROM
Fastboot ROMs are more complete. They have many more partition images inside than standard recovery zip ROMs. They are for completely restoring the phone. The Mi Flash Tool is for flashing the fastboot ROMs.
Once you've flashed the fastboot ROM, follow my earlier process to then install LOS
@Robbo.5000 Thanks to you and all the others - I got it to work now.
Is the procedure you described the go to way to also do a clean flash - e.g. when updating to a newer version of LOS?
Why is the reflashing of MIUI necessary everytime? Does it have something to do with the vendor?
KuroRyu said:
@Robbo.5000 Thanks to you and all the others - I got it to work now.
Is the procedure you described the go to way to also do a clean flash - e.g. when updating to a newer version of LOS?
Why is the reflashing of MIUI necessary everytime? Does it have something to do with the vendor?
Click to expand...
Click to collapse
No need to do all this every time. This is my failsafe method for when you can't get a custom ROM to install successfully.
You should be OK dirty flashing updates. Encryption can cause issues though it is best to temporarily remove it before flashing.
In future to dirty flash an update,
Remove all lockscreen security on the phone - this will temporarily remove encryption, reducing the risk of problems flashing.
Boot to TWRP.
Flash the latest LOS zip file.
When finished select the wipe cache and dalvik option.
Reboot to system.
Restore the lockscreen security.
To change to a new custom ROM with a clean flash.
Remove all lockscreen security on the phone.
Boot to TWRP.
Do a factory reset.
Flash the new ROM, plus any extras.
Reboot to system.
Setup lockscreen security.