Database Develop

Help needed: Attention: Please update system again (Func No: 11 / Error : No 2)

Hi guys,
I bought the phone from ebay as they said it was stuck in fastboot mode after an OTA update, and having unlocked and played around with custom roms on several other phones I thought "No problem".
However, this is a problem. The phone is not stuck in fastboot mode, and I cannot get the phone to boot into fastboot mode. It is not seen by my computer
On turning on, it shows the Huawei Logo and then shows the message that the phone is unlocked and cannot be trusted and I should visit:
http://zh.ui.vmail.com/emotiondownload.php?mod=restore
If I hold down vol down + power it says 'Your device is booting now' but nothing happens.
Pressing power, or vol up + power, or just the power button, or leaving it then boots to mr green android with the message:
Attention! Please update system again
Error
Func No: 11 (recovery image)
Error No : 2 (load failed)
I have tried:
Booting into fastboot mode via vol down + power
DC Phoenix (as mentioned here: https://forum.xda-developers.com/showthread.php?t=3759988)
This > https://forum.xda-developers.com/p10/help/tutorial-recovering-p10-p10-brick-t3600211
This> https://androidforums.com/threads/unlocked-p9-lite-stuck-at-boot.1225280/
I do not know if the bootloader is unlocked.
Also, it won't turn on at all if it is not plugged in so doesn't seem to be holding charge or battery information. It boots automatically once it's been charging for a couple of minutes,
Help much appreciated!
UPDATE - I can now get into fastboot mode. I sat with my finger on the vol down button until it gained enough power to turn on.
Phone is unlocked
FRP Unlock
UPDATE
I ran the DC Phoenix update and half-way through the phone turned off and now won't turn on again. It doesn't look as if it's even charging anymore. (as per this thread: https://forum.dc-unlocker.com/forum...-plus-not-powering-or-charging-after-flashing)
Marvellous. I'll continue to investigate. If anyone has any ideas, please let me know,

Any news here? Same issue on my device. Unfortunately I can't get into fastboot, I only see:
Attention! Please update system again
Error Mode
Func No: 11 (recovery image)
Error No : 2 (load failed)
It's not even recognised via USB. Maybe the phone still thinks it has to make the low level format after unlocking the bootloader, but can't start any of the recovery.
This is my most expensive brick so far...

On my phone I tried to revert to stock recovery within TWRP and flashed the recovery.img to recovery partition.
After doing this, recovery wasn't working and I unlocked the bootloader. Since that moment I cannot get into fastboot.

Attention! Please update system again
Error
Func No: 11 (recovery image)
Error No : 2 (load failed)
Man I have the same problem. Sorry I'm a beginner and I can't help you. I wanted to ask if you have some tips.
I have that error if I try to enter in TWPR but I can boot in eRecovery and the smartphone turns on and works normally.
I tried to reset by eRecovey but error occurs just the same.
What can I do?

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day

I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

I can't install twrp, make a hard reset, update by OTA, nothing O.o

SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.

SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.

Xiaomi MI A2, is stuck in bootloop

Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.

Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.

try the "fastboot continue" command

dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not

SM-T587P Tablet (Device turned off - Contact iT admin)

Went through my closet and found a tablet that was purchased awhile back from a shady offerup client. Pretty much gave up but figured I'd revisit it since it's been awhile.
So here's the issue:
1.) Tablet says on lock screen (device turned off - contact iT admin)
2.) I am unable to wipe/factory reset using the recovery that came with the device (It is NOT TWRP)
3.) Device shows FRP lock is on when in recovery
4.) Unable to flash TWRP via ODIN or recovery
5.) ADB only recognizes the device when I attempt to sideload (Attempting to sideload TWRP results in a verification error)
6.) I can't access settings to verify that OEM unlock is enabled (as the tablet is disabled)
7.) Safe mode isn't an option
8.) Can't even attempt to enter a password on the lock screen.. Swiping up just presents: Device is turned off - Contact iT department.
*I have no clue who I would even contact in regard to the IT department.. As it was purchased on offerup.
*At this point I am fresh out of ideas as to what I can do with it.. Is it really paperweight status or is there hope?

bump