[Recovery] EVA NoCheck Recovery - Flash unapproved OTA firmwares!

Atarii

Senior Member
May 10, 2011
734
652
0
Overview
This is a patched recovery image which bypasses the usual checks performed during a firmware flash, allowing you to flash unapproved OTA firmwares. For example, the latest FullOTA-MF b394:



You can also downgrade without using the b300 rollback package (untested)

Prerequisites
  • Unlocked bootloader
  • Rooted
  • Backup your data (flashing may cause bootloader to re-lock or restore factory default etc. - don't blame me if it goes wrong!)

Instructions
Download firmware:
  • Use Huawei Firmware Finder (Play Store link) to download the latest firmware files - you will need all 3 zip files:
    - update.zip
    - update_data_full_public.zip
    - update_full_EVA-L09_hw_eu.zip

Tips: check for the latest number (102064 for b394) and ensure you have the larger filesize (around 2GB). For example, these are the latest at time of writing b394:


Flash nocheck recovery:
  • Reboot device to fastboot mode (power off fully, hold down volume button and connect USB cable)
  • Run the following to flash recovery:
    Code:
    fastboot flash recovery eva_l09b391_nocheckrecovery.img
    fastboot reboot

Send commands via ADB
  • Phone should be booted back to system - connect phone via adb and allow root prompt:
    Code:
    adb shell
    su
  • Create HWOTA folder:
    Code:
    mkdir /data/update/HWOTA
  • Copy firmware to HWOTA folder (replace 102064 below with correct value - this is for b394):
    Code:
    cp /sdcard/HWFF/102064/update* /data/update/HWOTA/
  • Paste recovery command:
    Code:
    echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
    echo "--update_package=/data/update/HWOTA/update_data_full_public.zip" >> /cache/recovery/command
    echo "--update_package=/data/update/HWOTA/update_full_EVA-L09_hw_eu.zip" >> /cache/recovery/command
    exit
  • Finally reboot to recovery to start firmware upgrade:
    Code:
    adb reboot recovery
  • Firmware should install and reboot automatically :)

Extras
You can probably Re-Brand to alternative customers too i.e. c636 (Asian region) to c432 (European region). Follow the tutorial here: https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886 - you'll need the correct OEMINFO files, this is untested.

Thanks
- Olddroid
- Mankindtw
- Hackslash
- DkiOnline (L09 tester)
- jimz6 (L19 tester)
- LastStandingDroid

XDA:DevDB Information
EVA NoCheck Recovery, Tool/Utility for the Huawei P9

Contributors
Atarii

Version Information
Status: Stable

Created 2017-11-14
Last Updated 2017-11-17
 
Last edited:

ekhi

New member
Nov 7, 2017
3
0
0
updated succesfully.
only two points, on prerequisites I think you should add that the phone should be rooted cause after I flashed the nochechrecovery I needed to reflash twrp and root.
and the second point is that there is missing a / before de * in the step when you copy the 3 zips to data.
nice to know there is a method to bypass the verification on firmwares :good::good:
 

kukubau

Senior Member
May 24, 2015
114
25
0
Hamburg
You haven't read OP #1?
You didn't understand my question.

Can one modify the recovery.img from another firmware package, other than B391?

Let's say I'd like to do a HEX file diff between two image files and modify the img file myself.

Is this possible? What should I look for?

For learning purposes.
 
Last edited:

Atarii

Senior Member
May 10, 2011
734
652
0
You didn't understand my question.

Can one modify the recovery.img from another firmware package, other than B391.

Let's say I'd like to do a HEX file diff between two image files and modify the img file myself.

Is this possible? What should I look for?

For learning purposes.
You can use this recovery with any firmware and ignore the version - I just used b391 as the base as that's the firmware I was on at the time.

You can't modify other recovery images by diffing the hex - you need to disassemble the recovery binary and overwrite the checks with arm assembly
 
  • Like
Reactions: kukubau

kukubau

Senior Member
May 24, 2015
114
25
0
Hamburg
You can use this recovery with any firmware and ignore the version - I just used b391 as the base as that's the firmware I was on at the time.

You can't modify other recovery images by diffing the hex - you need to disassemble the recovery binary and overwrite the checks with arm assembly
Thanks for the clarification.

I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.

I'll try the B390 OTA later today, to see if it makes a difference.
 

dkionline

Senior Member
Oct 15, 2012
2,449
1,810
193
Thanks for the clarification.

I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
if not, boot up and hold vol+ like you would enter to twrp, then it should flash automatically.
 

Atarii

Senior Member
May 10, 2011
734
652
0
Thanks for the clarification.

I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.

I'll try the B390 OTA later today, to see if it makes a difference.
Did you use the 2GB file?
 

kukubau

Senior Member
May 24, 2015
114
25
0
Hamburg
Did you use the 2GB file?
Yes.

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------

if not, boot up and hold vol+ like you would enter to twrp, then it should flash automatically.
I've flashed my phone and unbricked it hundreds of times.

I've even posted an unbrick guide here on XDA forums.

I guess I know how to force flash it using the three key combo.
 

dkionline

Senior Member
Oct 15, 2012
2,449
1,810
193
Yes.

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------



I've flashed my phone and unbricked it hundreds of times.

I've even posted an unbrick guide here on XDA forums.

I guess I know how to force flash it using the three key combo.
Im not using 3 key, only 1.
If not boot, you have manually boot with key i posted before.