Hello,
After having flash KERNEL_B360a_TOUCH_FIX.img to solve a problem of mount with TWRP on my Honor 9 stf-l09, here I am completely blocked,
When i access TWRP, the screen hangs on teamwin, so I restart the laptop, I waited on "your device has been unlocked and can not be trusted", I do POWER to boot normally and I stumble upon Huawei eRecovery
He offers me: Download latest version and recovery, reboot and shutdown, when I go to Download latest version and recovery it connects to my wifi but still it marks that it does not work ..
I followed this tutorial https://forum.xda-developers.com/honor- ... k-t3696892
I took the last link STF-L09 C432B130 Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary Android 7.0 EMUI 5.1
I did as agreed, create the dload folder at the root of my sdcard with inside UPDATE.APP
I did Vol + and - + POWER to install and it marks: Software install failed!
What can I do ? Thank you
What firmware version were you on before flashing KERNEL_B360a_TOUCH_FIX.img ?
Nougat service repair firmware won't work over oreo.
You pasted wrong your link.
Hello,
I used this link https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Yeah, won't work if you were already on oreo.
For the firmware I think it's Android Oreo on Honor 9 (EMUI 8.0) so I have to redo the manipulation with this version ?
I' m guessing you flashed B360 kernel over a B362 kernel partition.
But you could have done something else wrong.
Would you have a link? What should I install?
Don't rush.
When you access TWRP, the screen hangs on teamwin, so you restart. Could you WAIT more when you fell it hangs ? and what twrp version are you using ?
About your kernel flashing ; could you post here the command you used ?
version twrp: stf-twrp-zxz-0.3.img
I waited 10 minutes but nothing.
For the kernel i used fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
So assuming you flashed B360 kernel over a B362 kernel partition ;
Just flash this stock B362 kernel over your kernel partition to solve your booting problems :
https://mega.nz/#!bdEgiIAJ!sfkzPeBBKVeDzB2ifsczFxJHrKF8JWY1WP1a8PH9fFg
with :
' fastboot flash kernel Stock_KERNEL_STF-L09C432B362.img '
How to fastboot adb on my computer because normally I had to authorize the connection with my honor 9?
Connect your phone to computer via USB.
Hold Volume.down and keep holding it.
Power off phone, then power on while still keeping Vol.down held until you're in bootloader mode aka fzstboot mode.
This should boot you into fastboot mode where you can issue these commands :
fastboot devices
fastboot flash kernel Stock_KERNEL_STF-L09C432B362.img
My phone is USB connected to the PC, I'm in fastboot & rescue mode: Phone unlocked and unlock
On my computer, when I do adb devices it does not detect my phone but when I do fastboot flash kernel .. it marks
target reported download size of 471859200 bytes
sending 'kernel' (24576 KB) ...
OKAY [0.526s]
writing 'kernel' ...
OKAY [0.263s]
finished. total time: 0.792s
Then I did fastboot reboot and it did not solve the problem.
http://prntscr.com/jarq6a
Deadfightmc said:
My phone is USB connected to the PC, I'm in fastboot & rescue mode: Phone unlocked and unlock
On my computer, when I do adb devices it does not detect my phone
Click to expand...
Click to collapse
fastboot is not adb.
adb is not fastboot.
Deadfightmc said:
but when I do fastboot flash kernel .. it marks
target reported download size of 471859200 bytes
sending 'kernel' (24576 KB) ...
OKAY [0.526s]
writing 'kernel' ...
OKAY [0.263s]
finished. total time: 0.792s
Then I did fastboot reboot and it did not solve the problem.
http://prntscr.com/jarq6a
Click to expand...
Click to collapse
So you successfully flashed via fastboot a C432B362 stock kernel over C432B360 kernel fix and it's still bootlooping...
Do you think your region cust may have been something else than European C432 ? Maybe : Japanese C635 ? Russian C10 ?
Download again stf-twrp-zxz-0.3.img and try to flash your non-working twrp with :
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
I downloaded and flash again stf-twrp-zxz-0.3.img but it still hangs on "teamwin" Should I test all possible kernels?
If your bootloops really appeared because you flashed B360kernelfix, flashing the stock kernel of your actual version will solve your issue.
But, before that, does twrp was working ? What do you call 'a problem of mount with twrp' ?
-I'll say user problem- [emoji14]
I wanted to install SuperSU with twrp so I put it on my sdcard, I installed it with twrp but there was an error so I looked at this link https://forum.xda-developers.com/honor-9/development/oreo-t3754483
problems:
Mount system rw
Custom kernel required because of Huawei MMC protection (check second post)
And there he said Download kernel http://www.mediafire.com/file/6n1wfb..._TOUCH_FIX.img
Flash with fastboot.exe kernel flash KERNEL_B360a_TOUCH_FIX.img
So:
1. system and twrp 0.3 were working.
2. you flashed a 'random' supersu via twrp and it gave you errors
3. you flashed B360kernelfix
Am I right ?
Yes that's it
So first we'll try to fix what you did when you flashed a bad supersu (which one ?) by flashing a stock B360 boot image :
fastboot flash ramdisk STF-L09_ramdisk.img
https://forum.xda-developers.com/attachment.php?attachmentid=4420592&d=1518680458
Related
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
maybe you should tell more info about your device, brand,chipset, etc ?
so people can be more easy to help.
just newbie suggestion, ignore this if its no help xD
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
lolet said:
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
Click to expand...
Click to collapse
The system image is not corrupted, because I can safely flash it using Clockworkmod. The filesystem is yaff2, and I have tried opening it using some software and my file is there. I think the problem lies on fastboot who failed flashing properly.
simple
yokowasis said:
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
Click to expand...
Click to collapse
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
I stuck with my Mate 9 Error mode numbers 11 and 2
MEGHSHAH said:
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in a tutorial
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Hi everyone !
Some month ago I flashed on my device a beta test of Nougat for Honor 5c. Yesterday I wanted to leave it and go back to a stable rom but I was unable to find a flashable ZIP of stock Rom so I used FlashFire to flash a update.app firmware package (some **** from Huawei...).
After flashing it I tried to reboot my phone but I just got a Error Mode - Please update your system again. (and Recovery image error + load error)
To solve this I reboot to fastboot and on my computer I tried to flash TWRP with fastboot flash recovery twrp.img and I got a error : remote : command not allowed. I search and search and search on forums but I found nothing.
I tried some other fastboot commands, i tried to boot from a img, ... but nothing, just Command not allowed.
I have a Honor 5c NEM-L51, fastboot is "working" lol, no recovery, no force dload update, bootloader unlocked, FRP lock (idk what is this), i was rooted with Magisk and I flashed the package with FlashFire.
Please help me :crying:
Siffrein
Hi there
I think my phone is briked. I wantet to downgrade my phone to the 108 version becaus there was android auto working.
So i tried to flash the System.img from the 108 Software. I tried 2 different:
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-lx1&firmware_page=0
and the Middle east from the thread here.
Id did flash over fastboot, but after every start the Build number was still on the 112 Firmware.
So i tried the Trebel ASOP, RR and LOS. ASOP Booted but had only forceclose on every service. RR and LOS did not work.
Then i tried to flash the ramdisk, recovery, vendor kernel etc from the update.app from the 108 Firmware. No my phone is briked.
I tried to flash eveyrthing from the .112 updateapp from the Official thread but nothing happend.
Then i tried to flash every possible .img file from the .112 app but most of them gave "Error Command not allowed"
So here i Am. Bootlooping phone and i dont know what else to do.
Since the beginning i could flash every system.img but it still was on the 112 Build and suddenly it bricked. I cant get to the 112 Version back with flashing system.img because it bootloops. Same for Treble and the newest 126 Version or the old 108 Build.
The only thing booting is ASOP Treble but i cant navigate coz of the 1000 of forceclosed errors.
I formated the userpartition as i was asked from Huawei, and bevore i did those installations i did a fullwipe with EMUI.
The Recovery cant connect to the server, and yeah.. i dont know what to do next. ofc i have unlocked bootloader. I bought the Phone in Switzerland with Dual Sim. ANE-LX1.
Does anyone have another idea?
Cheers
EDIT:
After 10000 billions klicks i managed to get through the treble wizzard, even when the com.android.phone has stopped is comming every second.
At the Moment im in the About Phone Screen and i see this: (I am in the newest ASOP Treble SU with gapps)
Model: ANE-LX1
Android Version 8.1
Baseband: unknown
Kernel Version 4.4.23+ (gcc version 4.9x 20150123 (prerelease) (GCC))
Fri Mar 9 09:51:47 CST 2018
Build Number ANE-LX1 8.0.0.112(c432) <------- WTF ?!?
I hope this informations is something to work with.
SIM CARD is not readable.
Edit2:
I connected it to HI SUit. It says my device running properly on the .112 Version (WTF i got Treble installed)
I cant connect anything. How the hell can i get rid of this ****ing wong Build number??
Same for Checking Updates. .112 should be newest (its not its 126) Any ideas?
Edit3:
Can only Flash with fastboot. Twrp cant mount the partitions. Trying to installing the zip or adb sideload gives me an error code or command not allowed :\
i think the best way is
download a FULL-Update for your build
https://forum.xda-developers.com/9-lite/help/huawei-honor-firmware-download-t3790327
read this https://forum.xda-developers.com/hon...flash-t3778085
if you understand and have the know how : good luck
with this way i have my Ho9L reflash to stock-rom
you have to know what you're doing
use Magisk (search inside xda the thread)
this work by me better as SuperSU (with less problem's)
use this twrp, it's work WITH encryption
ttps://forum.xda-developers.com/huawei-p20-lite/development/recovery-testing-t3783587
if you understand what i am write - you can reset your phone to "delivered-state" and beginning by zero (initial-setting's) and
what ever you flash - you have a chance to reset your phone
first look on bootloader-screen if
- bootloader unlocked
- FRP unlock
THIS is essential !
last tip: let the fingers from custom-rom if this not expressly build for OREO
OREO is other as NOUGAT ! very different !
Relock your bootloader before trying an Erecovery...
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
I'm getting this error when I'm trying to extract UPdate.app of anE-LX1 8.0.0.108(C185)
https://ibb.co/k0HmGy
haidermiz said:
I'm getting this error when I'm trying to extract UPdate.app of anE-LX1 8.0.0.108(C185)
https://ibb.co/k0HmGy
Click to expand...
Click to collapse
go to settings, untick all options that have "verify" in it, and try extract again.
heindrix said:
go to settings, untick all options that have "verify" in it, and try extract again.
Click to expand...
Click to collapse
thanks it worked
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
When i did fastboot flash vendor vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
haidermiz said:
When i did fastboot flash vendor vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
heindrix said:
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
Click to expand...
Click to collapse
Tried then phone was stuck at installing update 5% after 5 mins there was a screen android written on it then again it booted to erecovery i factory reset data, wiped cache then again it rebooted and it's finally open now thanks
heindrix said:
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
Click to expand...
Click to collapse
I did that a installed stock rom after that I tired to reset data it said failed, it failed at 20% then I WIPED CHAHE and now when It opened I sign in and downloaded snapchat but it's noy opening and in settings about phone there's no model number mentioned it says unknown I don't know what to do
haidermiz said:
I did that a installed stock rom after that I tired to reset data it said failed, it failed at 20% then I WIPED CHAHE and now when It opened I sign in and downloaded snapchat but it's noy opening and in settings about phone there's no model number mentioned it says unknown I don't know what to do
Click to expand...
Click to collapse
if you could, please provide screenshot so i can see it more clearly.
after you flashing the rom, one thing you must do is to format the data and cache through emui erecovery, as long as you're not format the data and cache successfully, the rom will not works properly.
for another reference, please refer to my other post here : https://forum.xda-developers.com/ma...0-pro-help-t3776050/post76916307#post76916307
heindrix said:
if you could, please provide screenshot so i can see it more clearly.
after you flashing the rom, one thing you must do is to format the data and cache through emui erecovery, as long as you're not format the data and cache successfully, the rom will not works properly.
for another reference, please refer to my other post here : https://forum.xda-developers.com/ma...0-pro-help-t3776050/post76916307#post76916307
Click to expand...
Click to collapse
Greetings, I downloaded the rom of my Huawei p20 EML-L09 and it has two Update.app
How and in what order should I install them?
Udpate.app that weighs 4.62gb and
update_EML-L09_hw_la.app which weighs 1.5gb
Thanks a lot.
ajbn7 said:
Greetings, I downloaded the rom of my Huawei p20 EML-L09 and it has two Update.app
How and in what order should I install them?
Udpate.app that weighs 4.62gb and
update_EML-L09_hw_la.app which weighs 1.5gb
Thanks a lot.
Click to expand...
Click to collapse
Hi,
this guide is two years old, if you want to recover your phone, download Service ROM from androidhost.ru website, and flash it using dload method .
Which EMUI version are you running? Your region is C605 ?
-Alf- said:
Hi,
this guide is two years old, if you want to recover your phone, download Service ROM from androidhost.ru website, and flash it using dload method .
Which EMUI version are you running? Your region is C605 ?
Click to expand...
Click to collapse
Correct, my region is 605. I already downloaded the latest version available for download on that page which is 8.1.
Before my phone went into brick, it had version 9.1
And bring those two update.app
ajbn7 said:
Before my phone went into brick, it had version 9.1
Click to expand...
Click to collapse
For 9.1 you can download
https://androidhost.ru/2bCG
Unpack .zip archive , find dload file and simply transfer it to the SD card, without unpacking it! (instructions can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo.
Note: Service ROM L-29 contains both version - L-29 & L-09 .
-Alf- said:
For 9.1 you can download
https://androidhost.ru/2bCG
Unpack .zip archive , find dload file and simply transfer it to the SD card, without unpacking it! (instructions can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo.
Note: Service ROM L-29 contains both version - L-29 & L-09 .
Click to expand...
Click to collapse
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Are there any risks if I try to install version 8.1?
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
ajbn7 said:
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Click to expand...
Click to collapse
Are you sure?
I'm really sorry, but most of the packages are universal.
ajbn7 said:
Are there any risks if I try to install version 8.1?
Click to expand...
Click to collapse
It may brick your phone definitively.
ajbn7 said:
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
Click to expand...
Click to collapse
Yes, you can.
ajbn7 said:
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Are there any risks if I try to install version 8.1?
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
Click to expand...
Click to collapse
Okay, I definitely don't get the 9.1 for Eml-09 for free.
So last query (I hope), what is less risky, install Rom 8.1 which is for my region and exact model, or install Rom 9.1 with my region but for model L-29 or install a Rom 9.1 for my model but with a different region?
Thank you for your support.
ajbn7 said:
what is less risky?
Click to expand...
Click to collapse
L29 EMUI 9.1 C605. Even if it succeeds the phone will not work correctly.
Most probably you will get the wrong model or in build number "system_0.46 (xxxx)" . HiSuite will not recognize your device (and no OTA update).
Hi everybody, i'm new on huawei, i've got a bla 029, apparently it was on emui 8.0 and i wanted to upgrade to 9.0 with root and magisk.
i'm on unlocked bootloader and no frp
But now i can't boot ( your device has been unlocked ....) i'm stuck on this.
i ve got access to bootloader and E recovery.
When ive tried to flash recovery stock or twrp... no boot and no recovery or twrp. Only E recovery. It write okay finished but when i enter "reboot recovery" i've got" command not allowed"
ive tried to extract Update.app to have all images. Flashed system, boot, kernel etc .... Flashed success in cmd
But no boot.
When i try softwares AIO. same result.
Drivers are installed but when i'm in E recovery, I ve got no ADB and windows says " unknow driver doesn't work etc .... "
If you have any ideas or solutions
Thanks in advance !
shadowsami4 said:
It write okay finished but when i enter "reboot recovery" i've got" command not allowed"
Click to expand...
Click to collapse
You have to prompt "fastboot reboot recovery" and not only "reboot recovery"
Is USB still connected? Try to restart with unplugged USB.
yes sorry i know the right commands it was just a short description. Even with Fastboot reboot recovery it didn't work.
With usb connected or not it's the same. And with power and vol - button to enter recovery it's the same.
Always E recovery and that's all
thanks
Try factory reset and cache clear
lingarajug said:
Try factory reset and cache clear
Click to expand...
Click to collapse
Same thing, reboot on warning message and no recovery only the E recovery and i can't use adb with this one
With my usa moel its volume + and power to enter regular recovery not erecovery and volume - is fstboot, maybe try that.
yes but i've tried many times vol+ and power but still goes to "warning message + 3 options (1 power to continue 2 press vol up to enter Erecovery 3 will continue to boot if no operation)
And then i'm blocked
i've tried to flash all partitions manualy and nothing no recovery no twrp no boot. Huawei is like a pain to flash.
Any ideas ? and can i do DLOAD via OTG ?
shadowsami4 said:
i've tried to flash all partitions manualy and nothing no recovery no twrp no boot. Huawei is like a pain to flash.
Any ideas ? and can i do DLOAD via OTG ?
Click to expand...
Click to collapse
OTG USB-C to USB-A (female) and a memory stick/sd adapter works. Service/dload firmware from androidhost.ru (use russian VPN if you have to increase download speed).
However, this uses recovery to flash so chances are it won't work... But you could test before doing it by booting holding vol up + down + power + usb plugged in.
When you have the dload, if dload mode does work, just extract the downloaded zip and copy the 'dload' folder in 'Software' to your memory stick. Do not extract the zip(s) in the dload folder. They need to remain zipped.
If no dload mode, extract all recovery partitions from update.app (recovery_ramdisk, recovery_vendor, recovery_vbmeta) and kernel.
Flash to the corresponding partition using fastboot (example: fastboot flash recovery_vendor RECOVERY_VENDOR.img etc.)
edit: Also a question, you flashed 'boot'?
Boot has not been part of EMUI since Nougat. Use a Pie update.app. It should not contain 'ramdisk' as that's gone too in Pie.
thanks i'm downloading now from androidhost.
Will give it a try,
I've already flash all recovery img in fastboot flash was ok but no recovery.
I've not flashed boot.img cuz in update.zip when i extract all the images. theres no boot.img
But even in pie update.app there are many ramdisk images see in attachment.
https://ibb.co/BqqwSRZ
thanks for your help
And this is when i flash via fastboot
(
PS C:\SDK\platform-tools> ./fastboot devices
AQH7N18201013919 fastboot
PS C:\SDK\platform-tools> ./fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot: error: cannot load 'recovery_ramdisk.img': No such file or directory
PS C:\SDK\platform-tools> ./fastboot flash recovery_ramdisk recovery_ramdis.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.738s]
Writing 'recovery_ramdisk' OKAY [ 0.175s]
Finished. Total time: 0.931s
PS C:\SDK\platform-tools> ./fastboot flash recovery_vendor recovery_vendor.img
Sending 'recovery_vendor' (16384 KB) OKAY [ 0.372s]
Writing 'recovery_vendor' OKAY [ 0.077s]
Finished. Total time: 0.483s
PS C:\SDK\platform-tools> ./fastboot flash recovery_vbmeta recovery_vbmeta.img
Sending 'recovery_vbmeta' (6 KB) OKAY [ 0.006s]
Writing 'recovery_vbmeta' OKAY [ 0.030s]
Finished. Total time: 0.055s
PS C:\SDK\platform-tools> ./fastboot flash kernel kernel.img
Sending 'kernel' (24576 KB) OKAY [ 0.554s]
Writing 'kernel' OKAY [ 0.290s]
Finished. Total time: 0.859s
)
i've got news ! i used the firmware on androihost RU.
extract the update.app and then extract imgs
Flashed images of recovery and system and kernel !
Now i've got recovery stock showing.
But no boot, no adb in recovery, is it driver related on windows ? cuz i ve got an error message " unknow peripheral don't work"
ho so i succeded ! i've flashed images to have recovery. Next i've done dload method via OTG. Update success and then Boot.
Thanks for your help and i will make a little tuto to help users in the same situation.
shadowsami4 said:
ho so i succeded ! i've flashed images to have recovery. Next i've done dload method via OTG. Update success and then Boot.
Thanks for your help and i will make a little tuto to help users in the same situation.
Click to expand...
Click to collapse
we could use that tutorial.. where is it?
ante0 said:
OTG USB-C to USB-A (female) and a memory stick/sd adapter works. Service/dload firmware from androidhost.ru (use russian VPN if you have to increase download speed).
However, this uses recovery to flash so chances are it won't work... But you could test before doing it by booting holding vol up + down + power + usb plugged in.
When you have the dload, if dload mode does work, just extract the downloaded zip and copy the 'dload' folder in 'Software' to your memory stick. Do not extract the zip(s) in the dload folder. They need to remain zipped.
If no dload mode, extract all recovery partitions from update.app (recovery_ramdisk, recovery_vendor, recovery_vbmeta) and kernel.
Flash to the corresponding partition using fastboot (example: fastboot flash recovery_vendor RECOVERY_VENDOR.img etc.)
edit: Also a question, you flashed 'boot'?
Boot has not been part of EMUI since Nougat. Use a Pie update.app. It should not contain 'ramdisk' as that's gone too in Pie.
Click to expand...
Click to collapse
tkalfaoglu said:
we could use that tutorial.. where is it?
Click to expand...
Click to collapse
Here
ante0 said:
OTG USB-C to USB-A (female) and a memory stick/sd adapter works. Service/dload firmware from androidhost.ru (use russian VPN if you have to increase download speed).
However, this uses recovery to flash so chances are it won't work... But you could test before doing it by booting holding vol up + down + power + usb plugged in.
When you have the dload, if dload mode does work, just extract the downloaded zip and copy the 'dload' folder in 'Software' to your memory stick. Do not extract the zip(s) in the dload folder. They need to remain zipped.
If no dload mode, extract all recovery partitions from update.app (recovery_ramdisk, recovery_vendor, recovery_vbmeta) and kernel.
Flash to the corresponding partition using fastboot (example: fastboot flash recovery_vendor RECOVERY_VENDOR.img etc.)
edit: Also a question, you flashed 'boot'?
Boot has not been part of EMUI since Nougat. Use a Pie update.app. It should not contain 'ramdisk' as that's gone too in Pie.
Click to expand...
Click to collapse
Sorry dear, what must it be the firmware of the BLA-L09 8.0.0.128(c55) ? i should choose the 8.0 or also the c55 ? i see some 8.0.0.137 would that be okey ?
thank you
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
sentavn said:
you should format by using fastboot. First download your stock ROM and extract with Huawei Firmware Extracter. Select UPDATE.APP and extract following files:
erecovery_kernel.img
erecovery_ramdisk.img
erecovery_vbmeta.img
cust.img
erecovery_vendor.img
kernel.img
ramdisk.img
recovery_vbmeta.img
recovery_vendor.img
system.img
Reboot your device in to fastboot mode (recovery mode) and flash those files one by one:
fastboot flash erecovery_kernel erecovery_kernel.img
...
fastboot flash system system.img
//
Erase your userdata space:
fastboot -w
//reboot
fastboot reboot
Now go to your stock recovery and do factory reset, wide cache.
Now your device back to stock OREO
Click to expand...
Click to collapse
Any Ideas?
HOW I FIXED:
I downloaded this EMUI 5 Nougat, Thanks to bozka1:
https://androidhost.ru/5SZ
I extracted UPDATE.APP file using Huawei Update Extractor.
I was trying to flash everything via fastboot: BOOT.img, RECOVERY.img, RECOVERY2.img, CUST.img, SYSTEM.img but nothing helped me.
I found out what you can flash via fastboot here:
https://forum.xda-developers.com/general/general/huawei-fastboot-commands-t3850123
There was no hope for me, so I tried to flash USERDATA.img
fastboot flash userdata USERDATA.img
Click to expand...
Click to collapse
And then cmd promped something unusual:
target reported max download size of 471859200 bytes
sending 'userdata' (24576 KB)...
OKAY [ 0.646s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.401s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then I proceeded to flash: BOOT.img, RECOVERY.img, RECOVERY2.img and CACHE.img
I didn't flash SYSTEM.img because I flashed it before like 1500 times.
My phone didn't work yet so I used the DLOAD method because RECOVERY finally worked, so I shut down the device and used three buttons combo:
First holding Volume Up, Volume Down and then pressing Power Button.
There is a documentation in the firmware I downloaded, SDcard must be in exFAT format.
Thank You bozka1.
voltzero2 said:
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
Any Ideas?
Click to expand...
Click to collapse
What is your original location, C461?
Which oeminfo you have flashed?
bozka1 said:
What is your original location, C461?
Which oeminfo you have flashed?
Click to expand...
Click to collapse
My original location is C432, I don't remember flashing any oeminfo
voltzero2 said:
My original location is C432, I don't remember flashing any oeminfo
Click to expand...
Click to collapse
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
bozka1 said:
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
Click to expand...
Click to collapse
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
voltzero2 said:
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
Click to expand...
Click to collapse
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
bozka1 said:
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
Click to expand...
Click to collapse
It says its unlucked:
https://imgur.com/a/LEDKWFr
I hope this link works
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
So I'll have to wait a little before I'll download Service ROM, my internet connection isn't the greatest, but I flashed Your TWRP and unfortunately it doesn't work;
If I hold the Power button and Volume Up - the same story as before, I see the loading TWRP screen and nothing happends,
If I let the device to boot up and then press only the Volume Up button - it says "Your device is booting up" and nothing happens.
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
EDIT:
I did some testing and Your TWRP doesn't boot at all on my device, I flashed another one, Catuva21 3.1.1 Nougat, and that is the one that I had before - it is booting but never loads.
voltzero2 said:
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
Click to expand...
Click to collapse
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
bozka1 said:
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
Click to expand...
Click to collapse
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
voltzero2 said:
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
Click to expand...
Click to collapse
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
bozka1 said:
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
Click to expand...
Click to collapse
Yeah, I've done it already, unfortunately nothing changed. How about BOOT.img? Can this influence something?
EDIT:
I also wonder about just following the steps in my first post, I've got UPDATE.APP for Oreo, but I don't know if it will only make it worse.
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
Do I have to install oeminfo to be able to use the "three buttons combo"? Because I tried it today and it doesn't work, phone is just stuck at "Your device is booting.." screen, guess I'm out of luck
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
voltzero2 said:
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
Click to expand...
Click to collapse
You're welcome
Hi help me
Bozka1
My huawei mate 10 lite is brick stock on erecovery what can i do now
Lj08 said:
My huawei mate 10 lite is brick stock on erecovery what can i do now
Click to expand...
Click to collapse
Hi, have you tried to do something with your phone? Can you provide some info?
voltzero2 said:
Hi, have you tried to do something with your phone? Can you provide some info?
Click to expand...
Click to collapse
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Lj08 said:
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Click to expand...
Click to collapse
Alright, so did it just happened randomly or did you tried to do something with your phone? Did you unlocked bootloader or flashed custom recovery etc? You need to explain what happened, that's quite important if you want someone to help you.