Hello, I have bricked my phone when I was trying to go back to stock firmware from RR.
TWRP does not work for me, internal storage can not be read (even though I've tried all images I've found for this phone..) so I had to do it through fastboot and hwota.
Somehow it bricked the phone and I get
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 7 (teeos image)
Error NO: 1 (security verify failed!)
If I extract TEEOS.img from UPDATE.app (8.0.0.145(C432)) and try
fastboot flash teeos TEEOS.img
I get
FAILED (remote: command not allowed)
I've tried to flash
SYSTEM.img
RECOVERY_RAMDIS.img
RAMDISK.img
If anyone know what I can do to fix this please enlighten me..
monsterkaka said:
Hello, I have bricked my phone when I was trying to go back to stock firmware from RR.
TWRP does not work for me, internal storage can not be read (even though I've tried all images I've found for this phone..) so I had to do it through fastboot and hwota.
Somehow it bricked the phone and I get
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 7 (teeos image)
Error NO: 1 (security verify failed!)
If I extract TEEOS.img from UPDATE.app (8.0.0.145(C432)) and try
fastboot flash teeos TEEOS.img
I get
FAILED (remote: command not allowed)
I've tried to flash
SYSTEM.img
RECOVERY_RAMDIS.img
RAMDISK.img
If anyone know what I can do to fix this please enlighten me..
Click to expand...
Click to collapse
Can you still get a bootloader mode?
If you still get bootloader enough to fix it.
This job must be solved on DC Phoenix Only
I'm sucess with this link
https://www.******.com/recover-huawei-bricked-devices-dc-phoenix/
I accomplished these images. ..good luck..
My device : huawei nova 2i [RNE-L22]
You can try this:
https://forum.xda-developers.com/showpost.php?p=74853704&postcount=91
Im not sure why is was removed from first post...?
taddzio said:
You can try this:
https://forum.xda-developers.com/showpost.php?p=74853704&postcount=91
Im not sure why is was removed from first post...?
Click to expand...
Click to collapse
I payed for funkyhuawei... it fixed the recovery. I now have a working eRecovery and recovery but failed to download OS. I will try hwota method. Does it work with 8.0.0.145(c432)??
Just download the official files and run?
The download link seem to be removed
monsterkaka said:
I payed for funkyhuawei... it fixed the recovery. I now have a working eRecovery and recovery but failed to download OS. I will try hwota method. Does it work with 8.0.0.145(c432)??
Just download the official files and run?
Click to expand...
Click to collapse
Can you fix it?? Please let me know how you do it?? I´m in the same situation
ï have the same problem please add me on discord if you can help i will reward you Moose#9703
Related
I experience the same symptoms as this thread, but the proposed solution does not work for me. (the sd_update.log says
Failure: OSBL°æ±¾Æ¥Åäʧ°Ü.
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
Click to expand...
Click to collapse
I rooted the phone, and misread the instructions for altering the recovery.img, which is what caused the problem in the fist place.
I have tried flashing with B925, B927 without luck.
I have also tried to use sudo fastboot boot recovery.img with a local recovery.img, and tried flashing fastboot flash recovery recovery.img - but it says
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
which i presume is because the bootloader is not unlocked.
I also tried fastboot getvar all - but that came out empty.
I also tried http://androidforums.com/huawei-ideos-x5-u8800/593253-unlock-bootloader-huawei-supply-code.html but the model is not listed...
I have an idea that essentially i just have to get in and delete recovery.img and rename recovery.backup.img to recovery.img - but i haven't got a clue about how to do it.
Phone responds to fastboot commands.
I look forward to your input.
Jonas
[SOLVED] patch to enable B919 was the missing link
Solved: www .shadowandy .net/2013/01/huawei-honor-u8860-shendu-rom-flashing-guide.htm the first link (dload_B929rus.rar (MD5 = 7264f7ad3bd7eebd298a8be978823734)) solved the problems, i am now on a B919 chinese rom.
Hi !
I desesperatly seeking a root process for the Archos Diamond 2 Plus.
I can not find it by google.
As it looks like the P9000 of Elephone, I wondered if it was possible to use its recovery.img and supersu 1 and 2.
An idea ? A link for tutorial or for the stock rom (If root process failed) ?
Please ?
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
fanfan7110 said:
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
Click to expand...
Click to collapse
What android version?
android 6.0 marshmallow
fanfan7110 said:
android 6.0 marshmallow
Click to expand...
Click to collapse
You can boot into fastboot, which is good, in fastboot, type fastboot oem startftm. It will give you an error in the command line but what this allows you to do, is push files into partitions that are mounted R/W, that is of course, if this actually works for your device since every device is different.
Report results!
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Please please please make a whole IMG backup since what we'll do might brick your device. I can't help you till Thursday, hit me up on Thursday with a reply on this thread.
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Also, it is supposed to say failed when you start it.
hummm i can't take a backup of boot.img, because SU is not installed..
fanfan7110 said:
hummm i can't take a backup of boot.img, because SU is not installed..
Click to expand...
Click to collapse
Well, since the device is running mtk, try this. Flash the superuser binary and report, also, I am NOT responsible for anything, YOU are making these changes.
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
fanfan7110 said:
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
Click to expand...
Click to collapse
Well, now you have a mission to somehow port a working recovery to your phone.
[you can use this tool to solve brick problems https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279]
Hi everyone, I'm "new" on the forum. "New" because they are days looking for answers to repair my Honor 9...
After unlocking it, installed twrp and RRos 6.0 I made a mistake, I uninstalled the gapps from the system manually, and after restarting the phone, various error messages continued on terminated processes (com.google... stopped working).
I tried again to reinstall the gapps via twrp but nothing to do, after trying to reinstall the RRos (with full wipe), new error messages kept going out, but this time not only the gapps.. (trebuchet etc ...).
Trying several wipes and reinstallations of the RRos, I tried to go back to the EMUI 8.0, so I tried to install the European firmware via SD and folder DLOAD, but once I got to 5% the installation crashes.
Via fastboot I also tried to install the twrp again, but the recovery stock continues to appear.
Looking on xda and generally on the internet I have found various people with this problem and they have tried to solve with programs like DC-Unlocker or Phoenix, but they had locked bootloader or frp .. I from fastboot I have PHONE Unlocked and FRP Unlock.
I also tried to flash the img contained in the UPDATE.APP file, but nothing happens ... just recovery stock. Help please i am desperate :crying: and sorry for my english.
EDIT - 27/03/2018
-I solved many of the problems I had in this post, now I'm still in the twrp and I can not flash the stock firmware.
-I'm trying to format the microsd in exfat and then install update.app.
-I can not copy the 4.66GB update.app file to the MicroSD in exfat, fat or ext4 via twrp / PC. I will try with another SD reader.
-I formatted the sd in exfat and I managed to copy the dload folder, run the restore and no longer blocked at 5% (gave a 99% error). The system started and I went back to the b130 with nougat, now I try again to install the b120 to restore the captive keys. (trying again with hwota)
-Hwota worked, now with the b120 everything works correctly, now I'm looking for a way to restore OTA Updates.(I will try to install the b183)
-With the b183 ota works, but not the keys / flash. I will try to downgrade to b120, than reupdate to b183 without wipe anything .
-b120 keys working, update to b183 and not working again, I try update ota oreo and search for a kernel.
-Almost everything resolved! After switching from the b183 to the b360, I reunlocked the Honor and installed the kernel with the fix to the capacitive keys. Relock the phone but the Google Logo appears at boot, even after installing the stock kernel.
Kodex_99 said:
Trying several wipes and reinstallations of the RRos, I tried to go back to the EMUI 8.0, so I tried to install the European firmware via SD and folder DLOAD, but once I got to 5% the installation crashes.
Via fastboot I also tried to install the twrp again, but the recovery stock continues to appear.
Click to expand...
Click to collapse
If you were on oreo, it's normal the nougat service repair files don't work with dload.
You're still on RRos ?
oslo83 said:
If you were on oreo, it's normal the nougat service repair files don't work with dload.
Click to expand...
Click to collapse
Can I try with non-European firmware such as Russian or Chinese upgraded to Oreo?
oslo83 said:
You're still on RRos ?
Click to expand...
Click to collapse
No, I did several wipe and tried to restore other system.img
Kodex_99 said:
Can I try with non-European firmware such as Russian or Chinese upgraded to Oreo?
No, I did several wipe and tried to restore other system.img
Click to expand...
Click to collapse
To my knowledge, they are no oreo service repair firmware publicly available yet. So, for now, no flashing firmware with dload once on oreo.
You could use HWOTA8to8 or HWOTA8to7 or the translated russian TOOL from last febuary.
oslo83 said:
You could use HWOTA8to8 or HWOTA8to7 or the translated russian TOOL from last febuary.
Click to expand...
Click to collapse
I only find missing files
Honor 9 multitool eng (feb2018)
https://forum.xda-developers.com/hon...5#post75662105
oslo83 said:
Honor 9 multitool eng (feb2018)
https://forum.xda-developers.com/hon...5#post75662105
Click to expand...
Click to collapse
========================================================================================
Copying the firmware files to the SD card
Please wait ....
========================================================================================
adb: error: failed to get feature set: no devices/emulators found
unfortunately when I try to install the EMUI 8 (the one I had previously installed) from fastboot I get this error message..
Kodex_99 said:
Copying the firmware files to the SD card
Please wait ....
========================================================================================
adb: error: failed to get feature set: no devices/emulators found
unfortunately when I try to install the EMUI 8 (the one I had previously installed) from fastboot I get this error message..
Click to expand...
Click to collapse
You need to be in twrp or system to copy file from your pc to sdcard with adb.
oslo83 said:
You need to be in twrp or system to copy file from your pc to sdcard with adb.
Click to expand...
Click to collapse
The problem is just that... also flash system or twrp, I always get eRecovery, I can try to copy the files on sd from another system however (as I did previously with the dload) but erecovery stucks at 5%
Kodex_99 said:
The problem is just that... also flash system or twrp, I always get eRecovery, I can try to copy the files on sd from another system however (as I did previously with the dload) but erecovery stucks at 5%
Click to expand...
Click to collapse
Once in fastboot boot, what command did you typed to flash stock recovery ?
---------- Post added at 20:20 ---------- Previous post was at 20:20 ----------
Or twrp
oslo83 said:
Once in fastboot boot, what command did you typed to flash stock recovery ?
---------- Post added at 20:20 ---------- Previous post was at 20:20 ----------
Or twrp
Click to expand...
Click to collapse
As I had an official oreo, I used it "fastboot flash recovery_ramdisk twrp.img"
I have just discovered that I can not even wipe from the recovery stock :/
Good, maybe you're doing the key combination wrong:
https://4pda.ru/forum/index.ph...72246&st=800#entry55689846
---------- Post added at 20:27 ---------- Previous post was at 20:26 ----------
So you manage to boot to stock recovery or was it erecovery again ?
oslo83 said:
Good, maybe you're doing the key combination wrong:
https://4pda.ru/forum/index.ph...72246&st=800#entry55689846
Click to expand...
Click to collapse
404
oslo83 said:
So you manage to boot to stock recovery or was it erecovery again ?
Click to expand...
Click to collapse
I have Stock recovery with + button, eRecovery with normal system boot and Fastboot with - button
So, boot to fastboot and flash oreo twrp.
Then boot to twrp recovery like you would have done for booting to stock recovery.
---------- Post added at 20:37 ---------- Previous post was at 20:31 ----------
https://4pda.ru/forum/index.php?showtopic=772246&st=800#entry55689846
oslo83 said:
So, boot to fastboot and flash oreo twrp.
Click to expand...
Click to collapse
I flash it, but when I try to start it I always go back to the recovery stock...
Previously I had installed the twrp but I do not know why the stock returned after several wipes
Do again:
fastboot devices
Then
fastboot flash recovery_ramdisk twrp.img
Then
fastboot reboot recovery
Paste us your output.
What twrp do you used ? 0.2 or 0.3 ?
oslo83 said:
Do again:
fastboot devices
Then
fastboot flash recovery_ramdisk twrp.img
Then
fastboot reboot recovery
Paste us your output.
Click to expand...
Click to collapse
" PS C:\Users\Kodex\Downloads> fastboot devices
7BK0217B04002898 fastboot
PS C:\Users\Kodex\Downloads> fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.289s]
finished. total time: 0.979s "
unrecognized reboot command.
oslo83 said:
What twrp do you used ? 0.2 or 0.3 ?
Click to expand...
Click to collapse
Up to a few hours ago the 0.2, now the 0.3 but does not change anything...
Keep trying to boot to twrp recovery
---------- Post added at 21:03 ---------- Previous post was at 21:02 ----------
Usb must be unpgugged
oslo83 said:
Keep trying to boot to twrp recovery
Click to expand...
Click to collapse
nothing.. only stock recovery
oslo83 said:
Usb must be unpgugged
Click to expand...
Click to collapse
i tried this
PS C:\Users\Kodex\Downloads> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.696s
I would like to flash the original recovery on my C432 with .120 on it.
I tried the .104 file but this does not work.
I am getting the ADB error
FAILED (remote: partition length get error)
who can help?
Solved myself adb command is now fastboot flash recovery_ramdisk !!!!
boris03 said:
I would like to flash the original recovery on my C432 with .120 on it.
I tried the .104 file but this does not work.
I am getting the ADB error
FAILED (remote: partition length get error)
who can help?
Click to expand...
Click to collapse
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Hello,
- In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Hi, thanks for your fast answer!
fastboot oem get-build-number
Code:
(bootloader) :System 8.0.0.046(09B8)
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem get-product-model
Code:
(bootloader) ANE-LX1
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot getvar vendorcountry
Code:
vendorcountry: ti/it
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
Code:
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.019s
fastboot oem oeminforead-SYSTEM_VERSION
Code:
(bootloader) :ANE-LX1 8.0.0.151(C55)
OKAY [ 0.013s]
finished. total time: 0.014s
I don't know why but the CUSTOM_VERSION reading failed...
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
-Alf- said:
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
Click to expand...
Click to collapse
I think it's C55 , correct me if I'm wrong...
-Alf- said:
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
Click to expand...
Click to collapse
I tried, but doesn't work at all...
-Alf- said:
I think it's C55 , correct me if I'm wrong...
Click to expand...
Click to collapse
Yeah, it is C55. I don't know what to do anymore
andreasaracino said:
I tried, but doesn't work at all...
Yeah, it is C55. I don't know what to do anymore
Click to expand...
Click to collapse
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
I did this once to my kiwi (5x) then it went totally blank when i tried flashing an Huawei related system flashing tool. Do not try that.
-Alf- said:
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
Click to expand...
Click to collapse
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
andreasaracino said:
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
Click to expand...
Click to collapse
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
-Alf- said:
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
Click to expand...
Click to collapse
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
andreasaracino said:
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Click to expand...
Click to collapse
andreasaracino said:
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
Click to expand...
Click to collapse
then it is not FULLOTA-MF but Service ROM, bro ...okay, it doesn't matter now.