Stock recovery extraced from BTV-W09C233B019 ROM - untested

[sselpeelsxx]

Hi M3 users,

I'm a long time lurker and reader on XDA. Now it's time to give something back or at least participate
Following my recent M3 purchase a dugg a bit deeper into this topic and tried to get us the stock recovery for our devices.
I'm not really a dev. I just used the information I found here and in the russian forum where greatslon (thank you guy) is posting his work.
If you find an error in the process please let me know. The files have not been tested in any way. I have no idea if this would even work (encryption and so on).
So I managed to extract the recovery.img file from the chinese rom. This method will also work for the LTE variant.

Maybe @greatslon or @somboons can share their view on the topic or maybe @somboons can even use it in his tool.

Resources
http://4pda.ru/forum/index.php?showtopic=780572&st=120
http://forum.xda-developers.com/showthread.php?t=2433454
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder

Tools used
Huawei Firmware Finder (Team MT)
Huawei Update Extractor

Download
M3_BTV-W09C233B019_recovery.zip

Process
1. Start firmware finder (did use the android version)
2. Change device to BTV-W09C233
3. Downloaded the firmware B019 for BTV-W09C233 (no firmware for other variants present ATM)
4. Extracted and copied update.app to SD card
5. copy to PC
6. Extract recovery.img and recovery2.img using Huawei Update Extractor

Best regards,
Benjamin

 

[Slavon-93]

Don't quite understand what's this for. First of all, recovery should be the same version as your ROM. I don't know if their mismatch will immediately lead to some malfunction, but some people on 4pda said they should match. Second - stock recovery's functions are limited to factory reset (wiping data, cache, etc.) and installing OTA updates. Without changing OEMINFO (and it's still unconfirmed), you won't be able to install any OTA except those, intented for your model and region, so again there's no need to install a higher version of recovery than your ROM is. But anyway, thank you for the extraction instruction.

P.S. I think there's no need to flash both recovery and recovery2. Recovery2 can be successfully replaced with TWRP and this combination is really great, cause you can launch TWRP by holding Volume Up button only.
And the only reason why you should keep recovery original is that it doesn't really wipe /data - it also creates some files there like custom.bin, containing your regional settings.

 

[sselpeelsxx]

Hi Slavon,

Thanks for your highly appreciated comment. @somboons was looking for a stock recovery so I thought this might help.
Your given information are really helpful. I did not know that you could flash TWRP in recovery2 and replace erecovery Handy information.
I'm pretty new to the Huawei structure so always glad to learn something.

EDIT
A lot of good information can be found here: http://forum.xda-developers.com/honor-7/general/dual-recovery-honor-7-t3308398

Thank you very much,
sselpeelsxx

 

[0D0A]

Giving Back

Benjamin,

I've also been a long time XDA lurker. Most of the devices I have owned were mainstream and thus already had a very active XDA developer community; Even if root had yet to be achieved, there would be hundreds of messages on the topic.

It seems the Mediapad M3 is just getting started. I am a developer of over 20 years, but very little android experience. However, I have recently spent a considerable amount of time (about 50-100 hours) working with the low level ADB protocol source code. And I have rooted and flashed no less than 50 devices, everything from cell phones to Android TV devices to routers.

I'm going to take this device on as my first real dev effort in this arena.
I have a few goals:

1. Get working backups for people that soft-brick or need to revert (including myself).
2. Recompile TWRP for the M3 to confirm greatslon's work, and better understand the process.
3. Release a stock rom that's pre-rooted and cleaned up (not that there was a lot of bloat on my device).
4. Release a custom rom that's not MIUI (perhaps based of CyanogenMod).

Since I have virtually no experience, I am sure these goals are quite lofty and will take some time. But hey, you got to have a plan, and I don't have anything else to work on right now.

Let me know if you want to work on anything together, or if you need any help with anything development related.

- 0D0A

 

[sselpeelsxx]

Hey hey 0D0A,

I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work

Best regards,
Benjamin

 

[gardwired]

can flash twrp via fastboot but get error saying and no recovery

hi, first thanks greatslon for doing the work on m3.

i seem to have succeeded in getting stuck and can't get it to boot into your custom twrp. adb on linux was working fine, but no longer. ditto for fastboot just get "waiting for devices" now. i switched to win10 and installed the hisuite app so i can use fastboot but still no adb. so i have tried to flash recovery and recovery2 but when i try to boot recovery i get error "Func NO: 11 (recovery image) ERROR NO: 2 (load failed)."

i then downloaded your custom rom and tried to flash the boot for that still no luck. i can't use adb so i am not sure how to just flash the custom rom with fastboot without being able to get into any recovery.

i did have this all rooted and working with your twrp but kept having issues with dpi and there was an ota update (b003) which wouldn't apply. so i tried to restore backup and it wen't south from there. basically now can't do much other than see the unlock "can't be trusted" page and bootloader.

any suggestions?

 

[polynikesx]

Desperately need stock recovery img, not sure exactly what when wrong, but it is stuck in a horrible boot loop. Tried Benjamin's recovery files and they seem to remove twrp and put it somewhat back to normal, but can only access the emui recovery and that fails to load the files. Put twrp back and tried greatslon's ROMs, they load but goes back to boot loop. Wipe and format everything, install my original backup through twrp recovery, it says it works, but again, back to boot loop... at this point I think I'm dead... any ideas, any word on the official recovery img? anything? Help!!

 

[sselpeelsxx]

What device do you have? And what version were you on?

 

[polynikesx]

What device do you have? And what version were you on?

I have the M3, BTV-W09, not sure what version, MM6.0 EMUI 4.1

 

[polynikesx]

Anyone have any other ideas on horrendous boot loop?

 

[asianpianoman]

Hey hey 0D0A,

I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work

Best regards,
Benjamin

Hello, I am unlocked, TWRPed, and rooted, but am trying to reverse all of that. My build number is BTV-W09C128B002. Is it safe to download the stock recovery from the OP for my device? Or do I really need the C128 version?

 

[sselpeelsxx]

Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.

Regards

 

[asianpianoman]

Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.

Regards

Thanks! I have been able to use the Huawei Extractor to extract a recovery.img from OTA updates, but have been afraid to try flashing it. It has been recommended to hold off on trying that since that recovery.img is from an OTA and not a FULL update. Any thoughts?