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

[DallasCZ]

download full (approx 2.2GB) firmware c490b365 (if you have successfully flashed before the B365, when not, then B311) then inpack all three zips. Use huaweiextractor to extract partition images from update.app file. Then go to fastboot mode and flash erecovery_ramdisk, recovery_ramdisk, kernel, ramdisk try to reboot.
One more thing!!!! where you got stuck on the update process?on which step?

 

[Wempetje]

hi guys in the first post there is a link to the huawei site where you can request the Bootloader unlock code. This link is dead. Does anybody know how to unlock the bootloader?

 

[M1chiel]

hi guys in the first post there is a link to the huawei site where you can request the Bootloader unlock code. This link is dead. Does anybody know how to unlock the bootloader?

Contact Huawei Customer Service or pay some $ to DC Phoenix.

 

[Jannomag]

Thanks for reminder @Wempetje.
I added this information to my first post.

It seems there are only the two ways mentioned by @M1chiel - at the moment.

HonorUSA twittered that they have some problems with their website, but I really don't know if this is correct.

If Huawei decided to close the unlock process than the P10 will be my fist and last Huawei phone.
And if this is true I believe more and more that DC Phoenix is driven by Huawei or is supported by Huawei just to make some extra money with the community.

 

[Wempetje]

Thanks for reminder @Wempetje.
I added this information to my first post.

It seems there are only the two ways mentioned by @M1chiel - at the moment.

HonorUSA twittered that they have some problems with their website, but I really don't know if this is correct.

If Huawei decided to close the unlock process than the P10 will be my fist and last Huawei phone.
And if this is true I believe more and more that DC Phoenix is driven by Huawei or is supported by Huawei just to make some extra money with the community.

Just contacted Huawei but that the site is down is a temporary issue and they hope to have it fixed early May/the next couple of days

 

[SwiftingDuster]

Successfully updated from L29C636B162 to B362. However my bootloader was relocked after the update. Now I have to redownload and customize everything again

 

[Jannomag]

Successfully updated from L29C636B162 to B362. However my bootloader was relocked after the update. Now I have to redownload and customize everything again

I'm very sorry about that, never heard about it.
Maybe you downloaded a wrong firmware for your model? What does system info shows now after you updated?
If this is so, I will mention it in my guide.

 

[mleczan]

oreoupdate on P10 eMMC

@Jannomag does oreoupdate also work on P10 with eMMC memory? I'm asking because HWOTA which I already did to update Android 7.0 -> 8.0 required me to do some manutal changes in update script - recovery paritions are different than in UFS devices (device name and partition numbers are different). Since there is no open code of your script can you confirm that? I don't want to brick my phone

Does your script allow downgrade? Currently I'm on VTR-L29C636B361 (8.0.0.361) which seems to be laggy (in browsers and some apps) and I'd like to try B360 (Public version)

 

[theonlykamph]

how come after i done this, to unbrick it won't ask for my sim pin code anymore? I can't use the phone at all now

 

[Jannomag]

@Jannomag does oreoupdate also work on P10 with eMMC memory? I'm asking because HWOTA which I already did to update Android 7.0 -> 8.0 required me to do some manutal changes in update script - recovery paritions are different than in UFS devices (device name and partition numbers are different). Since there is no open code of your script can you confirm that? I don't want to brick my phone

Does your script allow downgrade? Currently I'm on VTR-L29C636B361 (8.0.0.361) which seems to be laggy (in browsers and some apps) and I'd like to try B360 (Public version)

I don't think that it will work without modifications.
If you know the changes you can edit my script just by editing the update-binary inside the zip.
Maybe we can work it out together and provide a special eMMC version?

 

[SwiftingDuster]

I'm very sorry about that, never heard about it.
Maybe you downloaded a wrong firmware for your model? What does system info shows now after you updated?
If this is so, I will mention it in my guide.

Pretty sure its the correct region firmware. I flashed from VTR-L29C636B162 stock with TWRP and root to VTR-L29C636B362.

 

[Jannomag]

Pretty sure its the correct region firmware. I flashed from VTR-L29C636B162 stock with TWRP and root to VTR-L29C636B362.

Than I really don't know why your bootloader was locked after update.
The process won't do it itself. It must be locked by the firmware, I really don't know if some firmware files can lock the bootloader.
For explanation: My script flashes the stock recovery and puts commands in cache for the stock recovery so it know what to flash. No magic behind this and this is the reason I don't know why this happened. I will mention it in my guide.

 

[SwiftingDuster]

Than I really don't know why your bootloader was locked after update.
The process won't do it itself. It must be locked by the firmware, I really don't know if some firmware files can lock the bootloader.
For explanation: My script flashes the stock recovery and puts commands in cache for the stock recovery so it know what to flash. No magic behind this and this is the reason I don't know why this happened. I will mention it in my guide.

To be fair the last time I flashed stock L29C636B162 the bootloader was locked after that too. Maybe its just something that only happens with my P10 brand in general.

 

[DallasCZ]

Yes, sotck firmware update on Android 7 always locked the bootloader. But on Android 8 it doesnt do it anymore. As I know the right upgrade to oreo is to go to the latest Android 7 firmware first, then upgrade to Oreo. Now on Android 8 the only way is "relock" the bootloader" so when you get your device to repair they will know it was unlocked before.
If you want complete stock A8 with "locked" bootloader. You have to downgrade to the latest stock A7 firmware, the let the OTA upgrade it to A8, or use firmware finder solution for upgrading. Then you will end with bootloader "locked" A8 stock firmware.

 

[mleczan]

I don't think that it will work without modifications.
If you know the changes you can edit my script just by editing the update-binary inside the zip.
Maybe we can work it out together and provide a special eMMC version?

Ok, now I can see that update binary is a script, not a binary
I'll try to update it to support both UFS and eMMC devices and sent it back to you when it's confirmed to work on my phone

 

[mleczan]

Update script with added eMMC support: https://mega.nz/#!W3xzkCRC!kp672KbhbFIwbstkzDhNO4OcgSsWmQ_s-TefuaMdNvo

 

[Jannomag]

Thanks @mleczan. I will add the parts from you to my scripts (both) and mention your work on the first page later this day, I think. I will edit the post title with a new version number, as well.
For now everyone with eMMC device: Test it by your own, if there's any problem with it, please tell us!

 

[mleczan]

Thanks @Jannomag!
If you update your script I can retest it on my device. I just did quick modification so I'm not sure if the change is "pretty" and can be included as is, but it worked.

 

[Jannomag]

UPDATE 040518 - Only oreoupdate
- Added support for eMMC devices.
Special thanks to @mleczan who provided the code for eMMC devices!

TESTERS NEEDED!

I need testers with eMMC devices to provide a 100% working script.
Also I need partition information for eMMC devices with Nougat installed!
For more information contact me via PM!

"How do I find out, which device I have?"
- Install any Termainl emulator app from Google Play
- Type in following command:

ls /proc/fs/*

The output should show this output for UFS devices:

[...]
/proc/fs/f2fs:
sdd**
[...]

And for eMMC devices:

[...]
/proc/fs/f2fs:
mmc**
[...]

 

[mleczan]

@Jannomag Full partition layout of eMMC version on Nougat can be found here: https://forum.xda-developers.com/showpost.php?p=73008866&postcount=155

I used this layout to upgrade From Nougat to Oreo using content of HWOTA script.
Here is my description of needed steps for eMMC device: https://forum.xda-developers.com/showpost.php?p=76349530&postcount=1174
According to this layout I flashed those two recovery partitions to upgrade 7.0 -> 8.0:
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"

Beside above two recovery partitions eMMC script should be the same as UFS