Database Users

[OTA] Stock XNPH25R OTA

Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000

I'm getting binary update script error by flashing with TWRP

I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!

With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?

Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.

iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me

Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")

I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok

Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?

ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.

housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO

truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One

housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO

truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One

housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO

Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app

truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"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 what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.

fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.

ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?

Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk

TWRP Nougat Edition [With Root Instruction!]

is now depreciated visit:
TWRP 3.0.3 with decyption support!
Your warranty is probably void. Do we care?
THIS IS NOT A FINAL RELEASE! IF ANYTHING GOES WRONG IT ISN'T MY FAULT! THIS IS NOT BUILT FROM SOURCE, IT USES RENEWED KERNEL FROM N AND EDITED FSTAB! AND DO NOT USE DATAFIX U CAN FORMAT DATA PARTITION IN ADVANCED WIPE! ​
HOW-TO ROOT YOUR MATE 9/P9/Honor 8
Download
Phh su r275 version and flash
Download and install Material phh apk: Release post
Done!
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Data Decryption
Battery status
Mounting Loop Devices (Kernel doesn't support this)
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status:Stable
Stable: Sort OF
Created: 2016-11-20

Something

unable to flash anything as its saying no storage

nintendolinky said:
unable to flash anything as its saying no storage
Click to expand...
Click to collapse
I noticed
You need to flash one zip
Just make sure you backup all data on your internal storage since it'll wipe it
Here it is https://mega.nz/#!SgpTiRaJ!7vLP2bLrDfbQ4eWb_Tzevlv3_Nwx2SpwvJx4iBKb9s0
You might need to wipe it after again.
Just make sure you resize the partition afterwards.
Sent from my FRD-L09 using Tapatalk

TWRP Recovery is working, SuperSU in the TWRP can not flash?
{
"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"
}
TWRP, delete Cache & Dalvik takes very long?
Formating Cache using make_ext4fs...

Hen Ry said:
TWRP Recovery is working, SuperSU in the TWRP can not flash?
View attachment 3944122 View attachment 3944123 View attachment 3944124 View attachment 3944125 View attachment 3944126 View attachment 3944127 View attachment 3944128
TWRP, delete Cache & Dalvik takes very long?
Formating Cache using make_ext4fs...
Click to expand...
Click to collapse
No you can't flash supersu for now.
I don't feel like twrp takes long time to wipe unless battery is low
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
No you can't flash supersu for now.
I don't feel like twrp takes long time to wipe unless battery is low
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
http://androiding.how/huawei-mate-8-nougat-root-twrp/ -> How to Root Huawei Mate 8 Nougat update with SuperSU
Again the B552 update.zip and the update_data_full_all_cn.zip installed in the TWRP.
Despite the factory reset (the TWRP was started), the data are still available.
The very slow formatting existed already times in an earlier TWRP version.
In the latest version for EMUI 4 / 4.1 it was very fast again.

Hen Ry said:
http://androiding.how/huawei-mate-8-nougat-root-twrp/ -> How to Root Huawei Mate 8 Nougat update with SuperSU
Again the B552 update.zip and the update_data_full_all_cn.zip installed in the TWRP.
Despite the factory reset (the TWRP was started), the data are still available.
The very slow formatting existed already times in an earlier TWRP version.
In the latest version for EMUI 4 / 4.1 it was very fast again.
Click to expand...
Click to collapse
Problem is when it tries to mount the su image it reboots.
Sent from my FRD-L09 using Tapatalk

Working in Mate 8 NXT-L29C432?
Hi Hen Ry, you mentioned 'TWRP recovery working' is on Mate 8 NXT-L29C432 please? I want to give a try.
______________________
Able to port the above TWRP on Mate 8 NXT-L29C432 successfully and boot to TWRP recovery.
SuperSU failed to flash (tried both SR3 and SR4 of SuperSU-v2.7

A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken

Very slow formatting?
NXT-L29 with Tapatalk

Hen Ry said:
Very slow formatting?
NXT-L29 with Tapatalk
Click to expand...
Click to collapse
As I feel it. No
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Click to expand...
Click to collapse
Looking forward to it. Thank you

LastStandingDroid said:
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Click to expand...
Click to collapse
Will this fix the Bluetooth issue?
Sent from my FRD-L04 using XDA-Developers mobile app

manny18pr said:
Will this fix the Bluetooth issue?
Sent from my FRD-L04 using XDA-Developers mobile app
Click to expand...
Click to collapse
has nothing to do with the bluetooth, but yes it can apply it

could you build this for the Huawei P9? pleeaaseee! we have no working TWRP for the P9 nougat beta.
the phones are nearly identical so it should not need much adaption.
you would be our hero and your thanksmeter will explode!

Bluetooth, NFC and DUAL SIM Manager works for me.
with update_data_full_all_cn.zip

Do you have an eta for the build?

UnchartedRd said:
Do you have an eta for the build?
Click to expand...
Click to collapse
Hmm, not sure yet, still have some things i want to check first.
Hen Ry said:
Bluetooth, NFC and DUAL SIM Manager works for me.
with update_data_full_all_cn.zip
Click to expand...
Click to collapse
:good:
paratox said:
could you build this for the Huawei P9? pleeaaseee! we have no working TWRP for the P9 nougat beta.
the phones are nearly identical so it should not need much adaption.
you would be our hero and your thanksmeter will explode!
Click to expand...
Click to collapse
Sure if u have the stock recovery.img for it i can fix a fast backport

LastStandingDroid said:
Sure if u have the stock recovery.img for it i can fix a fast backport
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B9gJ44ME0ZkcSFdySTNBeTlZeTA
if you need someone to test pm me!

[Recoveries]TWRP Recovery For Meizu M2 Mini

{
"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"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Requirements
Root+Bootloader Unlocked
Flashing Instructions
After Unlocking Bootloader (If you dont know how to do it then go here)
[url]https://forum.xda-developers.com/meizu-m2-mini/how-to/guide-unlock-bootloaderinstall-twrp-t3390799[/URL]
Enter In fastboot.Then type.
"fastboot flash recovery recovery.img"
wait a minute turn off the phone. and enter recovery (Power + vol up until vibration)you'll Be in TWRP
Download Links
Old Recovery Version 2.8
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlMXd3YzJhTnUxeVU[/URL]
Mid Recovery 3.10 Latest
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlYnpCaXhSOUxjX0E[/URL]
New Recovery 3.1.1
[url]https://drive.google.com/file/d/0Bz6Fq2POoJTlRjh4ZkppWUJ4Qm8/view?usp=drivesdk[/URL]
Latest Recovery 3.2.1
[url]https://drive.google.com/file/d/1ftYtD2Tm0MdKBv_ZtVQHGJEcCuflb6Oe/view?usp=drivesdk[/URL]
Don't Forget To Press Thanks if you like it :good: :good:
Regards~
Murtaza Piplod

what's news bro?

ADIB27 said:
what's news bro?
Click to expand...
Click to collapse
updated with latest features of the latest recovery released by TWRP read changelogs at there TWRP site

heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.

maxisgsm said:
heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.
Click to expand...
Click to collapse
Try clear dalvik and cache.

adarshm4you said:
Try clear dalvik and cache.
Click to expand...
Click to collapse
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......

maxisgsm said:
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......
Click to expand...
Click to collapse
I think there will be some mess in installed os reflash it after taking a backup.

adarshm4you said:
I think there will be some mess in installed os reflash it after taking a backup.
Click to expand...
Click to collapse
my phone hang while i do a format storage.

maxisgsm said:
my phone hang while i do a format storage.
Click to expand...
Click to collapse
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.

adarshm4you said:
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.
Click to expand...
Click to collapse
every time the phone boot into twrp, it only go back to last state and keep fail then reboot...... it will cycle until battery die. i cannot go anywhere in twrp .....
now i at fastboot state, when i try to flash stock rom, it gave me the error
G:\adbFire>fastboot flash update update_8.zip
sending 'update' (1115283 KB)...
OKAY [ 88.153s]
writing 'update'...
FAILED (remote: partition table doesn't exist)
finished. total time: 88.237s

Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:

adarshm4you said:
Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:
Click to expand...
Click to collapse
adb cannot detect my devices ..... if i not mistake, last time i unlcock my OnePlus one without any problem, and adb can detect my phone,
now cannot detect ....

@murtaza1326
TWRP 3.2.1.0 is out!
Update the post

rushiranpise said:
@murtaza1326
TWRP 3.2.1.0 is out!
Update the post
Click to expand...
Click to collapse
post updated new latest 3.2.1 TWRP is added @Dinolek TWRP is alread there in his post so I don't think i should repost it here ??
Regards~

how to recovery install meizu m2 mini flyme 6.2.0.0g

thanks sir.. i wanna install this twrp

Pretty good!

[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!

Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
​
Pre-requisite
Redmi Note 4 - Snapdragon version!
Unlocked Bootloader
Common sense
Steps
Download latest build of the recovery from here and correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on icon on the top - section with RedWolf specific settings.
Here find and enable this checkbox: "Support OTA Survival trigger package"
Clean flash some full MIUI ROM and flash whatever you want after that.
Reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Now you can flash SuperSU or Magisk and incremental OTA's without any hustles, enjoy!
{
"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"
}
​
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you are really sure that you followed the installation process correctly then send us a log or screenshot and we will look at it.
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.This recovery can be used with any ROM?
Ans: Yes! You can use this recovery with any ROM.
Q.I'm stuck on patching system image unconditionally already for 10 minutes, what to do?
Ans: Zip is probably corrupted, re-download file which you're flashing again.
Q.Why j have to use updater app for it? Why we can't just flash it manually from recovery?
Ans: Zip must be decrypted first.. Updater application is automatically decrypting it so recovery can fully access files inside the zip.

How much space it takes in Internal storage for this process @ATG Droid as ZCX TWRP is taking almost 3GB internal storage space for the same purpose.

bravonova said:
How much space it takes in Internal storage for this process @ATG Droid as ZCX TWRP is taking almost 3GB internal storage space for the same purpose.
Click to expand...
Click to collapse
It depends on OTA survival... If you won't include system in OTA survival process then it will take only 60MB. Unfortunately you won't be able to modify system partition after that or OTA update will fail. Anyway you will still be able to flash Magisk or anything what isn't modifying it.

I have installed RWR V.3.1-0.20 and wanna install last version V.3.1-021,does install new zip in recovery finished all or is other steps required to update new version,thanks!

danube59sailor said:
I have installed RWR V.3.1-0.20 and wanna install last version V.3.1-021,does install new zip in recovery finished all or is other steps required to update new version,thanks!
Click to expand...
Click to collapse
Yup.. Just flash it as the zip. :good:

<deleted>

How much space is needed for 1.2 GB OTA update.. ?? I got space full error and I have around 10GB free internal storage..
Thanks.
Sent from my Redmi Note 4 using Tapatalk

FurqanHanif said:
How much space is needed for 1.2 GB OTA update.. ?? I got space full error and I have around 10GB free internal storage..
Thanks.
Click to expand...
Click to collapse
That's weird.. It should work with at least 3GB of free space... Will try to look at this

Ok , so this time . I haven't got low storage error but still when MIUi starts it says update failed..
And see this video , some /firmware unable to mount ( in your screenshot their is no such error). This /firmware thing might be the culprit.. [emoji848]
Thanks..
Video link ( http://www.fileconvoy.com/dfl.php?id=g8938d6cbe6545d9b1000032500c24a04eb85e637f6 )
View attachment 4342128
Sent from my Redmi Note 4 using Tapatalk

FurqanHanif said:
Ok , so this time . I haven't got low storage error but still when MIUi starts it says update failed..
And see this video , some /firmware unable to mount ( in your screenshot their is no such error). This /firmware thing might be the culprit.. [emoji848]
Thanks..
Video link ( http://www.fileconvoy.com/dfl.php?id=g8938d6cbe6545d9b1000032500c24a04eb85e637f6 )
View attachment 4342044
View attachment 4342128
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
There isn't right now any known way how to bypass that "miui update status check". From what i know same thing was on the first recovery called ZCX which first introduced this feature year ago. Anyway that recovery isn't open source so i had to build that code on my own and that error is still here. I think that i will need some testers for this. But this information doesn't mean that the update really failed. If you will look at the current build number then you will see that it updated successfuly.
Btw. that error with firmware isn't a problem. Just a different fstab compared to the stock
recovery. Maintainer for Mido will try to look at it when he will have some free time.

ATG Droid said:
There isn't right now any known way how to bypass that "miui update status check". From what i know same thing was on the first recovery called ZCX which first introduced this feature year ago. Anyway that recovery isn't open source so i had to build that code on my own and that error is still here. I think that i will need some testers for this. But this information doesn't mean that the update really failed. If you will look at the current build number then you will see that it updated successfuly.
Btw. that error with firmware isn't a problem. Just a different fstab compared to the stock
recovery. Maintainer for Mido will try to look at it when he will have some free time.
Click to expand...
Click to collapse
But I think because of that , system not updating properly.. for example I modified mixer file ( which can be found in system/etc folder) changed volume value from 84 to 90. No I flashed MIUi OTA update and after update that file is still untouched and another thing is now I can't modified it all ( and I have magisk installed, keeps getting unable to write file on solid explorer and total commander). But when I flashed OTA with stock recovery , everything is fine..
So what's that .. ??! [emoji848] It's just confusing.. is recovery changing permission or something or what. .. ? [emoji848]
Sent from my Redmi Note 4 using Tapatalk

FurqanHanif said:
But I think because of that , system not updating properly.. for example I modified mixer file ( which can be found in system/etc folder) changed volume value from 84 to 90. No I flashed MIUi OTA update and after update that file is still untouched and another thing is now I can't modified it all ( and I have magisk installed, keeps getting unable to write file on solid explorer and total commander). But when I flashed OTA with stock recovery , everything is fine..
So what's that .. ??! [emoji848] It's just confusing.. is recovery changing permission or something or what. .. ? [emoji848]
Click to expand...
Click to collapse
Stock recovery isn't including system in OTA survival. That's why it's working for you. You can also disable it in redwolf but you won't be able to modify system partition after that.
For that mixer file try to use this app: https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic

ATG Droid said:
Stock recovery isn't including system in OTA survival. That's why it's working for you. You can also disable it in redwolf but you won't be able to modify system partition after that.
For that mixer file try to use this app: https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Click to expand...
Click to collapse
Got it thanks.. and that root app works.. ( strange solid explorer root not working ). [emoji848]
One more thing , if redwolf unable to mount /firmware than it means if we ever get latest firmware via OTA it won't get updated .. right.. ?[emoji848]
Sent from my Redmi Note 4 using Tapatalk

FurqanHanif said:
Got it thanks.. and that root app works.. ( strange solid explorer root not working ). [emoji848]
One more thing , if redwolf unable to mount /firmware than it means if we ever get latest firmware via OTA it won't get updated .. right.. ?[emoji848]
Click to expand...
Click to collapse
That firmware is just mount point for ssd partition. So that's not a problem at all... Of course firmware partitions like aboot, tz etc. will be updated correctly. Don't worry

ATG Droid said:
That firmware is just mount point for ssd partition. So that's not a problem at all... Of course firmware partitions like aboot, tz etc. will be updated correctly. Don't worry
Click to expand...
Click to collapse
Got it.. thanks for clarifying everything...
Sent from my Redmi Note 4 using Tapatalk

Hey there,
If I flash this recovery over TWRP, check the boxes and then try to OTA updates via miui updater will it work ? Or do I have to flash through redwolf ? If so, can I dirty flash miui 9 over miui 8?
Thanks

Please,how to flash new 023.img. file through WRevovery? I can't find zip file,only IMG. Thanks again!

danube59sailor said:
Please,how to flash new 023.img. file through WRevovery? I can't find zip file,only IMG. Thanks again!
Click to expand...
Click to collapse
Just go to install option in RWR and select Install Image at bottom right.
Now choose your .img file.

Felix Siahaan said:
Just go to install option in RWR and select Install Image at bottom right.
Now choose your .img file.
Click to expand...
Click to collapse
Thanks, flashing successful last buil
d, thanks in advance!

biroot said:
Hey there,
If I flash this recovery over TWRP, check the boxes and then try to OTA updates via miui updater will it work ? Or do I have to flash through redwolf ? If so, can I dirty flash miui 9 over miui 8?
Thanks
Click to expand...
Click to collapse
Btw it worked : flashed Red Wolf from TWRP, reboot, enter Red Wolf, check the boxes for OTA survival, then updated from MIUI OTA tool.. Success!
Now in latest MIUI Build, with battery drain and all kinds of bugs!

[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!

Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
​
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Now you can flash SuperSU or Magisk and incremental OTA's without any hustles. Use the built-in SuperSU/Magisk option for rooting your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you are really sure that you followed the installation process correctly then send us a log or screenshot and we will look at it.
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.This recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.

ATG Droid said:
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
​
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
[SIZE="3! You can use this recovery in any ROM.
Click to expand...
Click to collapse
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.

What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk

Androbots said:
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
Click to expand...
Click to collapse
Can I flash this on 2gb ram variant?

lordsh said:
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Look at the thread in the development section.. Here is the feature list. Anyway the main difference here is that RedWolf is based on the latest TWRP base and it also support AOSP 8.0.0 based ROMs
rohan_45 said:
Can I flash this on 2gb ram variant?
Click to expand...
Click to collapse
Yup

In ZCX the system img file (size more than 1 gb) is stored in sdcard. Do RedWolf also stores the system img file in sdcard ? (for incremental ota updates)

What if i edit build.prop...will i still be able to update incremental updates??

is that really ota update working on it??anyone tested??

umang0712 said:
What if i edit build.prop...will i still be able to update incremental updates??
Click to expand...
Click to collapse
Depends on what will you edit.

I can't save my custom settings, like reverse nav bar, system time etc. It is auto defaulted after every reboot. How can I save them?

Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.

M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys

kg hggggg tightly said:
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
Click to expand...
Click to collapse
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me

dudemathai said:
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
Click to expand...
Click to collapse
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?

kg hggggg tightly said:
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
Click to expand...
Click to collapse
I don't think you need to flash it when you change roms,what I know is that lazyflasher bypasses miui so that you won't be stuck in bootloop while you flash anything into miui

otyg said:
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
Click to expand...
Click to collapse
What problem are you facing? This recovery seems better and updated than ZCX.
Sent from my Redmi Note 3

can i use magisk with this?

rs168 said:
can i use magisk with this?
Click to expand...
Click to collapse
Yes

is this support with newest miui 9..?

xerocracker said:
is this support with newest miui 9..?
Click to expand...
Click to collapse
Yes
Sent from my Redmi Note 3 using XDA Labs