Develop Bugs

Bricked

I have no Idea what i did to brick the phone but it wont get past the huawei splash screen. i am a complete noob at this so please dont explain everything clearly. i do not have any custom recovery installed (i have stock Android system recovery <3e>)
EDIT:
i have also downloaded the emotionUI UPDATE.APP and put it on the sd card but when i boot up this happens;
(i havent posted enough to allow me to send links and the attachment button is broken so just remove the spaces in the link and it will work
http s: //vimeo.com/121563634
i downloaded the firmware from some chinese place but im too lazy to check where but if it rly matters i can

mbdawg said:
I have no Idea what i did to brick the phone but it wont get past the huawei splash screen. i am a complete noob at this so please dont explain everything clearly. i do not have any custom recovery installed (i have stock Android system recovery <3e>)
EDIT:
i have also downloaded the emotionUI UPDATE.APP and put it on the sd card but when i boot up this happens;
(i havent posted enough to allow me to send links and the attachment button is broken so just remove the spaces in the link and it will work
http s: //vimeo.com/121563634
i downloaded the firmware from some chinese place but im too lazy to check where but if it rly matters i can
Click to expand...
Click to collapse
To me it looks like you made a bad update and now you need to reflash. Now if you know which firmware was the last working one on thw phone i can make a suggestion on what to put in the sd card to flash.
Sent from my SM-G850F

tileeq said:
To me it looks like you made a bad update and now you need to reflash. Now if you know which firmware was the last working one on thw phone i can make a suggestion on what to put in the sd card to flash.
Sent from my SM-G850F
Click to expand...
Click to collapse
sry for the late reply. i have fixed it (i just downloaded the firmware from huawei's website and it worked flawlessly DERP) thanks anyway

VS98613b saved image and rooted

Yesterday I took the vs98613b update. I saved the image, rooted the image, and put that image on my phone. Should I be sharing these images on here for others? Would sharing this even help others? Would my information be safe in sharing these images? I'm a junior member for a reason . Usually copying info off the backbones of others so wondering if this stuff would help the community.
Rootedsystem https://drive.google.com/file/d/0BzgjlYf1ixXVUk51U3lRT1RNOXc/view?usp=docslist_api
MD5 1c0a979e2f9ab35601b724ce17d7e141
System https://drive.google.com/file/d/0BzgjlYf1ixXVVkY0T2w2NGdzcDg/view?usp=docslist_api
MD5 4cd02a89c95730871a5e55f02442d94d

I would say yes, it could help people who did not make a stock backup or want a rooted image to flash.
I don't know what personal information, if any would be in the image and would like someone knowledgeable to answer that.

A system image won't have any personal info.
I know there's at least two of us that would prefer a stock, rooted image.

OK, is the best way to share it by uplaoding it to Google drive or are there better methods? They are each over 4 gig.

jmichalakjr said:
OK, is the best way to share it by uplaoding it to Google drive or are there better methods? They are each over 4 gig.
Click to expand...
Click to collapse
Zipping first will bring them down to less than 2GB. Post your MD5SUMs too.

OK, zipping them now on my phone, installing checksum md5 app to get the md5sum. Hopefully will have it up within the hour. My upload speeds are sub par, perhaps by morning the files will be uploaded.

If you can grab the boot.img too that would be awesome.

Rootedsystem https://drive.google.com/file/d/0BzgjlYf1ixXVUk51U3lRT1RNOXc/view?usp=docslist_api
MD5 1c0a979e2f9ab35601b724ce17d7e141
System https://drive.google.com/file/d/0BzgjlYf1ixXVVkY0T2w2NGdzcDg/view?usp=docslist_api
MD5 4cd02a89c95730871a5e55f02442d94d

Awesome, thanks for sharing!
I got as far as un-rooting 11a, getting OTA, doing factory reset and making a stock image of 13b. But don't know or have ubuntu to inject root into my own image. I can share my stock 13b image as well if people need it though.
Edit:
Did you use ubuntu/linux to inject root into your own image?
Is system your stock 13b image?
Thanks again for your images!
Edit2: If this link ever goes down, someone PM me and i'll upload my rooted image I created and tested.

Thanks! Downloaded at 4 mb/s, flashed, working great!

System is stock 13b. Found a program that loaded Ubuntu on my usb stick so I could temporarily run Ubuntu on my computer. Then injected the root from the ubuntu terminal per directions from the other thread.

Hey does anyone know how to disable the 10 attempts before wipe?
It is located at /system/customize/ACC/default.xml on other phones by changing the 10 to a 0
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">10</item>
Thanks

Raise it to 1000?

/system/customize/ACC/default.xml does not exist on the G4

The download doesnt work for me. It states the file is missing or has been deleted

tylerw1369 said:
The download doesnt work for me. It states the file is missing or has been deleted
Click to expand...
Click to collapse
Weird, I checked it and it wasn't there. I copied new links into the op.

Has anyone tried updating their G4 with the upgrade assistant? I have a G2 and I used the assistant to upgrade it to the new 3AA software and it said an upgrade was available and it had a 1.6 GB file to download and while it was downloading I found the KDZ for the 3AA version in C:\LGMobileUpgrade\LGMOBILEAX\phone. I have not been able to find the KDZ for that version anywhere on the net.....
I would love to see if anyone could do this in the assistant with their G4 to see if we can get a 13B KDZ......

I could use a 13B KDZ. my phone stuck in a bootloop
Installed a rooted 13B image and it was working great. Did a factory reset and started installing apps and whatnot. Totally forgot to copy a 13B image back onto phone incase I need to reflash root..... Not sure what happened, plugged phone into computer to move some backups back on phone and it restarted. now stuck on bootloop. This is not good.
I have my stock 13b image and the rooted image. Anything I can do with that?

I thought the system image was the kdz. But perhaps I am confused.

kdz's are not rooted. This is just the 13b system image that was rooted.

B163 OTA Update (Chinese)

Here is unreleased B163 OTA update. (Must be on B156)
https://drive.google.com/file/d/0B79PB4FhWfJAM0hMUWNDanE1ZW8/view?usp=sharing
Note that I haven't found a way to install it yet.
Change log is:
Dear customers, this update improved experience of camera and system performance. involved latest Google patch, Please update your device for improved experience.
Optimized experience of camera.
Improved system performance.
Improved security of system.
Improved system stability.
I have found a way to get all OTA and full updates. Unfortunately, this update only exists in OTA form right now.
I'm hoping someone who has a non-Chinese Mate8 can get in touch with me and I can find all the updates for it as well.

Thank you. How would you install it on the AL10 (stock recovery/unrooted) device?

wow, good work there buddy! looking forward to more OTA leaks from your side

Hiw to install?

please read the first post: "Note that I haven't found a way to install it yet."

Guys full rom (B156) here to hope to pass to B163
https://androidfilehost.com/?fid=24399994186367275

i think this technique can be used if we are able to extract the files into the OTA file.
http://forum.xda-developers.com/showpost.php?p=65113953&postcount=166

CyberMomo said:
i think this technique can be used if we are able to extract the files into the OTA file.
http://forum.xda-developers.com/showpost.php?p=65113953&postcount=166
Click to expand...
Click to collapse
No, mate ota file don't work in this way

If I have enough free time, I will create a way to install whatever OTA you want by reverse-engineering the network protocol. Stay tuned

good stuff, hope we manage on how to update by ota zip .
it seems mate8 is not allow local ota update.

hkfriends said:
good stuff, hope we manage on how to update by ota zip .
it seems mate8 is not allow local ota update.
Click to expand...
Click to collapse
download the ota zip file but it in dload folder and but it in sd card
then power off mate 8
and push volume up+down+power for 10 second
the update will begin

rowihel2012 said:
download the ota zip file but it in dload folder and but it in sd card
then power off mate 8
and push volume up+down+power for 10 second
the update will begin
Click to expand...
Click to collapse
I tried that with B156 and it froze at 5%

ajsmsg78 said:
I tried that with B156 and it froze at 5%
Click to expand...
Click to collapse
I confirm that...putting the zip on internal sd it doesn't give the message "impossible to find the update package" (or similar I don't remember) as you put it in the external...the verification starts, starts also the "updating phase" but it freezes immediately at 5% (in my opinion without modifying anything, cause I was able to reboot normally)....just to be clear, I'm on B156 but I've root and decrypted boot...maybe the success could be obtained starting from a clean b156....maybe rowihel2012 could kindly give us more details on his upgrade success (phone model, starting firmware status,...)

lukemo said:
I confirm that...putting the zip on internal sd it doesn't give the message "impossible to find the update package" (or similar I don't remember) as you put it in the external...the verification starts, starts also the "updating phase" but it freezes immediately at 5% (in my opinion without modifying anything, cause I was able to reboot normally)....just to be clear, I'm on B156 but I've root and decrypted boot...maybe the success could be obtained starting from a clean b156....maybe rowihel2012 could kindly give us more details on his upgrade success (phone model, starting firmware status,...)
Click to expand...
Click to collapse
Non-root stock does not work either to install this. There's an .app file that HiSuite recognizes if you unzip the file that you downloaded... However once loaded and phone restarts it just takes you to a screen where you can wipe or restart. Tried the other way too and get the 5% and then freezes. Something isn't right with the archive. Saw another dload folder on root but can't mess with it since I'm stock. Maybe you could try that directory

acer73 said:
Guys full rom (B156) here to hope to pass to B163
https://androidfilehost.com/?fid=24399994186367275
Click to expand...
Click to collapse
This rom is for NXT-L29 version?

theyre both for AL10 but u can crossflash. also, no one has gotten B163 to work yet
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

In the root directory there is a folder called dload and inside is a file called update_huawei_dload. Has anyone tried renaming the update to that same name and putting it in that folder?

Has anyone tried to flash this OTA zip file by TWRP ?
I just opened this zip file and found some of scripts which are similar with that's used in TWRP.

I flashed L29 152 update NXT-l29C432B152-FULL-OTA in TWRP on my AL10 after deleting all data. And everything works, so far, apart from themes.
They apply but doesnt do anything. Also it did throw up some error but forgot to take note of it.
I presume b163 will do the same thing,

ajsmsg78 said:
In the root directory there is a folder called dload and inside is a file called update_huawei_dload. Has anyone tried renaming the update to that same name and putting it in that folder?
Click to expand...
Click to collapse
it dosn't work.

Update from PI3 to official Nougat.

I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Here is the Odin files for PI3 for those that need it. G930VVRU4API3

Testing now
---------- Post added at 11:51 PM ---------- Previous post was at 11:17 PM ----------
Still not working. Didn't get the log though, but there was a mounting error and then I believe I saw something status 7. Not sure what else is wrong.

Are you on PI3?

CVertigo1 said:
Are you on PI3?
Click to expand...
Click to collapse
I am.

Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.

CVertigo1 said:
Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.
Click to expand...
Click to collapse
Thank you for your help.

Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.

CVertigo1 said:
Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.
Click to expand...
Click to collapse
It is not

The best advice I have is to Odin all four PI3 files, but not Home_CSC. It will give you the cleanest install and take everything else out of the equation. I'd backup everything with Smart Switch first, then restore it all after updating.

CVertigo1 said:
I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Click to expand...
Click to collapse
What if you are on PKC? You think it will still work?

Crsdr37 said:
What if you are on PKC? You think it will still work?
Click to expand...
Click to collapse
Im on pkc also

Probably not, but you are welcome to try. If it doesn't work, then flash back to PI3 and update from there.

Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through

Crsdr37 said:
Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through
Click to expand...
Click to collapse
I already put this in the steps, but I guarantee a lot of people will forget to follow it lol.

I got mine updated. Here's what I did.
I reluctantly used the Verizon software repair tool to "repair" the OS. It took quite a while but did reload everything. After that I just took the OTA and it seemed to work fine. I would imagine that Odin would have worked too.

I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?

mogulman01 said:
I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?
Click to expand...
Click to collapse
Updated using the process from OP, worked fine.

I was on PI3 firmware and I kept checking without getting the new software from yesterday. Just now I connect my phone to the PC and open up Smart Switch, it tells me the new update is available.

I was having this same problem. I couldn't get my phone to take the OTA even after unrooting and I had to end up using Odin and flashing that BL file as well as the other three that you normally flash. give that a go if you're still having problems!

Upgraded directly from PKC (beta) using SamFirm to download and flash new verizon firmware via odin. Worked great. Didn't have to downgrade back to pe1.

Problem: Bootloop and "software install failed"

Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.

Can you boot to erecovery?

adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
I can but it just puts out the message "Getting package info failed"

Filo83 said:
I can but it just puts out the message "Getting package info failed"
Click to expand...
Click to collapse
Please try another version of firmware.

adriansticoid said:
Please try another version of firmware.
Click to expand...
Click to collapse
That is my problem not to know which version to use because three dowloaded EU-versions weren't successful to install. It resulted in an error at 5 % of the 3-buttons-install mechanism.

Filo83 said:
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Click to expand...
Click to collapse
you download the nocheck recoveries from my rebranding guide, download the corresponding firmware by morph (important!), flash both recovery images just like stated in the guide, boot into recovery mode like you would do to boot into twrp, do a factory reset, reboot and insert the microsd with the dload folder from extracted downloaded firmware and boot into force dload mode (vol+ and vol- and power) - the installation should start now and reset everything back to full stock.
Regards

Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin

Filo83 said:
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Click to expand...
Click to collapse
OTA packages cannot be installed via twrp at the moment
you should use stock recovery for that!
Best regards
Grüße zurrück aus Berlin nach Berlin

Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.

Filo83 said:
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Click to expand...
Click to collapse
soooo, if you flashed one of @-=MoRpH=- 's firmwares, your device is back to stock and the recoveries have been overwritten again! I don't recommend flashing OTA updates or other things through the NoCheck version as it is only intended for worst-case cenarios.

But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.

Filo83 said:
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Click to expand...
Click to collapse
extract the firmware and flash manualy using fastboot

thilak devraj said:
extract the firmware and flash manualy using fastboot
Click to expand...
Click to collapse
That is just needed to be done as last resort. Better stick with dload.

adriansticoid said:
That is just needed to be done as last resort. Better stick with dload.
Click to expand...
Click to collapse
he said he got some errors doing dload, so this method works too

thilak devraj said:
he said he got some errors doing dload, so this method works too
Click to expand...
Click to collapse
He must find the right firmware first.

adriansticoid said:
He must find the right firmware first.
Click to expand...
Click to collapse
finding a firmware for huawei devices is a pain in the ass, you know

thilak devraj said:
finding a firmware for huawei devices is a pain in the ass, you know
Click to expand...
Click to collapse
That's why we have Firmware Finder.

adriansticoid said:
That's why we have Firmware Finder.
Click to expand...
Click to collapse
even in firmware finder, it will be difficult sometimes for sone devices

thilak devraj said:
even in firmware finder, it will be difficult sometimes for sone devices
Click to expand...
Click to collapse
Maybe. But they are constantly improving.

adriansticoid said:
Maybe. But they are constantly improving.
Click to expand...
Click to collapse
i appreciate the firmware finder, but sometimes, its just inappropriate