Mt7-tl10 cust fail,software update fail,region change,worked %100 - Ascend Mate 7 General

Switching to another regional firmware (change of locale)
http://4pda.ru/forum/index.php?showtopic=678766&st=980
my region channel/tr
converted region hw/eu
google translated txt (cust fail fix.txt)

What version you have installed ? B510?
Enviado do meu HUAWEI MT7-TL10 através de Tapatalk

paulopais said:
What version you have installed ? B510?
Enviado do meu HUAWEI MT7-TL10 através de Tapatalk
Click to expand...
Click to collapse
B324,good for now.

I Have now the Gold Mate 7 TL10 from the Philippines. Here in Germany don`t work this whit the LTE Band 20. Can i change this and need i root?

murat1369 said:
Switching to another regional firmware (change of locale)
http://4pda.ru/forum/index.php?showtopic=678766&st=980
my region channel/tr
converted region hw/eu
google translated txt (cust fail fix.txt)
Click to expand...
Click to collapse
does this file works for all firmwares?
please clarify

Brilliant, thanks so much for this, worked like a charm. This worked for me going from Chinese 5.1.1 firmware (TL7-MT10C00B357) to European 5.1.1 firmware (MT7-TL10C900B311).
Chinese firmware downloaded from:
http://forum.xda-developers.com/mate-7/general/official-lollipop-chinese-versions-mate-t3214997
European firmware downloaded from:
http://www.carbontesla.com/firmware-ota-section/huawei-firmware-ota-collection/huawei-ascend-mate-7-firmware-ota/

speedojames said:
Brilliant, thanks so much for this, worked like a charm. This worked for me going from Chinese 5.1.1 firmware (TL7-MT10C00B357) to European 5.1.1 firmware (MT7-TL10C900B311).
Chinese firmware downloaded from:
http://forum.xda-developers.com/mate-7/general/official-lollipop-chinese-versions-mate-t3214997
European firmware downloaded from:
http://www.carbontesla.com/firmware-ota-section/huawei-firmware-ota-collection/huawei-ascend-mate-7-firmware-ota/
Click to expand...
Click to collapse
Hi Speedo.
I tried it myself, and I changed the oeminfo with no problems.
however i did not understand the instructions besides that.
could you post a little set of instructions?
PS: I made a tool to make changing oeminfo easier, it's in my other thread.

xd4d3v said:
Hi Speedo.
I tried it myself, and I changed the oeminfo with no problems.
however i did not understand the instructions besides that.
could you post a little set of instructions?
PS: I made a tool to make changing oeminfo easier, it's in my other thread.
Click to expand...
Click to collapse
I'll try and summarise as best I can below by amending the original text below. As I said this worked for me going from the Chinese to European firmware versions I quoted above.
1. Open ES File Explorer (enabling root access by selecting Root Explorer)
2. Navigate to the folder ../dev/block/platform/hi-mci.0/by-name/
3. Copy the file "oeminfo" from this folder to your internal memory and rename it oeminfo.bak
4. Make a copy of this file (again onto your internal memory) and rename it oeminfo.img
5. Download oeminfo.rar onto your computer and extract the archive onto your harddrive
6. Copy the file oeminfo.img from your internal memory into the folder where the archive was extracted above
7. Run the file oeminfo.exe from the archive folder, in the dialogue box that opens change the text
8. To go from Chinese to EU change from "cmmcchannel/cn" to "hw/eu"
9. Exit the program and copy the file oeminfo.img from the archive folder back to the internal memory replacing the file that is there.
10. Rename the file in the internal memory from "oeminfo.img" to "oeminfo"
11. Copy this file (oeminfo) from the internal memory back to the folder ../dev/block/platform/hi-mci.0/by-name/ replacing the existing file
12. Using ES File Explorer, long tap on the file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
13. Open the folder ../data and then open the file custom.bin with a text editor (if the file is not there then create it, the file was there for me). Edit the file so it is a single line of text with the local you want to go to (so me I changed the text in the file to read "hw/eu") and save the edit
14. Using ES File Explorer, long tap on the edited file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
15. Open the folder ../system/ then open the file build.prop (with a text editor) and find the line ro.build.display.id = ??? (this was quite a long way down the file for me). Replace the text after the equals sign (where I have put the question marks) with the text from the first line of the file verlist.img (where this is extracted from the firmware you want to transfer to reading verlist.img with a text editor).
16. Copy the file UPDATE.APP from the firmware you are transferring to a folder called "dload" in the base directory of either your sdcard or internal memory.
17. Remove the SuperSu root using the option "Full unroot" from within the Setting tab of the SuperSu app
18. If you have a custom recovery installed, flash back to the stock recovery using fastboot
19. Shutdown the phone, disconnect any cables and restart it by holding down the power, volume up and volume down buttons. This should boot into the stock recovery and start the installed of the firmware placed on either the sdcard or the internal memory noting this will delete all data in the internal memory

speedojames said:
I'll try and summarise as best I can below by amending the original text below. As I said this worked for me going from the Chinese to European firmware versions I quoted above.
Click to expand...
Click to collapse
Thanks James.
you switched to the same model firmware?
meaning TL10 ch to TL10 eu?

Yes, straight swap, with the version numbers as quoted above.

xd4d3v said:
PS: I made a tool to make changing oeminfo easier, it's in my other thread.
Click to expand...
Click to collapse
Which thread would that be, mate? I can't find it anywhere.

speedojames said:
I'll try and summarise as best I can below by amending the original text below. As I said this worked for me going from the Chinese to European firmware versions I quoted above.
1. Open ES File Explorer (enabling root access by selecting Root Explorer)
2. Navigate to the folder ../dev/block/platform/hi-mci.0/by-name/
3. Copy the file "oeminfo" from this folder to your internal memory and rename it oeminfo.bak
4. Make a copy of this file (again onto your internal memory) and rename it oeminfo.img
5. Download oeminfo.rar onto your computer and extract the archive onto your harddrive
6. Copy the file oeminfo.img from your internal memory into the folder where the archive was extracted above
7. Run the file oeminfo.exe from the archive folder, in the dialogue box that opens change the text
8. To go from Chinese to EU change from "cmmcchannel/cn" to "hw/eu"
9. Exit the program and copy the file oeminfo.img from the archive folder back to the internal memory replacing the file that is there.
10. Rename the file in the internal memory from "oeminfo.img" to "oeminfo"
11. Copy this file (oeminfo) from the internal memory back to the folder ../dev/block/platform/hi-mci.0/by-name/ replacing the existing file
12. Using ES File Explorer, long tap on the file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
13. Open the folder ../data and then open the file custom.bin with a text editor (if the file is not there then create it, the file was there for me). Edit the file so it is a single line of text with the local you want to go to (so me I changed the text in the file to read "hw/eu") and save the edit
14. Using ES File Explorer, long tap on the edited file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
15. Open the folder ../system/ then open the file build.prop (with a text editor) and find the line ro.build.display.id = ??? (this was quite a long way down the file for me). Replace the text after the equals sign (where I have put the question marks) with the text from the first line of the file verlist.img (where this is extracted from the firmware you want to transfer to reading verlist.img with a text editor).
16. Copy the file UPDATE.APP from the firmware you are transferring to a folder called "dload" in the base directory of either your sdcard or internal memory.
17. Remove the SuperSu root using the option "Full unroot" from within the Setting tab of the SuperSu app
18. If you have a custom recovery installed, flash back to the stock recovery using fastboot
19. Shutdown the phone, disconnect any cables and restart it by holding down the power, volume up and volume down buttons. This should boot into the stock recovery and start the installed of the firmware placed on either the sdcard or the internal memory noting this will delete all data in the internal memory
Click to expand...
Click to collapse
Thanks a lot speedojames for this very informative post. I followed your instructions and got this working in no time. The only difference was that I did not set the permission on oeminfo file, as ES File Explorer continued to give error on that. Rest was a breeze. Thanks again.

Related

[HELP] Retrieving TWRP data [SOLVED]

Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse

How to use SMGVER.EXE on stock roms (.SBF's)

I've found that several people on XDA-Developers are confused or asking, how to use it or even wondering why the black window keep showing when they try to apply the sgmver.exe to a SBF. Most of the instructions I've seen are something like: Apply SGMVER to SBF...
Well, we need the following tools:
MotoAndroidDepaccker: 4shared.com/archive/4OvekGU7ba/-_MotoAndroidDepacker.html
SMGVER: 4shared.com/rar/yKlGlwiCba/smgver.html
We can use RDS lite 6.x to decompress the SBF if is in .gz format.
1. We start MotoAndroidDepacker once we have the SBF we wanna analyze
2. Click open from file and select the desired SBF file
3. Click split to folder and wait 'till it finish
4. Open the folder named affer the original sbf filename with the "extracted" addition,you'l find there de contents of the SBF.
5. Place (copy paste) the SGMVER.EXE and the VER.BAT files in that directory
6 Click the VER,BAT file and you are done.
A window will show you the bl version of the SGM files, it is common some of them have no signature data and it is normal, will display "no signatured data found. Close the window to finish, you can delete the files you pasted if you are going to repack them to a sbf.
I hope this minitutorial helps you,
Visit and subscribe my YouYube as knomon youtube.com/user/knomon I will make some video tutorials there.
Thaks a lot,
Greetz

How to flash OTA update manually?

The Huawei Firmware Finder app indicates that there is an OTA update for the Tab (BTV-DL09C100B009). It is 424 MB. I could download it but I don't know how to install it. The zip contains several .dat files and two folders besides the 'UPDATE.APP' file.
Meanwhile the Tab's own HiCare app cannot find any update.
My version number is still BTV-DL09C100B006.
Some help would be appreciated.
Just follow the steps of Firmware finder
1. ckick rom
2. click download
3.click chek MD5
4. click move to DLOAD
5. tunoff device
6. Press ALTOGETHER : Vol UP + Vol DOWN + POWER
wait a few seconds and MUI screen apears to install Firmware
Thanks, but in this case (incremental OTA) it does not seem to be the right solution.
The Firmware Finder copies only the update.app to the dload folder. That file is just 75 MB from the 433-MB-big whole package. The rest of the files and folders inside the ZIP are omitted.
So, another method should be used but I don't know what.
ctibor said:
Thanks, but in this case (incremental OTA) it does not seem to be the right solution.
The Firmware Finder copies only the update.app to the dload folder. That file is just 75 MB from the 433-MB-big whole package. The rest of the files and folders inside the ZIP are omitted.
So, another method should be used but I don't know what.
Click to expand...
Click to collapse
You can try to unpacked update after point 3 and before point 4 that SJGSM wrote!
Let's me if it's ok now!
ctibor said:
Thanks, but in this case (incremental OTA) it does not seem to be the right solution.
The Firmware Finder copies only the update.app to the dload folder. That file is just 75 MB from the 433-MB-big whole package. The rest of the files and folders inside the ZIP are omitted.
So, another method should be used but I don't know what.
Click to expand...
Click to collapse
YES sorry I missed Step 4.
You have 5 steps in Firmware Finder:
1. CHANGELOG
2. DOWNLOAD
3. CHECK MD5
4. UNPACK UPDATE
5. MOVE TO DLOAD
Any way it is always better to Install FULL FIRMWARE Rather than Incremental UPDATE, It only takes a few minutes longer but you have a FULL FIRMWARE UPDATE with all your data saved.
You can also use Firmware Finder for Windows and donwload your firmware, then you just have to copy the UNPACKED File UPDATE.APP to the: ( dload ) folder in your External SD
ctibor said:
The Huawei Firmware Finder app indicates that there is an OTA update for the Tab (BTV-DL09C100B009). It is 424 MB. I could download it but I don't know how to install it. The zip contains several .dat files and two folders besides the 'UPDATE.APP' file.
Meanwhile the Tab's own HiCare app cannot find any update.
My version number is still BTV-DL09C100B006.
Some help would be appreciated.
Click to expand...
Click to collapse
If you have already UNZIPPED the download file, Just copy ALL the UNZIPPED files to an dload Folder in your Externalñ SD. If you dont have one Just create a New Folder in your ExtSD and RENAME it : dload
Then Power OFF and press: (Vol Up +Vol DOWN + POWER ) and the system will recognize the UPDATE.APP file in the MUI screen
SJGSM said:
If you have already UNZIPPED the download file, Just copy ALL the UNZIPPED files to an dload Folder in your Externalñ SD. If you dont have one Just create a New Folder in your ExtSD and RENAME it : dload
Then Power OFF and press: (Vol Up +Vol DOWN + POWER ) and the system will recognize the UPDATE.APP file in the MUI screen
Click to expand...
Click to collapse
I did exactly the same what you wrote. And I flashed the update with the method you suggested. Everything went smoothly - seemingly.
(I am not totally noob, this is the fifth Huawei device I've been handling. My current phone is Huawei P9 Plus and I've put on all the new ROM versions 'by hand' becauce OTA did not come.)
But something was wrong because
a) the update process went through too fast, just a couple of seconds from 0 to 100%.
b) the version number has not changed. I still have BTV-DL09C100B006,
c) the dload folder and the whole extracted package in it were not deleted after the process, remained on the SD card.
So I suspect that only the UPDATE.APP was installed, the rest of the package not. The M3 now keeps working normally but unfortunately there is one problem: the tab lost its 4G (LTE) capability after the update, now the phone radio works only in 3G and/or GSM mode.
You are right, a full ROM flashing is always better, more secure but there is NO full ROM available for this Tab! I've searched the whole net and found only OTAs for the M3. I'd like to get back the normal functionality because I bought the device exactly to have quick access to the internet everywhere.
So I don't know what to do. If you or somebody else could find a full ROM for the device I'd be very grateful!
Problem solved!
Problem solved!
Earlier I tried to update the M3 with HiSuite but there was no package available at that time. Now, after my unsuccessful manual update, I connected the Tab to my notebook again and ran HiSuite. And voilá: now it offered the B009 update.
The install went without problem and now I have BTV-DL09C100B009. The LTE data capability came back, and everything works well so far.
Anyway, thanks to those who tried to help!
I have downloaded a firmware file from firmware finder but I didn't see anywhere how to check MD5. The file unzipped OK but I don't want to install until I check MD5. Where is the MD5 information for each download firmware?
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
I have downloaded a firmware file from firmware finder but I didn't see anywhere how to check MD5. The file unzipped OK but I don't want to install until I check MD5. Where is the MD5 information for each download firmware?
SJGSM said:
YES sorry I missed Step 4.
You have 5 steps in Firmware Finder:
1. CHANGELOG
2. DOWNLOAD
3. CHECK MD5
4. UNPACK UPDATE
5. MOVE TO DLOAD
Any way it is always better to Install FULL FIRMWARE Rather than Incremental UPDATE, It only takes a few minutes longer but you have a FULL FIRMWARE UPDATE with all your data saved.
You can also use Firmware Finder for Windows and donwload your firmware, then you just have to copy the UNPACKED File UPDATE.APP to the: ( dload ) folder in your External SD
Click to expand...
Click to collapse

Android 7.0 on P9 lite

I found a site with a tutorial on how to install Android 7.0 on P9 lite.On version VNS-L31C636B361 there are 3 files, and acording to them, you need to follow these steps:
Extract the contents of the zip files you downloaded from above.
Create a folder named “dload” in the root directory of your device’s SDcard.
Copy all the extracted contents of the zips into the dload folder.
Open the dialer app and dial *#*# 2846579#*# *
Select Project Menu > Software upgrade > SDcard upgrade > confirm the installation.
The firmware will begin installing and once that is done your device will reboot automatically.
But the problem is, if I extract all the contents from all 3 files, some of them have the same name and overwrite, and when I try to install by *#*# 2846579#*# *, it stops after 5% and gives me fail error.
What is the correct way to install and why are there 3 separate files ? (also, do I need to have some settings ? the phone should be connected to PC while installing ? )
Thank you very much!
What model you have?
Seems you have another oeminfo...
i have the same problem, it runs now on version vns-l31c432b161, if a want to install android 7 i get the same message as above
gtdaniel said:
What model you have?
Seems you have another oeminfo...
Click to expand...
Click to collapse
the omeinfo is 100% the same, otherwise if would have said its not compatible.The problem is there are 3 different files for this model to download, and if u extract them in the same folder, they overwrite ? What is the correct way to install them ?
erader said:
the omeinfo is 100% the same, otherwise if would have said its not compatible.The problem is there are 3 different files for this model to download, and if u extract them in the same folder, they overwrite ? What is the correct way to install them ?
Click to expand...
Click to collapse
EDIT: i tried again and it stucks on 5%, doesnt say anything.
Good to know!
If you are in MM 6.0 you can not go to Nougat 7.0 without some preparation until Huawei release official version.
I you are already in Nougat 7.0 (B3xx) you can go to B360-B361, directly with Sdcard upgrade or with three keys pressed method.
U dint answer my question though.Let me be more clear.
Here is a tutorial on how to install Android 7.0 on P9 Lite: http://www.droidviews.com/update-huawei-p9-lite-manually-official-android-7-0-nougat-emui-5-0/
On my model, there are 3 files:
4. VNS-L31C636B361
update.zip
update_data_full_VNS-L31_B360_hw_meafnaf.zip
update_data_full_VNS-L31_B361_hw_meafnaf.zip
and they say
Extract the contents of the zip files you downloaded from above.
Create a folder named “dload” in the root directory of your device’s SDcard.
Copy all the extracted contents of the zips into the dload folder.
But some of the files from these 3 .zips have the same name, and when I copy them in the same folder, they overwrite.
Is that tutorial sh1t ?

HwOTA for Huawei P9 Lite

HwOTA for Huawei P9 Lite​1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA.zip
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
vovan1982 said:
HwOTA for Huawei P9 Lite​1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA.zip
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
Click to expand...
Click to collapse
Hi, ", it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip" - doesn't work. Is it possible to manually rename files?
Edit: It was my stupidity , everything works fine, thank you !!!
where do I download the firmware files by the way?
there are lots of errors,
there are conflicts in folder names and script paths
Error
there are errors
it's can't run
can you fix it

Resources