Database Info

[Completed] problem with huawei mt1-u 06

Hello,
I have a problem with a Huawei mt1-U06. When I turn it on it remains on the upload page Android and crashes. By starting the phone from recovery and tells me: Can not mount etc.
I tried to download the original firmware, I created the folder on the sd dload and inserted inside the file Update.app, but when I go to install the firmware on the phone can not find the file.
how can I proceed to reset the phone?

Hello,
Please post your question here:
http://forum.xda-developers.com/ascend-p6/ascend-mate
That forum covers more than one version of Ascend Mate but the members there should be able to help you.

Solution for B521 install problem

Hi everyone,
Problem: I tried every method I know to install B521 on my H60-L04; but every time I encountered a problem: the installer failed at "post_processing cust" (at 96%). After rebooting, the OS seemed to be half installed: ugly arrangement of icons, no keyboard, no hide navigation bar, ... and factory reset did not work. In short, I had a bad feeling about it.
Solution: Thanks to this post, there is a simple procedure to solve this problem. In cust partition of B521, there is only a folder for "eu" region and my phone requires a "ru" folder, so I just renamed "eu" to "ru" .
The procedure is:
Install B521.
Root the phone (I did by Multi-Tool).
Install an explorer which can access and modify root (I used ES File Explorer).
Go to "/cust/hw".
Rename "eu" folder to "ru".
Do factory reset.
Done! enjoy your life.
After above procedure, my phone has this features:
Swype and Google keyboards
Supports 4G and has a button for it in notifications
Hide navigation bar button
Motion control
Mirror and Smart Controller
Some games!
...
Note that may be your phone requires different country code than "ru", but even in indian rom B510, there is a "ru" folder in "/cust/hw".
Also I find a procedure for users who don't want to root their phones:
you can extract "cust.img" from "update.app" using HuaweiUpdateExtractor and unpack "cust.img" contents by ext4_unpacker. Then rename the "eu" folder to ru" and repack it by tools described here. Finally flash modified "cust.img" in fastboot mode. Note that because repacking tools need linux, I did not do this and don't know even it works or not.

what's your base version of kitkat?
i have B370, can i directly go for the update of B521?

droyd.014 said:
what's your base version of kitkat?
i have B370, can i directly go for the update of B521?
Click to expand...
Click to collapse
I tried to upgrade from B370, B380, B390, B394 and B500 and all are the same. If you buy your phone from eu region, it must upgrade with no problem.

thanks! i would give it a try
keep you posted

je.nickp said:
Hi everyone,
Problem: I tried every method I know to install B521 on my H60-L04; but every time I encountered a problem: the installer failed at "post_processing cust" (at 96%). After rebooting, the OS seemed to be half installed: ugly arrangement of icons, no keyboard, no hide navigation bar, ... and factory reset did not work. In short, I had a bad feeling about it.
Solution: Thanks to this post, there is a simple procedure to solve this problem. In cust partition of B521, there is only a folder for "eu" region and my phone requires a "ru" folder, so I just renamed "eu" to "ru" .
The procedure is:
Install B521.
Root the phone (I did by Multi-Tool).
Install an explorer which can access and modify root (I used ES File Explorer).
Go to "/cust/hw".
Rename "eu" folder to "ru".
Do factory reset.
Done! enjoy your life.
After above procedure, my phone has this features:
Swype and Google keyboards
Supports 4G and has a button for it in notifications
Hide navigation bar button
Motion control
Mirror and Smart Controller
Some games!
...
Note that may be your phone requires different country code than "ru", but even in indian rom B510, there is a "ru" folder in "/cust/hw".
Also I find a procedure for users who don't want to root their phones:
you can extract "cust.img" from "update.app" using HuaweiUpdateExtractor and unpack "cust.img" contents by ext4_unpacker. Then rename the "eu" folder to ru" and repack it by tools described here. Finally flash modified "cust.img" in fastboot mode. Note that because repacking tools need linux, I did not do this and don't know even it works or not.
Click to expand...
Click to collapse
Does screen off gestures working after this like double tap to wake the screen?

yash4505 said:
Does screen off gestures working after this like double tap to wake the screen?
Click to expand...
Click to collapse
I think this features requires an additional sensor which honor 6 doesn't have it.

je.nickp said:
I think this features requires an additional sensor which honor 6 doesn't have it.
Click to expand...
Click to collapse
Thanks for replying...

Downgrading Honor 6_L04 from B507 to B380-Honor 6-Honor
Do you have any Youtube link to solve this issue of Downgrading Honor 6_L04 from B507 to B380-Honor 6-Honor

Hi, My l01 flashed B560 of l04, how to go back to B535, please help me.

How To Create a Flashable ZIP File Through TWRP Using Update.app File ???

Hi
I Think the title says it all ....
so here is my problem
I have the L29C900B133 update.app file And I want to be able to flash it via TWRP
This Rom is the most complete Rom till today for mate 8 and I think flashing it will solve my problems including applying themes and missing vendor
So please help
How can I make a flashable zip file using this update.app file ??
If there is any method please let me know or send a link
And Before anyone says anything i already looked in huawei update extractor and using it you can make flashable zip files but huawei mate 8 partition map is not available yet and i'm afraid that if i use mate 7 partition map it will brick my phone
tnx in advance

Camera is broken.

Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?

SeanPHTRPW said:
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
Click to expand...
Click to collapse
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.

ante0 said:
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
Click to expand...
Click to collapse
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!

SeanPHTRPW said:
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
Click to expand...
Click to collapse
It would probably fix it yes, but no boot image or hw/public exist for B110 so I'm guessing it shipped with that build.
You'd have to update, using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't think you can use Firmware Finder as you're probably missing the System Update feature.
Either that one I linked or FunkyHuawei, but Funky cost money to use.

Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile

SeanPHTRPW said:
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
Click to expand...
Click to collapse
Yes, download base, os and MHA. Extract all to the same folder. You should only have one folder named HWOTA and the files/folders in that. If it extracts to a folder with the same name as the zips, enter the folders and copy hwota folder then go back one folder and paste/merge so you end up with one folder named HWOTA. Easiest way is putting it directly in C:\hwota\, if your windows version allows it. Else place it on desktop. (long file paths or a path containing spaces might make hwota not function correctly).
You need to download all 3 files (fullota update.zip, hw zip and Public zip), easiest way is using firmware finder to download. Either mobile or the pc version. For pc go to the common base tab and search for your model and then download the build you want including public and HW zips.
You only need to download the fullota update, hw and Public zip of the build you're updating to. If you're on b110 and going to update to B172 you only need to download B172.
Rename the files according to the guide (update.zip, update_all_hw.zip and update_data_public.zip), place them in either hwota/update folder or make a HWOTA folder on your sdcard and put the renamed files there.
When running hwota, select script update folder or sdcard update folder depending on where you put the files. Select same model update.

One last question:
Does it have to be FULLOTA, not just OTA?

Unbrick you Mediapad M5 - Install OTAs - Customized HuRUpdater for Mediapad M5

I am sharing with you here my version of HuRUpdater 0.4 customized for the Mediapad M5. I am not taking any credit here for HuRUpdater, the original work can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279. Please follow the instructions there on how to install it to an SD card. Also unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the as card where you have the other zips. Finally run it from custom recovery.
Your boot loader needs to be unlocked.
HuRUpdater can be used to:
Recover the tablet from a soft brick or bootloop. As long as you can install and access TWRP, it should be good to go.
Restore the tablet back to stock after installing a custom ROM.
Install full OTA updates after unlocking the bootloader, since it appears you cannot install OTAs anymore once the bootloader is unlocked.
Revert back to an older version of the ROM (watch out for XLOADER versions though, make sure that match https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241)
When I was trying to install an OTA after unlocking my bootloader and installing a custom ROM, I found out that HuRUpdater doesn't work out of the box for the Mediapad M5, so I made some minor customizations:
HuRUpdater looks for the volume keys when it starts up in order to read user inputs, and if it doesn't find it, it bails out. I removed that check for the volume keys, so the script will now run without requiring any user input.
HuRUPdater brings its own busybox binary, but it uses unzip trying to install it, which doesn't seem to be available on the M5. I changed it to copy it to the destination instead from the same folder as the other zips.
HuRUpdater checks whether the update will lock your bootloader, and then require you to press a volume key to confirm. Since volume keys are not working and this locking is probably undesired, the script will now bail out if it finds that your booloader may become locked.
NOTE: After successful flash you have to factory reset! And this must be done using the stock recovery, not TWRP!
I have only used it successfully on the Mediapad M5, but but there should be no reason why it wouldn't work on other devices on which HuRUpdate fails when looking for volume keys.

First big thanks for your post! I have a blank Mediapad here without anything any system flashed on it. When I flash HuRU it states an error with the following lines in recovery.log:
Code:
mkdir: 'utils': File exists
cp: bad '/external_sd/CMR-W09C432/hurupdate-binary': No such file or directory
chmod: utils/hurupdate-binary: No such file or directory
cp: bad '/external_sd/CMR-W09C432/busybox': No such file or directory
chmod: utils/busybox: No such file or directory
/tmp/updater[261]: unzip: not found
/tmp/updater[261]: /tmp/utils/busybox: not found
Error with update.zip file. See recovery.log for more details
Updater process ended with ERROR: 1
Any idea on how to fix this?

valko8877 said:
First big thanks for your post! I have a blank Mediapad here without anything any system flashed on it. When I flash HuRU it states an error with the following lines in recovery.log:
Code:
mkdir: 'utils': File exists
cp: bad '/external_sd/CMR-W09C432/hurupdate-binary': No such file or directory
chmod: utils/hurupdate-binary: No such file or directory
cp: bad '/external_sd/CMR-W09C432/busybox': No such file or directory
chmod: utils/busybox: No such file or directory
/tmp/updater[261]: unzip: not found
/tmp/updater[261]: /tmp/utils/busybox: not found
Error with update.zip file. See recovery.log for more details
Updater process ended with ERROR: 1
Any idea on how to fix this?
Click to expand...
Click to collapse
Oh, sorry, think you found a bug and I need to update the instructions. Please unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the sd card where you have the zips and try again.

konradsa said:
Please unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the sd card where you have the zips and try again.
Click to expand...
Click to collapse
Thanks a lot! That worked. It got way too late for me, to come to this idea by my own. Spent several hours to revert to stock firmware and now your version of HuRU seems to to do its work. Currently its flashing Huawei's ZIP files.

valko8877 said:
Thanks a lot! That worked. It got way too late for me, to come to this idea by my own. Spent several hours to revert to stock firmware and now your version of HuRU seems to to do its work. Currently its flashing Huawei's ZIP files.
Click to expand...
Click to collapse
Great, glad it worked for you, I updated the instructions in the first post. The reason I ended up with variant of hurupdater is just like you I found out nothing else works, I was trying to install an OTA.l after unlocking boot loader. When I have some time I will think about how to make this a little more seamless. Let me know if you see any other problems.

konradsa said:
Let me know if you see any other problems.
Click to expand...
Click to collapse
Yeah, so far so good, tablet is now on stock firmware. The flash was successful, after extracting both binaries from your HuRU ZIP to same folder as the other ZIP's including HuRU, flashing the HuRU ZIP itself again and letting it do it's magic. That tool saved me a lot of more hours of working out on how to revert to Stock, while every Huawei way to go and also the Androids way to go have failed. Thanks again! I can also confirm, that the "vanilla" version of HuRU does not work on Mediapad because of the mentioned error of not finding the user input device. Using the specialized Mediapad one instead did it's thing. Thumbs up!

You really saved me!!!! I tried everything before this post... I was about to give up.
Wanted to install multi user function (which has been deleted in the lite version), gone through a series of steps and post including unlocking, rooting, flashing custom bootloader, installing a mask, etc... throughout the way something happened and I got stuck at the TWRP bootloader, nothing worked, everything I tried yielded an error of some kind. This was my salvation! I'll be forever in debt! Tanks a lot!!!!