This will be basically the copy of this thread:
https://forum.xda-developers.com/p10-plus/development/downgrade-p10-plus-oreo-to-nougat-t3724382
But it seems to me that I am not the only one who didn't find it first, so I post it here
I am not responsible if you brick your device, or just damage it!
And all credit goes to @mankindtw and @NoMercyWWE
Always make a backup of your important data, and if you rollback, you need to make a factory reset!
I only tested it with L09, but should work with L29 as well
First of all, you need a P10
2. It only works with oreo firmwares
3. Download the three zip files that are required for update, these are:
update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
3/b. You can download them with Firmware Finder, or just search on xda. If you want to make a rollback to Nougat, you need rollback firmwares!
3/c. update_data_public and update_all_hw comes with a slightly different name, but rename both files to these names, otherwise the update will fail!
4. Download HWOTA8 from this topic
5. Put the three update files in HWOTA8 dir
5/b. If you want to rollback, but your files in the repack folder, and run repack.bat
6. Create a new folder on your EXTERNAL sd, named HWOTA8
7. Put your three files in it, plus copy MHA_RECOVERY8_NoCheck.img, and hwota8_update.zip
8. Now install P10 Plus twrp_oreo.img, if you havent't yet:
fastboot flash recovery_ramdisk twrp_oreo.img
Click to expand...
Click to collapse
credit to @OldDroid
9. Reboot into recovery, install hwota8_update.zip it replaces your recovery with the Mate 9 one, reboots and updates
10. Done! If you downgraded, or just encounter any problems, go back in recovery, and make a factory reset!
Can I do this without an sdcard?
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
I think it is possible, but you need to rewrite hwota8_update.zip, since the links there are pointing to the external sd. But I dont know what you need to write there instead
Not sure if I did this right but now my phone shows---> Build number System 8.0.0.046(02ZP)
I had showing before---> Build number System 8.0.0.046(01BN)
I don't seem to have it right still
I also have somethong like System 8.0.0.046(02BQ) but .321(C10) installed. And there were some visible updates from the C900log Oreo, eg auto shazam disappeared from the status bar.
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Droiduser67 said:
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Click to expand...
Click to collapse
Here he says that you need to install su, and rename three directories, but for me themes are working even without this. As soon as I try it, these steps will be added to the tutorial though.
EDIT: I followed the steps and renamed the directories, but there was no change anywhere.
Yes just tried it myself too and no change...still no themes...had an extra folder in there on mine named "optus"...not sure but the twrp and rooting work awesome but wasn't able to make a nandroid backup to my external storage...it failed
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
Without a SD card it is impossible, with firmware via TWRP, internal memory can be reset and then the firmware will not go to the end. Therefore, the programs are located on the SD.
urn said:
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
Click to expand...
Click to collapse
If this question is for me, I did not test the rollback (I am fine with Oreo), but I would use C432B180. You can check the description of an update in FF to see if it's a rollback one.
Here's the solution : https://youtu.be/WYSVq1TE2kI
OREO
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Nakedchef said:
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Click to expand...
Click to collapse
Hey, there are many ways of doing it i would recommend https://forum.xda-developers.com/showthread.php?t=3691013
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo it works great. Go for the hwota rebrand way, it work like charm for me.
Sent from my [device_name] using XDA-Developers Legacy app
Perfect! I applied the update as described in the OP, then did a factory reset and relocked the bootloader (which did another factory reset). Now, at least I can't tell anymore that the phone has been unlocked and rooted...
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
dukenuken said:
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
Click to expand...
Click to collapse
Which TWRP are you using?
Related
I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
Hi guys
The official OTA update (B380) with Andoid 6 and Emui 4.0.1 arrived on my PLK-AL10 around a week ago and I was very disappointed when I saw the "privacy protection" feature is not there anymore. This feature allowed me to create "visitor" account and the visitor could not see all the apps and albums.
Now I installed B395 hoping the feature included but it is still not.
I would like to revert to the previous system (as I remember it was B320) or any working version with Android 5 and EMUI 3.1.
I tried to install all the rollback files I found on the net but all stopped after a few percentages with the error message "software install failed".
Pls help me, what can I do?
You can root your device and add a couple of lines in /system/build.prop to get back the multiuser mode.
Sent from my PLK-L01 using Tapatalk
DigiGoon said:
You can root your device and add a couple of lines in /system/build.prop to get back the multiuser mode.
Sent from my PLK-L01 using Tapatalk
Click to expand...
Click to collapse
Really?
May I get a bit more detailed explanation what to modify?
tgergo said:
Really?
May I get a bit more detailed explanation what to modify?
Click to expand...
Click to collapse
http://forum.xda-developers.com/cro...ti-user-mode-guest-mode-simple-build-t3064829
This thread explains what you need to add to build.prop
Or do you need to know how to root your phone?
You can set how many users you want by editing max user line.
lionboy33 said:
http://forum.xda-developers.com/cro...ti-user-mode-guest-mode-simple-build-t3064829
This thread explains what you need to add to build.prop
Or do you need to know how to root your phone?
Click to expand...
Click to collapse
I can find in other topics how to root the phone, thank you. I think I can do it with these. Thanks a lot.
DigiGoon said:
You can set how many users you want by editing max user line.
Click to expand...
Click to collapse
Great.
I will come back if I get into trouble.
tgergo said:
Great.
I will come back if I get into trouble.
Click to expand...
Click to collapse
Always here to help buddy.
DigiGoon said:
Always here to help buddy.
Click to expand...
Click to collapse
Hi again,
Finally I managed to edit my build.prop and got "users" option. The problem is that is is not the same function as "Privacy protection" was in android 5. Privacy protection left the icon layout untouched, it was just possible to hide albums and applications.
Here when I create a guest and switch to it, it shows a completely empty system without any installed apps, pictures, etc..
Therefore I still want to go back to Android 5. How is it possible? I have TWRP installed. My current rom is B395 and phone is PLK-AL10.
To add to previous post, please unroot, flash stock boot.img and recovery.img BEFORE attempting to flash any ROM, including transitional package.
zinko_pt said:
To add to previous post, please unroot, flash stock boot.img and recovery.img BEFORE attempting to flash any ROM, including transitional package.
Click to expand...
Click to collapse
I don't think he was rooted, as the official update was missing a feature and he just wanted to get back to Lollipop.
Sent from my PLK-L01 using Tapatalk
pixelitect said:
You have to first flash the transition package to go back to Lollipop. For transition package to work you have to first flash STOCK recovery.img.
To do that execute the following command:
Code:
fastboot flash recovery recovery.img[/b]
Here [b]recovery.img[/b] is the name of your recovery file, and execute this command from the folder where you have saved the STOCK recovery.img. If you don't have STOCK recovery then you can extract it form the [b]UPDATE.APP[/b] using [URL="http://forum.xda-developers.com/showthread.php?t=2433454"]Huawei Update Extractor tool[/URL].[/QUOTE]
First I wanted to do so, but I could not find any transition package that worked with B380 stock rom (now I have 395). All I tried stopped with "software install failed" :(
Click to expand...
Click to collapse
pixelitect said:
Oh, then you can debrand your device using Multi-Tool to the one which has rollback package, and flash the Lollipop of that model.
Click to expand...
Click to collapse
Ok, I haven't heard about this yet but I'll try.
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
I managed to get back to Android 5 and EMUI 3.1 with a rollback file.
Here what I did:
1. Download Downgrade pack.
2. Download C185B130 ROM, which i want to install.
3. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
4. Copy update app from Downgrade pack to dload folder on mobile internal memory.
5. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
6. The system will be installed from mobile internal memory. I had no issues with the installation.
7. Copy update app from C185B130 ROM to dload folder on mobile internal memory.
8. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
9. The system will be installed from mobile internal memory. I had no issues with the installation.
10. Factory reset the mobile if the memory is showing 4gb.
11. The the native app icons look different than my previous lollipop system.
Thanks to tgergo and rest of everyone for the kind help.
Follow my guide at your own risk.
*WARNING* You are doing it at your own risk, I am not responsible for any damages due to bricked phones or broken ones
Sometimes Huawei releases an update package without approving it. For instance, my device (VIE-L29C636) is getting a B382 update, but the update isn't approved for installation. Here's how to update to those update packages.
NOTE: Using this method, you can also safely upgrade your device even if it is rooted, or has some files system partitions altered. (Of course after finished this process, your device will become unrooted and any alteration to the system partitions mentioned below will revert).
Prerequisites:
Your device is already running EMUI 5 (do not attempt this procedure on EMUI 4 ROM, as the partition layout may differ, and the various firmware (modem, sensor hub, etc.) may not compatible.
Unlocked Bootloader AND FRP.
Latest TWRP from OpenKirin (more on that, including download link, click here).
Huawei Update Extractor, for extracting UPDATE.APP.
imgtool, to convert the sparse android image into an ext4 raw image file.
Method:
Download your preferred update package from Firmware Finder app (Make sure to select the one which has 'FullOTA' designation on it. The package doesn't have to be a 'PV' package). Choose 'update.zip' and the other zip that has your region name on it (for instance, on my C636, look for the zip which has 'spcseas' on it's name). I will refer this 2nd zip as 'regional zip'.
Extract the 'UPDATE.APP' from both zip archive.
Using the Update Extractor on a Windows PC, Extract BOOT, SYSTEM, PRODUCT and VENDOR partitions from UPDATE.APP retrieved from 'update.zip', and extract CUST and VERSION from UPDATE.APP retrieved from your regional zip. You should end up with BOOT.IMG, SYSTEM.IMG, PRODUCT.IMG, VENDOR.IMG, CUST.IMG and VERSION.IMG.
Convert PRODUCT.IMG, VENDOR.IMG and VERSION.IMG to an ext4 image using imgtool, for example:
Code:
imgtool PRODUCT.IMG extract
Beware of overwriting the converted image. imgtool is hardcoded to output the converted file to 'extracted/image.img' folder. ALWAYS rename the image.img to something like 'product.ext4.img' after conversion.
Reboot your device to bootloader mode. Flash BOOT.IMG, SYSTEM.IMG and CUST.IMG via fastboot. For example:
Code:
fastboot flash boot BOOT.IMG
Reboot your device to recovery mode. Type
Code:
fastboot reboot
and hold the Vol Up button on your device to enter recovery mode.
Upload the *.ext4.img converted earlier to your device (doesn't matter where, but I recommend using a safe place like '/sdcard', or USB OTG or external micro SD card). you can use 'adb push', MTP or OTG to upload/copy the ext4.img files to your device.
for each *.ext4.img files, flash it to the appropriate named partitions in
Code:
/dev/block/platform/hi_mci.0/by-name/*
. You can use adb shell on your PC, and a command line program called dd on your device. For faster transfer, try to adjusting the block size to 8M. Example commands (execute from adb shell):
Code:
dd if=/sdcard/product.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/product
dd if=/sdcard/vendor.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/vendor
dd if=/sdcard/version.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/version
Exit TWRP (reboot to system), wait for several minutes for the system to build up it's AOT cache, and enjoy your new EMUI 5 with newer security patch, newer kernel and various features and bug fixes .
EDIT: I apologize that IMGTOOL isn't available in binary form for windows. You can try to use Linux virtual machines to run the IMGTOOL. Any modern GNU/Linux distro should be able to run the IMGTOOL.
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
In my case (upgrading from VIE-L29C636B370 to B382), it doesn't erase user data at all. And there is no reason it should erase the data.
But as always, backup your data before performing this procedure, in case something goes wrong.
How to extract product version Vendors use imgtool..
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that IMGTOOL is only available as binary in GNU/Linux OS. I think you have to use a VM running a GNU/Linux distro to extract product.img, version.img and/or vendor.img using the IMGTOOL.
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
faakher said:
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
Click to expand...
Click to collapse
Good Evening i had tried the guide but in my VIE-L09 doesn't work. What can i do? Bootloop infinity
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
great post, but as a simple user, i have no idea how to do this steps.
i have a p9 plus c605 b361 and rooted, and i cant update to anything
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
heeey...anyone here ?!!?
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
AYahooo said:
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
Click to expand...
Click to collapse
what this is ?!
---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
maahmd said:
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
Click to expand...
Click to collapse
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
Tecalote said:
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Click to expand...
Click to collapse
I know this but I have a version vie-l29c185 So I do not know which version I chose
maahmd said:
I know this but I have a version vie-l29c185 So I do not know which version I chose
Click to expand...
Click to collapse
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Tecalote said:
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Click to expand...
Click to collapse
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
maahmd said:
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Tecalote said:
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Click to expand...
Click to collapse
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
maahmd said:
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
Click to expand...
Click to collapse
I don't know what you mean now
Download the Nocheck Recovery for L29 from the Link I give you
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
and do the instructions from the OP
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But with the RIGHT Firmware for your VIE-L29 device (3 zips from Firmware Finder /FullOTA)
After updating Firmware Bootloader is closed and Root is gone.
You have to open again (Factoryreset low-level wipe - if it doesn't do 100% do it manually from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage - this is important! ) and flash TWRP and Root again
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Any idea how the phone installs this OTA zip file?
Is the updater-script failing because of assert statements for cust and system?
Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?
Thanks for your efforts on this and answering my questions.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse
Hey everyone so I have a BLA-A09 c567 (US) I got this phone used and it came with the bootloader unlocked. I managed to get the code and relock the bootloader at a later time. After going through the settings I noticed that the system update feature is still gone? I thought after relocking the bootloader and factory resetting it would come back. Is there something I am missing or will I not be able to receive OTA updates now? Please give me some guidance and thank you!
What's the status of the phone when you got it aside from Unlocked BL? Is it rooted?
You should never loose system update regardless of the BL status. I suspect the previous owner debloated it.
side_flip15 said:
What's the status of the phone when you got it aside from Unlocked BL? Is it rooted?
You should never loose system update regardless of the BL status. I suspect the previous owner debloated it.
Click to expand...
Click to collapse
They didn't flash the hw/public zip when updating.
Or possibly just removed it, for some reason...
So is there something I can do to return the system update feature? Or should I enjoy the blessing of a free debloat? My only issue is how will I get OTA updates. Can I just use the hisuite app the update instead?
Currently my Bootloader is relocked and unrooted looks like they messed around with the device then just relocked it and unrooted. When I purchased the device it was "like new" used for a week only.
I am on the C567 .119 patch
A flashable zip with instructions or apk would be amazing please help, but if it isn't an issue and I can just use hisuite to update I won't lose sleep over it.
Also is there anything important in the bloat zip besides system update?
I had the same issue when I flashed my phone with 119. I extracted the update ap apk from the hw zip file of 119, attempted an install, but it will not work. The app is in the play store but won't install on the phone. I will try to pm you the apk
innocentone1 said:
So is there something I can do to return the system update feature? Or should I enjoy the blessing of a free debloat? My only issue is how will I get OTA updates. Can I just use the hisuite app the update instead?
Currently my Bootloader is relocked and unrooted looks like they messed around with the device then just relocked it and unrooted. When I purchased the device it was "like new" used for a week only.
I am on the C567 .119 patch
A flashable zip with instructions or apk would be amazing please help, but if it isn't an issue and I can just use hisuite to update I won't lose sleep over it.
Also is there anything important in the bloat zip besides system update?
Click to expand...
Click to collapse
nabril15 said:
I had the same issue when I flashed my phone with 119. I extracted the update ap apk from the hw zip file of 119, attempted an install, but it will not work. The app is in the play store but won't install on the phone. I will try to pm you the apk
Click to expand...
Click to collapse
It won't install by using the package manager.
You can however download the hw zip file and flash it through TWRP, this requires unlocked bootloader and TWRP.
It will show a bunch of errors when installing through TWRP but the hw_init folder is copied successfully to /data/hw_init/
You can find it here: https://forum.xda-developers.com/showpost.php?p=77248270&postcount=72
ante0 said:
It won't install by using the package manager.
You can however download the hw zip file and flash it through TWRP, this requires unlocked bootloader and TWRP.
It will show a bunch of errors when installing through TWRP but the hw_init folder is copied successfully to /data/hw_init/
You can find it here: https://forum.xda-developers.com/showpost.php?p=77248270&postcount=72
Click to expand...
Click to collapse
For some reason, in TWRP, I cannot see the contents of my sdcard. I wiped the data partition when I flashed the 119 zip files using huru, so I don't know why I cant see that directory.
nabril15 said:
For some reason, in TWRP, I cannot see the contents of my sdcard. I wiped the data partition when I flashed the 119 zip files using huru, so I don't know why I cant see that directory.
Click to expand...
Click to collapse
Try going to Mount and unmount then mount Data again.
Or just mount if it's not mounted
(If you are encrypted and not using Pretoriano80's TWRP you won't be able to anyway as it would require either TWRP with decryption support or decrypting by Format Data then edit fstab and remove encryption. Dont Format Data now as it will wipe your /data)
ante0 said:
Try going to Mount and unmount then mount Data again.
Or just mount if it's not mounted
(If you are encrypted and not using Pretoriano80's TWRP you won't be able to anyway as it would require either TWRP with decryption support or decrypting by Format Data then edit fstab and remove encryption. Dont Format Data now as it will wipe your /data)
Click to expand...
Click to collapse
thanks ante
I unmounted and mounted and I now see a bunch of folders whose name starts with a (.). I am using twrp version 3.2.1.0, which is the same version as BLANC, I believe, which is for unencrypted data.
nabril15 said:
thanks ante
I unmounted and mounted and I now see a bunch of folders whose name starts with a (.). I am using twrp version 3.2.1.0, which is the same version as BLANC, I believe, which is for unencrypted data.
Click to expand...
Click to collapse
If it's just a bunch of random lettera/numbers it means your are encrypted. You could switch to https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Just flash it and reboot recovery. You will get a Pin/password input prompt, input your pin/pw and it will decrypt.
You can use adb to push the image to /data:
adb push twrp.img /data/
Then select Install and tap the dots to go up a level, go into /data, tap the Install Image button, scroll down and select twrp.img.
Or flash using fastboot as thats easier xD
ante0 said:
If it's just a bunch of random lettera/numbers it means your are encrypted. You could switch to https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Just flash it and reboot recovery. You will get a Pin/password input prompt, input your pin/pw and it will decrypt.
Click to expand...
Click to collapse
Thanks again. I did not know that we can flash twrp using twrp itself. Weird.
What pin/password is to be used?
nabril15 said:
Thanks again. I did not know that we can flash twrp using twrp itself. Weird.
What pin/password is to be used?
Click to expand...
Click to collapse
The one you use on lockscreen
When it's done, transfer zip to sdcard and flash.
As I said, it will error and say it failed but it does copy hw_init.
ante0 said:
The one you use on lockscreen.
Click to expand...
Click to collapse
I have a pattern
nabril15 said:
I have a pattern
Click to expand...
Click to collapse
Try entering it as numbers. Pattern would look like this in number mode:
1 2 3
4 5 6
7 8 9
I guess you could just remove pattern temporarily if your only goal is to flash hw
@ante0/culi
I flashed the twrp blanc, and as able to see my downloads. Cool. I then flashed the update_all_hw.zip file and it errored out at the end of the script with a write data error update_huawei_pkg from the zip file.
E:unknown command
Error installing file
Nothing else gave an error
EDIT - disregard..I rebooted and I see that I have the system update app now AND, it found the long-seeked 119 patch, which I installed. Cool. After the patch was applied, the phone rebooted itself into recovery, I saw it run some script, and then it rebooted into system. Weird. The phone, however, still shows the version as 119, and not 119 patch 01 or something.
RE-EDIT - redisregard. THe version shows as 119 patch AND the themes got installed from the zip. Ok, so it looks like I now have a complete version 119 US variant of the stubborn and cumbersome Mate 10 Pro. Though I read that an update came out yesterday with the August security patches.
nabril15 said:
@ante0/culi
I flashed the twrp blanc, and as able to see my downloads. Cool. I then flashed the update_all_hw.zip file and it errored out at the end of the script with a write data error update_huawei_pkg from the zip file.
E:unknown command
Error installing file
Nothing else gave an error
EDIT - disregard..I rebooted and I see that I have the system update app now AND, it found the long-seeked 119 patch, which I installed. Cool. After the patch was applied, the phone rebooted itself into recovery, I saw it run some script, and then it rebooted into system. Weird. The phone, however, still shows the version as 119, and not 119 patch 01 or something.
Click to expand...
Click to collapse
Yeah, flashing hw/public zips will give errors. This is because its supposed to be installed using Huaweis update binary. So twrp can't process the commads.