Related
Hello guys,
Let me preface this with the fact that I have been searching this forum for the past hour and could not find anything pertinent for my situation.
I've updated to the latest GSM OTA (the Vodafone EU one) and all was great, decided to reboot my phone and got into a bootloop. I don't have a recovery to boot from and going to be short on battery soon.
The way I see it, I'm stuck with a bricked phone until the RSD package for the OTA is released. Is that correct? am I missing anything?
Can anyone point me to a relevant thread where I can catch a break?
Cheers!
tuxcomputing said:
Hello guys,
Let me preface this with the fact that I have been searching this forum for the past hour and could not find anything pertinent for my situation.
I've updated to the latest GSM OTA (the Vodafone EU one) and all was great, decided to reboot my phone and got into a bootloop. I don't have a recovery to boot from and going to be short on battery soon.
The way I see it, I'm stuck with a bricked phone until the RSD package for the OTA is released. Is that correct? am I missing anything?
Can anyone point me to a relevant thread where I can catch a break?
Cheers!
Click to expand...
Click to collapse
Fixed, please close.
How did you fixed it?
Sent from my XT910 using xda premium
Please tell us how you fixed this, i have same problem but i already screwed it up more by trying to flash back to ics after i was stuck at boot on JB vodafone. Now i have bricked phone and i wait for Fastboot files, which we dont know when will come out
Got the same problem here
Alright, here goes.
I am not responsible to whatever happens to your phones. This process is described for the Vodafone OTA.
Also, you will lose root
I'm guessing your phones are in a constant bootloop right about now. If they are, you have to make sure you still have some battery left so that on AP Fastboot it shows battery OK. If you don't, follow the guides here to get more juice or get a 'factory cable' and charge your phone.
To download:
- Fastboot from here: http://dfiles.eu/files/bih3tmg7b
- OTA kernel (here: http://d-h.st/xat )
- The whole OTA here ON YOUR SDCARD
- original ICS RSD Image here
Process:
Extract the fastboot somewhere accessible like c:/fastboot
Extract the kernel and the original ICS files on your desktop
Copy the OTA kernel (boot_3.0.8-g7198280) to your c:/fastboot folder
Copy 'system_signed' from the original ICS archive to your fastboot folder
Open the command prompt (search for cmd.exe in your programs)
Navigate to c:/fastboot (use "cd .." to excape a folder and "dir" to list the files in a folder )
Go to AP fastboot on your phpne and do the following from the command prompt:
fastboot flash boot boot_3.0.8-g7198280.img
fastboot flash system system_signed
fastboot reboot-bootloader
Now restart your phone and enter recovery the normal way volUp+volDown + power button then select Recovery, then volUp+volDown to see the menu.
Do a factory reset
Flash the OTA (that should be on your card)
Reboot
Ta-da!
If after the whole process you get a flash failure when rebooting your phone, use this guide to get rid of that: http://forum.xda-developers.com/showthread.php?t=1634223
If this helped you, please show the 'Thanks' button some love. Also, post here if you run into trouble, DO NOT PM!
tuxcomputing said:
Alright, here goes.
I am not responsible to whatever happens to your phones. This process is described for the Vodafone OTA.
Also, you will lose root
I'm guessing your phones are in a constant bootloop right about now. If they are, you have to make sure you still have some battery left so that on AP Fastboot it shows battery OK. If you don't, follow the guides here to get more juice or get a 'factory cable' and charge your phone.
To download:
- Fastboot from here: http://dfiles.eu/files/bih3tmg7b
- OTA kernel (here: http://d-h.st/xat )
- The whole OTA here ON YOUR SDCARD
- original ICS RSD Image here
Process:
Extract the fastboot somewhere accessible like c:/fastboot
Extract the kernel and the original ICS files on your desktop
Copy the OTA kernel (boot_3.0.8-g7198280) to your c:/fastboot folder
Copy 'system_signed' from the original ICS archive to your fastboot folder
Open the command prompt (search for cmd.exe in your programs)
Navigate to c:/fastboot (use "cd .." to excape a folder and "dir" to list the files in a folder )
Go to AP fastboot on your phpne and do the following from the command prompt:
fastboot flash boot boot_3.0.8-g7198280.img
fastboot flash system system_signed
fastboot reboot-bootloader
Now restart your phone and enter recovery the normal way volUp+volDown + power button then select Recovery, then volUp+volDown to see the menu.
Do a factory reset
Flash the OTA (that should be on your card)
Reboot
Ta-da!
If after the whole process you get a flash failure when rebooting your phone, use this guide to get rid of that: http://forum.xda-developers.com/showthread.php?t=1634223
If this helped you, please show the 'Thanks' button some love. Also, post here if you run into trouble, DO NOT PM!
Click to expand...
Click to collapse
I tried your method but I get a:
Preflash validating failure
when writing the system_signed to the device
pirondello said:
I tried your method but I get a:
Preflash validating failure
when writing the system_signed to the device
Click to expand...
Click to collapse
That's weird. Prolly the flash was messed up somewhere..
Try this before "fastboot flash boot boot_3.0.8-g7198280.img":
extract recovery_signed and allow-mbmloader-flashing-mbm.bin from the ICS folder and put them into the fastboot folder
do this
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash recovery recovery_signed
Let me know if that works
tuxcomputing said:
That's weird. Prolly the flash was messed up somewhere..
Try this before "fastboot flash boot boot_3.0.8-g7198280.img":
extract recovery_signed and allow-mbmloader-flashing-mbm.bin from the ICS folder and put them into the fastboot folder
do this
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash recovery recovery_signed
Let me know if that works
Click to expand...
Click to collapse
Unfortunately still the same problem, can't flash the system_signed file.
Really appreciate your help, thank you anyway!
tuxcomputing said:
That's weird. Prolly the flash was messed up somewhere..
Try this before "fastboot flash boot boot_3.0.8-g7198280.img":
extract recovery_signed and allow-mbmloader-flashing-mbm.bin from the ICS folder and put them into the fastboot folder
do this
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash recovery recovery_signed
Let me know if that works
Click to expand...
Click to collapse
Well i give you thumbs up and thanks for you helping hand, however it still doesnt work gives preflashvalidation failure on system_signed flashing. If you have some more ideas it would be really nicce to try, meanwhile i think we will just have to wait for fastboot files. Verizon version for xt912 got FF already maybe we will get ours in a week or so.
Use this method .. Hsd pilot again nailed it to save our asses ..
It should definatly unbrick your mobile because i tried it on same version and i am back on jellybean ..
http://forum.xda-developers.com/showthread.php?t=2194825
Hit the thx to hsd pilot on the op and me if ya think i helped ya to share link :thumbup:
Thx in advance btw
Sent from my Droid Razr HD (4GLTE) using Tapatalk 2
Edit: Always refresh before you reply
anurag.dj2u said:
Use this method .. Hsd pilot again nailed it to save our asses ..
It should definatly unbrick your mobile because i tried it on same version and i am back on jellybean ..
http://forum.xda-developers.com/showthread.php?t=2194825
Hit the thx to hsd pilot on the op and me if ya think i helped ya to share link :thumbup:
Thx in advance btw
Sent from my Droid Razr HD (4GLTE) using Tapatalk 2
Click to expand...
Click to collapse
Didn't work for me. Flashing went fine but when trying to enter recovery I get "Invalid Flash Mode (S) (Boot Failure)
HSD-Pilot said:
Edit: Always refresh before you reply
Click to expand...
Click to collapse
Sorry again :thumbdown:
Sent from my Droid Razr HD (4GLTE) using Tapatalk 2
No, you was first, i mean myself
HSD-Pilot said:
No, you was first, i mean myself
Click to expand...
Click to collapse
TeddyOFLove said:
Well i give you thumbs up and thanks for you helping hand, however it still doesnt work gives preflashvalidation failure on system_signed flashing. If you have some more ideas it would be really nicce to try, meanwhile i think we will just have to wait for fastboot files. Verizon version for xt912 got FF already maybe we will get ours in a week or so.
Click to expand...
Click to collapse
For your information, I managed to unbrick my phone. Problem seemed to be my CID.IMG. After erasing it, I could enter recovery and installl JB from ext-sdcard. Now I have to use BP Tools tools to boot, because as soon as I restore CID, the device doesn't boot.
Really strange, because my phone is actually from Europe (d/a/ch), Switzerland. Maybe it's due to the fact that I switched to the chinese JB Ota leak before updating to the EU leak.
Hi,
I have bricked my Honor 5x after flashing custom recovery. This these the steps I followed:
1) Unlocked the bootloader
2) Flashed TWRP recovery
3) Flashed root
4) Tried to update OTA
Now the phone is stuck at boot screen. I can enter recovery by pressing volume down and power, but now is stock recovery. And I don't know what to do.
Can someone help me?
OK u can't OTA update with twrp AND U SHOULD try adb flashing twrp through fastboot and maybe restoring a nandroid if u have one if not there's some u can download around here
Hey, my phone is bricked too. How did you manage to flash adb during twrp. How did you restore the backup and where did you get it from?
Or could someone please explain to me how I can get back to stock. I saw one thread with the .app file, but there you had to go the setting or something, which I can't do.
I have twrp installed and I have the L21 version.
Ok, I figured it out. I took the backup and the instructions from this thread: http://forum.xda-developers.com/honor-5x/development/unrooted-stock-rom-t3308902
heinzwilli6 said:
Hey, my phone is bricked too. How did you manage to flash adb during twrp. How did you restore the backup and where did you get it from?
Or could someone please explain to me how I can get back to stock. I saw one thread with the .app file, but there you had to go the setting or something, which I can't do.
I have twrp installed and I have the L21 version.
Click to expand...
Click to collapse
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
Download Huawei Update Extractor
http://d-h.st/wwfQ
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
After that you should be back on stock firmware
I tried to do that too. But the problem was that my adb didn't recognize my phone. Of course I had everything installed.
When I unlocked the bootloader earlier, it worked. But there I had to enable USB debugging. When my phone was broke, I couldn't enable it. Maybe that's why?
However, my phone is working right now, so thanks anyway.
fixed
jperez1132 said:
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
Download Huawei Update Extractor
http://d-h.st/wwfQ
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
After that you should be back on stock firmware
Click to expand...
Click to collapse
I have a practically dead honor 5x, flashed a L-24 firmware on L-22. TWRP doesnt let me do anything, no touch functions work so i cannot restore my back up.
Fastboot commands on format /data and flash cust cust.img fail with the error "Remote: Command not allowed", bootloader is unlocked, pls help.....I need to flash back the default cust.img to get it back to normal
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
nandakalyan said:
I have a practically dead honor 5x, flashed a L-24 firmware on L-22. TWRP doesnt let me do anything, no touch functions work so i cannot restore my back up.
Fastboot commands on format /data and flash cust cust.img fail with the error "Remote: Command not allowed", bootloader is unlocked, pls help.....I need to flash back the default cust.img to get it back to normal
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
Click to expand...
Click to collapse
WORKED: update.app in dload folder WORKED !!! Thanks a lot
narengowda said:
WORKED: update.app in dload folder WORKED !!! Thanks a lot
Click to expand...
Click to collapse
Glad it worked! did you figure out what caused the issue?
jperez1132 said:
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
Download Huawei Update Extractor
http://d-h.st/wwfQ
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
After that you should be back on stock firmware
Click to expand...
Click to collapse
Is your fingerprint ID working good?
---------- Post added at 09:14 AM ---------- Previous post was at 08:46 AM ----------
fastboot flash cust CUST.img
target max-download-size: 254MB
sending 'cust' (196335 KB)...
OKAY [ 6.493s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.493s
Cant flash cust. How did you do that?
sad1996 said:
Is your fingerprint ID working good?
---------- Post added at 09:14 AM ---------- Previous post was at 08:46 AM ----------
fastboot flash cust CUST.img
target max-download-size: 254MB
sending 'cust' (196335 KB)...
OKAY [ 6.493s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.493s
Cant flash cust. How did you do that?
Click to expand...
Click to collapse
Yes, it is working perfectly.
Hi, sorry for hijacking a thread but I thought it'd be better than making a new one.
I did pretty much the same as the OP, unlocked the bootloader, flashed TWRP recovery, rooted and then stupidly tried to do an official update on the phone (I believe it was kiw-l21c432b140)
The phone is just now stuck at the boot screen, I can get into fastboot mode but cannot use ADB, says device isn't found no matter what I try. I also tried putting stock firmware on the SD card and going into download mode (EMUI) but it just says software install failed.. Any help appreciated, only got the phone today and have spent longer trying to fix it than I have using it..
Thanks!
tomblast66 said:
Hi, sorry for hijacking a thread but I thought it'd be better than making a new one.
I did pretty much the same as the OP, unlocked the bootloader, flashed TWRP recovery, rooted and then stupidly tried to do an official update on the phone (I believe it was kiw-l21c432b140)
The phone is just now stuck at the boot screen, I can get into fastboot mode but cannot use ADB, says device isn't found no matter what I try. I also tried putting stock firmware on the SD card and going into download mode (EMUI) but it just says software install failed.. Any help appreciated, only got the phone today and have spent longer trying to fix it than I have using it..
Thanks!
Click to expand...
Click to collapse
As long as you are able to boot into fastboot you still have hope
Are you able to get into TWRP? (Power + Vol up) If yes, download the L-21 stock rom in the file repository thread and flash it. In all likelihood, that will solve any corruption of system files. If not, read on.
Did you check if you have installed the ADB drivers? I am assuming it should have been installed considering you flashed TWRP, but better to check and reinstall. Device not found is usually a driver error. Alternatively, you can install HiSync, it refreshes and replaces the drivers needed for Honor 5X. Further to installing that, try adb fastboot commands and flash the stock recovery using the steps in this post:
http://forum.xda-developers.com/showpost.php?p=65659088&postcount=5
nandakalyan said:
As long as you are able to boot into fastboot you still have hope
Are you able to get into TWRP? (Power + Vol up) If yes, download the L-21 stock rom in the file repository thread and flash it. In all likelihood, that will solve any corruption of system files. If not, read on.
Did you check if you have installed the ADB drivers? I am assuming it should have been installed considering you flashed TWRP, but better to check and reinstall. Device not found is usually a driver error. Alternatively, you can install HiSync, it refreshes and replaces the drivers needed for Honor 5X. Further to installing that, try adb fastboot commands and flash the stock recovery using the steps in this post:
http://forum.xda-developers.com/showpost.php?p=65659088&postcount=5
Click to expand...
Click to collapse
When I do power and vol up I get EMUI recovery, not TWRP I put the stock rom on the SD card and tried to install it and it just says "Software install failed" and the only option is to shut the phone down again.
I had all the ADB drivers installed, will reinstall it all and see if it helps. When I run adb now and use the "adb devices" command it just says "List of devices attached" and doesn't show anything..
tomblast66 said:
When I do power and vol up I get EMUI recovery, not TWRP I put the stock rom on the SD card and tried to install it and it just says "Software install failed" and the only option is to shut the phone down again.
I had all the ADB drivers installed, will reinstall it all and see if it helps. When I run adb now and use the "adb devices" command it just says "List of devices attached" and doesn't show anything..
Click to expand...
Click to collapse
Oh then you have stock recovery, are you using the update.app provided by Huawei? Or using any ROMs/images posted here? It is possible that you may have a corrupted download, look up the Huawei site for downloads in the support section for your region and download the official update.app, try with that
nandakalyan said:
Oh then you have stock recovery, are you using the update.app provided by Huawei? Or using any ROMs/images posted here? It is possible that you may have a corrupted download, look up the Huawei site for downloads in the support section for your region and download the official update.app, try with that
Click to expand...
Click to collapse
It wasn't stock recovery before, after the phone updated it went back to stock and wouldn't boot. I downloaded the firmware from http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 and that's what I try to install through recovery and it says there's an error, a load of other texts flashes up before it says error but it's too quick to read. When I have better internet I'll re-download it in case it was corrupt. Thanks for your help, hopefully I can get it fixed as I only just got this to replace my old phone. Would be a shame to spend the money on it and have no use from the device.. Just wish the computer would detect through adb as I can get into fastboot easily enough.
tomblast66 said:
It wasn't stock recovery before, after the phone updated it went back to stock and wouldn't boot. I downloaded the firmware from http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 and that's what I try to install through recovery and it says there's an error, a load of other texts flashes up before it says error but it's too quick to read. When I have better internet I'll re-download it in case it was corrupt. Thanks for your help, hopefully I can get it fixed as I only just got this to replace my old phone. Would be a shame to spend the money on it and have no use from the device.. Just wish the computer would detect through adb as I can get into fastboot easily enough.
Click to expand...
Click to collapse
Sure, we all help each other
BTW, just to be sure, you using the single "Update.app" file, that runs into a couple of gigs or the extracted one? You can't flash extracted Update.app through stock recovery.
HiSync (the official Huawei tool) also provides an option to recover the phone, tried that?
nandakalyan said:
Sure, we all help each other
BTW, just to be sure, you using the single "Update.app" file, that runs into a couple of gigs or the extracted one? You can't flash extracted Update.app through stock recovery.
HiSync (the official Huawei tool) also provides an option to recover the phone, tried that?
Click to expand...
Click to collapse
It's the single one, about 2.66GB I believe, I tried the recovering through the Huawei tool and it says "Your device is not supported for system recovery".
tomblast66 said:
It's the single one, about 2.66GB I believe, I tried the recovering through the Huawei tool and it says "Your device is not supported for system recovery".
Click to expand...
Click to collapse
Oops! I am no techie, so am at the end of my wits, but thing I do suspect is a corrupted download, so if you can try downloading the file again from a stable connection and try is all I can think of. I've had this corrupted file thing quite a few times, so suggesting.
Problem already solved. Thanks!
Hi everyone, this is Sarry. I got my new huawei mate 9 pro on Wednesday this week, the version is LON-L29C636, I was trying to flash a custom ROM into the phone, but unfortunately I was too careless, flashed a different version ROM into it and cause immediate start up loop. As I finally boot into fastboot and twrp rec mode, I noticed that the computer won't recognize the USB portal of the device. So I went in eRecovery mode and tried to download an updated version but it failed to find any useful version.
Since mate 9 pro doesn't support SD card, I brought a USB-OTG cable and also usb type-c microSD adapter, when I connected the sd card to the phone, twrp reads the information, but when I tried to flash the update.zip file, it failed. I tried to copy the dload folder with update.app by twrp into phone storage, even if I got successful, the file just disappeared when i refresh the page. So now I don't have any idea on how to unbrick the phone, felt really bad.
Feel free to ask me any question or information needed, I really hope to unbrick the phone, I've been using huawei cellphone for more then 2 years and love it very much. Thanks for the help!!
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
TheShadowMC said:
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
Click to expand...
Click to collapse
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
However what error does it give during flashing system.IMG I would like to know, also as well as twrp custom ROM flashing?
Aquarius_2333 said:
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
Click to expand...
Click to collapse
well brother about the driver issue, sorry about being late, you must have downloaded the fastboot drivers and installed them.
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.
I installed EMUI 9 on my p20 lite and didn't like it, so I tried one of the openkirin 9.0 beta roms. There was some features that didn't work so I decided I wanted to go back. I followed the guide on openkirin's website about going back to stock by flashing system.img, ramdisk.img, kernel.img and recovery_ramdisk.img however trying to flash ramdisk.img gives "partition length get error". Now, the phone only is able to boot into fastboot and eRecovery mode. In eRecovery the options to backup and to factory reset are grayed out however, and the "update to latest version" doesn't work. When I plug the charger in from being turned off it shows the white error screen with error 10 (boot image) and error 2 (load failed). I have a suspicion that flashing kernel.img is what causing the problem, but I don't really know enough to be sure and I don't want to do anything to make it worse since it seems like this should be fixable.
This is the only phone I have which properly worked so any help is greatly appreciated.
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
ars_chelsea said:
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
Click to expand...
Click to collapse
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Afifus said:
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Click to expand...
Click to collapse
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Tried Oreo build 150 for ane-lx1c432 and ane-lx1c782 since those are the only models my phone could be.
Although, when I do the get-build-number command in fastboot it still says I'm on a Pie build. I'm gonna try doing a Pie build and I'll get back to you.
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Yeah, pie didn't work either.
Afifus said:
Yeah, pie didn't work either.
Click to expand...
Click to collapse
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
ars_chelsea said:
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
Click to expand...
Click to collapse
I got it off of firmware finder. Are those not signed?
Afifus said:
I got it off of firmware finder. Are those not signed?
Click to expand...
Click to collapse
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
ars_chelsea said:
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
Click to expand...
Click to collapse
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Afifus said:
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Click to expand...
Click to collapse
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
yassine2217 said:
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
Click to expand...
Click to collapse
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Afifus said:
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Click to expand...
Click to collapse
great happy for you