[SOLVED] Needed Stock Recovery for EVA-L19 - Huawei P9 Guides, News, & Discussion

Hi,
after having TWRP, the factory reset function won't work since the data partition isn't recognized yet. Does anyone have the stock recovery version for this?
i already tried downloading from http://huaweidevices.ru/huaweiserviceworkarchivehuawei/eva-l19/recovery.img but it fails with the below message:
fastboot.exe flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35180 KB)...
OKAY [ 1.318s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.318s
edit: found out the issue was related to the allow OEM unlock as turned off

is your bootloader still unlocked?

4Fighting said:
is your bootloader still unlocked?
Click to expand...
Click to collapse
Yups, still unlocked bootloader and currently on twrp recovery, but will need stock recovery if any operations like upgrade or factory reset needs to be done.

Related

Unbrick Moto 4G Orange

So my Moto 4g has freeze and reboot during the last official lollipop update and now my phone is unable to boot
I try to reflash a stock rom using fastboot mode (and mflashtool) but I got errors
sending 'recovery' (10240 KB)...
OKAY [ 0.382s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.770s
After searching on xda forum it seems that the bootloader is locked so I'v try to use motorola's website to get the unlocked code (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) but I'v always get the error "Your device does not qualify for bootloader unlocking"
I've try to remove place and using the Unlock Data Scrub Tool but always the same issue.
As my phone is unable to boot is there anyway to unbrick it ? Maybe and official tool able to flash with locked bootloader or something ?

Can't install TWRP

Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
are you sure you dont have FRP lock activated?
well thats why it wont flash. BL unlocked means nothing if you're FRP locked. you have 2 choices. try removing all security options and accounts / factory reset and hope FRP lock is removed, or use dload method to reflash stock rom. you wont be able to flash twrp otherwise, well, unless u use some of those "pay to remove FRP lock" tools
hypnotik8systeme said:
are you sure you dont have FRP lock activated?
well thats why it wont flash. BL unlocked means nothing if you're FRP locked. you have 2 choices. try removing all security options and accounts / factory reset and hope FRP lock is removed, or use dload method to reflash stock rom. you wont be able to flash twrp otherwise, well, unless u use some of those "pay to remove FRP lock" tools
Click to expand...
Click to collapse
Yes i got frp lock i will try To see tomorrow
ImEraaz said:
Yes i got frp lock i will try To see tomorrow
Click to expand...
Click to collapse
Did it work? If, can you tell me how you did it?
ImEraaz said:
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
Click to expand...
Click to collapse
FRP lock and system security triggers in bootloader itself cause that some partition/blocks are unaccessible even when there is a "full" unlocked bootloader, but full unlocked bootloader option is not as it should be.
Security options while flashing some partition and the system flashing boot loops security option enables this well known security feature.
ImEraaz said:
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
Click to expand...
Click to collapse
Enable OEM unlock.... In developer setting

Flashed magisk patched boot image - killed phone :(

I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
thecdn said:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
Click to expand...
Click to collapse
You need to restore your original ramdisk. Also, you have to patch your own ramdisk.img with Magisk Manager if you want to try rooting your device.
And btw, this is a development forum, not General or Q&A one. Read carefully before trying to mod this device, or you will end up with an expensive brick.
please contact me on hangouts i may be able to help [email protected]
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
Edit: Link updated
[email protected]_USA said:
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kf...yiH2t-srYBBvN3
Click to expand...
Click to collapse
I"m getting a web page not found 404 when I try that link.
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
Same
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
freeza said:
Same
Click to expand...
Click to collapse
look like chris didnt updated the link,
bdw here you guys go https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
thecdn said:
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
Click to expand...
Click to collapse
You need to restore ramdisk, not recovery_ramdisk.
Pretoriano80 said:
You need to restore ramdisk, not recovery_ramdisk.
Click to expand...
Click to collapse
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
thecdn said:
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
Click to expand...
Click to collapse
Try to also flash kernel : fastboot flash kernel kernel.img
Pretoriano80 said:
Try to also flash kernel : fastboot flash kernel kernel.img
Click to expand...
Click to collapse
No joy yet but I do appreciate all the help.
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Did you tried a factory reset from stock recovery?
Pretoriano80 said:
Did you tried a factory reset from stock recovery?
Click to expand...
Click to collapse
I've tried two factory resets after completing the above mentioned actions. Both times reported they were successful it still won't boot to the os, goes to the EMUI screen after several boot attempts.
Same problem here on a US BKL-L04 =(
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
akasek said:
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
Click to expand...
Click to collapse
Flash stock kernel, ramdisk and recovery ramdisk for your model in fastboot and you'll be able to boot again
Rommco05 said:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Use this tool for flash full fw
Click to expand...
Click to collapse
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Finally back up and running - Thanks Tecalote!
FYI: I am finally back up and running - Tecalote's post worked perfectly (and BKL-L04 update zips are linked earlier in the thread also): https://forum.xda-developers.com/showpost.php?p=76331841&postcount=46
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
try to install twrp and then do hruupdate from twrp
get your files from firmware finder and search xda forums to how to install those files
its very easy and your system will be back in stock format
after that you can try to root and install custom rom
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Hi, what helped you there? I have a similar situation.
"Hi,
I need some advice on what can be done with my Honor View10 as it keeps gracing a bootloop followed by fasrboot mode.
Mine is a C675 variant and I was on 190 when I decided to unroot and update the device to 218. Once that was done, I flashed a patched recovery_ramdisk boot image that was patched using magisk to support it. Worked fine. Did a reboot and it got stuck in a bootloop.
I have tried flashing other patch.imgs too, due instance tried extracting recovery.img of the current version of rom, flashed it, no luck!
Tried flashing the patched version of that, still did not help.
I am on EMUI9, any help please?
Also can anyone help me with the link of one of the latest versions of C675 update please? "
This is what happened to me

Can't get into recovery mode

Hi.
After trying to upgrade my rooted P20 eml-l09 c605 with EMUI 9.x, I couln't get into recovery mode anymore (on button + vol up)
What I did was flash original ramdis.img and recovery_ramdis.img to unroot it, so i could upgrade it directly from the phone, but something bad happened so I couldn't get the recovey menu anymore.
Help please.
PS: (Bootloader is unlocked)
This message appears when I try to flash recovery_ramdisk
- Flashing TWRP recovery
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.577s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.590s
Where did you find the original ramdisk image from?
I need it too because i accidently flashed a TWRP version that doesent work
I can't flash anything, even with the original ramdisk (downloaded from firmware finder).
I really don't know what to do.
My phone is an EML-L09C605, it is working and rooted.
Only I can get to fastboot menu.
I still haven't got a solution but, Is downgrading it the way to follow?
Help please.

NXT-L29 TWRP installed without error but isn't accessible

Hi. I unlocked bootloader and flashed twrp via fastboot, but when I try to boot into it, the phone gets stuck at "your phone is booting now". The stock recovery no longer works. The phone's never been updated, still on Android 6.0 and EMUI 4.0. I tried several twrp versions with the same effect. What am I doing wrong? Can dm-verity be somehow interfering with twrp? Any ideas? Thanks in advance.
Code:
fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 0.129s]
finished. total time: 0.830s
Months later I tried the same, also NXT-L29
Endless:
"Your device has been unlocked and can't be trusted....."
Your device is booting now...
Any solution please?

Categories

Resources