[GUIDE] Manual Oreo update - v190219 - Pie upgrade now supported (Tut #4)

[Jannomag]

Just another question...
Is it right, that it isn't possible at the moment to go back to Oreo after Pie update???

Some say it is, some say it isn’t.
Some people saying that HiSuite is able to rollback.
In the P20 forums is a Tutorial with a script for downgrading. This script contains the exact same commands as my script, so I rewrite my own script and tried to downgrade to Oreo - now my phone won’t show anything else but a black screen with working fast boot. I tried to reflash everything but I’ve still just a door stopper.
I tried DC Phoenix with test point, also no success.
I ordered a used mainboard and hope it’s working.

So, be careful with Pie. Play store certification isn’t working, if you don’t need this you can stay on Pie until there’s a working rollback.

 

[fatjoez]

I updated my P10 from v8 b360 to emui 9 beta succesfully.

* I had b360 so don't worry about minimum b376 warning
* My device is UFS not emmc. The sequential read was about 400.
* I previously had SUPERSU root installed but no problems
* playstore not certified
* overall ok

* Successful root with magisk (followed instructions here: https://forum.xda-developers.com/mate-10/how-to/guide-magisk-root-mate-10-pro-t3886967)
1. patch stock recovery_ramdis.img with magisk 2. flash patched file in fastboot 3. reboot phone to recovery then phone will boot rooted

 

[Jannomag]

I updated my P10 from v8 b360 to emui 9 beta succesfully.

* I had b360 so don't worry about minimum b376 warning
* My device is EMMC. The sequential read was about 400.
* I previously had SUPERSU root installed but no problems
* playstore not certified
* overall ok
Will try flashing magisk now

Magisk is using recovery_ramdisk but this didn’t work for me when I tried. Huawei messed it up with EMUI9, everytime you want to Boot rooted you need to boot like you want to boot into recovery. If you want to use recovery you need to flash it over Magisk

 

[Disillusionedsal]

P10 Plus VKY-L09 (No recovery, No Boot, Error! Func NO : 11)

Background:
Phone was successfully rebranded to VKY L29, however since VoLTE doesn't work on it, an attempt was made to debrand back to VKY L09. Phone is unlocked, FRP is unlocked.

What went wrong:

• After flashing OEMINFO, I tried using Tutorial 2 (Oreo update) by OP @Jannomag. I had all three update files in place and used TWRP to flash oreoupdate.zip which prompted everything was successful.
• Unfortunately, after reboot the phone got stuck on warning screen but it won't enter recovery.
• While attempting regular boot, phone would show below:
  
  Error Mode
  Attention!
  Please Update system again.
  
  [Green Android]
  
  Error!
  Func NO : 11 (reovery image)
  Error NO : 2 (load failed!)​

What have I tried to fix it:

• Tried flashing recovery multiple times viz. original, TWRP but the phone would always get stuck on warning screen.
• Tried flashing all files under update.app viz. system, recovery, ramdisk, odm, product, cache and whatnot, many would fail with error FAILED (remote: Command not allowed)
• Tried multi-tool to flash various boot / kernel, ramdisk, recovery but to no avail.
• Tried DC-Unlocker only to get below:

Build number: :System 8.0.0.046(0PF0)
Model: VKY-L09
Battery state: 3564mv

Device with unsupported security patch
User accepted to update device with unsupported security patch

Writing XLOADER partition
XLOADER partition UPDATE :FAIL Command not allowed

Device with unsupported security patch
2/23/2019 3:01:49 PM Writing device finished - INCOMPLETE​

What I've understood is, OP's patch writes two images to two different areas in memory.

adb shell "dd if=/tmp/VTR_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37 bs=1048576"
adb shell "dd if=/tmp/VTR_RECOVERY2_NoCheck.img of=/dev/block/mmcblk0p34 bs=1048576"

These two areas correspond to laf and rct partition. However, when I try writing or erasing these partitions or memory blocks through fastboot, I get command not allowed error.

Seems like this annoying phone is beyond repair, but would appreciate any input that I can try to fix it.

 

[burimselmani]

I did the method 4 and it worked perfect, It even unbricked my phone! thanks a lot!

 

[netmaniack]

Some say it is, some say it isn’t.
Some people saying that HiSuite is able to rollback.
In the P20 forums is a Tutorial with a script for downgrading. This script contains the exact same commands as my script, so I rewrite my own script and tried to downgrade to Oreo - now my phone won’t show anything else but a black screen with working fast boot. I tried to reflash everything but I’ve still just a door stopper.
I tried DC Phoenix with test point, also no success.
I ordered a used mainboard and hope it’s working.

So, be careful with Pie. Play store certification isn’t working, if you don’t need this you can stay on Pie until there’s a working rollback.

You tried to flash Oreo rollback fw or previous Oreo fw?

 

[Jannomag]

You tried to flash Oreo rollback fw or previous Oreo fw?

I didn’t found any rollback Firmware and didn’t know if there are any differences. If you know more about that, please report.
Maybe this was the reason why my phone is a piece of junk now.
But I also have to say that it’s very bad engineering when software can destroy the phone completely just by flashing something wrong. Even test point isn’t working and the security patches are preventing that you’re able to flash necessary partitions.

 

[tkalfaoglu]

I recently upgraded my OmniROM and I did not have to wipe anything.. So happy -- it works great and nothing is lost..

 

[lukastob]

...
In the P20 forums is a Tutorial with a script for downgrading. This script contains the exact same commands as my script, so I rewrite my own script and tried to downgrade to Oreo ...

Could you briefly explain what exactly you rewrote on your script? Or upload it, because I downloaded all the scripts to make some comparsion and I have noticed some differences in paths. I could give a try to downgrade but first would like to fully understand all the commands in order not to fry it.

 

[Jannomag]

Could you briefly explain what exactly you rewrote on your script? Or upload it, because I downloaded all the scripts to make some comparsion and I have noticed some differences in paths. I could give a try to downgrade but first would like to fully understand all the commands in order not to fry it.

First I removed all the security and text parts of my script like path checking.
Then I changed the recovery path from /.../recovery_ramdisk_a to /.../recovery_ramdisk.
After that I edited the paths of the update files to fit to my sdcard so all three needed files are available for the update command which is still getting written in the cache.

I’m not able to view my script because I can’t open it on my spare phone - iPhone 6S. Maybe later after work I can post my script, but above is all I changed.

 

[skolebolle]

Hi! Short question. Is Huawei messaging app finally replaced by Android Messages in this build?

 

[aalmeida1972]

Is there a twrp for android pie? I want to install magisk.
Thanks

 

[Jannomag]

Is there a twrp for android pie? I want to install magisk.
Thanks

Not yet and it’s also not needed. You can use Oreo TWRPs m but you’re not able to decrypt /data.

Read through the tutorials and Huawei related posts in Magisk forums. You need to modify your recovery_ramdisk within the Magisk app. Then flash it. EMUI 9 doesn’t have a boot partition anymore. So you need to boot like you want to boot into recovery every time you reboot your phone.
You can extract the original recovery_ramdisk from EMUI 9 update.app.
If you want to update your phone you need to reflash Stock recovery first.

 

[aalmeida1972]

So, it means, that it's not possible to install magisk?

 

[Jannomag]

So, it means, that it's not possible to install magisk?

it is, as I said above.
Please visit the Magisk forums here at XDA and search for Huawei. You’ll see tutorials. It’s just different as it is under EMUI8.

BTW, for me it fits perfectly into Huaweis new politics for „better user experience“ by stopping people from unlocking and rooting by making it harder to unlock their devices and install things like Magisk. There’s no need to remove the actual boot partition, this will cause extremely hard to fix problems like I had. You can deep fry your phone just by flashing things as usual.

 

[aalmeida1972]

I tried to install it, but in the end gives me an error

 

[Jannomag]

I tried to install it, but in the end gives me an error

Again, go into Magisk forums for support. And without postin the error no one is able to help you.
I got it working by doing a factory reset and install it after that. Installing without reset seems to be a problem.

 

[aalmeida1972]

There are so many tutorials, but no one seems to talk about this.
By the way, the error is "Failed to mount /vendor (Device or resource busy)

 

[Jannomag]

There are so many tutorials, but no one seems to talk about this.
By the way, the error is "Failed to mount /vendor (Device or resource busy)

- Download Update.zip from FF, fitting to your firmware
- extract containing recovery_ramdisk from update.app with Huawei Update Extractor
- load the recovery_ramdisk.img on your sd
- Open Magisk Manager, select install and “patch boot image “.
- select the recovery_ramdisk.img and patch it
- copy the patched img to your pc
- start your phone into fast boot
- flash patched recovery with “fastboot flash recovery_ramdisk \PATH\TO\PATCHED.IMG”
- reboot your phone with holding Vol+ like you want to boot into recovery

This should work, if not, do a factory rest with eRecovery. If you want to get into stock recovery you need to reflash the stock image.
You also need to boot like this every time, otherwise Magisk isn’t working.

 

[netmaniack]

I didn’t found any rollback Firmware and didn’t know if there are any differences. If you know more about that, please report.
Maybe this was the reason why my phone is a piece of junk now.
But I also have to say that it’s very bad engineering when software can destroy the phone completely just by flashing something wrong. Even test point isn’t working and the security patches are preventing that you’re able to flash necessary partitions.

Rollback fw for c432 was released just before Pie. It contains rollback feature in changelog and fw is following new design - just two zips to download, not three as it was before.