[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo "Updated_19.5.2018"

LwannaCM

Senior Member
Nov 8, 2014
158
76
0
First of all, please excuse any dumb things I might say, as this is my first time doing this.
In the firmwarefinder, no version matched both L29 and AL00, so I just decided to give one of the versions provided in the thread a try, and downloaded B179. Should I use a version that supports AL00 instead?
I waited for around 2 hours, furthermore, I checked in the code of the script and some other messages should appear when the files are being copied if I’m not mistaken. None of them appeared for me.
Thanks for helping.
You should not try to use a version that isn´t approved for your phone. Maybe check some older versions. If you want to brand to l29, then you should only check for the this one, not for thr AL00.
Besides, did you already install the oreo update on your phone? If yes, be aware that the partionlayout has changed from nougat to oreo.
If you want to build it yourself just replace the 3 updates in the updatefolder with a version you can approve in firmwarefinder.
Simply check with firmwarefinder and imei and then download the version from here:
http://pro-teammt.ru/firmware-database/?firmware_model=vtr-l29c432&firmware_page=0
If you click on filelist, you can download the 3 parts of the firmeware and place them in the hwota\update folder. Be sure to rename them exactly as the files that were in that folder.
 

eribs4e

Member
Jan 3, 2018
19
0
0
As per the instructions on the first page I was able to successfully rebrand my P10 from a VTR-L09C557B312 to the VTR-L29C432B179 firmware. The first run through I applied the update using option 2 of the script to "Rebrand" and then a ran the process a second time with option 1 for the "Same brand". Doing this twice was required so that the phone would be able to run the system updates going forward.

However, when I go into the system updates and search for a new update i get "No Updates" found. I know there are new updates for the device (C432B180). In fact there are a few versions of it. Any ideas as to what I'm missing? Phone appears to be functioning correctly otherwise.

---------- Post added at 02:45 AM ---------- Previous post was at 02:08 AM ----------

As per the instructions on the first page I was able to successfully rebrand my P10 from a VTR-L09C557B312 to the VTR-L29C432B179 firmware. The first run through I applied the update using option 2 of the script to "Rebrand" and then a ran the process a second time with option 1 for the "Same brand". Doing this twice was required so that the phone would be able to run the system updates going forward.

However, when I go into the system updates and search for a new update i get "No Updates" found. I know there are new updates for the device (C432B180). In fact there are a few versions of it. Any ideas as to what I'm missing? Phone appears to be functioning correctly otherwise.
Found my answer. Even though the L29C432B180 is listed in FF, it has not been approved when i check via IMEI number. So it appears that all is working as it's supposed to. Once the B180 is approved, I'll test the system update to make sure it's working.
 

J4G3D

Senior Member
Nov 22, 2009
102
3
0
N00B attempting this great guide :)

Bootloader unlocked and the whole of step 1 done OK! including the backup.

Now im onto step 2 and, if i can get past this part i think i will be home dry.

My issue is:

I have VTR-L09C02
using HUAWEI firmware finder, the recommended firmware i can use is: VTR-L09C02B159

But I want to use VTR-L29 and im now confused as to which one of these I can use:
HWOTA_P10_B164
HWOTA_P10_B130

EDIT:
If i manually add the model VTR-L09C432 in the firmware finder (love this app used it a few times in the past)
Then do a search, B179 says its approved for my device.
 
Last edited:

eribs4e

Member
Jan 3, 2018
19
0
0
N00B attempting this great guide :)

Bootloader unlocked and the whole of step 1 done OK! including the backup.

Now im onto step 2 and, if i can get past this part i think i will be home dry.

My issue is:

I have VTR-L09C02
using HUAWEI firmware finder, the recommended firmware i can use is: VTR-L09C02B159

But I want to use VTR-L29 and im now confused as to which one of these I can use:
HWOTA_P10_B164
HWOTA_P10_B130

?
My understanding is that if you rebrand an L09 to another L09 your sim card will not work (see first post of this thread). Therefore you HAVE to rebrand to a valid L29 firmware. The main advantage here is you will activate the second sim feature, even if you don't use it, there's no harm.

In order to find the valid firmware to download, us FF and add the VTR-L29C432 model and search. Validate the returned firmwares against your phone to find the most recent one that is allowed (use IMEI check). Make sure to use a "FULL" firmware and not an OTA one. I used the windows version of FF to download the files and put them in the appropriate location. Then follow the rest of the steps carefully.

I successfully rebranded my VTR-L09C557 to VTR-L29C432 last night with B179, but be sure to validate with FF to make sure you use a valid firmware.
 

J4G3D

Senior Member
Nov 22, 2009
102
3
0
My understanding is that if you rebrand an L09 to another L09 your sim card will not work (see first post of this thread). Therefore you HAVE to rebrand to a valid L29 firmware. The main advantage here is you will activate the second sim feature, even if you don't use it, there's no harm.

In order to find the valid firmware to download, us FF and add the VTR-L29C432 model and search. Validate the returned firmwares against your phone to find the most recent one that is allowed (use IMEI check). Make sure to use a "FULL" firmware and not an OTA one. I used the windows version of FF to download the files and put them in the appropriate location. Then follow the rest of the steps carefully.

I successfully rebranded my VTR-L09C557 to VTR-L29C432 last night with B179, but be sure to validate with FF to make sure you use a valid firmware.
Yeah the L29 B179 is confirmed on my device via FF.

Could i not continue the install of this via FF or do i need to follow the guide and download the B179 file from the OPS mega account?.

I've reached my download limit on mega as i use it to download all sorts. Have to wait 3 hours now.
 
Last edited:

eribs4e

Member
Jan 3, 2018
19
0
0
Yeah the L29 B179 is confirmed on my device via FF.

Could i not continue the install of this via FF or do i need to follow the guide and download the B179 file from the OPS mega account?.

I've reached my download limit on mega as i use it to download all sorts. Have to wait 3 hours now.
L29C02B179 or the L29C432B179? If it's the L29C432 then you need to use the guide so the debranding steps will take place.

You can download the firmware files directly from Huawei using the PC version of FF (There's a FF thread on this site with the link, just search for it). Validate the firmware with your phone, then search and download it using the PC version.
 

J4G3D

Senior Member
Nov 22, 2009
102
3
0
L29C02B179 or the L29C432B179? If it's the L29C432 then you need to use the guide so the debranding steps will take place.

You can download the firmware files directly from Huawei using the PC version of FF (There's a FF thread on this site with the link, just search for it). Validate the firmware with your phone, then search and download it using the PC version.
Had numerous problems but got there in the end. The UPDATE.BAT finished like this:

https://i.imgur.com/Pui3oYT.jpg

Obviously it didn't finish properly. Also when i logged into my phone it said the following:
BUILD NUMBER: NRD90M test-keys

So i followed the process 3 times and it eventually is now working as L29.
 
Last edited:

LwannaCM

Senior Member
Nov 8, 2014
158
76
0
Had numerous problems but got there in the end. The UPDATE.BAT finished like this:

https://i.imgur.com/Pui3oYT.jpg

Obviously it didn't finish properly. Also when i logged into my phone it said the following:
BUILD NUMBER: NRD90M test-keys

So i followed the process 3 times and it eventually is now working as L29.
I work for a company that gets their phones from Vodafone, which are known for being lazy in deploying updates for their phones.
That said i testet a few devices with different cables and in different systems.
You always get NRD90M test-keys, if the updatefiles aren´t pushed correctly to device.
My tests showed that almost in any case the cables were the problem and if you use the orginalcable that came with the device, it sometimes a problem of your USB-controller or driver.
So i now recommend using a sdcard for the update. Simply copy the folder "update" to your sdcard. But this can also fail, if the sdcard is corrupted or a very cheap one, if not the update seems to be smoother and without errors.
 

J4G3D

Senior Member
Nov 22, 2009
102
3
0
I work for a company that gets their phones from Vodafone, which are known for being lazy in deploying updates for their phones.
That said i testet a few devices with different cables and in different systems.
You always get NRD90M test-keys, if the updatefiles aren´t pushed correctly to device.
My tests showed that almost in any case the cables were the problem and if you use the orginalcable that came with the device, it sometimes a problem of your USB-controller or driver.
So i now recommend using a sdcard for the update. Simply copy the folder "update" to your sdcard. But this can also fail, if the sdcard is corrupted or a very cheap one, if not the update seems to be smoother and without errors.
Cheers.

Yeah it seems i got there in the end using a aftermarket cable and updating from the PC rather than SD card. It took numerous attempts.

Out of interest, can you get vodafone unlock codes? My shiney new L29 now needs unlocking lol.
 

eribs4e

Member
Jan 3, 2018
19
0
0
Had numerous problems but got there in the end. The UPDATE.BAT finished like this:

https://i.imgur.com/Pui3oYT.jpg

Obviously it didn't finish properly. Also when i logged into my phone it said the following:
BUILD NUMBER: NRD90M test-keys

So i followed the process 3 times and it eventually is now working as L29.
Based on your screenshot above, you didn't let the script complete. When doing my phone, it hung up at that location for quite a while also, but eventually moved on and finished properly.

Either way, glad to see you got it sorted out!!
 

Mostar088

Senior Member
Oct 1, 2012
2,220
677
193
Stockholm
Cheers.

Yeah it seems i got there in the end using a aftermarket cable and updating from the PC rather than SD card. It took numerous attempts.

Out of interest, can you get vodafone unlock codes? My shiney new L29 now needs unlocking lol.
Dc Unlocker should do the trick to unlock the provider.

Sent from my LON-L29 using XDA Labs
 
  • Like
Reactions: J4G3D

camp04

Member
Jan 9, 2018
16
2
0
Error: 9

Hi guys, I need your help, cuz I am stucked.

First a couple of info:
I have the P10 VTR-L09C432B179 and I would like to use the 2nd SIMcard slot so start to update it to L29C432B179.
First I was stucked with the script several times so decided to do this step:

STEP 3 (Optional Update Method 1)
If you have already unlocked your bootloader und installed TWRP, you can also use this method to install the new system update:

1. Make a complete backup of your current system via twrp and save the backup to sd or your pc.
2. Download one of the Huawei P10_HWOTA files from above, save it on your device and unzip it
3. Navigate to the update folder in the HWOTA-folder and copy the 3 files to your device (sdcard recommended)
4. Now Boot your device into TWRP
5. In TWRP flash "update.zip" and don´t reboot!!!
6. Flash "update_all_hw.zip" and don´t reboot!!!
7. Flash "update_data_public.zip"
6. Wait until all files are flashed
7. Done! Reboot TWRP

Sadly I am stucked here to at step 5. Till there I did everything as it says.
I have unlocked the bootloader, have TWRP installed and copied the complett HWOTA folder with the 3 zips (HWOTA/update/update.zip, update_all_hw.zip, update_data_public.zip).
Now when I try to flash update.zip or update_all_hw.zip in TWRP I receive and ERROR: 9 message.
If I flash the update_data_public.zip it seems to be good to me and TWRP says "Success".

from the logs:
"script aborted: update_huawei_pkg_from_ota_zip: update package from zip failed
check_write_data_to_partition,write data error
update_huawei_pkg_from_ota_zip: update package from zip failed
Func: hw_create_verify_and_update_thread, Line: 463, result = 9.
Func: main, Line: 439, result = 9, verify failed.
open nv file error
read nv VMODE failed, retNv = -1
set verift mode as logging failed.
E:unknown command [errno]
Updater process ended with ERROR: 9
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/external_sd/HWOTA/update/update.zip'
Updating partition details...
I:Data backup size is 888MB, free: 51959MB.
I:Can't probe device /dev/block/sda
I:Unable to mount '/usbotg'
I:Actual block device: '/dev/block/sda', current file system: 'auto'
...done"


Thank you in advance for any help.
More from logs here:
Updater process ended with ERROR: 9
I:Legacy property environment disabled.
I:Install took 23 second(s).
Error installing zip file '/external_sd/HWOTA/update/update_all_hw.zip'
Updating partition details...
I:Data backup size is 1918MB, free: 50925MB.
I:Can't probe device /dev/block/sda
I:Unable to mount '/usbotg'
I:Actual block device: '/dev/block/sda', current file system: 'auto'
...done
I:Set page: 'flash_done'
I:eek:peration_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:eek:peration_start: 'Flashing'
E:[MTP] request read returned -1, errno: 5, exiting MtpServer::run loop
Installing zip file '/external_sd/HWOTA/update/update_data_public.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
[2018-01-10 10:48:00 130] failed to read /etc/recovery.fstab
[2018-01-10 10:48:00 131] unknown volume for path [/data]
mount data failed, error: No such file or directory.
/data/hota_pkg_stat is not exist.
This is the first or the last hota package, no need to unlink it in update-binary
there is no file cust.new.dat in package.
there is no file cust.patch.dat in package.
there is no file system.new.dat in package.
there is no file system.patch.dat in package.
there is no file product.new.dat in package.
there is no file product.patch.dat in package.
there is no file vendor.new.dat in package.
there is no file vendor.patch.dat in package.
there is no file:full_mainpkg.tag in package,it's diff mainpkgthere is no file UPDATE.APP in package.
ext4_percent = 0.000000.
there is no file cust.transfer.list in package.
there is no file system.transfer.list in package.
there is no file product.transfer.list in package.
there is no file vendor.transfer.list in package.
total_blks = 0.
[2018-01-10 10:48:00 131] unknown volume for path [/data]
mount data partition fail!
File META-INF/com/google/android/pre-script is not exist in package.
script = META-INF/com/google/android/verify-script, script_count = 1.
[2018-01-10 10:48:00 131] unknown volume for path [/data]
mountencrypt: failed to mount /data: Success
mountencrypt: failed to mount /data: Success
File META-INF/com/google/android/mid-script is not exist in package.
script succeeded: result was []script = META-INF/com/google/android/updater-script, script_count = 1.
Verifying current userdata...
Removing unneeded files...
Patching userdata files...
Removing empty directorys...
Unpacking data new files...
I:[MTP] MtpServer::run fd: 17
add link type file...
script succeeded: result was []File META-INF/com/google/android/post-script is not exist in package.
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 6 second(s).
Updating partition details...
I:Data backup size is 888MB, free: 51959MB.
I:Can't probe device /dev/block/sda
I:Unable to mount '/usbotg'
I:Actual block device: '/dev/block/sda', current file system: 'auto'
...done
I:Set page: 'flash_done'
I:eek:peration_end - status=0
E:[MTP] request read returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 17
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:eek:peration_start: 'Flashing'
Installing zip file '/external_sd/HWOTA/update/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
[2018-01-10 10:48:36 803] failed to read /etc/recovery.fstab
[2018-01-10 10:48:36 803] unknown volume for path [/data]
mount data failed, error: No such file or directory.
/data/hota_pkg_stat is not exist.
This is the first or the last hota package, no need to unlink it in update-binary
there is no file cust.new.dat in package.
there is no file cust.patch.dat in package.
there is no file system.new.dat in package.
there is no file system.patch.dat in package.
there is no file product.new.dat in package.
there is no file product.patch.dat in package.
there is no file vendor.new.dat in package.
there is no file vendor.patch.dat in package.
[2018-01-10 10:48:36 803] unknown volume for path [/data]
mount data partition fail!
File META-INF/com/google/android/pre-script is not exist in package.
script = META-INF/com/google/android/verify-script, script_count = 1.
set zip_file_size = 4294967295.
[2018-01-10 10:48:36 804] failed to read /etc/recovery.fstab
[2018-01-10 10:48:36 804] get_partition_info,line=1350: begin
[2018-01-10 10:48:36 804] get_lun_nums,line=445: ufs node name:/dev/block/sda
[2018-01-10 10:48:36 804] is_file_exist,line=1188: /dev/block/sda is exist
[2018-01-10 10:48:36 806] partition_verify_mbr_signature,line=397: MBR signature does not match.
[2018-01-10 10:48:36 806] mmc_boot_read_mbr,line=573: partition_verify_mbr_signature failure
[2018-01-10 10:48:36 806] get_lun_nums,line=445: ufs node name:/dev/block/sdb
[2018-01-10 10:48:36 806] is_file_exist,line=1188: /dev/block/sdb is exist
[2018-01-10 10:48:36 806] partition_verify_mbr_signature,line=397: MBR signature does not match.
[2018-01-10 10:48:36 806] mmc_boot_read_mbr,line=573: partition_verify_mbr_signature failure
[2018-01-10 10:48:36 806] get_lun_nums,line=445: ufs node name:/dev/block/sdc
[2018-01-10 10:48:36 806] is_file_exist,line=1188: /dev/block/sdc is exist
[2018-01-10 10:48:36 806] mmc_boot_read_mbr,line=590: (dtype == MBR_PROTECTED_TYPE),gpt_partition_exist
[2018-01-10 10:48:36 806] mmc_get_device_capacity,line=883: buff = 16384
, Length = 6
[2018-01-10 10:48:36 806] mmc_get_device_capacity,line=885: sector = 0x00004000
[2018-01-10 10:48:36 806] mmc_get_device_capacity,line=887: emmc_capacity = 0x800000
[2018-01-10 10:48:36 806] mmc_get_device_blocksize,line=270: ufs_node:/dev/block/sdc
[2018-01-10 10:48:36 806] mmc_get_device_capacity,line=883: buff = 16384
, Length = 6
[2018-01-10 10:48:36 806] mmc_get_device_capacity,line=885: sector = 0x00004000
[2018-01-10 10:48:36 806] mmc_get_device_capacity,line=887: emmc_capacity = 0x800000
[2018-01-10 10:48:36 807] get_lun_nums,line=445: ufs node name:/dev/block/sdd
[2018-01-10 10:48:36 807] is_file_exist,line=1188: /dev/block/sdd is exist
[2018-01-10 10:48:36 807] mmc_boot_read_mbr,line=590: (dtype == MBR_PROTECTED_TYPE),gpt_partition_exist
[2018-01-10 10:48:36 807] mmc_get_device_capacity,line=883: buff = 124928000
, Length = 10
[2018-01-10 10:48:36 807] mmc_get_device_capacity,line=885: sector = 0x07724000
[2018-01-10 10:48:36 807] mmc_get_device_capacity,line=887: emmc_capacity = 0xee4800000
[2018-01-10 10:48:36 807] mmc_get_device_blocksize,line=270: ufs_node:/dev/block/sdd
[2018-01-10 10:48:36 807] mmc_get_device_capacity,line=883: buff = 124928000
, Length = 10
[2018-01-10 10:48:36 807] mmc_get_device_capacity,line=885: sector = 0x07724000
[2018-01-10 10:48:36 807] mmc_get_device_capacity,line=887: emmc_capacity = 0xee4800000
[2018-01-10 10:48:36 807] parse_args,line=796: This phone is secureboot phone.
[2018-01-10 10:48:36 862] get_receiving_property_buf,line=218: oeminfo get OEMINFO_OEMSBL_VER_TYPE error
[2018-01-10 10:48:36 862] get_receiving_property_buf,line=225: oeminfo get OEMINFO_AMSS_VER_TYPE error
[2018-01-10 10:48:36 862] set_platform_type,line=262: curr_type:1
[2018-01-10 10:48:36 862] get_lun_nums,line=445: ufs node name:/dev/block/sde
[2018-01-10 10:48:36 862] is_file_exist,line=1193: /dev/block/sde not exist
[2018-01-10 10:48:36 862] ufs_ptable_init_to_ram,line=1684: init to ram OK
[2018-01-10 10:48:36 862] get_partition_info,line=1368: end
[2018-01-10 10:48:36 862] vrlinfo_init_to_ram,line=1191: Begin to initialize vrlinfo to ram
[2018-01-10 10:48:36 862] get_partition_vrlinfo_from_ram,line=1155: i=49, break
[2018-01-10 10:48:36 862] vrlinfo_init_to_ram,line=1193: Initialize vrlinfo to ram end
[2018-01-10 10:48:36 862] get_partition_info,line=1372: in common partition,Contains in source code:
.
.
.
[2018-01-10 10:48:36 876] crcmbn_post_write_func,line=1304: check Success : CRC
[2018-01-10 10:48:36 876] newapp_send_cmd_to_recovery,line=119: 0 == total_pkg!
[2018-01-10 10:48:36 876] get_update_type,line=2072: get cur_ptr_receiving_buf_property->update_type=2
[2018-01-10 10:48:36 876] get_update_type,line=2072: get cur_ptr_receiving_buf_property->update_type=2
[2018-01-10 10:48:36 876] void usb_ota_update_message(int, char *),line=737: update_mode = 2
skip data:2
module name:CURVER
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=625:
========Module name:CURVER,module ID:FFFFFFF0 ========
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=626: dwMagicNum :A55AAA55
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=627: szDispName :CURVER
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=628: UnlockCode :HW7x27ÿÿðÿÿÿ
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=629: dwDataStartAddr :0xFFFFFFF0
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=630: dwDataLen :0x00000018
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=631: dwBlockSize_hw :0x00
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=632: dwBlockSize :0x1000
[2018-01-10 10:48:36 876] get_part_property,line=2444: Finding: CURVER,0xfffffff0
[2018-01-10 10:48:36 876] get_part_property,line=2484: common table Find by Name : 0xfffffff0, CURVER
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=724: module_offset_in_emmc_or_nand : 0x00000000
[2018-01-10 10:48:36 876] one_write_pre_write_func,line=936: Pre Write CURVER ...
[2018-01-10 10:48:36 876] cmd_unit_write_post_func,line=796: cmd_unit_write_post_func()...
[2018-01-10 10:48:36 876] crc_mbn_check_32k,line=288: crc_mbn_offset = 0,crc0_length=297034
[2018-01-10 10:48:36 876] dload_vendor_country_info_get,line=1356: read vendor/country error!
[2018-01-10 10:48:36 876] curver_check_pkg_validate,line=1854: get vendor info failed.
[2018-01-10 10:48:36 876] curver_check_pkg_validate,line=1858: dataptr is:Victoria_Global_C999B000.
tmp_str is:DATA_.
[2018-01-10 10:48:36 876] curver_write_func,line=1902: this image ok
[2018-01-10 10:48:36 876] default_post_func_no_action,line=844: Attention:No Action!
skip data:0
module name:VERLIST
[2018-01-10 10:48:36 876] cmd_unit_write_begin_func,line=625:
========Module name:VERLIST,module ID:FFFFFFF1 ========
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=626: dwMagicNum :A55AAA55
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=627: szDispName :VERLIST
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=628: UnlockCode :HW7x27ÿÿñÿÿÿ.
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=629: dwDataStartAddr :0xFFFFFFF1
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=630: dwDataLen :0x0000002E
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=631: dwBlockSize_hw :0x00
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=632: dwBlockSize :0x1000
[2018-01-10 10:48:36 877] get_part_property,line=2444: Finding: VERLIST,0xfffffff1
[2018-01-10 10:48:36 877] get_part_property,line=2484: common table Find by Name : 0xfffffff1, VERLIST
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=724: module_offset_in_emmc_or_nand : 0x00000000
[2018-01-10 10:48:36 877] one_write_pre_write_func,line=936: Pre Write VERLIST ...
[2018-01-10 10:48:36 877] cmd_unit_write_post_func,line=796: cmd_unit_write_post_func()...
[2018-01-10 10:48:36 877] crc_mbn_check_32k,line=288: crc_mbn_offset = 2,crc0_length=297034
[2018-01-10 10:48:36 877] amss_version_list_write_func,line=1789: amss version list check Begin!
[2018-01-10 10:48:36 877] amss_version_list_write_func,line=1793: version checked ok
[2018-01-10 10:48:36 877] default_post_func_no_action,line=844: Attention:No Action!
skip data:2
module name:pACKAGE_TYPE
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=625:
========Module name:pACKAGE_TYPE,module ID:FFFFFFF2 ========
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=626: dwMagicNum :A55AAA55
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=627: szDispName :pACKAGE_TYPE
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=628: UnlockCode :HW7x27ÿÿòÿÿÿ
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=629: dwDataStartAddr :0xFFFFFFF2
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=630: dwDataLen :0x0000000E
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=631: dwBlockSize_hw :0x00
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=632: dwBlockSize :0x1000
[2018-01-10 10:48:36 877] get_part_property,line=2444: Finding: PACKAGE_TYPE,0xfffffff2
[2018-01-10 10:48:36 877] get_part_property,line=2484: common table Find by Name : 0xfffffff2, PACKAGE_TYPE
[2018-01-10 10:48:36 877] cmd_unit_write_begin_func,line=724: module_offset_in_emmc_or_nand : 0x00000000
[2018-01-10 10:48:36 877] one_write_pre_write_func,line=936: Pre Write PACKAGE_TYPE ...
[2018-01-10 10:48:36 877] cmd_unit_write_post_func,line=796: cmd_unit_write_post_func()...
[2018-01-10 10:48:36 877] crc_mbn_check_32k,line=288: crc_mbn_offset = 4,crc0_length=297034
[2018-01-10 10:48:36 877] package_type_write_func,line=1966: package type check Begin!
[2018-01-10 10:48:36 877] package_type_write_func,line=1974: package type online,need check
[2018-01-10 10:48:36 877] AuthErrCode getAuthResult(),line=74: update auth result failed[14]
[2018-01-10 10:48:36 877] package_type_write_func,line=1976: auth result is 14!
[2018-01-10 10:48:36 877] package_type_write_func,line=1979: package auth check fail!
[2018-01-10 10:48:36 877] check_write_data_to_partition,line=525: push SD_WRITE_FAIL_L4
[2018-01-10 10:48:36 877] cmd_unit_write_post_func,line=822: ERROR,write_func
[2018-01-10 10:48:36 877] update_from_zip_module_post,line=201: cmd_unit_write_begin_func failure
error:update_device_func,line:312, all_module_func[1]
minzip: Process function elected to fail (in inflate)
minzip: ### result: -1 vs pEntry->uncompLen: 4294967295, ignore...
[2018-01-10 10:48:36 877] all_data_32K_checked_ok,line=2536: ( cur_ptr_receiving_buf_property->crc_mbn_offset != cur_ptr_receiving_buf_property->rec_crc_length )
script aborted: update_huawei_pkg_from_ota_zip: update package from zip failed
check_write_data_to_partition,write data error
update_huawei_pkg_from_ota_zip: update package from zip failed
Func: hw_create_verify_and_update_thread, Line: 463, result = 9.
Func: main, Line: 439, result = 9, verify failed.
open nv file error
read nv VMODE failed, retNv = -1
set verift mode as logging failed.
E:unknown command [errno]
Updater process ended with ERROR: 9
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/external_sd/HWOTA/update/update.zip'
Updating partition details...
I:Data backup size is 888MB, free: 51959MB.
I:Can't probe device /dev/block/sda
I:Unable to mount '/usbotg'
I:Actual block device: '/dev/block/sda', current file system: 'auto'
...done
I:Set page: 'flash_done'
I:eek:peration_end - status=1
E:[MTP] request read returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 17
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
E:[MTP] request read returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 17
I:Set page: 'copylog'
I:Set page: 'action_page'
I:eek:peration_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
 
Last edited:

LwannaCM

Senior Member
Nov 8, 2014
158
76
0
Cheers.

Yeah it seems i got there in the end using a aftermarket cable and updating from the PC rather than SD card. It took numerous attempts.

Out of interest, can you get vodafone unlock codes? My shiney new L29 now needs unlocking lol.
The unlock code is generated especially for each phone, so it won't help you much ;)
 

camp04

Member
Jan 9, 2018
16
2
0
Stucked

Hi guys, I am following the steps, but something is wrong. I got stucked and nothing happens.

.
.
.
2. Run the update.bat file from a preopended CMD with adminrights, It will ask you if you copied the files. Press any key to continue.
3. Now connect your device and Reboot into Bootloader mode using “Volume Down + Power” or just use “adb reboot bootloader” then press any key.
4. The above step will install TWRP in your device.
5. Now Disconnect USB Cable and turn off your device and use “Volume Up + Power” to enter TWRP.
6. Once you’re in TWRP mode, plug in the USB cable again and press the Enter key on your computer.

And here at Step 6
- I am in TWRP mode
- mobile is connected to the PC via USB cable
- update.zip and the other 2 zip is on SDCard in HWOTA folder and of course renamed.
- I also have the zip files on my PC in HWOTA/update folder

Here is the screen what I can see
and I have waited here 30 mins, pressed a couple of times ENTER too, and tried to disconnect the phone and start again in TWRP recovery and connected again... nothing seems to work.

I have tried also to flash the update.zip and other in TWRP but then I receive an ERROR: 9 message. More information about that here: https://forum.xda-developers.com/android/help/error-9-flashing-update-zip-t3732838/page3#post75159049 and on page 1.

Any suggestions?
 
Last edited:

rexvillavelez

Member
Nov 20, 2012
6
0
0
vtr-l29c432
Be sure to stick exactly to the steps! After its finished wait at least 15min.
If the device won´t reboot itself, you have to switch it off and maybe make a low level reset via orginal recovery, if you´re stuck in a boot loop.
Happened to me on 1 of 5 flashes.
did all the steps and the udpates successfully installed , how ever the device now is stuck in boot loop, any advice
 

maly82

Senior Member
Nov 4, 2014
63
17
0
I just want to say thank you for this guide. I successfully managed to debrand my P10 from VTR-L09GBRC (Three UK) to VTR-L29C432 European version.

I had to do it twice as my phone had some trouble with sdcard so I refollowed the guide with files transferred from PC and it done it trick.

Thank you.
 

BADS_

New member
Oct 9, 2008
2
0
0
Unfortunaly even if I follow and try everything I always got stuck here "Please wait for upload files and do not press any key. " Any help?
 

maly82

Senior Member
Nov 4, 2014
63
17
0
Unfortunaly even if I follow and try everything I always got stuck here "Please wait for upload files and do not press any key. " Any help?

I had same problem debrand in first time. I selected to use Sdcard - which rendered process hang for 25 minutes doing nothing. Restarted the phone manually. Which took me to rom without any changes. Then I started using script again and choose to use files from my pc hdd. That ended up process to be finished. Then I restarted a phone and voila rebranded device.
 
Last edited:
  • Like
Reactions: BADS_
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone