Huawei Error Mode Please Update System Again

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

• #1

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:

ERROR MODE
Attention!
Please update system again.

Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)

Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"

Helllllp lpeaeaeaeaeaseeee!!!

Last edited: Jun 16, 2018

• #2

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:

ERROR MODE
Attention!
Please update system again.

Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)

Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"

Helllllp lpeaeaeaeaeaseeee!!!

Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.

Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

Last edited: Jun 16, 2018

• #3

Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.

Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

• #4

Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

• #5

Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

On the extractor app. On options tab uncheck the verify header option, it should extract then.

Then perhaps first do these three partitions.

Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

• #6

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:

ERROR MODE
Attention!
Please update system again.

Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)

Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"

Helllllp lpeaeaeaeaeaseeee!!!

I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder

adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause

in fastboot type:
fastboot -w

after all it's works to me to bypass google account verification

and if now your problem is

ERROR MODE
Attention!
Please update system again.

Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)

i solve with re-flash system from this

https://androidfilehost.com/?fid=673956719939830152

fastboot flash system system.img

and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads

fastboot flash recovery_ramdisk complete_twrp_ramdisk.img

and voila my problem solved..

• #7

On the extractor app. On options tab uncheck the verify header option, it should extract then.

Then perhaps first do these three partitions.

Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Last edited: Jun 18, 2018

• #8

So now is locked frp. Does phone have twrp or stock now.?

I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"

I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.

There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.

Link is to rusian language page. Google should translate for you.

https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

Last edited: Jun 18, 2018

• #9

So now is locked frp. Does phone have twrp or stock now.?

I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"

I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.

There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.

Link is to rusian language page. Google should translate for you.

https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

It have stock recovery.

• #10

in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.

you have broken system, from failed root attempt, followed by failed update.

device condition is as follows.

--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status

options are limited, at best.

I think "dload" method with service rom is best.

other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

• #11

in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.

you have broken system, from failed root attempt, followed by failed update.

device condition is as follows.

--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status

options are limited, at best.

I think "dload" method with service rom is best.

other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

No. System boot successfully!
I will send you screenshot:

• #12

No. System boot successfully!
I will send you screenshot:

here you are

Attachments

• #13

what about the "about phone" screen

what does it show for version?

If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]

after relock and rebooted oem switch should be enabled again.

****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.

Still not sure how to get IMEI back even if unlocked frp though.

**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

Last edited: Jun 18, 2018

• #14

what about the "about phone" screen

what does it show for version?

If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]

after relock and rebooted oem switch should be enabled again.

****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.

Still not sure how to get IMEI back even if unlocked frp though.

**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.

I think he did it with using special box.

Last edited: Jun 23, 2018

• #15

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:

ERROR MODE
Attention!
Please update system again.

Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)

Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"

Helllllp lpeaeaeaeaeaseeee!!![/QUOTE

Are u able.to boot into twrp ?

• #16

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.

I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.

Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

• #17

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.

I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.

Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.

Power off , long press power button.

Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.

Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

• #18

I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.

Power off , long press power button.

Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.

Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.

Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

Last edited: Jul 15, 2018

• #19

I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.

Power off , long press power button.

Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.

Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

Do you know what the boot.img files name is after extraction?

I have extracted all 3 update zips and cannot find anything called boot.img

By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

Last edited: Jul 15, 2018

• #20

Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.

Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.

i have all the files already extracted for oreo and a backup from nougat as well.

https://androidfilehost.com/?w=files&flid=265998

make sure you know what you are doing before flashing.

for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

Similar threads

daygooming57.blogspot.com

Source: https://forum.xda-developers.com/t/error-mode-attention-please-update-system-again.3804892/

Share this post