I need to understand how to update to the new Stock merged partition. Have been reading general advice in various threads that we need to flash new China developer rom. Can someone elaborate regarding how to do this and where to get this rom? Do we need to re-root? Do we need to reflash recovery?
I see that many new MM roms are using this new Stock partition like Matoxxi's newest RR rom. So want to know. Detailed help is highly appreciated... Thanks...
+1
I too would like to see a proper procedure..
This is what I personally did. Was on extended partition. With TWRP as recovery.
1) Flash the cwm r11( or any working cwm) recovery. Needed to flash the repartition zip!! Don't use TWRP. Did this once and had a dead phone. Reboot to recovery. You'll be on CWM.
2) Flash the back to stock partition zip. Choose the one with "el pierro verde" in it.
3) Flash TWRP recovery. Boot to recovery.
4) Flash the 5/12/17 miui zip. This is the ROM which merges the partitions. At this point the partitions are not merged yet!
4.1) Boot the phone up. Reboot to recovery
5) Repeat step 4. Now the partitions are merged.
6) Flash any ROM that you desire.
Of you are on stock partition with TWRP skip steps 1-3.
Good luck.
If you are on MIUI ROM, install 5.12.17 first to merge partitions and then 6.2.4 via Updater app. Xiaomi.eu version is tuned for europe/outside china, Google Apps are included in rom.
https://www.androidfilehost.com/?fid=24369303960690691
https://www.androidfilehost.com/?fid=24415232478676696
Or you can just MiFlash 6.2.4 chinese developer rom factory image from en.miui.com.
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
The only quick way to setup the new partition for now is to fastboot flash the Chinese Dev ROM, as you yourself already stated. You can flash it by fastboot flashing it using Mi PCSuite and choosing the Beta ROM.
On my experience, after the flash I got my bootloader locked ("fastboot oem device-info" resulted in Device unlocked = false), but I can simply unlock it through fastboot without any problem.
From that point, you can easily flash any custom ROM.
Or even MIUI V6, with manual, per partition fastboot flash rather than using MiFlash/Mi PCSuite because of different partition layout; V6 and lower got two boot, modem and system partitions for TDB, while the new has only one.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Can you boot the phone after the first flashing? Than reboot to recovery and try step 4 again.
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
I believe you have to use default Mi Recovery. One time flash of 5.12.17 was enough on my Mi4.
ksloh1 said:
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
Click to expand...
Click to collapse
It got auto updated? So did you flash stock recovery? Or used twrp
I downloaded 6.2.4 into my phone and then choose the file to update from miui itself, and it will reboot to twrp recovery and install. After fully install and reboot. Only then it will have merged partition and MM miui. And back to stock recovery automatically.
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
anshude1 said:
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
Click to expand...
Click to collapse
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
rxl.noir said:
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
Click to expand...
Click to collapse
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
anshude1 said:
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
Click to expand...
Click to collapse
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
rxl.noir said:
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
Click to expand...
Click to collapse
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
anshude1 said:
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
Click to expand...
Click to collapse
Yeah, it might be set to true once you had flashed another unsigned image to the eMMC (or when you disconnect the battery, IDK), probably for the warranty checks :q.
knoxwalles said:
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
Click to expand...
Click to collapse
Worked for me
Thank you very much.
Related
I have a Alcatel 1s (5024D) and i cant find any custom recovery for it can someone help me PLEASE
Hello @Xander20190
Have you tried ROM from this website: romprovider.com/alcatel-5024d-firmware-support
Sorry for the link structure, but my account is too young and I cannot paste the full link...
brt80 said:
Hello @Xander20190
Have you tried ROM from this website: romprovider.com/alcatel-5024d-firmware-support
Sorry for the link structure, but my account is too young and I cannot paste the full link...
Click to expand...
Click to collapse
I ment a custom recovery sorry for not putting custom before recovery
Xander20190 said:
I ment a custom recovery sorry for not putting custom before recovery
Click to expand...
Click to collapse
I am sorry, I believe I don't understand you. What does it mean "custom recovery"? You mean TWRP?
You possibly can't install custom recovery on Alcatel 1, as it doesn't allow you to flash anything other than System partition. TWRP is a recovery tool and needs to be flashed on the recovery partition.
sachb_htc said:
You possibly can't install custom recovery on Alcatel 1, as it doesn't allow you to flash anything other than System partition. TWRP is a recovery tool and needs to be flashed on the recovery partition.
Click to expand...
Click to collapse
If you are able to unlock bootloader with these commands, you should be able to flash whatever you want.
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
I was successfull unlocking bootloader of my Alcatel 1S (2020) 5028D-EEA at least but I cant find anything to flash for my device, no stock rom out there anywhere.
RavZ75 said:
If you are able to unlock bootloader with these commands, you should be able to flash whatever you want.
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
I was successfull unlocking bootloader of my Alcatel 1S (2020) 5028D-EEA at least but I cant find anything to flash for my device, no stock rom out there anywhere.
Click to expand...
Click to collapse
Even if you managed to unlock the bootloader, I bet you can't write on boot, & recovery partition.
I have the Alcatel 1 5033D, I can only flash files on the so called "system partition".
Therefore making it useless for anything apart from installing roms.
Lineage is an alternative OS for Alcatel 1 but comes without Google apps (gapps).
Sent from my LM-G710 using Tapatalk
I'll repeat... I cant find anything to flash for my device, no stock rom out there anywhere.
This means if I do flash anything random not suited for my device and it does succeeds with the flash, I could brick my device byebye and no way of unbricking it.
When I unlocked my bootloader with fastboot flashing unlock command, I can't run the same command again without it telling me error already unlocked.
I was however able to run the fastboot flashing unlock_critical command just fine and it again asked if I'm sure to unlock.
What unlock_critical does is as simply as it states, unlocks for flashing of those partitions that the manufacturer have set/locked as "critical" partitions.
I know of LineageOS yes and indeed it doesn't come with GApps...
With no stock rom so I can revert mistakes if being made, I am not myself gonna touch and poke around with that.
You who have an Alcatel 1 5033D are more than welcome to actually give it a try, maybe then you have something of value to add here.
Like if it does work... or even if it doesn't, this is of interest. Instead of "oh I bet"...
Bcuz as far as I have seen it, everyone here have gone with the old command flasboot oem unlock. That command doesn't unlock critical partitions.
RavZ75 said:
I'll repeat... I cant find anything to flash for my device, no stock rom out there anywhere.
This means if I do flash anything random not suited for my device and it does succeeds with the flash, I could brick my device byebye and no way of unbricking it.
When I unlocked my bootloader with fastboot flashing unlock command, I can't run the same command again without it telling me error already unlocked.
I was however able to run the fastboot flashing unlock_critical command just fine and it again asked if I'm sure to unlock.
What unlock_critical does is as simply as it states, unlocks for flashing of those partitions that the manufacturer have set/locked as "critical" partitions.
I know of LineageOS yes and indeed it doesn't come with GApps...
With no stock rom so I can revert mistakes if being made, I am not myself gonna touch and poke around with that.
You who have an Alcatel 1 5033D are more than welcome to actually give it a try, maybe then you have something of value to add here.
Like if it does work... or even if it doesn't, this is of interest. Instead of "oh I bet"...
Bcuz as far as I have seen it, everyone here have gone with the old command flasboot oem unlock. That command doesn't unlock critical partitions.
Click to expand...
Click to collapse
I have flashed "Lineage 16 treble" OS on my Alcatel 1 and it worked, but I've been unsucessfull in flashing the custom recovery, "TWRP" as even after unlocking the bootloader, only partition which can be flashed is the "System partition", so I flashed the original Alcatel 1 firmware back on it for gaaps.
So, this device is pretty much useless even if you have it unlocked, as you're limited to flashing the system partition only.
Sent from my LM-G710 using Tapatalk
well you don't seem to even gonna bother...
guess I'll have to do a flash myself once I find a rom for my device.
What I am specifically asking you is if you have unlocked critical partitions. Am I being unclear about that?
Could be that it is only your device model, maybe we'll see if other devices of Alcatel have better "flashability" then.
If I get hold of a stock rom to my device 5028D-EEA, I could try flash stock recovery or boot images myself only to try out and see if it does flash.
I didn't know there is an TWRP recovery for 5033D and it shouldn't even exist if it isn't possible to flash it.
This is the one, correct? No mention about "fastboot flashing unlock_critical" here either.
https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
RavZ75 said:
well you don't seem to even gonna bother...
guess I'll have to do a flash myself once I find a rom for my device.
What I am specifically asking you is if you have unlocked critical partitions. Am I being unclear about that?
Could be that it is only your device model, maybe we'll see if other devices of Alcatel have better "flashability" then.
If I get hold of a stock rom to my device 5028D-EEA, I could try flash stock recovery or boot images myself only to try out and see if it does flash.
I didn't know there is an TWRP recovery for 5033D and it shouldn't even exist if it isn't possible to flash it.
This is the one, correct? No mention about "fastboot flashing unlock_critical" here either.
https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
Click to expand...
Click to collapse
It's unbelievable, that you can't seem to get the point. No matter, what command you use, the only accessible partition for alcatel 1 will be the"System Partition".
I have tried all the commands, including unlock_critical, and still I'm unable to flash anything apart from system partition.
If you don't believe me, here is another user with the same issue:
https://r.tapatalk.com/shareLink/to...1&share_fid=3793&share_type=t&link_source=app
Sent from my LM-G710 using Tapatalk
What exactly is so unbelieveble about it? I spew out a whole lot about unlocking critical partitions and in vain for that matter, what I get back is LineageOS 16 treble and unlocked bootloader you say. It's not being very clear about your point as people type in command fastboot oem unlock and say yeah I unlocked bootloader..
"I have tried all the commands, including unlock_critical, and still I'm unable to flash anything apart from system partition." <- This is very good. This is exactly what I wished was clear about from the beginning and now it is.
Now finally done with this, I am gonna admit that I see your point and that It's not gonna work. So I'll withdraw that argument that it all should be unlocked with those commands as this is not the case for your device.
Can anyone give me a pac file for the 1se. my phone is stuck on a bootloop and I need to flash it
You can root it but it's a long journey: https://forum.hovatek.com/thread-32678.html
Also, you can port TWRP but you need to modify it for the touchpad to work: https://forum.hovatek.com/thread-32743.html
KikoPlays44 said:
Can anyone give me a pac file for the 1se. my phone is stuck on a bootloop and I need to flash it
Click to expand...
Click to collapse
A package installer file? What is pac? you have sys as root and a only partition that's treble supported and Vulcan supported.you need a clean sys image.xz
I was wondering is there any RP2 ROMS like Lineage os or other ROMS? Or not yet or it's not possible to make for this kind of phone or maybe i didn't search more to know what's going on??
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
chris5s said:
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
Click to expand...
Click to collapse
Okay Thanks for the info, But i'm trying to root my phone on mr2 i can't find any thread that shows how to root mr2 with steps ??
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
chris5s said:
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
Click to expand...
Click to collapse
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
AssyrianHero said:
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
Click to expand...
Click to collapse
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
JDBarlow said:
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
Click to expand...
Click to collapse
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
chris5s said:
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
Click to expand...
Click to collapse
The problem there is no steps that shows what to do I'm just using my own steps, and I'm not using any Magisk I'm just trying to flash Arter's kernel.
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
AssyrianHero said:
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Click to expand...
Click to collapse
Honestly it's easier to root phones today than it ever has especially the RP2.
If you are truly unlocked this should only take you minutes to do.
First things first. Open a terminal where you have ADB / FASTBOOT installed or if you setup the attributes properly just open a terminal.
Type adb devices and it should give you your serial number of your phone. If not adb isn't installed properly.
If so, type adb reboot bootloader and phone will boot to bootloader.
Type fastboot devices and again it should give you the phones ID. If not fastboot isn't installed properly.
If so, type fastboot flash boot and the name of your arter97 file.img this will also install TWRP.
After installation from bootloader menu scroll down to reboot recovery and it should boot to TWRP.
Click cancel then swipe to allow modifications. In TWRP menu select INSTALL then choose where you've saved the magisk 20.3 file on your SD or internal drive.
After installation reboot system then install magisk manager if not already installed. At this point you're rooted. Have a great weekend!!
Good luck! :good:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
chris5s said:
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
Click to expand...
Click to collapse
The bootloader is unlocked i do have adb and i i know how to use it I've been rooting all my phones HTC M9 Samsung S7-8-9 and OnePlus 7 I've rooted too many phones but this one is little bit different than others i tried my own steps like i used to do:
I reboot my phone into bootloader and type fastboot devices and it gives me the Serial number and i then i type fastboot boot boot.img i don't know if this command works with this phone it actually worked with other phones this one not..
finixs said:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
Click to expand...
Click to collapse
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Look on the Razer website for the specific instructions to unlock bootloader/critical.
The fastboot command to flash a boot img is
fastboot flash boot boot.img
Peace
AssyrianHero said:
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Click to expand...
Click to collapse
"fastboot flashing unlock" unlock bootloader
"fastboot flashing unlock_critical" unlock the bootloader critical partitions
Also, make sure you're using the Razer recommended USB cord and ADB/Fastboot.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Cables
When connecting your Razer Phone to a computer for any development, it is advised by Razer to not use the in-box USB Type-C to Type-C charging cable for flashing. The supplied cable is specifically engineered for fast power delivery, not for data transfer. Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Upgrade your ADB/Fastboot here.
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?
JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.
WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse
KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.
KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse
[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.
Hi all,
After multiple issues with this phone, I finally opt out and pass to Pixel 7 Pro.
So, i would like to know how to relock bootloader avoiding the problems of bootloop.
I've uninstall Magisk with option "complete uninstall".
I saw it's better to flash stock image before relock bootloader but how ?
Simply by flashing boot.img on the two slot OR flashing full.zip generated by Oxygen Updater OR other method ?
Thanks a lot for your help !
fma388 said:
Hi all,
After multiple issues with this phone, I finally opt out and pass to Pixel 7 Pro.
So, i would like to know how to relock bootloader avoiding the problems of bootloop.
I've uninstall Magisk with option "complete uninstall".
I saw it's better to flash stock image before relock bootloader but how ?
Simply by flashing boot.img on the two slot OR flashing full.zip generated by Oxygen Updater OR other method ?
Thanks a lot for your help !
Click to expand...
Click to collapse
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
zopostyle said:
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
Click to expand...
Click to collapse
This phone was promising on paper but the user experience was much less so...
Thank you for the answer !!
For the full zip of Oxygen Updater, I flash it with "fastboot flash full.zip" or how? (I've never flashed a full zip )
fma388 said:
This phone was promising on paper but the user experience was much less so...
Thank you for the answer !!
For the full zip of Oxygen Updater, I flash it with "fastboot flash full.zip" or how? (I've never flashed a full zip )
Click to expand...
Click to collapse
You can use the Local installation system, from the update screen and it that does not support use the OPLocalUpgrade app that Oxygen Updater provides.
zopostyle said:
You can use the Local installation system, from the update screen and it that does not support use the OPLocalUpgrade app that Oxygen Updater provides.
Click to expand...
Click to collapse
Ok thanks !
zopostyle said:
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
Click to expand...
Click to collapse
Dear sir, i'm using Ne2213_11_C.30 (Newest Rom). Can u give me the Instructions to relock the bootloader (step by step). I don't know how to flash the boot.img. Thank so much.
hoaianh1505 said:
Dear sir, i'm using Ne2213_11_C.30 (Newest Rom). Can u give me the Instructions to relock the bootloader (step by step). I don't know how to flash the boot.img. Thank so much.
Click to expand...
Click to collapse
If you're on the latest rom there is no need to relock the bootloader
But if you want to, download this https://gauss-componentotacostmanua...23/03/21/b6cfe6d4ec4f4cf7bcb316891f9f8db9.zip
It's the full NE2213 C30 zip file.
Than download https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Intall it on you phone, It will show a new app Local Upgrade, using this tool you will install the above zip file.
After the installation complete, it's recommended to full wipe your device.
Than using adb and fastboot that you can download from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
plug you device into your computer
reset it to fastboot mode (turn off, hold power, vol + and vol - until the device start than release power button, once the screen shows the options you can release all buttons and choose fastboot mode if its not there)
on the command prompt type:
Fastboot flashing lock
And that's it.
zopostyle said:
If you're on the latest rom there is no need to relock the bootloader
But if you want to, download this https://gauss-componentotacostmanua...23/03/21/b6cfe6d4ec4f4cf7bcb316891f9f8db9.zip
It's the full NE2213 C30 zip file.
Than download https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Intall it on you phone, It will show a new app Local Upgrade, using this tool you will install the above zip file.
After the installation complete, it's recommended to full wipe your device.
Than using adb and fastboot that you can download from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
plug you device into your computer
reset it to fastboot mode (turn off, hold power, vol + and vol - until the device start than release power button, once the screen shows the options you can release all buttons and choose fastboot mode if its not there)
on the command prompt type:
Fastboot flashing lock
And that's it.
Click to expand...
Click to collapse
Thank you so much. Your advice's no need to relock the bootloader, i just worry about the information security. Eg: Banking app can work normal?
After updated to oxygen 13, my phone appear the warning: "phone has been unlocked and cant be trusted ..." each time i boot my device. How can i turn off this warning?
hoaianh1505 said:
Thank you so much. Your advice's no need to relock the bootloader, i just worry about the information security. Eg: Banking app can work normal?
After updated to oxygen 13, my phone appear the warning: "phone has been unlocked and cant be trusted ..." each time i boot my device. How can i turn off this warning?
Click to expand...
Click to collapse
There is no reason to worry about that warning. As your bootloader is not locked the only breach is that a user can manually flash another firmware.
But as he will not have the device on hand there is no problem.
My advice is to not relock, many users bricked their devices doing that.
Also everything works just fine, so no need to relock.
zopostyle said:
There is no reason to worry about that warning. As your bootloader is not locked the only breach is that a user can manually flash another firmware.
But as he will not have the device on hand there is no problem.
My advice is to not relock, many users bricked their devices doing that.
Also everything works just fine, so no need to relock.
Click to expand...
Click to collapse
Thanks for your helpful advice.
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D
dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!
Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?
I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.