Database Users

Software install failed!

Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Many thanks and regards

demonjo2001 said:
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Click to expand...
Click to collapse
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.

1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk

zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Thank you for answering, I did used Huawei MultiTool and Unbricked my device. I flashed four img files(SYSTEM,CUST,RECOVERY,BOOT) and now i am back to stock rom and running smoothly.
I tried to use force update feature on my device after that but again i got the same result, it stopped at 5% and failed. I guess i will keep it the way it's now.
Many thanks; you guys are awesome!

hamzio7 said:
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
Click to expand...
Click to collapse
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,

demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
It's for the other partitions like cust, modem etc.

demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
Don't use any other img file. And don't flash userdata.
If it works, don't change it. ?

Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.

goldfinv said:
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
Click to expand...
Click to collapse
Fastboot woukd be the only choice.
Sent from my honor 5X using XDA Labs

adriansticoid said:
Fastboot woukd be the only choice.
Click to expand...
Click to collapse
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.

goldfinv said:
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
Click to expand...
Click to collapse
What partitions did you flash?
Sent from my Galaxy Tab 3 using XDA Labs

adriansticoid said:
What partitions did you flash?
Click to expand...
Click to collapse
The usual. Boot. System. Recovery. Cust.

goldfinv said:
The usual. Boot. System. Recovery. Cust.
Click to expand...
Click to collapse
No errors in fastboot?
Sent from my Galaxy Tab 3 using XDA Labs

adriansticoid said:
No errors in fastboot?
Click to expand...
Click to collapse
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.

goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
Goodluck with it man. I am sorry I can't help you any further as I am new in hsing fastboot. I got used to Odin in Samsung.
Sent from my Galaxy Tab 3 using XDA Labs

goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
There's no other solution, either stock img files or some sort of transitional package.

zinko_pt said:
There's no other solution, either stock img files or some sort of transitional package.
Click to expand...
Click to collapse
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.

goldfinv said:
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
Click to expand...
Click to collapse
Let us know if you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs

Same issue with me as well please help me in this case.
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the lasthttps://cdn-cf-3.xda-developers.com/images/smilies/frown.gif installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse

Huawei P10 Lite (WAS-LX1AC109B110) bricked?!

I wanted the unofficial LineageOS on my device, but i messed up some things. Since it didn't work I asked for help and was told that I should flash the stock ROM's image files via fastboot. So I downloaded the WAS-LX1AC109B110 version update.zip file, grabbed the update.app file and extracted it. I got the BOOT.IMG, CUST.IMG, RECOVERY.IMG, SYSTEM.IMG files. Flashed them one-by-one via fastboot and ended up bricking my devices.
I don't know what happened, but now all my device can do is to boot the Huawei eRecovery, where I can do nothing;
and to boot the EMUI updater (or what is it called; the one what uses the dload folder on the sd card), but it either says that the package file doesn't exist, or if I put the update.app file(and the other files from the update.zip) into the dload folder it says "Software install failed! Get help from: (an emui page link)" (the link redirects to a 404 error page).
I can't boot into fastboot mode, neither into the recovery.
Please tell me that I don't need to buy a new phone, it's pretty new.

Have you tried the service ROM unbrick from this thread https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 ?

Drain the battery, than hold volume down and connect the USB cable. You should use fastboot again.
Sent from my [device_name] using XDA-Developers Legacy app

Zoeriva said:
Drain the battery, than hold volume down and connect the USB cable. You should use fastboot again.
Click to expand...
Click to collapse
Well, it helped. Thank you! Now I am able to enter fastboot mode, however it's nothing much of a help, because no matter what I do it just won't boot. I flashed everything once again. Now it's slightly better, since the Huawei boot animation is played, but then it restarts. Any idea? (yes, i did erase the user data and cache)

hundred_miles_high said:
Have you tried the service ROM unbrick from this thread https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 ?
Click to expand...
Click to collapse
My version isn't listed there. WAS-LX1AC109B110

Try Google. Than flash boot.img, recovery.img, recovery2.img and as last system.img.
Sent from my [device_name] using XDA-Developers Legacy app

Zoeriva said:
Try Google. Than flash boot.img, recovery.img, recovery2.img and as last system.img.
I already did that. Doesn't work.
Click to expand...
Click to collapse

You are flashing the wrong rom.
Sent from my [device_name] using XDA-Developers Legacy app

Zoeriva said:
You are flashing the wrong rom.
Click to expand...
Click to collapse
I checked my carriers site. It says that as of 16.05.2017 the last approved firmware for their Warsaw-L01A is WAS-LX1AC109B100.
Even if there was any newer version, that wouldn't change the case, would it? So I should be able to flash the WAS-LX1AC109B[anything] firmwares, right?

keretrendszer said:
I checked my carriers site. It says that as of 16.05.2017 the last approved firmware for their Warsaw-L01A is WAS-LX1AC109B100.
Even if there was any newer version, that wouldn't change the case, would it? So I should be able to flash the WAS-LX1AC109B[anything] firmwares, right?
Click to expand...
Click to collapse
Otherwise, just rebrand your phone and use stock FW explained earlier.

supersu - maybe these make bootloop?

Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks

I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk

so...i'm in 8.1 and these is the conclusion in that state after few tests.

I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk

What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk

stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.

the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..

Wifi wont toggle on after flashing boot img

I flashed twrp on boot using fastboot instead of on recovery and was stuck in a bootloop. So I found a stock boot img online and flashed that back onto boot and now it boots but wifi won't turn on anymore.

Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.

oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
Found it, will try it now thank you.

oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
I have no idea how to go about using a python script to unpack the OTA images from the file. What should I do?

Don't download the OTA image. Download the fastboot image. Use 7-zip to extract.

There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.

racer1077 said:
There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.
Click to expand...
Click to collapse
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.

oreo27 said:
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.
Click to expand...
Click to collapse
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.

racer1077 said:
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.
Click to expand...
Click to collapse
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".

oreo27 said:
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".
Click to expand...
Click to collapse
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.

racer1077 said:
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.
Click to expand...
Click to collapse
Mi Flash doesn't seem to accept spaces in the path of the firmware so that was probably the issue. No worries! You'll want to update to the latest version using the system updater to get back on your actual version.

How to update vendors successfully.

I went from stock with the February security patch to rooted running the latest update from Havoc. I am getting a vendor mismatch message when I reboot my phone. I am looking for the correct steps to update my vendors update to both slots in tarp. I've read different approaches. Just a bit confused.
Sent from my [device_name] using XDA-Developers Legacy app

gregg0829 said:
I went from stock with the February security patch to rooted running the latest update from Havoc. I am getting a vendor mismatch message when I reboot my phone. I am looking for the correct steps to update my vendors update to both slots in tarp. I've read different approaches. Just a bit confused.
Click to expand...
Click to collapse
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:

Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
I'm not close to a computer so option 1 is not available to me. Is adb the best way or is just user preference?
Sent from my [device_name] using XDA-Developers Legacy app

gregg0829 said:
I'm not close to a computer so option 1 is not available to me. Is adb the best way or is just user preference?
Click to expand...
Click to collapse
Either way will get the job done. I flashed vendors all the time with twrp in my rom hopping days without issue. Strictly your call my friend :good:

Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
Huh? I've never had to flash the vendor in TWRP more than once.

Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
What's up man, long time no see! So you happen to have a link that contains Pixel slot commands like this? I'm bootloader unlocked on the Pixel 2 already via Nathanchance's guide but still catching up on the differences from my Nexus 5X. I'm just curious about the slot specific/all slot commands like the one above.

SlimSnoopOS said:
What's up man, long time no see! So you happen to have a link that contains Pixel slot commands like this? I'm bootloader unlocked on the Pixel 2 already via Nathanchance's guide but still catching up on the differences from my Nexus 5X. I'm just curious about the slot specific/all slot commands like the one above.
Click to expand...
Click to collapse
Hope you've been good my friend. I don't have a link for the commands, many I have just learned over time. I'm sure google search could help you out, and, you can always type...fastboot help...while in fastboot mode that will show a list of commands :good:

another way to update the vendor is to download the full factory image, then open it in a file explorer. open the zip inside the zip and find vendor.img. extract that somewhere and flash it. this is how ive done it. cuz i never have a computer handy when i want to update.