HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
rahulrk.2303 said:
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
Click to expand...
Click to collapse
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Please take a full back up before you roll back.
mrmazak said:
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Click to expand...
Click to collapse
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
rahulrk.2303 said:
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
Click to expand...
Click to collapse
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
mrmazak said:
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
Click to expand...
Click to collapse
I've already tried the dload method. But holding both volume buttons + power button didn't work. It loads into the error mode screen again. Maybe I'll copy the update.zip into the root of SD card and try again. But i think the phone won't boot into software update mode.
Is it hard bricked or soft bricked?
Should i try taking it to the service center?
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
RSGI said:
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
Click to expand...
Click to collapse
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
There is Oreo downgrade proceedure on Chinese huiwei club website. But your device needs full firmware package available.
There is full downgrade packages for al00 al10 and tl10.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
That's the one i tried.
The BNDAL10 one.
rahulrk.2303 said:
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
Click to expand...
Click to collapse
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Click to expand...
Click to collapse
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
rahulrk.2303 said:
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
Click to expand...
Click to collapse
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
Click to expand...
Click to collapse
but i think the update.zip listed in file list is same , don't really know.
all three are needed for full package.
RSGI said:
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
Click to expand...
Click to collapse
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
The problem is that we can't rollback from oreo to nougat because of different partitions.
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
rahulrk.2303 said:
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
**The problem is that we can't rollback from oreo to nougat because of different partitions.
Click to expand...
Click to collapse
???Well to be true you did not flash a roll-back(did you?) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
Click to expand...
Click to collapse
mrmazak said:
???Well to be true you did not flash a roll-back(did you) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
Click to expand...
Click to collapse
Tbh, i did everything one by one because nothing seems working.
I've tried every single method, trust me.
PHP:
Respected senior members,
My honor 7x bnd-l21c185 after I flashed twrp and OEM unlocked as well as bootloader unlocked. I flashed su zip but didn't succeed. I try to revert to stock rom but failed. Then I lost recovery as well as backup. I have downloaded my version firmware from mt. When I try to boot to twrp I got error mode with func 10: no recovery and boot failed. Then I relocked bootloader. Now my phone keep restarting when I plugged USB cable as well the phone didn't boot to bootloader nor recovery and not even twrp. When I plugged it to PC it keep restarting. What should I do? Please guys help me
y_asirkhan said:
PHP:
Respected senior members,
My honor 7x bnd-l21c185 after I flashed twrp and OEM unlocked as well as bootloader unlocked. I flashed su zip but didn't succeed. I try to revert to stock rom but failed. Then I lost recovery as well as backup. I have downloaded my version firmware from mt. When I try to boot to twrp I got error mode with func 10: no recovery and boot failed. Then I relocked bootloader. Now my phone keep restarting when I plugged USB cable as well the phone didn't boot to bootloader nor recovery and not even twrp. When I plugged it to PC it keep restarting. What should I do? Please guys help me
Click to expand...
Click to collapse
you are pretty much left with useless device. Maybe paid service like dc-unlock could help, not sure.
You intentionally locked bootloader with phone in a no-recovery non booting condition.
The unlocked bootloader was you rescue method if something goes wrong, and now you don't have that option.
**** MAybe the following will help you .. Remember I said MAYBE.....
#Service-Rom
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Dear member,
My phone keep restarting and the three button do nothing not even holding volume down plus power. Is there any thing else method please please would be highly appreciated.
I am having a similar problem. My device gets this. I tried flashing boot ages from various sources. It isn't working. PS. I still have access to fastboot, recovery and twrp. This shows up instead of the boot animation.
ERROR MODE
Attention!
Please update system again.
[Android bootloader image]
Error!
Function No : 10 (boot image)
Error No : 2 (load failed!)
kst1997 said:
I am having a similar problem. My device gets this. I tried flashing boot ages from various sources. It isn't working. PS. I still have access to fastboot, recovery and twrp. This shows up instead of the boot animation.
ERROR MODE
Attention!
Please update system again.
[Android bootloader image]
Error!
Function No : 10 (boot image)
Error No : 2 (load failed!)
Click to expand...
Click to collapse
you are lucky than me just try HWOTA or HuR update it will do solve your problem plus search the said for procedure budyy
y_asirkhan said:
you are lucky than me just try HWOTA or HuR update it will do solve your problem plus search the said for procedure budyy
Click to expand...
Click to collapse
I dont know how to fo that. Any link?
kaustubhtopre said:
I dont know how to fo that. Any link?
Click to expand...
Click to collapse
Here is the link budyy
https://www.******.com/huawei-hwota-tool-for-huawei-devices/
y_asirkhan said:
Here is the link budyy
https://www.******.com/huawei-hwota-tool-for-huawei-devices/
Click to expand...
Click to collapse
Just put ****** instead of stars in the address bar I think it is not allowed ok
y_asirkhan said:
Just put ****** instead of stars in the address bar I think it is not allowed ok
Click to expand...
Click to collapse
I have no idea what the stars stand for
Download Full rom and flash using Dload method
HELP. (SOLVED)
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
With a locked bootloader, you cannot flash system images. You need to be unlocked to do so.
But it seems that you did something wrong when re-locking the bootloader: It is normal that a factory reset is performed, but the OS should stay on the phone.
So I would first unlock the bootloader again - both fastboot flashing unlock and fastboot flashing unlock_critical, like described here: https://developers.google.com/android/images
Also note that you always need to update the Android SDK Platform-Tools, like descibed in the link. As always: Those who can read do have an advantage
Then you should be able to flash the latest factory image again and are ready to go.
Badger50 said:
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
SOLVED WITH [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5
Thanks alot guys
mikelikesbikes said:
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
Click to expand...
Click to collapse
Thanks my friend works like a charm..
exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
Solved with [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5..
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
This is for Google Pixel 2 XL.
SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.
Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.
So i was just following the instructions from this page https://wiki.lineageos.org/devices/flox/install, was able to unlock the bootloader of my nexus 7 device. Now at this point i didnt know my device codename, i thought it was flox but i just noticed on the bootloader page it says deb. [Im a noob..guilty]
Now the 2nd step was no biggie either, i was able to flash twrp recovery, but somehow it was not working as i was keep getting error 1 and vendor invalid argument when i tried to flash the lineage 18.1 zip.
The recovery img i tried were
lineage-18.1-20211018-recovery-flox.img
twrp-3.4.0-0-deb.img
twrp-3.5.0_9-0-flox.img
twrp-3.5.2_9-0-flo.img
twrp-3.5.2_9-0-flo_followmsi.img
Now after flashing twrp recoveries i was getting the problem of not able to flash the LOS 18.1 rom file, plus if i would format the device and then try to reboot the device back to recovery i would get an error with android logo collapsed [check the image]
what am i doing wrong? plz help.
I sense its repartitioning process? also i am not sure if i did an EFS Persists back up.
so if someone can give a walkthrough. would be very greatful _/\_
thanks again
rigerp said:
if someone can give a walkthrough. would be very greatful
Click to expand...
Click to collapse
"automatic single-click installation" is better than a walkthrough - use CROSS