which recovery.img should i pull from update.app? - Huawei Mate 9 Questions & Answers

Hi
I want to remove twrp in order to ota april patch (from .360-367).
I have extracted the update.app and there are several recovery.img.
my q is which one of the recovery should i flash via adb?
thx in advance for any help

the-light said:
Hi
I want to remove twrp in order to ota april patch (from .360-367).
I have extracted the update.app and there are several recovery.img.
my q is which one of the recovery should i flash via adb?
thx in advance for any help
Click to expand...
Click to collapse
Hi, you should not do that if don't want your phone brick.
You can use these guides:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
All of them work for me.

For future reference or troubleshooting purposes, the one you would use is recovery_ramdisk.
Flashing is done from fastboot - 'fastboot flash recovery_ramdisk recovery.img'
the-light said:
Hi
I want to remove twrp in order to ota april patch (from .360-367).
I have extracted the update.app and there are several recovery.img.
my q is which one of the recovery should i flash via adb?
thx in advance for any help
Click to expand...
Click to collapse

mp187263 said:
For future reference or troubleshooting purposes, the one you would use is recovery_ramdisk.
Flashing is done from fastboot - 'fastboot flash recovery_ramdisk recovery.img'
Click to expand...
Click to collapse
Thank you all for the help, the future looks brighter now

Related

FRD-L09C432 pre-rooted boot

FRD-L09C432 pre-root booted (superuser-r310)
1. Unlock booloader
2. Flash boot.img via fastboot
3. Install phh.superuser https://play.google.com/store/apps/details?id=me.phh.superuser
B381 Boot.img http://www.datafilehost.com/d/3204ea04
B389 Boot.img http://www.datafilehost.com/d/079e483c
B392SP01 Boot.img http://www.datafilehost.com/d/874fb9b1
Ps: i will keep update rooted boot when a new version is released, but only for L09C432.
So if I want to flash that, I have to be already on B381?
There's no need for this, as we can already root B381 through recovery using SuperSU or PHH. Also, when you flash an SU zip you can also flash the unSU zip to recover from bootloops where as flashing a boot.img has no fallback
NeophyteGS2 said:
There's no need for this, as we can already root B381 through recovery using SuperSU or PHH. Also, when you flash an SU zip you can also flash the unSU zip to recover from bootloops where as flashing a boot.img has no fallback
Click to expand...
Click to collapse
unsu zip? where's that file? is for supersu unroot?
deadko said:
unsu zip? where's that file? is for supersu unroot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=63615067
oberfeldwedler said:
So if I want to flash that, I have to be already on B381?
Click to expand...
Click to collapse
Yes.
NeophyteGS2 said:
There's no need for this, as we can already root B381 through recovery using SuperSU or PHH. Also, when you flash an SU zip you can also flash the unSU zip to recover from bootloops where as flashing a boot.img has no fallback
Click to expand...
Click to collapse
It's aimed to users that like to stay with stock recovery.
You can easy resore stock boot image via flashboot.
Hi!
Perfecto
Thank you very much.
For what is this? (Para qué sirve esto?)
TheDave86 said:
For what is this? (Para qué sirve esto?)
Click to expand...
Click to collapse
Root.
B389 rooted Boot.img added to first post
B392SP01 rooted Boot.img added to first post.
Thanks bro .
Thanks a lot. But how can i change my AL10C000 to L09C432?
n_polo said:
Thanks a lot. But how can i change my AL10C000 to L09C432?
Click to expand...
Click to collapse
? Have to rebrand.
venugopalu007 said:
? Have to rebrand.
Click to expand...
Click to collapse
Yes,use some apps. Then , I can flash L09C432B360 and update to B392 of eu.
Can you add b399 version?

Mi A1 Android Pie 10.0.9.0 Official Fastboot Rom link (bigota)

http://bigota.d.miui.com/V10.0.9.0....0.PDHMIXM_20190514.0000.00_9.0_3ded3e7b82.tgz
Is this final release? how did you find it?
http://en.miui.com/download-333.html
alienspl said:
http://en.miui.com/download-333.html
Click to expand...
Click to collapse
This is developer rom right? This is for test?
This oficial ROm MIA1 ,OTA
alienspl said:
This oficial ROm MIA1 ,OTA
Click to expand...
Click to collapse
How i can flash this? I have unlocked but i have still 8.0 with root. I can do this without clean personal data?
All you need to do is update in your phone's settings. Or in this way. http://en.miui.com/thread-807252-1-1.html
https://www.youtube.com/watch?v=z3ByqpYquQY&t=232s
Easiest way to upgrade without losing data is to reboot to bootloader, then use ADB tools and run the below commands:
Fastboot flash system system.img
Fastboot flash boot boot.img
(Copy system.img and boot.img from .tgz file)
Upgrade worked perfectly for me.
rambojambo21 said:
Easiest way to upgrade without losing data is to reboot to bootloader, then use ADB tools and run the below commands:
Fastboot flash system system.img
Fastboot flash boot boot.img
(Copy system.img and boot.img from .tgz file)
Upgrade worked perfectly for me.
Click to expand...
Click to collapse
And realy better is this pie than oreo?

BLU V50

Anyone have a root method for the BLU V50? Thanks in advance
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
I managed to find a way. Lol I'm just going to have to squeeze the old brain to to get this done it looks like. Thanks for the tip. The methods provided all require a system dump of stock firmware to patch TWRP for the phones recovery partition. I may have to cross my fingers and flash the generic unofficial boot image TWRP for android 10 and hope it fits lol. There are absolutely no custom fits at the moment. Of course I accepted the security patch update which made this a bit more tricky. QP1A.190711.020. I found a thread talking about almost the same update except it was two digits more than the version I got. It's been 6 or 7 years since I stopped theming for the galaxy s3. Course I was only changing xmls and pngs for custom roms back then. None of my old team are active anymore. Team Venum and team nOObz are long history. I even lost my log in info for my old profile. Anyways. Wish me luck. I'm going to learn how to port and develope this time around.
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
Hello. Thanks again in advance. I've tried several command prompt methods to unlock this boot loader with no luck including the Magisk method. I have however managed to patch the TWRP file.
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
I managed to patch the TWRP boot image using the Magisk apk and patch tools but I have no luck unlocking the boot loader..
1. find your firmware file by searching this forum for blu stock firmware repository
2. extract your boot/recovery img file using spd flash tool
3. patch img file with magisk, re-sign it with avbtools
4. patch vbmeta file with avbtools
5. re-flash both vbmeta and boot/recovery using spd research tool
rooted my blu advance l5 with these steps learned from hovatek. ymmv
luridphantom said:
1. find your firmware file by searching this forum for blu stock firmware repository
2. extract your boot/recovery img file using spd flash tool
3. patch img file with magisk, re-sign it with avbtools
4. patch vbmeta file with avbtools
5. re-flash both vbmeta and boot/recovery using spd research tool
rooted my blu advance l5 with these steps learned from hovatek. ymmv
Click to expand...
Click to collapse
Can anyone quickly tell me the easiest way to brick this device? My wife will buy me a new phone "when this one stops working"
Did anyone manage to root this device without bricking it? Firmware is not available in the Blu Repo (at least not yet). Our team would love to find a workable method for this phone. We have access to a bunch and want to be able to run Linux Deploy on them and also write app to automatically reboot the phone if the network connectivity is loss.
Hey, I was able to figure out how to deal with this bootloader stuff after many hours of work
Give this thread a look, it pretty much details every step needed to unlock the bootloader: https://forum.hovatek.com/thread-32287.html
Keep in mind that the OP of that thread is using a way older version of fastboot. For me, r26.0.1 worked best:
Windows: https://dl.google.com/android/repository/platform-tools_r26.0.1-windows.zip
Mac: https://dl.google.com/android/repository/platform-tools_r26.0.1-darwin.zip
Linux: https://dl.google.com/android/repository/platform-tools_r26.0.1-linux.zip
The above step is essential as newer versions of fastboot do NOT have the "fastboot flashing unlock_bootloader <bin>" step
again YMMV, but good luck
Me again, 6 hrs after the fact
Trial and Error enabled root on the V50 - follow these steps
1. Unlock bootloader as above
2. Create a custom signed vbmeta https://forum.hovatek.com/thread-32664.html (I used the same .pem from https://forum.hovatek.com/thread-32287.html to do this) - Make sure the VBMETA IS ANDROID 10 despite G0350WW firmware saying it's Android 9
3. Create custom boot with magisk (plenty of instructions to do this online, go with the github instructions)
4. Sign the custom magisk boot with THE SAME PUB KEY FROM STEP 2
5. Flash your new vbmeta and boot onto your phone via fastboot
6. Reboot, hope and pray it turns on
This is what worked for me, but again YMMV.
njoaquin said:
Me again, 6 hrs after the fact
Trial and Error enabled root on the V50 - follow these steps
1. Unlock bootloader as above
2. Create a custom signed vbmeta https://forum.hovatek.com/thread-32664.html (I used the same .pem from https://forum.hovatek.com/thread-32287.html to do this) - Make sure the VBMETA IS ANDROID 10 despite G0350WW firmware saying it's Android 9
3. Create custom boot with magisk (plenty of instructions to do this online, go with the github instructions)
4. Sign the custom magisk boot with THE SAME PUB KEY FROM STEP 2
5. Flash your new vbmeta and boot onto your phone via fastboot
6. Reboot, hope and pray it turns on
This is what worked for me, but again YMMV.
Click to expand...
Click to collapse
to be clear, the v50 uses the same firmware as the g50 plus?
dtingley11222 said:
to be clear, the v50 uses the same firmware as the g50 plus?
Click to expand...
Click to collapse
Correct, you can see it when you go to the firmware details of the v50 itself. You can get the firmware files when you search this forum for blu stock firmware repository
V50 is essentially a re-wrapped g50
njoaquin said:
Correct, you can see it when you go to the firmware details of the v50 itself. You can get the firmware files when you search this forum for blu stock firmware repository
V50 is essentially a re-wrapped g50
Click to expand...
Click to collapse
Hey, is there any way you could get me a rooted image and signed vbmeta? I have all the information that you would need, I just can't do the steps because im stupid. I would pay you to do it if you wanted
If the BLU V50 uses the same stock rom as the blu g50, if someone were to give out their patched vb meta and boot img, wouldn't it work for anyones BLU V50 if they just flashed it?
dtingley11222 said:
If the BLU V50 uses the same stock rom as the blu g50, if someone were to give out their patched vb meta and boot img, wouldn't it work for anyones BLU V50 if they just flashed it?
Click to expand...
Click to collapse
you need to patch recovery flash it back using the spreadtrum research tool and use the key combo to boot into root
luridphantom said:
you need to patch recovery flash it back using the spreadtrum research tool and use the key combo to boot into root
Click to expand...
Click to collapse
If I unlock the Bootloader, could I just flash it back with Fastboot?
Just tried flashing recovery and it bricked my phone
dtingley11222 said:
If I unlock the Bootloader, could I just flash it back with Fastboot?
Click to expand...
Click to collapse
you cant unlock the bootloader. follow this tutorial or you'll keep bricking your v50
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
luridphantom said:
you cant unlock the bootloader. follow this tutorial or you'll keep bricking your v50
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
Click to expand...
Click to collapse
Actually you can unlock the Bootloader. I already did. I don't know how to follow that tutorial. If I gave you my boot and vbmeta could you do it for me?
https://drive.google.com/file/d/1q1vt6f6-0Wg6iF4prOJS2o9ZauWM4qNy/view?usp=sharing : vbmeta
https://drive.google.com/file/d/1gEV2jxhnmmjKuUaqVhqPnH9oZNmzZBGi/view?usp=sharing : boot
dtingley11222 said:
Actually you can unlock the Bootloader. I already did. I don't know how to follow that tutorial. If I gave you my boot and vbmeta could you do it for me?
Click to expand...
Click to collapse
oh weird i thought blu doesnt even support bootloader unlocking
can you access fastboot? with an unlocked bootloader you can flash an empty vbmeta and dont have to go through the above steps

rooting c.36

can i use c.33 patched boot img to root c.36 ? or i need to downgrade to c.33 ?
MevishL said:
can i use c.33 patched boot img to root c.36 ? or i need to downgrade to c.33 ?
Click to expand...
Click to collapse
Why can't you use patched boot img of c.36?
TheNewHEROBRINE said:
Why can't you use patched boot img of c.36?
Click to expand...
Click to collapse
because i used oxygen updater app and it shows only full rom of c.33 . i extracted boot.img from it. i can't find c.36 boot.img
MevishL said:
because i used oxygen updater app and it shows only full rom of c.33 . i extracted boot.img from it. i can't find c.36 boot.img
Click to expand...
Click to collapse
Do you have TWRP installed?
TheNewHEROBRINE said:
Do you have TWRP installed?
Click to expand...
Click to collapse
nope , still waiting for unlock token to unlock bootloader. how to root using twrp?
MevishL said:
nope , still waiting for unlock token to unlock bootloader. how to root using twrp?
Click to expand...
Click to collapse
If you make a backup of the boot partition, TWRP will create a file called boot.emmc.win that is nothing different than a boot.img file. You can then pass it to Magisk to patch it.
TheNewHEROBRINE said:
If you make a backup of the boot partition, TWRP will create a file called boot.emmc.win that is nothing different than a boot.img file. You can then pass it to Magisk to patch it.
Click to expand...
Click to collapse
ok thnk u so much , will try it
TheNewHEROBRINE said:
If you make a backup of the boot partition, TWRP will create a file called boot.emmc.win that is nothing different than a boot.img file. You can then pass it to Magisk to patch it.
Click to expand...
Click to collapse
what if my device get bricked , can i unbrick it by flashing c.33 full rom in msm?
MevishL said:
because i used oxygen updater app and it shows only full rom of c.33 . i extracted boot.img from it. i can't find c.36 boot.img
Click to expand...
Click to collapse
[KB2003] Stock & Magisk patched boot.img (latest KB2003_11.C.33)
Hello everyone! Welcome to the thread I was hoping to see every time OnePlus would release a new update... Eventually I decided to do it myself! In the link below you can download stock & Magisk patched boot.img files of given OOS versions for...
forum.xda-developers.com
MevishL said:
can i use c.33 patched boot img to root c.36 ? or i need to downgrade to c.33 ?
Click to expand...
Click to collapse
This worked for me but just boot it without flashing by using "fastboot boot boot.img", that way if it fails your boot partition is still in tact. Once booted you can use Magisk direct install to patch your c.36 boot.

How do i restore stock recovery img F.15 KB2005?

hello , i want to restore stock recovery.img , and i have orangefox recovery. i dont want to downgrade . and may i use recovery.img of f.13?
MevishL said:
hello , i want to restore stock recovery.img , and i have orangefox recovery. i dont want to downgrade . and may i use recovery.img of f.13?
Click to expand...
Click to collapse
Extract if from firmware and flash to recovery partition.
Rootk1t said:
Extract if from firmware and flash to recovery partition.
Click to expand...
Click to collapse
f.15 is an incremental update.
f.13 is a full update , can i use recovery.img from f.13?
MevishL said:
f.15 is an incremental update.
f.13 is a full update , can i use recovery.img from f.13?
Click to expand...
Click to collapse
Link is to F.15 full ^
Its for KB2003, but recovery images should be identical between KB2001/2003/2005.
Rootk1t said:
Link is to F.15 full ^
Its for KB2003, but recovery images should be identical between KB2001/2003/2005.
Click to expand...
Click to collapse
okay thank you

Categories

Resources