Here is my problem,
I have a BLN-L29, now:
running on Lineage OS Beta 4
unlocked bootloader
TWRP
Now my mission is to revert back to stock EMUI Firmware.
Apparently, many of you guys refer to this thread and this thread for solution.
However, i still cant understand the steps. Especially this:
Download Update ZIP
A. Get ROM update link through hwmt.ru. Click "filelist.xml".
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA from previous step. Example ALP-L29 8.0.0.115 (C636) filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "ALP-L29_hw_spcseas/update_ALP-L29_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip"
I have downloaded three zip for BLA-L29C636b139 (8.0.0.139) that contains:
update.zip
BLA-L29_hw-spcseas/update_full_BLA0L29_hw_spcseas.zip
public/ update_data_full_public.zip
I hope there are the correct one needed to restore my phone back to stock.
Can anyone guide me please?
Hi, I was at LineageOS too.
I didn't need TWRP flash to install it.
I returned to Stock without problems, so my advice is to follow the next steps, but remember, it is you who decides to do it, I only offer you a solution that should NOT make things worse.
1. Stock recovery flashes from the version you were before Lineage, NONE other recovery version.
2. You go into recovery and do a Wipe Cache, and then a Factory Reset.
3. You restart Fastboot, and Syste.img flashes the version before Lineage.
4 Restart in recovery, and Reset Factory again, restart, and you're good to go.
To find the recovery and the Systen.img you should download the version that had your phone, download it, the full version, no other, unzip it, and with Huawei update Extractor, you get those two files that I told you.
I repeat, this should work if or if I'm not responsible for anything.
And above all, make sure first that you have the OEM Unlock, and the Bootloader open
Good luck
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
rey_lagarto said:
Hi, I was at LineageOS too.
I didn't need TWRP flash to install it.
I returned to Stock without problems, so my advice is to follow the next steps, but remember, it is you who decides to do it, I only offer you a solution that should NOT make things worse.
1. Stock recovery flashes from the version you were before Lineage, NONE other recovery version.
2. You go into recovery and do a Wipe Cache, and then a Factory Reset.
3. You restart Fastboot, and Syste.img flashes the version before Lineage.
4 Restart in recovery, and Reset Factory again, restart, and you're good to go.
To find the recovery and the Systen.img you should download the version that had your phone, download it, the full version, no other, unzip it, and with Huawei update Extractor, you get those two files that I told you.
I repeat, this should work if or if I'm not responsible for anything.
And above all, make sure first that you have the OEM Unlock, and the Bootloader open
Good luck
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
babadaba said:
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
Click to expand...
Click to collapse
latest update,
after the phone stuck at bootlooping,
i "fastboot flash system" the old lineage OS system img
now my phone is still in custom ROM.
back to square 1.
babadaba said:
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
Click to expand...
Click to collapse
If, your phone logs into bootloop, logs back into recovery, an option should appear to download the latest version available to you, it installs itself.
Anyway, if you have a bootloop problem, the terminal takes you to that step by itself, that's what happened to me when I installed Xposed Framework.
In any case, the first step should have been to do a Factory reset. I hope you can work it out.
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
babadaba said:
latest update,
after the phone stuck at bootlooping,
i "fastboot flash system" the old lineage OS system img
now my phone is still in custom ROM.
back to square 1.
Click to expand...
Click to collapse
Okay, I didn't read that last one. You're back at TWRP? I hope not.
You should check to see if you have any objections to entering Recovery Stock. In case of no problems, you can try a Factory Reset again, and Wipe Cache, then just flash System.img, and again Factory Reset.
Those, and NOT others, are the steps I took, and I had no problems.
Perhaps as it is a different process from your move to Custom, it must also be different to return to Stock.
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
Hey, have you made any progress?
Greetings.
Enviado desde mi BLA-L29 mediante Tapatalk
Related
I really need help on this issue.
It got into a bootloop and the only thing available is fastboot. No recovery or erecovery. This happened when I was at B170 with unlock bootloader and un-rooted on my L01.
Since this, I´ve flashed
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
using Update.app from B100, B121 and B130. No erros with any of these.
I´ve read all the threads about similar problems and used other solutions like:
Change the order of fastboot flash;
Use Multitool-unbrick
Flash TWRP and oficial recovery with multitool but none worked
Remove sim tray
Connect fastboot to Hisuite, but the PC detects the phone, as it plays a sound, but the Hisuite says no phone is connected
Right now my phone is on at fastboot, because I cant even turn it off. It just restarts, vibes, shows Honor screen and restarts after a few seconds.
I really appreciate any help on this.
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi !
A few months ago I unlocked my bootloader in order to root the phone. Last month I decided that I no longer needed root, so I flashed stock recovery and stock ROM. I updated yesterday to B180 without problem. You don't need to re-lock bootloader. It can stay unlocked without affecting the phone behaviour.
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Hi man, can you explain it more clearly pls? Having same problem even masters keeping silent,3 of them couldn't fix it.
---------- Post added at 06:44 AM ---------- Previous post was at 06:28 AM ----------
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi Zinko
It seems to me you have a great experience fixing that type of problem,please share with me as well,I have Huawei Mate 7 and it's rebooting only after trying to upgrade to Marshmallow.
As Sideness said for sure it's due to a bad recovery and boot partition flashed.In my case it's most probably "boot partition".
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Demeth said:
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Click to expand...
Click to collapse
I guess if you try to update from B170 to B313 it will mess the recovery.
To fix this, it is required to re-flash the recovery from B170, AND THEN go back to B121. After that it is up to you to go through B140 and jump to B313 or follow the Lollipop path until B180.
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
leholtet said:
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
Click to expand...
Click to collapse
Flash a complete B121 and then go all the way untill B180. The updates will show automatically, as you will have only to choose to update.
Hello,
i was on EMUI 9 with my BKL-L09 and decided to give the custom roms a new try.
So i backed up my recovery_ramdisk (it was rooted with magisk before) and then flashed twrp (version 3.2.3-3).
Now i went for Wipe>format data and gave it a try. Result: it was hanging after makefs->(..) done. So i done the whole procedure again but it was still hanging.
Now i can't get back into twrp, because only the twrp bootscreen is showing up. Even after restoring my recovery_ramdisk backup with fastboot i can't get back into erecovery Is there anything i can do?
Thanks.
Ok, i solved this by myself through downloading the full ota update, extracting everything and flashing new kernel, system and recovery from ota update contents.
Can you put the CMD lines to do it?
Thank you anyway. I think i have the same problem.
jesusdoar said:
Can you put the CMD lines to do it?
Thank you anyway. I think i have the same problem.
Click to expand...
Click to collapse
I don't have this smartphone anymore but i remember the following:
1. Download the Full OTA Zip (e.g. here: https://www.getdroidtips.com/huawei...-update-for-honor-view-10-download-available/
2. Use the Huawei Update Extractor to extract the partitions from the content in the zip file. (https://forum.xda-developers.com/showthread.php?t=2433454)
3. Flash the partitions over the existing ones on your V10 using fastboot "fastboot flash recovery_ramdisk recovery_ramdisk.img , ...) - these contents are inside the full ota package
Greetings
Did it work out for you?
You can also try to flash the original erecovery using fastboot und use the download option inside the Recovery App. This will reset all partitions back to default. But also all data is lost.
Brodelpiet said:
Did it work out for you?
You can also try to flash the original erecovery using fastboot und use the download option inside the Recovery App. This will reset all partitions back to default. But also all data is lost.
Click to expand...
Click to collapse
it works thank you, now the problem is that the erecovery doesn´t download the package to flash.
jesusdoar said:
it works thank you, now the problem is that the erecovery doesn´t download the package to flash.
Click to expand...
Click to collapse
Did you just flash the erecovery or also the normal recovery partition und Kernel from the zip? What kind of error do you get?
Brodelpiet said:
Did you just flash the erecovery or also the normal recovery partition und Kernel from the zip? What kind of error do you get?
Click to expand...
Click to collapse
Yeah i flashed the kernel and the recovery ramdisk. And now it boots into erecovery, but inside the erecovery, the option to download and install the last version of emui doesn´t work, it just shows an error that it can´t get the package info.
thanks for your attention.
greets
Hi everyone,
I ran out of ideas with my problem, and could really use some help / advice with this.
Trying to updgrade my STF-L09C432 from B368 to B385 using HuRu updater, something went wrong and now it bootloops after the blue Honor logo.
Fastboot, Huawei eRecovery and TWRP are still working and accessible, my device is bootloader unlocked and says FPR unlock in fastboot mode.
So here's the detailed steps and procedure which I followed:
0) TWRP Backup of System + Data
1) Load three update files (FullOTA) via FF: update.zip (update.zip), update_data_full_public.zip (update_data_full_public.zip), update_full_STF-L09_hw_eu.zip (STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip)
2) Create folder on SD-card with above files and TWRP v0.3 as recovery.img and the HuRu 0.4 zip file. Additionally I've left the HuRu 0.3 in the same folder renamed as HuRUpdater_0.3_old.zip
3) Installed the HuRu 0.4 from TWRP with zip verification disabled (tried before with enabled, but it failed -> call me stupid but I've double checked the checksum with a new download, so I took the risk).
4) the installation log showed warnings about some missing .zip files, but I ignored those as well, as I've never heard of them and didn't have them from FF.
5) rebooted the system and caught the first bootloop
Now I tried myself to fix it the following way, but unsuccessful until now:
1) Flashed TWRP into recovery_ramdisk because I didn't know the right procedure to boot into it
2) Flashed the new B385 versions of KERNEL.img, RAMDISK.img and RECOVERY_RAMDIS.img which I extracted from the UPDATE.APP -> still bootloop
3) Flashed TWRP into recovery_ramdisk again because I still didn't know the right procedure to boot into it
4) Flashed the old B368 versions of KERNEL.img, RAMDISK.img which I extracted from the UPDATE.APP, but not the RECOVERY_RAMDIS.img this time -> still bootloop
5) Then I've managed to boot into TWRP finally, and tried to restore my previous backup as a last resort, but that still didn't resolve my bootloop
Anybody has any idea what I could still try? Maybe I'm missing something obvious, or I'm still to new to this to see what is wrong.
If possible I'd like to keep my data intact, but I could probably extract most of it out of the backup, if nothing else helps.
Thank you very much!
Best regards,
Chris
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Schrubbi said:
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Click to expand...
Click to collapse
well, aslong as its still unlocked (frp & bl) i'm able to help.
Do you have telegram? if so, send me your username through pm.
Regards
I managed to get into TWRP again when I've installed the latest kernel and recovery images. After that I've realized that I still had Magisk installed and Active.
Uninstalling that solved my bootloop for now.
Unfortunately my backup restore just returned me to the previous version B368 which I already had installed... so lets see what happens if I apply the update again
---------------------
Edit:
Update applied, without magisk installed, still bootloop... At least the way back was quicker this time
Any hints what's going wrong are appreciated!
Hello
I have an Amazfit pace A1602 with ROM Version 2.6.5.0 (Chinese) and with the TWRP recovery.
I am having a problem when trying to update it to 2.6.6 because of the TWRP.
So, can I flash the stock recovery only? I searched in many many threads, but most are old and outdated and have no answers. Do I need to reflash the entire firmware just to have stock recovery? I am afraid of this because since the libraries were updated to Stratos libraries, I have many watchfaces that are from stratos, and may stop the entire launcher when ROM boots (this is the reason I have TWRP, I couldn't boot because of a broken watchface... long story short)
So, does anyone know if I can and how to do it?
Thanks in advance.
otaviobravim said:
Hello
I have an Amazfit pace A1602 with ROM Version 2.6.5.0 (Chinese) and with the TWRP recovery.
I am having a problem when trying to update it to 2.6.6 because of the TWRP.
So, can I flash the stock recovery only? I searched in many many threads, but most are old and outdated and have no answers. Do I need to reflash the entire firmware just to have stock recovery? I am afraid of this because since the libraries were updated to Stratos libraries, I have many watchfaces that are from stratos, and may stop the entire launcher when ROM boots (this is the reason I have TWRP, I couldn't boot because of a broken watchface... long story short)
So, does anyone know if I can and how to do it?
Thanks in advance.
Click to expand...
Click to collapse
Unzip the attached file and copy recovery.img to the sdcard/internal memory of the watch, reboot into recovery
Code:
adb reboot recovery
When TWRP boots (here I may be a bit wrong) tap on Install and you should see a button to change from installing .zip files to .img, files, select recovery.img from sdcard, and flash it as Recovery, then reboot the watch.
This should flash stock recovery you should be able to update via OTA.
Or use fastboot:
Code:
fastboot flash recovery recovery.img
Saratoga79 said:
Unzip the attached file and copy recovery.img to the sdcard/internal memory of the watch, reboot into recovery
Code:
adb reboot recovery
When TWRP boots (here I may be a bit wrong) tap on Install and you should see a button to change from installing .zip files to .img, files, select recovery.img from sdcard, and flash it as Recovery, then reboot the watch.
This should flash stock recovery you should be able to update via OTA.
Click to expand...
Click to collapse
Worked Perfectly, thank you for your kindness in answering and attaching the file!
Also, I used Fastboot as suggested by @lfom, because I find very hard to click on TWRP in Pace. :silly:
Thank you both
otaviobravim said:
Worked Perfectly, thank you for your kindness in answering and attaching the file!
Also, I used Fastboot as suggested by @lfom, because I find very hard to click on TWRP in Pace. :silly:
Thank you both
Click to expand...
Click to collapse
Which would be the process for a stratos 2 watch?
Thanks
Enviado desde mi HMA-L29 mediante Tapatalk
This might help you after realizing that you want to install custom ROM again after upgrading to android 11 MIUI but you cannot install android 10 or 11 based ROM and stuck with either boot loop or android rescue party.
WARNING: This might wipe every writable partition. Charge your phone at least 20% or more to prevent from destroying these partitions.
Instructions:
1. Download firmware from here
2. Download full ROM (either recovery or fastboot) from here
3. Save the firmware zip file it in either internal storage or sdcard. Reboot to TWRP afterwards
4. Tap install and find the zip file in your storage and install. Wait for a couple of seconds to get done.
To install full ROM
Recovery
1. After installing firmware from recovery mode, don't reboot. If you reboot the system it will fail to boot. Boot to fastboot if you fail this step and flash a recovery image. Proceed with next step.
2. Install full ROM flashable zip from sdcard or internal storage.
3. Format /data. Reboot.
Using fastboot
1. Boot from fastboot mode
2. Extract full ROM fastboot zip file.
3. Open miflash and locate the fastboot folder.
4. Choose flash_all. Click start.
5. The phone reboots itself. Boot to recovery mode and wipe data.
All done. The phone is now downgraded from android 11 back to android 10.
Note: I got 2 anti triggered when attempting to downgrade the phone using recovery and fastboot without installing firmware zip file first. RIP me I guess I voided my warranty anyways so doesnt matter as I already applied some insurance for my device.
TL;DR: Installed Recovery will get erased as I mentioned in WARNING. Please don't skip every step.
Edit: since it made confusion, I split steps for recovery and fastboot mode.
Has anyone tried this procedure?
Im on 12.0.6.0(EU). Bootloader locked (wait 3days) so no TWRP. Want downgrade to 12.0.8.0(EU) and flash Pixelexperience ROM.
It will work?
I'm a bit confusing... Links inserted in first 2 points seem to be the same link. So what I've to download exactly?
I'm on 12.0.7.0 Android 10 but I'm curious to try 12.0.6.0 Android 11 stable beta released some days ago...
PYCON said:
I'm a bit confusing... Links inserted in first 2 points seem to be the same link. So what I've to download exactly?
I'm on 12.0.7.0 Android 10 but I'm curious to try 12.0.6.0 Android 11 stable beta released some days ago...
Click to expand...
Click to collapse
Its not the same. First one is cca. 80MB of size while full rom is 2.4GB for recovery and 4.4GB for fastboot.
I did this method yesterday and its working. No problems whatsoever.
The only thing i would add is you need both versions of rom - recovery and fastboot. Recovery when you flash for the first time in recovery and fastboot when you flash with Mi flash.
And my advice is, android 11 miui is really bad. Its not finished, it stutters a lot, u can't use third party launchers with gesture navigation (at least in my case, Nova lanucher), performance is bad.
Not worth any time.
Steelrock said:
Its not the same. First one is cca. 80MB of size while full rom is 2.4GB for recovery and 4.4GB for fastboot.
I did this method yesterday and its working. No problems whatsoever.
The only thing i would add is you need both versions of rom - recovery and fastboot. Recovery when you flash for the first time in recovery and fastboot when you flash with Mi flash.
And my advice is, android 11 miui is really bad. Its not finished, it stutters a lot, u can't use third party launchers with gesture navigation (at least in my case, Nova lanucher), performance is bad.
Not worth any time.
Click to expand...
Click to collapse
Ok, ok, good to know. I'm just curious... I'll remain with A10 till when A11 will be good enough to be used as a daily driver
Hi. Does this method requires unlocked bootloader? Thanks
hi. this method not working for me !
*phone is unlocked !
ar-rabbiar said:
hi. this method not working for me !
*phone is unlocked !
Click to expand...
Click to collapse
This error is normal because ur phone is unlocked....but the phone should reboot normal in the new ROM. It did not happen this way?
Alin45 said:
This error is normal because ur phone is unlocked....but the phone should reboot normal in the new ROM. It did not happen this way?
Click to expand...
Click to collapse
reboot with bootloop and again. and just miui 12 a11 or rom with selinux permissive working for flash.
The same in here. Bootloop, bootloop....
But if flash the a11 rom it works.
ar-rabbiar said:
hi. this method not working for me !
*phone is unlocked !
Click to expand...
Click to collapse
did you try to flash firmware file from twrp recovery first? also that error means that a checkpoint failed which you need to disable or remove in configuration settings.
tourofeio said:
The same in here. Bootloop, bootloop....
But if flash the a11 rom it works.
Click to expand...
Click to collapse
did you tried recovery or fastboot flashing? and did you installed firmware first before installing full rom?
endva3 said:
Has anyone tried this procedure?
Im on 12.0.6.0(EU). Bootloader locked (wait 3days) so no TWRP. Want downgrade to 12.0.8.0(EU) and flash Pixelexperience ROM.
It will work?
Click to expand...
Click to collapse
i only tried recovery method and it works fine after days of trying. 12.0.6 android 11 is still buggy and miui needs to fix it a lot. most of apps are not well optimized for this flavor.
Today unlocked bootloader. Flashing 12.0.8.0 (i have 12.0.6.0 A11).
Everything work perfect. No bootloop, bootloader relock and works fine
People are probaly skipping some steps.
1. Download Firmware small size files
2. Download full Firmware, both - fastboot and recovery (put it on SD card, small and recovery)
3. Install Twrp or Orangefox recovery (download it from somewhere)
4. Enter into recovery and install small firmware FIRST, dont reboot, install big firmware (recovery version) SECOND
5. do not reboot
6. format data
7. Now reboot into fastboot
8. Extract fastboot firmware zip into new folder on desktop
9. Start Mi flash, select that folder where u extracted files and tick "clean only" on the bottom of the Mi flash if u want to leave bootloader unlocked and from drop down menu near that pick "flash_all.bat".
Thats how i did it.
Steelrock said:
People are probaly skipping some steps.
1. Download Firmware small size files
2. Download full Firmware, both - fastboot and recovery (put it on SD card, small and recovery)
3. Install Twrp or Orangefox recovery (download it from somewhere)
4. Enter into recovery and install small firmware FIRST, dont reboot, install big firmware (recovery version) SECOND
5. do not reboot
6. format data
7. Now reboot into fastboot
8. Extract fastboot firmware zip into new folder on desktop
9. Start Mi flash, select that folder where u extracted files and tick "clean only" on the bottom of the Mi flash if u want to leave bootloader unlocked and from drop down menu near that pick "flash_all.bat".
Thats how i did it.
Click to expand...
Click to collapse
i did the same, but looking to partitions of system, product and vendor, i understand that flashing the files via recovery and fastboot they dont write in that partitions.
looks like the partitions are read only. thanks
I try to flash a custom rom like arrows os via recovery , the rom shows the boot logo of arrows rom, and then bootloop.
tourofeio said:
I try to flash a custom rom like arrows os via recovery , the rom shows the boot logo of arrows rom, and then bootloop.
Click to expand...
Click to collapse
Most probable, u forgot to do a Format data (yes) before reboot to system.
endva3 said:
Today unlocked bootloader. Flashing 12.0.8.0 (i have 12.0.6.0 A11).
Everything work perfect. No bootloop, bootloader relock and works fine
Click to expand...
Click to collapse
Did you flash it from the built-in recovery or with MiFlash? (My 167 hour waiting period ends tomorrow)
Solved people. change the version of the Mi Flash.