Database Develop

Bootloader version 3.41 problems

I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34

I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.

how do you flash the old bootloader? if you don't mind me asking.

I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.

ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus

You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063

I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.

anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.

Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse

Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.

Bricked Phone

Ok so I tried to flash a new rom and image onto my phone and well unfortunately now I can't enter recovery or do anything really. I still have access to the bootloader but nothing else. I have tried to factory reset my phone and that didn't work. The rom I was coming from was the latest viper one with Clockwork Recovery and I was going to the latest android revolution with twrp. I really have no idea what else I can do. Please help. Oh yeah I should mention my computer is not playing well with adb currently

Reflash recovery via fastboot --> fastboot flash recovery recoveryname.img
Enter recovery.
Flash the ROM

Julio209 said:
Ok so I tried to flash a new rom and image onto my phone and well unfortunately now I can't enter recovery or do anything really. I still have access to the bootloader but nothing else. I have tried to factory reset my phone and that didn't work. The rom I was coming from was the latest viper one with Clockwork Recovery and I was going to the latest android revolution with twrp. I really have no idea what else I can do. Please help. Oh yeah I should mention my computer is not playing well with adb currently
Click to expand...
Click to collapse
It's not bricked you just have to reflash the recovery.
Go into the bootloader on your phone, then fastboot, and plug into your pc.
Download the last recovery TWRP. Open a command on the sdk fastboot folder:
Code:
fastboot flash recovery "recovery.img"
Where "recovery.img" stands for the name of the recovery downloaded.

How to flash images with fastboot?

My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?

revery0 said:
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
Click to expand...
Click to collapse
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.

arthios said:
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
Click to expand...
Click to collapse
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success

revery0 said:
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
Click to expand...
Click to collapse
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?

87insane said:
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
Click to expand...
Click to collapse
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...

revery0 said:
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
Click to expand...
Click to collapse
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.

87insane said:
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
Click to expand...
Click to collapse
Thank you but I already did flash the official recovery image, both extracted from a factory update.app and your recovery.IMG also... None of them worked.... Iam still in the same bootloop.
I am starting to believe that the partitions have been ****ed up.
Any way to repartition?
Also is there a procedure to create a flashable zip with huawei software extractor? I edited the accompaning XML to add the p7 device on the list (copy data from p6 and changed the name) created the zip but fastboot doesn't flash the zip because its missing 2 XML files which I can't remember their name.
And at this point I would like to give my 2 cents of advice to everyone who might listen,
Before you flash anything from a microsd, first verify the card with h2testw, and always use high quality microsd and never ever stop a flashing procedure by any means. . i would like to make it more extreme and advise to use a software with copy verification (like richcopy) when you copy files that are going to be flashed.
I tend to believe that a faulty microsd is the cause of my problems... Even though I checked the microsd afterwards and didn't got any errors.
I would advise the ROM creators to append this on their posts!

Unlocked Bootloader, Can't root? [XT1096]

Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...

I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html

There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.

RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.

oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.

So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!

TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.

Redmi 4X bootloop after installing TWRP?

Hi,
I'm having a bit of trouble. I had a brand new Redmi 4X, and I was advised to install TWRP, root it, and install the Xiaomi.eu rom until LineageOS is released. I unlocked the bootloader, flashed TWRP, managed to get into it once and now I can't do it again. When TWRP loaded it asked me for a password for decryption but it let me just skip it it seems (not sure if that is the problem) but now I can't boot normally, I can't boot into recovery, but fastboot seems to work okay. How do I go about fixing this?
I've tried reflashing TWRP but I still can't get to it, and I don't really know enough about this stuff to know where I've gone wrong.
UPDATE - I think this is to do with dm-verity and having the stock kernel installed. Now it's too late to undo what I've already done, so I hope to god that someone knows how to fix this.
UPDATE - Right, the problem is solved I think. I had to do an awful lot of googling, and I'm not entirely sure what it was specifically that fixed it. But I found a guide that taught me the fastboot command "fastboot boot twrp.img" which saved the day. Even when my phone wouldn't let me into recovery, it allowed me to flash a no-verity.zip which i think is what allowed me to boot, and it allowed me to flash superSU.zip and then the ROM I was aiming for. And now I've booted into the ROM successfully and hopefully I am rooted and all is well. Plus I can access TWRP as normal now.
Any help would be greatly appreciated

Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.

brljak83 said:
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
Click to expand...
Click to collapse
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?

brokemyG2 said:
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
Click to expand...
Click to collapse
Hii
I just have been reading about this bootloop
Go over here and read all of the 6 pages..will not take much time but could help you out much
https://forum.xda-developers.com/xiaomi-redmi-4x/development/official-twrp-3-2-1-0-xiaomi-redmi-4x-t3718217

Hey, I have exactly the same problem. Latest stock rom, flashed twrp in fastboot and got into the boot loop. Nothing works. I can only enter fastboot. What exactly did you do then? What is this no-verity.zip? I can't find anything about it.

I had a problem
I unlocked bootloader then installed redwolf recovery and took a nandroid backup. After that i rebooted to system but stuck into bootloop, could not boot to recovery, could not boot into system, So the only thing worked was that i flashed fastboot rom with mi flasher. And syccessfully rebooted to system with bootloader locked and stock recovery. So, if anyone have same problem you can do the same. How do i install recovery safely again? Should i use TWRP only? Should i flash v3.1.0 with lazy flasher or v3.2 directly without lazy flasher? I don't want to stuck into bootloader again, have to get all data deleted.