Database Users

[Q] [Mi2S] Impossible to flash custom recovery on MIUI 5.5.15 Beta

Hi everyone,
I've run out of ideas on this one and other threads couldn't really help me/were closed already.
I tried CM, stock android by Ivan and M1cha as well as some others, but about a month ago, I was curios for MIUI 6 based on Lollipop for my Mi2s and changed from M1cha's CM12 5.0.1.
Now that I've seen that Ivan published his 5.1.1 I wanted to try it out. He also provides us with a modified custom recovery that I wanted to flash.
First, I renamed the file to update.zip and tried to flash it in Mi-Recovery 2.0.1, which didn't work due to the failing signature verification.
Also, choosing update package in the Updater app in MIUI didn't work out, it immediately tells me something went wrong.
Then I thought, why not use fastboot? That worked before.
Not this time. I tried the simple way, meaning just fastboot flash recovery recovery.img: Then, bc it didn't work, I first erased the recovery partition and then flashed the recovery.img, which was still unsuccessful.
Whenever I try to enter recovery mode, my phone just gets stuck showing the MI logo and not doing anything.
I can reenter fastboot mode or simply reboot to the system as usual, except for when no system is installed.
When I gave up on the custom recovery thing, I simply tried to flash the ROM via update.zip methods, as well as via fastboot. None of them worked, either because the signature verification fails (stock recovery) or because the zip file does not contain the android-info.txt and the other txt file.
As mentioned above, upon entering fastboot -w and then flashing the recovery.img, I can suddenly enter recovery mode. This sucks!
TL;DR: No usual method of flashing either custom rom or recovery works (to my knowledge)
Can anyone help me? I know its stupid but I start feeling kind of boxed in on MIUI.
Thanks in advance

fastboot oem unlock
fastboot flash recovery recovery.img

unfortunately, that didn't work either...

leonfromotown said:
unfortunately, that didn't work either...
Click to expand...
Click to collapse
Do fastboot devices and tell us the output

SkiFire13 said:
Do fastboot devices and tell us the output
Click to expand...
Click to collapse
5b799fb fastboot
looks just the way it did before

Help installing a ROM.zip from ASUS on ZE500KL

Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks

Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?

Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed

Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.

kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.

Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip

Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.

Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.

Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172

I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??

Can you try to ADB Sideload the ASUS ROM?

sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.

Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.

If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.

up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:

2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases

Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy

I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script

Hi,
I'll test it, and will give feed-back
Thanks

Problem after root attempt

Hello,
I tried to root my P8 Lite, which is something I've already done on a lot of other smartphones. So I first unlocked my bootloader, then I tried to follow a guide to root it. Everything was going smooth, but when I hit enter for the last time into the command line (at this point of the process, it just installed superSU) my phone rebootd and stucked on the huawei logo. After 20mn I decided it was enough, I unplugged it and hard rebooted it, but still stuck on huawei logo.
Since this, I wasn't able to reboot my phone, nor enter the fastboot/rescue mode. Now I tried on more time to enter the fastboot, and I don't know why but after a few time it showd up !
So basically my phone is now on fastboot mode, unlocked, and I come here to seek answers about the method to flash it and start again with a fresh android. I don't even know where to find the correct rom to flash, nor how to flash, if for instance I should use adb, etc.
If someone here is able to help me, that would be greatly appreciated.
By the way, I manually updated the phone to android 6 and EMUI 4.
Thank you a lot for enlightments.

Hello! Since you are in fastboot mode you can easily fix the issue. Just download a stock rom you wanna flash and use (you can try the new B588) and with the Huawei Update Extractor, extract the boot.img, recovery.img, cust.img, system.img from the UPDATE.APP file. Then flash these in the order i wrote them (using the fastboot command for example:
Code:
fastboot flash boot boot.img
, same thing for all of these just change the file names). That is how i fixed my last 2-3 bootloops. I would suggest looking here first though: https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 on Chapter 4. Hope this helps and good luck

Hi,
Thank you for your answer.
Problem is now, my phone ran out of bttery so not in fastboot mode anymore and I just can't figure out how to go back in fastboot anymore.
I tried to power on the phone while pressing vol up, wait for the huawei logo and wait for ten more seconds, nothing except a black screen. I tried vol down, both vol up and down, still nothing. Thing is, yesterday I don't even know how I managed to enter fastboot, I just tried, didn't work, so I put my phone on the bed, and ten minuts later I realized it was on fastboot mode. Informatics huh.
If you have any idea on how to go back in fastboot mode, I tried using adb, but it needs the phone to reach systm to be able to reboot.
By the way you talked about a specific rom, where can I find this one ?
Thank you again for your time.
EDIT : Ok I managed to reach fastboot, what I did was to plug it on my laptop, powered off, then pressed vol down and power on, and it worked. Informatics has its reasons...
Still interested into the rom ou talked. I'll try to find it on my own though. But if you got a link, I would be happy to download it.
EDIT2 : Ok I tried to flash, everything went good, but my huawei is still in its bootloop. I extracted the B588 rom, but there was way more than 4 img files. I still flashed only the four you and the link you gave me told me, but maybe I need to flash more than these 4 ?

Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.

yodaofborg said:
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
Click to expand...
Click to collapse
Single stable SuperSu v2.76 also works for builds less than b580.. For builds greater than that, use 2 zips method

Well, it obviously didn't

I stuck in rescue mode. P8 LITE DUAL SIM

Hi,
I have a problem. I tried to flash stock rom, but I forgot about hifi image.
There's a photo of my phone.
imgur.com/aVUBTRD
I have unlocked bootloader, but I can't flash hifi. "Command not allowed."
I tried method with put microsd card with update.app in dload into smartphone and I when I pressed power button
and VOLUME UP and VOLUME DOWN nothing happened.
I tried just flash all partitions separately, with huawei update extractor, again nothing.
I saw the same problem in this site, but I don't know how he solwed this.
Please help me :crying:

Flash a Huawei recovery, a old one b584 or something, then download b596 DS or b597 SS i don't know your device, extract update.app and copy to sd card dload folder, try to flash it!

persona78 said:
Flash a Huawei recovery, a old one b584 or something, then download b596 DS or b597 SS i don't know your device, extract update.app and copy to sd card dload folder, try to flash it!
Click to expand...
Click to collapse
I flashed recovery and nothing happened, I can't get into recovery mode, only fastboot.
I have the same phone.

adamektv said:
I flashed recovery and nothing happened, I can't get into recovery mode, only fastboot.
I have the same phone.
Click to expand...
Click to collapse
You flashed the recovery and everything say okay, right?
Now flash a rom with dload and the 3 keys, do you know how?
.

persona78 said:
You flashed the recovery and everything say okay, right?
Now flash a rom with dload and the 3 keys, do you know how?
.
Click to expand...
Click to collapse
I don't know, when I pressed three buttons I didn't enter to recovery mode, but to rescue mode, as if recovery wasn't flashed.

adamektv said:
I don't know, when I pressed three buttons I didn't enter to recovery mode, but to rescue mode, as if recovery wasn't flashed.
Click to expand...
Click to collapse
Do you have a dload folder with update.app inside, in sd card?
With that and pressing vol +, vol - and power at same time you enter in flash mode and start to flash the rom

persona78 said:
Do you have a dload folder with update.app inside, in sd card?
With that and pressing vol +, vol - and power at same time you enter in flash mode and start to flash the rom
Click to expand...
Click to collapse
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard

adamektv said:
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
Click to expand...
Click to collapse
How da start it???

adamektv said:
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
Click to expand...
Click to collapse
Try opening the phone and disconnecting the battery .. do it if u only gave up with other methods someone said it worked

adamektv said:
Hi,
I have a problem. I tried to flash stock rom, but I forgot about hifi image.
There's a photo of my phone.
imgur.com/aVUBTRD
I have unlocked bootloader, but I can't flash hifi. "Command not allowed."
I tried method with put microsd card with update.app in dload into smartphone and I when I pressed power button
and VOLUME UP and VOLUME DOWN nothing happened.
I tried just flash all partitions separately, with huawei update extractor, again nothing.
I saw the same problem in this site, but I don't know how he solwed this.
Please help me :crying:
Click to expand...
Click to collapse
Hi Have got succeeded or not, if not follow the guide.
Is your phone being detected by PC if yes then you have chances of recovering your phone.
1. Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
2. Install Huawei HiSuite which will install drivers .
3. If HiSuite doesn't install Install drivers then install universal drivers for your device .
Now connect your device to pc and open HiSuite and click on system recovery it will show options for recovery if it is success then you are fine if not then proceed to this method.
Connect your phone to PC.
Open Command Prompt in the directory where you have extracted the ADB files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
1. Type the following command in ADB :
Code:
adb devices
If your device is being detected and it shows list of devices attached and its serial number.
2.Now download the firmware of the phone before your phone got bootlooped extract the update using the file here
3.Now copy the following files ( boot.img, recovery.img and system.img ,cust.img ) from the extracted files to the ADB files directory.
4.Now Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
5.Now Perform a Factory Reset if your phone got recovered.
If not then download the stock recovery of your Device and try steps 2,3,4.
Even if it doesn't get succeeded then try this option .
If your device got bootlooped while on Lollipop or Marshmallow then you have one more way to recover .
6.Now download the latest TWRP from here and boot into TWRP recovery if you cant enter TWRP recovery for this version then try the previous TWRP versions like 2.8.7 ,
7.Use the following command to flash the TWRP recovery
Code:
fastboot flash recovery twrp.img
8.Then download any of the custom ROMs or ask any of the XDA members for TWRP backup for your device and flash them through Recovery.
Then Reboot your Device.
You would most probably recover your device from any of the above methods . I too had the same problem and My device was use less for almost 6 months but after several trial and error methods my device got recovered.
Credits:
1.https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
2.https://forum.xda-developers.com/showthread.php?t=2433454

miststudent2011 said:
Hi Have got succeeded or not, if not follow the guide.
Is your phone being detected by PC if yes then you have chances of recovering your phone.
1. Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
2. Install Huawei HiSuite which will install drivers .
3. If HiSuite doesn't install Install drivers then install universal drivers for your device .
Now connect your device to pc and open HiSuite and click on system recovery it will show options for recovery if it is success then you are fine if not then proceed to this method.
Connect your phone to PC.
Open Command Prompt in the directory where you have extracted the ADB files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
1. Type the following command in ADB :
Code:
adb devices
If your device is being detected and it shows list of devices attached and its serial number.
2.Now download the firmware of the phone before your phone got bootlooped extract the update using the file here
3.Now copy the following files ( boot.img, recovery.img and system.img ,cust.img ) from the extracted files to the ADB files directory.
4.Now Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
5.Now Perform a Factory Reset if your phone got recovered.
If not then download the stock recovery of your Device and try steps 2,3,4.
Even if it doesn't get succeeded then try this option .
If your device got bootlooped while on Lollipop or Marshmallow then you have one more way to recover .
6.Now download the latest TWRP from here and boot into TWRP recovery if you cant enter TWRP recovery for this version then try the previous TWRP versions like 2.8.7 ,
7.Use the following command to flash the TWRP recovery
Code:
fastboot flash recovery twrp.img
8.Then download any of the custom ROMs or ask any of the XDA members for TWRP backup for your device and flash them through Recovery.
Then Reboot your Device.
You would most probably recover your device from any of the above methods . I too had the same problem and My device was use less for almost 6 months but after several trial and error methods my device got recovered.
Credits:
1.https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
2.https://forum.xda-developers.com/showthread.php?t=2433454
Click to expand...
Click to collapse
I have already done this and still stuck in rescue

adamektv said:
I have already done this and still stuck in rescue
Click to expand...
Click to collapse
Did you try flashing different variant ROM ie different builds?
Actually I too got the same problem bootlooped on LP but cant flash the LP ROM back so I flashed different Region ROM.
Give a try to TWRP Method It should give you success.
Imp:
Try the previous ROM where you got Bootloop, or the version earlier to it.If it doesn't succeed try the rom which you got initially on your mobile.
PS: If your phone is being detected by your PC you have good chances of recovering your phone.

Stuck in fastboot. Can't access eRecovery.

Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?

yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best

Gamkutopolowk said:
yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best
Click to expand...
Click to collapse
So you're saying that I wait until my battery drains, then go into fastboot and roll back to C432B185? Maybe you could help me by outlining the steps to flash via fastboot?

flash via fastboot by HWOTA follow this link https://romprovider.com/2018/01/download-install-b185-nougat-update-huawei-p10-plus/
only method 1

Gamkutopolowk said:
flash via fastboot by HWOTA follow this link
only method 1
Click to expand...
Click to collapse
So i tried this method, but it didn't work. It flashes TWRP, and instructs me to disconnect the USB cable and boot into TWRP, but i can't boot into TWRP. It goes directly to the error message even when holding the buttons down.

because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............

Gamkutopolowk said:
because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............
Click to expand...
Click to collapse
So after waiting for the battery to drain, holding vol down, and plugging the USB, I'm back where I was before with being in fastboot. Running HWOTA results in the same problem for when it tells me to reboot to TWRP after install, the phone goes to error mode.
I'm pretty sure the bl31 image corruption is preventing me from booting into recovery.

try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it

Gamkutopolowk said:
try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it
Click to expand...
Click to collapse
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'

Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds

Gamkutopolowk said:
Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds
Click to expand...
Click to collapse
Still goes straight to the error screen.

blahblah31415 said:
Still goes straight to the error screen.
Click to expand...
Click to collapse
Please show me your mobile

blahblah31415 said:
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'
Click to expand...
Click to collapse
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode

Junaid Shafi said:
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode
Click to expand...
Click to collapse
How you did that?

blahblah31415 said:
Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?
Click to expand...
Click to collapse
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!

gonzalomorenorovetto said:
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!
Click to expand...
Click to collapse
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.

blahblah31415 said:
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.
Click to expand...
Click to collapse
I tried DC Phoenix and It did not work. They returned me my money.
At the service center they finally replaced my motherboard, in warranty, even though the phone was unlocked and I bricked it completely