Database Info

[Q] Back to stock recovery B137SP03 without recovery image

Hello all,
I have been going slightly mad today trying to get my mate 7 2GB back from CWM to stock recovery. The main problem is that I do not have a stock recovery image. But after being shown where to find one, I noticed that I could not get it successfully flashed either.
Since I do not really know how to do this, I used flashify, but that did not work and either returned me to the CWM or sent me to rescue.
Can someone help me to a) get a stock recovery image for the Mate 7 version MT7-L09 and b) show me how to properly flash it?

Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?

djzero86 said:
Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?
Click to expand...
Click to collapse
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?

Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device

dekraan said:
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?
Click to expand...
Click to collapse
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
Ali_adel_medo said:
Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device
Click to expand...
Click to collapse
You have a unlocked bootloader???

Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more

Ali_adel_medo said:
Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more
Click to expand...
Click to collapse
Do you tried flash via fastboot ?
fastboot flash recovery recovery.img
Or try to use this tool
http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424
This should work.

The fast boot just stucks at waiting for device
And the tool you send says that the stock recovery works only on tl_09 and my device is tl_10

djzero86 said:
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
You have a unlocked bootloader???
Click to expand...
Click to collapse
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?

I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
dekraan said:
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?
Click to expand...
Click to collapse
Ok.... you have the stock recovery now???

djzero86 said:
I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
Ok.... you have the stock recovery now???
Click to expand...
Click to collapse
I think so. If stock looks like I described: black screen, large EMUI logo, and the options reboot system now, wipe data/factory reset and wipe cache partition?

That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...

djzero86 said:
That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...
Click to expand...
Click to collapse
Great, thank you for your fantastic help!
I will get a new micro-sd card tomorrow, and will try it right away!

Good luck... come back to report

djzero86 said:
Good luck... come back to report
Click to expand...
Click to collapse
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??

dekraan said:
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??
Click to expand...
Click to collapse
Ok, I just reinstalled the B137P03 version from the how to install lollipop thread, and that went successful. Now going to try the update.zip! Keep you posted

Ah, now we're talking It seems to have worked. Phone is now showing 'Android is upgrading' and 'optimising app.....'
Great! It does seem strange I had to reinstall the B137SP03 rom, but that did the trick!

'warning bootloader unlocked, stuck on this screen after trying to flash

after trying to flash with twrp merlin .img file my phone is stuck on the warning bootloader unlocked screen . please help me as this is the only device that i have right now.

Merlin is the codename for Moto G Turbo, is that your device?

siredux said:
Merlin is the codename for Moto G Turbo, is that your device?
Click to expand...
Click to collapse
yes that is . motorola g turbo. what am i supposed to do now with my phone stuck on warning screen??

Are you hit ok when twrp ask to install supersu? If yes , restore your twrp backup and install supersu by your own , supersu 2.62.3 has no bootloops.

antonyjude30 said:
Are you hit ok when twrp ask to install supersu? If yes , restore your twrp backup and install supersu by your own , supersu 2.62.3 has no bootloops.
Click to expand...
Click to collapse
the only thing my phone does it stops on the bootloader screen i can only access only the recovery mode somehow and nothing else. it shows the teamwin screen. i dont knw wat to do after that. it was the latest supersu zip and i dont know wat went wrong.

flash the stock recovery or flash stock firmware.

xlr8sonic said:
the only thing my phone does it stops on the bootloader screen i can only access only the recovery mode somehow and nothing else. it shows the teamwin screen. i dont knw wat to do after that. it was the latest supersu zip and i dont know wat went wrong.
Click to expand...
Click to collapse
Did you make a TWRP back up before flashing SuperSU?

MrTooPhone said:
Did you make a TWRP back up before flashing SuperSU?
Click to expand...
Click to collapse
no i did not.
what can i do now

HelpMeruth said:
flash the stock recovery or flash stock firmware.
Click to expand...
Click to collapse
how can i do that ?

xlr8sonic said:
no i did not.
what can i do now
Click to expand...
Click to collapse
Without a backup, your only option is to re-flash stock firmware.

xlr8sonic said:
yes that is . motorola g turbo. what am i supposed to do now with my phone stuck on warning screen??
Click to expand...
Click to collapse
If I were you I would download stock firmware and flash it via fastboot to avoid any further inconviniences

I recommend flashing your factory firmware, which can easily be found on the forums here

siredux said:
If I were you I would download stock firmware and flash it via fastboot to avoid any further inconviniences
Click to expand...
Click to collapse
its is showing baseband error .. will it be gone if if i flash its firmware

xlr8sonic said:
its is showing baseband error .. will it be gone if if i flash its firmware
Click to expand...
Click to collapse
Sorry man , baseband errors normally result in no mobile network and ability to make phone calls :/. When I flashed marshmallow on my phone , it said not found next to baseband. You may want to fully flash MM then when it gets to bootloader unlocked screen , wait a few minutes. If it does nothing, try flashing twrp recovery and flashing a lollipop custom rom.
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
xlr8sonic said:
its is showing baseband error .. will it be gone if if i flash its firmware
Click to expand...
Click to collapse
Also what baseband error are you getting ?

therealduff1 said:
Sorry man , baseband errors normally result in no mobile network and ability to make phone calls :/. When I flashed marshmallow on my phone , it said not found next to baseband. You may want to fully flash MM then when it gets to bootloader unlocked screen , wait a few minutes. If it does nothing, try flashing twrp recovery and flashing a lollipop custom rom.
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
Also what baseband error are you getting ?
Click to expand...
Click to collapse
i attatched the imafe of the screen . i dnt knw exactluy wat baseband error it is

xlr8sonic said:
i attatched the imafe of the screen . i dnt knw exactluy wat baseband error it is
Click to expand...
Click to collapse
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that

xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.

MrTooPhone said:
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
Click to expand...
Click to collapse
it says could not find ,META-INF/com/google/android/update-binary, int the zip file
error installing zip file xt1557_merlin_ritasia_6.0

Mate , no one noticed that you are trying to flash the ota zip in recovery. you are not meant to do that. Flash it using Fastboot. Go download Motorola device manager to get the right drivers, and get minimal adb and fastboot, when you have done that, come back here !
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
You do realise you are trying to flash firmware files via recovery right..?
You are meant to extract the zip on the pc and then flash the files using fastboot commands
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
MrTooPhone said:
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
Click to expand...
Click to collapse
that trying to flash ota firmware files in twrp . that's why it failed

xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
Try using mfastboot instead of fastboot, go with 6.0 firmware, make sure you flash all sparsechunks included. Baseband should be restored

ROOT-TWRP-UNLOCK BOOTLOADER FOR LENOVO K6 NOTE (K53a48)

I am not responsible if you don't know
what you are getting into and end up messing up your phone
In order to root K6 Note you need to do the following,
1. Unlock boot loader. how to do that follow here >>
http://lenovo-forums.ru/topic/21685-lenovo-vibe-k6-note-разблокировка-bootloader
( It will Wipe all Data)
2. Install Twrp from here>>
http://lenovo-forums.ru/topic/21687-lenovo-vibe-k6-note-rasshirennoe-rekaveri-twrp-by-sevenmaxs/
3. Modify boot image and flash modified boot image with Carliv Image Kitchen from here >>
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
4. Changing Values in boot.img
Unpack the boot image using the above tool, once unpacked go the unpack folder then into ramdisk folder and edit the default.prop using notepad++ or wordpad
Change the value of the following lines
1. ro.secure=1 to ro.secure=0
2. security.pref_harden= 1 to security.pref_harden= 0
(Change only 1 to 0 nothing else & do not forget to save the file )
3.Once done repack the boot image using the above tool.
5 .Flash the modified boot.image through fastboot, how to flash through fastboot refer here>>
https://forum.xda-developers.com/showthread.php?t=1752270
6. Reboot into recovery and flash supersu from here>>
https://download.chainfire.eu/1001/S…perSU-v2.78-20
The supersu installation should be successful now. reboot and you will see supersu app in the app drawer. Cheers :good::good::good::good:
(P.S I have attached the modified boot image for firmware k53_s123_170216_ROW, so no need to modify the boot image if you are on this firmware.)

Where is the attached k53_s123_170216_ROW boot image ?

mehmet6ok said:
Where is the attached k53_s123_170216_ROW boot image ?
Click to expand...
Click to collapse
Boot.img updated. Cheers

Sounds interesting thanks as I keep getting errors trying to flash SuperSU or Magisk.
I'm on firmware k53_s123_170216_ROW so I will be able to use your boot.img but how would one go about getting the boot.img to modify ? The Nandroid backup is in the boot.emmc.win format and the whole partition I suppose ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
Oops so I flashed your boot.img :
tools>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (24894 KB)...
OKAY [ 0.816s]
writing 'boot'...
OKAY [ 0.331s]
finished. total time: 1.151s
Click to expand...
Click to collapse
At the end on the screen it says in green at the top "flashing boot ...", rebooted into TWRP 3.0.3.0 with long "VOL UP+VOL DOWN" + "POWER" press.
Tried to install :
- UPDATE-SuperSU-v2.78-20160905010000.zip (the one you mention)
- SuperSU-v2.79-201612051815.zip
- Magisk-v12.0.zip
But they all fail unfortunately, same error message as before flashing your boot.img :
Magisk12 error :
"Unable to unpack boot.img"
SuperSU error :
"-Extracting ramdisk
--- Failure, aborting"
My model is K53a48
---------- Post added at 08:50 AM ---------- Previous post was at 08:36 AM ----------
ok, I updated to TWRP-3.1.0.1_K53a48_by_SevenMaxs.7z and I was able to flash SuperSU-v2.79-201612051815.zip without errors. All booted up and SuperSU in the app drawer and rooted, thanks for the tips, man !
A few more questions if I may :
- is there a stock recovery to put back the K6 Note in factory mode ?
- how does one go about getting the boot.img out of a device for patching ?

If will not modify the boot.img what will gonna happen?
Thanks to this furom....Really help for me

webvan said:
Sounds interesting thanks as I keep getting errors trying to flash SuperSU or Magisk.
I'm on firmware k53_s123_170216_ROW so I will be able to use your boot.img but how would one go about getting the boot.img to modify ? The Nandroid backup is in the boot.emmc.win format and the whole partition I suppose ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
Oops so I flashed your boot.img :
At the end on the screen it says in green at the top "flashing boot ...", rebooted into TWRP 3.0.3.0 with long "VOL UP+VOL DOWN" + "POWER" press.
Tried to install :
- UPDATE-SuperSU-v2.78-20160905010000.zip (the one you mention)
- SuperSU-v2.79-201612051815.zip
- Magisk-v12.0.zip
But they all fail unfortunately, same error message as before flashing your boot.img :
Magisk12 error :
"Unable to unpack boot.img"
SuperSU error :
"-Extracting ramdisk
--- Failure, aborting"
My model is K53a48
---------- Post added at 08:50 AM ---------- Previous post was at 08:36 AM ----------
ok, I updated to TWRP-3.1.0.1_K53a48_by_SevenMaxs.7z and I was able to flash SuperSU-v2.79-201612051815.zip without errors. All booted up and SuperSU in the app drawer and rooted, thanks for the tips, man !
A few more questions if I may :
- is there a stock recovery to put back the K6 Note in factory mode ?
- how does one go about getting the boot.img out of a device for patching ?
Click to expand...
Click to collapse
Big Question
If I will not patch the boot.img and flash the new 3.1.0.1_K53a48_by_SevenMaxs.7z and then flash the
SuperSU-v2.79-201612051815.zip
will it be successfull?
Yeah I can't flash SuperSU-v2.79-201612051815.zip
In old twrp...SuperSu App never apper in my home drawer...
---------- Post added at 06:29 AM ---------- Previous post was at 06:06 AM ----------
Do you have a custom kernel?

Why don't you want to use the patched boot.img ?
You tried with the new TWRP-3.1.0.1 and it doesn't work ?

firemax13 said:
Big Question
If I will not patch the boot.img and flash the new 3.1.0.1_K53a48_by_SevenMaxs.7z and then flash the
SuperSU-v2.79-201612051815.zip
will it be successfull?
Yeah I can't flash SuperSU-v2.79-201612051815.zip
In old twrp...SuperSu App never apper in my home drawer...
---------- Post added at 06:29 AM ---------- Previous post was at 06:06 AM ----------
Do you have a custom kernel?
Click to expand...
Click to collapse
webvan said:
Why don't you want to use the patched boot.img ?
You tried with the new TWRP-3.1.0.1 and it doesn't work ?
Click to expand...
Click to collapse
So I need to flash the modified boot.img to flash the updated twrp and then to flash the supersu.zip successfully?
I Mean flash the modified boot.img and the updated twrp will work?

firemax13 said:
So I need to flash the modified boot.img to flash the updated twrp and then to flash the supersu.zip successfully?
I Mean flash the modified boot.img and the updated twrp will work?
Click to expand...
Click to collapse
You cannot flash supersu without the modified boot image.
You need to flash the recovery and modified boot image to successfully flash supersu.

adilrenzu said:
You cannot flash supersu without the modified boot image.
You need to flash the recovery and modified boot image to successfully flash supersu.
Click to expand...
Click to collapse
Thanks to your reply.....sorry Im so curious about it.....
So we gonna still receiving the OTA updates after flashing the modified boot.img and twrp and ROOT? .....Or we can still update our devices after all the things happen??
sorry for noob question and bad ass english

firemax13 said:
Thanks to your reply.....sorry Im so curious about it.....
So we gonna still receiving the OTA updates after flashing the modified boot.img and twrp and ROOT? .....Or we can still update our devices after all the things happen??
sorry for noob question and bad ass english
Click to expand...
Click to collapse
To receive OTA's you need to be on stock recovery, and stock boot image without any modification to the system partition.

Can the stock recovery be downloaded anywhere ? Thanks !

adilrenzu said:
To receive OTA's you need to be on stock recovery, and stock boot image without any modification to the system partition.
Click to expand...
Click to collapse
Again thanks to your reply
Still waiting for official custom rom and official custom recovery.......I hope lineage os listening to us.....

firemax13 said:
Again thanks to your reply
Still waiting for official custom rom and official custom recovery.......I hope lineage os listening to us.....
Click to expand...
Click to collapse
as for custom roms i dont think thats gonna happen anytime soon, and there is nothing like official custom recovery, there is only custom recovery like TWRP or CMW.

Hi there, mate. If I do this process, will I be able to remove TWRP if needed (for updating reasons), if so, what would the process be?

adilrenzu said:
as for custom roms i dont think thats gonna happen anytime soon, and there is nothing like official custom recovery, there is only custom recovery like TWRP or CMW.
Click to expand...
Click to collapse
So you can't reflash the original recovery ? So that means no more OTA updates, but would it still work with an official update that was downloaded, assuming one becomes available ? Thanks !

adilrenzu
I was able to unlock bootloader, installed twrp and root according to your guide
and
also successfully returned to original stock 6.0 rom, stock recovery according to androidmtk's Lenovo_K53_USR_S107_1609131839_Q00380_ROW firmware.
This is a new toy for me now. Many thanks...:laugh:

Can you explain how you went back to stock?

webvan said:
Can you explain how you went back to stock?
Click to expand...
Click to collapse
Hi
Device cant update via ota. I dont really know K53_USR_S107_1609131839_Q00380_ROW firmware is last for some region or not. So Im trying to update to stock K53_S123_170216_ROW firmware. After testing and solving ota I will write all steps.

ok, thanks, I suppose it need to be downloaded first somewhere ?

Please Help Cant boot up Or Enter Recovery!

i flashed trwp and tried booting into it and its just will not do anything and my fastboot says this. AP_S_ABNORMAL.
Please help!!
Here is a pic https://ibb.co/k3KaU5

Rommco05 said:
For enter to twrp try this
- unplug cable from phone
- turn off
- turn on and hold together on/off button + vol up
- when you see honor blue logo release on/off button but still hold vol up
edit: which twrp u flash and which actual android?
Click to expand...
Click to collapse
i did but twrp will not boot up and i used this twrp-3.1.1-1-frd and i was running stock android. right now im using fastboot to flash boot recovery cust and system to the device.

Rommco05 said:
edit: which twrp u flash and which actual android?
Click to expand...
Click to collapse
also when i try to enter twrp the phone vibrates then it vibrates again and gets stuck at your device is booting.

Rommco05 said:
edit: which twrp u flash and which actual android?
Click to expand...
Click to collapse
okay good news after successfully flashing BOOT, RECOVERY, CUST, and SYSTEM. when i go into fastboot it says cold-boot now so i have made progress

it failed

Rommco05 said:
I installed update.app via dload? Probably u install not correct rom
Click to expand...
Click to collapse
whatever is wrong with my phone it is weird. okay so i can flash the stock stuff with fastboot then let it boot and it will boot into stock but when i flash twrp i cant boot into recovery and the phone fails to boot up and when it boots into stock it says my phone is a fdr-4 but mine is fdr-14

what is the android version and build number

Rommco05 said:
You need to extract OEM from update.app and flash via fastboot after will be your model correct
Click to expand...
Click to collapse
Where is that I don't see it in my update.app

venugopalu007 said:
what is the android version and build number
Click to expand...
Click to collapse
Android 6.0. build number FRD-C567B162.

Rommco05 said:
So download from Firmwarw Finder B162 and extract this update via Huawei Extractor OEM.img and flash via fastboot >> fastboot flash oem oem.img
Click to expand...
Click to collapse
It's not there :crying:

Rommco05 said:
hm, probably it is CUST.img
Click to expand...
Click to collapse
I have already flashed that and that didn't fix it :/

I still don't understand why when I flash TWRP the phone won't boot anymore or go into recovery

Rommco05 said:
ou you flashing 3.1.1-1 twrp?
Click to expand...
Click to collapse
Yes I did flash that version. And Everytime I do the phone will no longer boot up nor will it allow me to enter TWRP ?

damenbm said:
Yes I did flash that version. And Everytime I do the phone will no longer boot up nor will it allow me to enter TWRP
Click to expand...
Click to collapse
no bro you are doing wrong , u are flashing the wrong compatible twrp
flash this twrp https://www.androidfilehost.com/?fid=24588232905723836

damenbm said:
Android 6.0. build number FRD-C567B162.
Click to expand...
Click to collapse
bro try this https://www.androidfilehost.com/?fid=24588232905723836
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
Rommco05 said:
Yes this is problem, wrong twrp
Click to expand...
Click to collapse
yes bro ,he is flashing nougat version twrp ,he has to flash mm twrp,that's y i asked him about android version

venugopalu007 said:
bro try this https://www.androidfilehost.com/?fid=24588232905723836
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
yes bro ,he is flashing nougat version twrp ,he has to flash mm twrp,that's y i asked him about android version
Click to expand...
Click to collapse
I feel like a complete moron ?? I knew I was messing up somehow ? thank you so much!!

venugopalu007 said:
bro try this https://www.androidfilehost.com/?fid=24588232905723836
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
yes bro ,he is flashing nougat version twrp ,he has to flash mm twrp,that's y i asked him about android version
Click to expand...
Click to collapse
Okay bro now to completely fix what I have done should I format data then flash stock all over again?

damenbm said:
Okay bro now to completely fix what I have done should I format data then flash stock all over again?
Click to expand...
Click to collapse
Yes bro format data reboot again and flash rhe stock firmware.
Stock firmware got 2 zips first flash the updae_hw_full.zip big name zip , next the update.zip and then reboot
Now got to recovery and do a format factory once

venugopalu007 said:
Yes bro format data reboot again and flash rhe stock firmware.
Stock firmware got 2 zips first flash the updae_hw_full.zip big name zip , next the update.zip and then reboot
Now got to recovery and do a format factory once
Click to expand...
Click to collapse
again thank you so much

damenbm said:
again thank you so much
Click to expand...
Click to collapse
You are welcome.

How to install stock recovery without losing data?

I am using Peter's recovery and wish to go back to stock recovery as installing ota is tiring. How can I do that without losing data and files?

If you are using official MIUI ROM, dirty flashing full recovery ROM will also overwrite custom recovery with stock recovery.

AbioticSpoon said:
I am using Peter's recovery and wish to go back to stock recovery as installing ota is tiring. How can I do that without losing data and files?
Click to expand...
Click to collapse
are you rooted?
if ues then just unroot using magisk unistaller and reboot it will restore stock recovery then use ota to update then again you can flash twrp peter recovery by fastboot and boot in to recovery and then flash magisk it will again have both recovery and root
my device shows encrypted status

AbioticSpoon said:
I am using Peter's recovery and wish to go back to stock recovery as installing ota is tiring. How can I do that without losing data and files?
Click to expand...
Click to collapse
Just download the fast boot rom from the official website and flash it by mi flash tool.
And during flashing it select flash all except data.
And you will lose nothing and your recovery will be restored.
Then you can flash ota by that.
---------- Post added at 08:23 PM ---------- Previous post was at 08:21 PM ----------
blueandro said:
are you rooted?
if ues then just unroot using magisk unistaller and reboot it will restore stock recovery then use ota to update then again you can flash twrp peter recovery by fastboot and boot in to recovery and then flash magisk it will again have both recovery and root
my device shows encrypted status
Click to expand...
Click to collapse
Really?
I should try this.
Have you tried this, what is the concept behind this?
How can unrooting can restore stock recovery?

yes i have tried it and i m on latest stable 10.3
13

blueandro said:
yes i have tried it and i m on latest stable 10.3
13
Click to expand...
Click to collapse
Complete uninstall or just restore image option?
---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------
blueandro said:
yes i have tried it and i m on latest stable 10.3
13
Click to expand...
Click to collapse
And are u encrypted? Means does twrp ask for screen lock password during going to recovery?

gautamajay52 said:
Complete uninstall or just restore image option?
---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------
And are u encrypted? Means does twrp ask for screen lock password during going to recovery?
Click to expand...
Click to collapse
using peters recovery latest one
i m not using my fone with lock password so it didn't ask

blueandro said:
using peters recovery latest one
i m not using my fone with lock password so it didn't ask
Click to expand...
Click to collapse
Ok... I will try this... wating for new update that i can verify it too.
Thanks

I have one solution
simple
just things needed are:
1. miui stock recovery img
2. vbmeta
next,
1. First flash recovery image.
2. Then flash vbmeta image.
what does vbmeta do. it actually saves the recovery image after flashing new recovery.
3. Finished reboot