mate 10 lite bricked.....!!!!! - Huawei Mate 10 Questions & Answers

i did an upgrade from 7.0 nougat to oreo 8.0 using firmware finder.apk, after that every thing was going good, i backed up my stock rom and wanna try 8.0 custom rom and accidentally i formatted my backup and and tried many custom roms but no survival chances,
now my oem info shows RNE-L21C432B133, i had also downloaded the full ota + hw/eu file but dont know how to flash properly mate 10 lite.
can any one help ????

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

Install Stock ROM Huawei
-.phone connected USB
-.connected To On TWRP
-.Rename xxxxxx to update_all_hw
-.Rename xxxxxx to update_data_public
-----------------------------------------------------
Install
-.Shift + right click the folder and open command prompt here
-.adb push HuRUpdater_0.3.zip /sdcard
-.adb push update.zip /sdcard
-.adb push update_all_hw.zip /sdcard
-.adb push update_data_public.zip /sdcard
-----------------------------------------------------
install on TWRP
-.install - Press HuRUpdater_0.3.zip
-.Then follow instructions on screen VOLUME DOWN
-.Press back once more -- Select reboot recovery
-.Wipe data/factory reset -- Then reboot system
-.DONE GOODLUCK

JAZZYBUTT999 said:
i did an upgrade from 7.0 nougat to oreo 8.0 using firmware finder.apk, after that every thing was going good, i backed up my stock rom and wanna try 8.0 custom rom and accidentally i formatted my backup and and tried many custom roms but no survival chances,
now my oem info shows RNE-L21C432B133, i had also downloaded the full ota + hw/eu file but dont know how to flash properly mate 10 lite.
can any one help ????
Click to expand...
Click to collapse
ma sauvegarde de rne-l21c432b133 full https://mega.nz/#!ksdhmCQJ!fb5TDWpBEEA_BwXnO4gd86ry33tD6rVaGdXQ3kYy7LU
copy all to your TWRP folder from your SD card.
Use this TWRP because the backup was done with.
* https://mega.nz/#!c1tyRL7Z!r3fhcK5eNHR1aaN_s8OwafD1eQutvpc2cF-lG4guQdk
restart in TWRP.
go to wipe.
check all except oeminfo. and wipe all.
go to wipe, data format, write yes and validate.
go to wipe check data and change to f2f.
now, go to restore, and restore all files one by one, except oeminfo.
once finished, go to install, install the file meta-inf.zip (it's product).
https://mega.nz/#!d5sgDQba!Zntk05RjlDLFi7Wmz7mmVvvr7nc4vp7Kv2SZtcLjB5Q
then restart.
here is.

thanks for the info
Chisetdel31260 said:
ma sauvegarde de rne-l21c432b133 full https://mega.nz/#!ksdhmCQJ!fb5TDWpBEEA_BwXnO4gd86ry33tD6rVaGdXQ3kYy7LU
copy all to your TWRP folder from your SD card.
Use this TWRP because the backup was done with.
* https://mega.nz/#!c1tyRL7Z!r3fhcK5eNHR1aaN_s8OwafD1eQutvpc2cF-lG4guQdk
restart in TWRP.
go to wipe.
check all except oeminfo. and wipe all.
go to wipe, data format, write yes and validate.
go to wipe check data and change to f2f.
now, go to restore, and restore all files one by one, except oeminfo.
once finished, go to install, install the file meta-inf.zip (it's product).
https://mega.nz/#!d5sgDQba!Zntk05RjlDLFi7Wmz7mmVvvr7nc4vp7Kv2SZtcLjB5Q
then restart.
here is.
Click to expand...
Click to collapse
i will try asap and after that i will let u know the results.... thumbs up:good::good::good:

Help
Hi I also have my Mate 10 Lite RNE-L21C432 locked. I can only get into fastboot.
These are the results of fast boot:
C:\adb fastboot oem get—product—mode1
(bootloader) RNE-L21
OKAY [ 0.016s]
finished, total tine: 0.031s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished, total tine: 0.016s
C:\adb>fastboot oem get-build-number
(bootloader) :Systen 8.0.0.046(07P2)
OKAY [ 0.031s]
finished, total tine: 0.031s
C:\adb)fastboot getvar rescue_enter_recovery
(bootloader) This is sec phone??
(bootloader) NOT secboot recovery image?
getvar:rescue_enter_recovery FAILED (remote: FAIL:verify secure image fail? )
finished, total tine: 0.078s
C:\adb)fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :Systen 8.0.0.046(07P2)
OKAY I 0.031s]
finished, total tine: 0.031s
C:\adb>
can someone help me? Thank you

pabbata said:
Hi I also have my Mate 10 Lite RNE-L21C432 locked. I can only get into fastboot.
These are the results of fast boot:
C:\adb fastboot oem get—product—mode1
(bootloader) RNE-L21
OKAY [ 0.016s]
finished, total tine: 0.031s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished, total tine: 0.016s
C:\adb>fastboot oem get-build-number
(bootloader) :Systen 8.0.0.046(07P2)
OKAY [ 0.031s]
finished, total tine: 0.031s
C:\adb)fastboot getvar rescue_enter_recovery
(bootloader) This is sec phone??
(bootloader) NOT secboot recovery image?
getvar:rescue_enter_recovery FAILED (remote: FAIL:verify secure image fail? )
finished, total tine: 0.078s
C:\adb)fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :Systen 8.0.0.046(07P2)
OKAY I 0.031s]
finished, total tine: 0.031s
C:\adb>
can someone help me? Thank you
Click to expand...
Click to collapse
Hello
do you have TWRP for emui 8.0 that starts?
if so, use HurUpdater 0.3, reinstall rne-l21c432b304.

Chisetdel31260 said:
Hello
do you have TWRP for emui 8.0 that starts?
if so, use HurUpdater 0.3, reinstall rne-l21c432b304.
Click to expand...
Click to collapse
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.

pabbata said:
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
Click to expand...
Click to collapse
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
pabbata said:
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
Click to expand...
Click to collapse
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
pabbata said:
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
Click to expand...
Click to collapse
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p

Chisetdel31260 said:
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
Click to expand...
Click to collapse
Hi I also installed this twrp, this is the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

pabbata said:
Hi I also installed this twrp, this is the result:
Click to expand...
Click to collapse
ME TOO Help Me
---------- Post added at 03:08 PM ---------- Previous post was at 03:00 PM ----------
++++++++++++++++

*Deleted*

tried but failed
Chisetdel31260 said:
ma sauvegarde de rne-l21c432b133 full https://mega.nz/#!ksdhmCQJ!fb5TDWpBEEA_BwXnO4gd86ry33tD6rVaGdXQ3kYy7LU
copy all to your TWRP folder from your SD card.
Use this TWRP because the backup was done with.
* https://mega.nz/#!c1tyRL7Z!r3fhcK5eNHR1aaN_s8OwafD1eQutvpc2cF-lG4guQdk
restart in TWRP.
go to wipe.
check all except oeminfo. and wipe all.
go to wipe, data format, write yes and validate.
go to wipe check data and change to f2f.
now, go to restore, and restore all files one by one, except oeminfo.
once finished, go to install, install the file meta-inf.zip (it's product).
https://mega.nz/#!d5sgDQba!Zntk05RjlDLFi7Wmz7mmVvvr7nc4vp7Kv2SZtcLjB5Q
then restart.
here is.
Click to expand...
Click to collapse
twrp does'nt flash, this happens see pic after flashing
https://lh3.googleusercontent.com/-...G99AIgCJoC/w530-h942-n-rw/AAAAAAAAAAAAAAA.jpg

I used HuRu today, to flash a Firmware Finder stock Oreo ROM as per my build number
I was partially on elemntal 1.1 (oreo) the phone got boot loop, I tried with my stock
oreo backups, it would show error on Venor and System, tried with Mounting unmounting
from TWRP, didnt work, restarted phone Lost TWRP, but the good thing was my Bootloader
and FRP were unlocked (used a file from Elemental rom thread to unlock FRP,
when my bootloader was already unlocked). In TWRP finally I tried to wipe
every thing (not SD Card), then tried to restore my back up again, unchecked vendor then
restarted, after a few bootloop restarts, I got stock recovery and used Format option, then got nothing on phone just the Stock recovery, format would close with ! mark in between.
So at this point, I would repeatedly get following error when installing any of TWRPs for mate 10 lite:
FAILED (remote: Command not allowed)
Was worried thinking I am not going to get any thing from this point, but then just tried the dload method
which worked only once for me in the past, and later always failed @ 5 %
So tried dload with the files for Nougat (RNE-L21C185B142), luckily it worked for me, I am on nougat again

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
Forgive me How is the exact procedure for formatting via fastboot Thanks I have the phone in these conditions

Diego1976 said:
Forgive me How is the exact procedure for formatting via fastboot Thanks I have the phone in these conditions
Click to expand...
Click to collapse
I think by running this command fastboot flash system system.img will automatically erase your data.

JAZZYBUTT999 said:
twrp does'nt flash, this happens see pic after flashing
https://lh3.googleusercontent.com/-...G99AIgCJoC/w530-h942-n-rw/AAAAAAAAAAAAAAA.jpg
Click to expand...
Click to collapse
hello did you solve it? the image like you comes out to me too ..
I also tried with hwota but nothing to do!
let me know if you found a solution
thanks in advance

Aniwat12 said:
Install Stock ROM Huawei
-.phone connected USB
-.connected To On TWRP
-.Rename xxxxxx to update_all_hw
-.Rename xxxxxx to update_data_public
-----------------------------------------------------
Install
-.Shift + right click the folder and open command prompt here
-.adb push HuRUpdater_0.3.zip /sdcard
-.adb push update.zip /sdcard
-.adb push update_all_hw.zip /sdcard
-.adb push update_data_public.zip /sdcard
-----------------------------------------------------
install on TWRP
-.install - Press HuRUpdater_0.3.zip
-.Then follow instructions on screen VOLUME DOWN
-.Press back once more -- Select reboot recovery
-.Wipe data/factory reset -- Then reboot system
-.DONE GOODLUCK
Click to expand...
Click to collapse
This Works on Semi-Brick (Start normally and when Android wakes up it reboots in recovery)?

hi, my mate 10 seems bricked. i can't go into fastboot mode neither in recovery. when i charge the phone, the led remain off.
but if i connect the phone to pc, hisuite starts. what can i do?
if i use hwota, the results is
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.529s

Dyzzy Solution
Guys I am now with some dyzzy solution but... with some logic to me, ok I will explain how I have my device alive again.
to be clear, this brick was caused because I want to have my device from ATT Mexico rebranded with dual sim ROM, then I lost oem info and cant go back 4G, so I installed Custom MORFUZ ROM 3.4, but I still without 4G and now with my second simcard deactivated, so... I tried to reflash with HWOTA the RNE-L03 rom single sim and... that was the mistake, after the procedure.. I got the semi-brick (since 2 days ago), ok then I was searching and reading a lot (and using more common sense haha) so, I needed to repair my device partitions because there was a mess triying to flash from another partition so, thats how I ended here, let's start:
*** First of all, prepare an SD card with the files for the HuRUpdater_0.3 mode, (just a tip, I leaved my phone run out of battery because I had the bootloop on the prompt screen that says that "your bootloader is unlocked and device is not trusted" so its easier to have acces to fastboot mode if you do this way)
- Step 1: I did the fastboot manual flashing unpacking my UPDATE.APP with HuaweiUpdateExtractor (see post#2)
once succesfully finished I rebooted my phone and still bricked
- Step 2: I entered fastboot mode and flashed the recovery image from CATUVA21 for Oreo (see post #9)
(IMPORTANT: DO NOT TRY TO ENTER ON TWRP RECOVERY RIGHT NOW OR YOU WILL NEED TO START AGAIN FROM STEP 1)
-Step 3: Connect the phone to energy (charger?, sorry I have very bad english) just 2 percent an unpplug, that's because if you can't go forward from here, you have to wait less to re-enter in fastboot and try another solution
-Steep 4: Here is the magic, press vol+ and plug the phone to your pc (yea, like entering eRecovery Wifi Mode) and Voilá!!! entered TWRP
-Steep 5: Flash HuRUpdater_0.3.zip, leave it finish, reboot device
Now you will be prompted to EMUI black screen with a message that says "partition is several damaged, you need to clean all partitions" you click on "clean all partitions" once finished, click in "Reboot System" be patient, for me was 4-6 minutes and some bootloops untill I heared the bootanimation tune and there is, initial config and now you are in a very dirty ROM but from here you can reflash a full rom, I hope It Help to anyone.

Related

[SOLVED] Can't install TWRP on Xiaomi Redmi note 4 :'(

Hi everyone !
I'm a little stuck now, so i really need your help !
I want to install LineageOS on my Xiaomi redmi note 4. So i followed the installation instructions on official Lineage website.
At the step "Install TWRP recovery" i'm stuck.
Here are the logs :
Code:
> $ fastboot flash recovery twrp-3.1.0-0-mido.img
target reported max download size of 134217728 bytes
sending 'recovery' (26840 KB)...
OKAY [ 1.328s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.331s
So after searching on the web I tried splitting img into chunks with the following command :
Code:
> $ fastboot flash -S 20M recovery twrp-3.1.0-0-mido.img
Invalid sparse file format at header magi
sending sparse 'recovery' (20476 KB)...
OKAY [ 1.015s]
writing 'recovery'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 1.019s
I choosed 20M for my chunks randomly (inferior to recovery image of 26840KB).
Other informations :
I can't boot to origin system
I can access to fastboot
I can use adb but my device is in sideload mode
Please feel free to answer if you have any idea.
You're great! Thanks.
Did you already unlock the bootloader? It seems not yet..
crok.bic said:
Did you already unlock the bootloader? It seems not yet..
Click to expand...
Click to collapse
Yes I did !
Code:
> $ fastboot getvar all
...
(bootloader) unlocked: yes
...
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
crok.bic said:
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
Click to expand...
Click to collapse
I'm not sure if it's Mido or Nikel.
Do you have a link for Nikel ? Because it doesn't appear in twrp list :\
For adb i've downloaded with
Code:
sudo apt-get install android-tools-adb
I've tried with 3.1.1-0-mido and same error than 3.1.0 :\
@crok you really rock !
I've tried with this link of Nikel : https://xiaomifirmware.com/downloads/twrp-custom-recovery-redmi-note-4-mtk/
And I'm having the recovery mode!
I continue the tutorial !
Great news. Please mark the thread [solved] just to help people who has the same trouble and seeking for info/solution.

twrp fastboot not working for me on Huewai Mate 10 Pro

I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
ChaseRxx said:
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
Click to expand...
Click to collapse
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
ikolbyi said:
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
Click to expand...
Click to collapse
GL!
Enviado de meu BLA-L29 usando o Tapatalk
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
LLoTE said:
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
Click to expand...
Click to collapse
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
LLoTE said:
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
Click to expand...
Click to collapse
okay - steps?
ikolbyi said:
okay - steps?
Click to expand...
Click to collapse
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
LLoTE said:
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
Click to expand...
Click to collapse
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
LLoTE said:
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
Click to expand...
Click to collapse
Thank you. I'm new at this and learning.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
look at this one
Toggling OEM unlocking in developer options is not enough, as that simply enables the ability to unlock your bootloader within fastboot. You need to retrieve a bootloader unlock code either directly from Huawei or a third party. I believe there is a guide for it in the guides sub-forum.
LLoTE said:
look at this one
Click to expand...
Click to collapse
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
ikolbyi said:
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
Click to expand...
Click to collapse
And how will you edit it? You'll root the phone or?
LLoTE said:
And how will you edit it? You'll root the phone or?
Click to expand...
Click to collapse
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
ikolbyi said:
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
Click to expand...
Click to collapse
No problem man

TWRP - Wiped Internal Storage now I can't boot into recovery

I've just unlocked the phone, via minimal ADB
tried fastboot getvar current-slot and got the output that my slot was a
then I've tried flashing TWRP at a utilizing
fastboot flash recovery twrp.img
then got the following output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 803868672 bytes
sending 'recovery' (39780 KB)...
OKAY [ 1.663s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 1.695s
so, I've tried fastboot flash boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 803868672 bytes
sending 'boot_a' (35452 KB)...
OKAY [ 1.063s]
writing 'boot_a'...
OKAY [ 0.183s]
finished. total time: 1.254s
then I've manually pressed the power button + volume up and successfully entered TWRP
there, I've gone to advanced wipe and wiped
Dalvik / ART Cache, system, Data and Internal Storage
I didn't know Internal Storage would give me problems... After that, I couldn't access my internal storage from the PC to copy the .zip of the custom rom.
Tried going to mount into TWRP to mount different partitions, no succes.
Then I thought that maybe if I restarted the phone it would be ok. So I've restarted and TWRP told me "no system installed, do you wish to continue?" I said yes.
Now, I'm stuck at fastboot and can't boot into twrp anymore...
I've tried repeating the same commands above and got the same outputs.
fastboot flash boot twrp.img got me the "OKAY" messages. But now, even if I hold the power + vol up button, I won't get to recovery.
I've tried
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.291s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.298s
because my frient told me to do so, but this command does not exist.
How can I proceed?
Try using mi flash tool
I was also stuck in fastboot mode I then tried installing twrp again with no success.
So I then went and flashed stock rom again into my phone using mi flash tool.
(Having a new account, I can't post link to these files. So download the files from official mi website, it is available there)
Steps to flash
1- Place the Flash File on Desktop.
2- open flash tool application.
3- Assign the Folder path.
4-Go to slot a using adb
5- Click on refresh & then tap Flash button

Can't flash system images in fastboot - FAILED (remote: 'sparse flash write failure')

Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
shaon121$ said:
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
Click to expand...
Click to collapse
It still doesn't work as administrator and with the image in the C drive root.
Change your img file and try again..or download again... What is your phone model?
shaon121$ said:
Change your img file and try again..or download again... What is your phone model?
Click to expand...
Click to collapse
I have already tried different images, the phone is a Huawei P Smart FIG-LX1.
useless double posts
Can't flash system.img in TWRP - E:Cannot flash images to file systems
I am trying to install a custom ROM on a Huawei P Smart FIG-LX1. I have a system.img that i should flash to the system partition. So when i try to flash the image i have two system partitions: Ona named "System" and one named "System Image". If...
forum.xda-developers.com
Size of image is larger than the target device in TWRP
Hi, I am trying to flash a system image in TWRP. When i try flashing the system.img to the System Image partiton i get this error: Size of image is larger than target device How can i solve this error? I tried the resize partition option on the...
forum.xda-developers.com
slx23 said:
Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Click to expand...
Click to collapse
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com

XT1941-4 stuck in bootloader with flashing locked

I have a Motorola XT1941-4, which I have from some time ago which is currently not able to be used. I wanted to try and fix it but cannot get any progress done. The problem I'm having is as follows: Whenever I boot the phone it goes right into the bootloader and at the bottom it says flashing_locked. I' able to communicate with the phone via fastboot and am able to boot into TWRP with fastboot boot twrp.img and when I am in TWRP the phone is also recognized in ADB. However I cannot get the phone to boot into Android. Is there anything I can do to fix this?
ogruendel said:
I have a Motorola XT1941-4, which I have from some time ago which is currently not able to be used. I wanted to try and fix it but cannot get any progress done. The problem I'm having is as follows: Whenever I boot the phone it goes right into the bootloader and at the bottom it says flashing_locked. I' able to communicate with the phone via fastboot and am able to boot into TWRP with fastboot boot twrp.img and when I am in TWRP the phone is also recognized in ADB. However I cannot get the phone to boot into Android. Is there anything I can do to fix this?
Click to expand...
Click to collapse
Have you tried to blankflash it?
FilipeET said:
Have you tried to blankflash it?
Click to expand...
Click to collapse
How would I go about doing that?
ogruendel said:
How would I go about doing that?
Click to expand...
Click to collapse
I'll leave the Motorola qboot utility in this reply.
Start device in fastboot mode, and
run the following command:
Code:
fastboot oem blankflash
fastboot oem blankflash
after that, extract and run the Unbrick.bat that I'll leave in this reply, your phone should be on a black screen when running the command, but after running the "Unbrick.bat" it should restart to the unlocked bootloader!
but before running it, verify if your phone codename is "deen"
FilipeET said:
I'll leave the Motorola qboot utility in this reply.
Start device in fastboot mode, and
run the following command:
Code:
fastboot oem blankflash
fastboot oem blankflash
after that, extract and run the Unbrick.bat that I'll leave in this reply, your phone should be on a black screen when running the command, but after running the "Unbrick.bat" it should restart to the unlocked bootloader!
but before running it, verify if your phone codename is "deen"
Click to expand...
Click to collapse
Sorry for the late reply, I had issues with my computer and then forgot about this... I've tried running the command fastboot oem blankflash but I get
Code:
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
ogruendel said:
Sorry for the late reply, I had issues with my computer and then forgot about this... I've tried running the command fastboot oem blankflash but I get
Code:
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Try to switch the slot,
Code:
fastboot set_active other
FilipeET said:
Try to switch the slot,
Code:
fastboot set_active other
Click to expand...
Click to collapse
I've tried this command, however this also fails with the message
Code:
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
What appears when you start the phone? could you send me a picture? Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
have you tried unlocking the bootloader again?
ogruendel said:
I've tried this command, however this also fails with the message
Code:
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
What appears when you start the phone? could you send me a picture? Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
have you tried unlocking the bootloader again?
I saw that you put in the post that you can start twrp, try changing the slot there in Reboot > Switch to slot B,
if it is in slot b: Reboot > Switch to slot A.
FilipeET said:
What appears when you start the phone? could you send me a picture? Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
have you tried unlocking the bootloader again?
I saw that you put in the post that you can start twrp, try changing the slot there in Reboot > Switch to slot B,
if it is in slot b: Reboot > Switch to slot A.
Click to expand...
Click to collapse
What appears when you start the phone?
Click to expand...
Click to collapse
https://imgur.com/a/Veg48Bs
Have you tried starting the recovery? Tried to use Lenovo Moto Smart Assistant?
Click to expand...
Click to collapse
Yes, however when I start the program it detects that a phone is connected but tells me "RSA detected, that your device flash is locked. [...]"
Have you tried unlocking the bootloader aagin?
Click to expand...
Click to collapse
Yes, I have. I remember when trying this before and following the steps on the official Motorola website, I would receive a new unlock code, however when I run fastboot oem get_unlock_data now and enter the output into the Motorola website it comes up with an error telling me that my device does not qualify for bootloader unlocking.
I saw that you put in the post that you can start twrp, try changing the slot there in Reboot > Switch to slot B,
if it is in slot b: Reboot > Switch to slot A.
Click to expand...
Click to collapse
I did this but the behaviour is the same. Commands come back with the same errors etc.
I saw the image, your phone can be unlocked, its says flashing_unlocked, so, he got unlocked 1 time, Just run "fastboot flashing unlock" ir "fastboot oem unlock"
ogruendel said:
https://imgur.com/a/Veg48Bs
Yes, however when I start the program it detects that a phone is connected but tells me "RSA detected, that your device flash is locked. [...]"
Yes, I have. I remember when trying this before and following the steps on the official Motorola website, I would receive a new unlock code, however when I run fastboot oem get_unlock_data now and enter the output into the Motorola website it comes up with an error telling me that my device does not qualify for bootloader unlocking.
I did this but the behaviour is the same. Commands come back with the same errors etc.
Click to expand...
Click to collapse
FilipeET said:
I saw the image, your phone can be unlocked, its says flashing_unlocked, so, he got unlocked 1 time, Just run "fastboot flashing unlock" ir "fastboot oem unlock"
Click to expand...
Click to collapse
When running
Code:
fastboot flashing unlock
two times (adb tells me to) it comes back with
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.002s]
Finished. Total time: 0.002s
Although the first part looks like the command failed, the OKAY in the end kind of contradicts that. The problem here is that I obviously cannot access the OS to enable OEM Unlocking in the Developer settings.
When running
Code:
fastboot oem unlock
the output says
Code:
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.002s
ogruendel said:
When running
Code:
fastboot flashing unlock
two times (adb tells me to) it comes back with
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.002s]
Finished. Total time: 0.002s
Although the first part looks like the command failed, the OKAY in the end kind of contradicts that. The problem here is that I obviously cannot access the OS to enable OEM Unlocking in the Developer settings.
When running
Code:
fastboot oem unlock
the output says
Code:
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.002s
Click to expand...
Click to collapse
Can you start the recovery?
FilipeET said:
Can you start the recovery?
Click to expand...
Click to collapse
If by starting the recovery you mean using the Motorola Smart Assistant, then no. The behaviour is the same as it was before. If you mean something else, please let me know
Try this:
fastboot flash partition gpt.bin
FilipeET said:
Try this:
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
When running this the output again looks kind of weird, both looking like it failed and it working.
Code:
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
Warning: skip copying partition image avb footer (partition partition size: 0, partition image size: 46592).
Sending 'partition' (45 KB) OKAY [ 0.168s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.081s]
Finished. Total time: 0.591s
ogruendel said:
When running this the output again looks kind of weird, both looking like it failed and it working.
Code:
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
Warning: skip copying partition image avb footer (partition partition size: 0, partition image size: 46592).
Sending 'partition' (45 KB) OKAY [ 0.168s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.081s]
Finished. Total time: 0.591s
Click to expand...
Click to collapse
try to start the phone now
FilipeET said:
try to start the phone now
Click to expand...
Click to collapse
When trying to start it now, it bootloops on this screen for a while.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I left it on there and went to do something else and when I came back it showed this.
ogruendel said:
When trying to start it now, it bootloops on this screen for a while.
View attachment 5936813
I left it on there and went to do something else and when I came back it showed this.
View attachment 5936815
Click to expand...
Click to collapse
Oh!!! Flash the stock rom now!
If it doesn't flash the stock rom, blank flash it.
You flashed the partition scheme, so it needs to be "UnHardBricked"
FilipeET said:
Oh!!! Flash the stock rom now!
If it doesn't flash the stock rom, blank flash it.
You flashed the partition scheme, so it needs to be "UnHardBricked"
Click to expand...
Click to collapse
Is there some central place for stock roms that I can trust or do I have to look for them on various different websites?
Edit: I think I was able to download the stock ROM directly from the Rescue Assistant. Also which commands do I need to run in order to flash the stock rom?

Categories

Resources