[TOOL] Huawei Update Extractor [UPDATED: v0.9.9.5] | OPEN-SOURCE LIBRARY

linus2014 · Nov 25, 2015 at 11:30 AM

nobody helps me

linus2014 · Nov 26, 2015 at 5:27 PM

linus2014 · Dec 28, 2015

Huawei Update Extractor [UPDATED: v0.9.9.4]

Huawei Update Extractor [UPDATED: v0.9.9.4]

I have Added Huawei P8 lite profile.

PanTra1978 · Dec 1, 2015 at 12:25 PM

Hello
I Can't find any post about Huawei Mediapad 10 in the search
So I post my questions here. Excuse me
With wrong information from store about tablet, my brother buy it.
The problem is here : no call applicable only sms and data net work
Is there any update that can solved the problem?
Stock or Costum not important
I just try to find a way to add call on that
Thanks for help be4?????

Sent from my FAST-717 using Tapatalk

custon3 · Dec 8, 2015 at 10:23 PM

Huawei okay for everyone?

Blackball · Dec 17, 2015

Hello,
is it possible to build a own UPDATE.APP with only some special imgs ?
I need it for my P8.

EDIT: Solved..

milanco · Dec 18, 2015

Huawei Extractor device Profile for Huawei G8

Hi, can you make the Profile for Huawei G8

I cannot update official firmware because of "version check fail" so I unlocked Bootloader and installed TWRP and I hope that after converting update.app to ZIP, I will be able to installe the firmware using TWRP.

PS: should I select all the files in the update.app and make of them flashable zip or should I select only some of them???

Thanks
Milan

linus2014 · Dec 19, 2015

milanco said:
Hi, can you make the Profile for Huawei G8

I cannot update official firmware because of "version check fail" so I unlocked Bootloader and installed TWRP and I hope that after converting update.app to ZIP, I will be able to installe the firmware using TWRP.

PS: should I select all the files in the update.app and make of them flashable zip or should I select only some of them???

Thanks
Milan

custom.img recovery.img fastboot.img and syetem.img files most important

Sai aswin · Dec 19, 2015 at 1:46 PM

I cant upgrade my honor 4c to lollipop at the time of upgrading it is showing that "version check fail".how can I fix this

milanco · Dec 18, 2015 4 0 0

linus2014 said:
custom.img recovery.img fastboot.img and syetem.img files most important

Hi, custom, system and recovery.img are there, but no fastboot.img
Beside that boot.img, crc, md5rsa etc...can I ignore all of these?

And still, I do not have the profile for Huawei G8. Can I just do it with the "unknown" profile?

linus2014 · Dec 21, 2015 at 11:15 AM

milanco said:
Hi, custom, system and recovery.img are there, but no fastboot.img
Beside that boot.img, crc, md5rsa etc...can I ignore all of these?

And still, I do not have the profile for Huawei G8. Can I just do it with the "unknown" profile?

I stand corrected "boot.img recovery.img custom.img and system.img" and ignore all the others.
extract update.app, Take the above files, and in fastboot mode flash them

xd4d3v · Dec 29, 2015 at 3:14 AM

Excellent tool. thanks for the hard work.
Can I suggest that you extend the tool in a way similar to flashtool for sony devices?
Not only for unpacking, but for flashing what was unpacked with fastboot.

You could also do a scripting trick to unlock the bootloader.
There is an APK flying around that provides the unlock code (Huawei's website is a pain to get it) but this needs root.

you could flash an rootable KK version,enable adb, install the apk, and use the provided unlock code for fastboot oem unlock.

worstenbrood · Dec 29, 2015 at 11:09 AM

xd4d3v said:
Excellent tool. thanks for the hard work.
Can I suggest that you extend the tool in a way similar to flashtool for sony devices?
Not only for unpacking, but for flashing what was unpacked with fastboot.

You could also do a scripting trick to unlock the bootloader.
There is an APK flying around that provides the unlock code (Huawei's website is a pain to get it) but this needs root.

you could flash an rootable KK version,enable adb, install the apk, and use the provided unlock code for fastboot oem unlock.

I don't have time anymore to put in these things, that's why i open sourced my work on the .app files. Maybe someone with more time on their hands (and i don't mean xml editors ...) can improve

ReyTech · Dec 29, 2015 at 4:50 PM

linus2014 said:
I stand corrected "boot.img recovery.img custom.img and system.img" and ignore all the others.
extract update.app, Take the above files, and in fastboot mode flash them

tks for the sharing that, can u pls share the precise adb commands as well to flash them! and any upgrade or downgrade protocol to be followed? pls inform?
wbr
reytech

linus2014 · Dec 29, 2015 at 5:30 PM

ReyTech said:
tks for the sharing that, can u pls share the precise adb commands as well to flash them! and any upgrade or downgrade protocol to be followed? pls inform?
wbr
reytech

with smartphone in fastbootmode the commands from prompt are:
- Fastboot flash boot boot.img
- Fastboot flash recovery recovery.img
- Fastboot flash cust cust.img
- Fastboot flash system system.img
- Fastboot reboot

---------- Post added at 06:30 PM ---------- Previous post was at 06:28 PM ----------

worstenbrood said:
I don't have time anymore to put in these things, that's why i open sourced my work on the .app files. Maybe someone with more time on their hands (and i don't mean xml editors ...) can improve

Hi, can you add my version 0.9.9.4, on your first post, it include p8 lite profile. thanks.
http://forum.xda-developers.com/showthread.php?t=2433454&page=31

FearFac · Jan 1, 2016 at 8:28 PM

Honor 7

@worstenbrood:

Can you include Honor 7 partition list (european distribution PLK-L01)?

ls -al /dev/block/platform/hi_mci.0/by-name/

lrwxrwxrwx root root 2016-01-01 21:10 3rdmodem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2016-01-01 21:10 3rdmodemnvm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-01 21:10 3rdmodemnvmback -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-01 21:10 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-01 21:10 cache -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2016-01-01 21:10 cust -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2016-01-01 21:10 dfx -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2016-01-01 21:10 dtimage -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-01 21:10 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-01 21:10 hifi -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-01 21:10 hisitest0 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2016-01-01 21:10 hisitest1 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2016-01-01 21:10 hisitest2 -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2016-01-01 21:10 mcuimage -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-01 21:10 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-01 21:10 modem -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2016-01-01 21:10 modem_dsp -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2016-01-01 21:10 modem_om -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-01 21:10 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-01 21:10 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-01 21:10 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-01 21:10 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-01 21:10 modemnvm_update -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-01 21:10 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-01 21:10 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-01 21:10 recovery -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-01 21:10 recovery2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-01-01 21:10 reserved0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-01 21:10 reserved1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-01 21:10 reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-01 21:10 securetystorage -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-01 21:10 sensorhub -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-01 21:10 splash -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-01 21:10 splash2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-01-01 21:10 system -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2016-01-01 21:10 teeos -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-01 21:10 trustfirmware -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-01 21:10 userdata -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2016-01-01 21:10 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-01 21:10 vrl_backup -> /dev/block/mmcblk0p2

narigondelsiglo · Jan 7, 2016 at 8:10 PM

xd4d3v said:
Excellent tool. thanks for the hard work.
Can I suggest that you extend the tool in a way similar to flashtool for sony devices?
Not only for unpacking, but for flashing what was unpacked with fastboot.

You could also do a scripting trick to unlock the bootloader.
There is an APK flying around that provides the unlock code (Huawei's website is a pain to get it) but this needs root.

you could flash an rootable KK version,enable adb, install the apk, and use the provided unlock code for fastboot oem unlock.

Could you point me to the APK you're talking about?

milanco · Dec 18, 2015 4 0 0

linus2014 said:
with smartphone in fastbootmode the commands from prompt are:
- Fastboot flash boot boot.img
- Fastboot flash recovery recovery.img
- Fastboot flash cust cust.img
- Fastboot flash system system.img
- Fastboot reboot

---------- Post added at 06:30 PM ---------- Previous post was at 06:28 PM ----------

Hi, can you add my version 0.9.9.4, on your first post, it include p8 lite profile. thanks.
http://forum.xda-developers.com/showthread.php?t=2433454&page=31

Hi, I get problem in Fast boot:
flashing boot.img - OK
falshing recovery.img - OK
by flashing cust.img and also by flashing system.img I get message:
FAILED <Remote: command not allowed>

why?

PS: the sizes of my 4 img. files are
boot.img = 43 364 352
recovery.img = 55 572 480
cust.img = 120 358 536
system.img = 2 468 607 568

linus2014 · Jan 9, 2016 at 11:40 AM

milanco said:
Hi, I get problem in Fast boot:
flashing boot.img - OK
falshing recovery.img - OK
by flashing cust.img and also by flashing system.img I get message:
FAILED <Remote: command not allowed>

why?

PS: the sizes of my 4 img. files are
boot.img = 43 364 352
recovery.img = 55 572 480
cust.img = 120 358 536
system.img = 2 468 607 568

your device is with bootloaer unlocked?

tileeq · Jan 9, 2016 at 1:46 PM

Fastboot wont allow for flashing kf the system. The file is too large.

Sent from my SM-G850F

[TOOL] Huawei Update Extractor [UPDATED: v0.9.9.5] | OPEN-SOURCE LIBRARY

Senior Member

Senior Member

Senior Member

Attachments

Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

New member

Senior Member

Senior Member