• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

GUIDE: eRecovery / HiSuite failing to restore - RESCUE on PIE: L29 L09 432 -- v190

Search This thread

chrissyyyw

Senior Member
Jan 15, 2017
128
5
No because you're going to be picking them via fastboot anyway, I don't believe the name matters.

The ones in the update I used were not named like that IIRC.

Trust tried again, everything flashed fine apart from VENDOR.img

c:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 16.711s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 16.719s

Any ideas?
 

dladz

Senior Member
Aug 24, 2010
13,114
4,165
Liverpool
Huawei Watch 2
OnePlus 8
Trust tried again, everything flashed fine apart from VENDOR.img

c:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 16.711s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 16.719s

Any ideas?

I don't pal , work I could help. Perhaps another firmware?
 

Johnny Eng

Senior Member
Apr 25, 2012
70
6
Which FW version did you flash? I’ve got the same on .282


I extracted. 280
Everything work fine without userdata.img
Now I'm on. 295

---------- Post added at 06:38 AM ---------- Previous post was at 06:38 AM ----------

As i'm still on 190 I wouldn't know this, but would it be possible that userdata isn't actually a part of the update app no more?

Seeing as it still works I would assume that is the case.


Everything work fine without userdata.img.
Thanks
 
  • Like
Reactions: dladz

DoricSan

Member
Jun 27, 2019
6
3
You saved my phone.
I wish I could give you a warm hug and a nice beer.
Thank you.
Thank you mate. :crying:
 
  • Like
Reactions: dladz

Xsjados

Member
Sep 28, 2017
23
6
I would just like to join the others in saying how much you've saved me from the painful FunkyHuawei credits and other paid hinderances, this is a f*ckin' godsend, cheers bud!

I also had the VENDOR not being able to flash but the phone (L29-C432)
For some reason, the files you gave me happens to flash my phone to .108 everytime and then I use re-flash9.0 to get myself upto .195 but I'm unable to update anyfurther or receive OTA updates...I think I may have to go down the OTG route.

Thanks again buddy.
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
13,114
4,165
Liverpool
Huawei Watch 2
OnePlus 8
I would just like to join the others in saying how much you've saved me from the painful FunkyHuawei credits and other paid hinderances, this is a f*ckin' godsend, cheers bud!

I also had the VENDOR not being able to flash but the phone (L29-C432)
For some reason, the files you gave me happens to flash my phone to .108 everytime and then I use re-flash9.0 to get myself upto .195 but I'm unable to update anyfurther or receive OTA updates...I think I may have to go down the OTG route.

Thanks again buddy.

Very welcome pal, glad to help.

Be careful as I relocked my bootloader that way
 

Zarapho

Member
Oct 4, 2018
11
0
WARNING

By doing this you may lose your data, this is intended for when you have nowhere else to turn to.

Back Story

Hi All,
Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
After the installation, I tried to install a bunch of ROM's, I messed up a bit.

Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.

So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.

Ton of files in there, the files i just mentioned which are all .img files and some others.
In the end i needed several to get a perfect restore which has worked every single time without fail.

As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way :D Yaay, also what to do and where to obtain the firmwares from my experiences.

Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.

Good luck, any questions let me know. :good:


START HERE

*NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
They require an account to be made but besides that they were faster and had more choice.


Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...

Anyway, moving on........ :D

FILES

At the foot of this guide is a link, inside it is everything you should require in order to complete this guide

ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)

IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
Move all of them after downloading to the ADB folder in C:\ADB

CACHE.img
CUST.img
ERECOVERY_RAMDI.img
KERNEL.img
RECOVERY_RAMDIS.img
USERDATA.img
VENDOR.img
SYSTEM.img

EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.

Pre-requisites

- A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
- A device variant of either L-09 or L-29 (others may work but i have not tested)
- A device variant of c432 (the 782 may work but i have not tested)
- Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
- Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
- I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
- A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can


GUIDE

On your computer / laptop

STEP 1 Download all the files from the mega link provided.

STEP 2 Copy the ADB Folder to the root of C: so it looks like this

C:\ADB

STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.

STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear

STEP 5 In the black window type the following:

cd c:\adb then press Enter

STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows

On your Phone

STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.

On your computer / laptop

Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img

*NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
You could then press the tab key and scroll through the files in the folder.
eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img


PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.

fastboot flash cust CUST.img
fastboot flash cache CACHE.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash userdata USERDATA.img
fastboot flash kernel KERNEL.img
fastboot flash vendor VENDOR.img
fastboot flash system SYSTEM.img


STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.

fastboot reboot

If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190


You can then root and use your device as you see fit.

Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN :) )

https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg

Any questions, please ask away and i'll do what i can to help ;)

Thanks for this, but if I try flash Vendro.img it says

c:\adb>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460796 KB)...
OKAY [ 19.387s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 19.397s


Any help?
 

dladz

Senior Member
Aug 24, 2010
13,114
4,165
Liverpool
Huawei Watch 2
OnePlus 8
Thanks for this, but if I try flash Vendro.img it says

c:\adb>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460796 KB)...
OKAY [ 19.387s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 19.397s

Any help?

I never had that, can you flash a more up to date vendor?

Or does it boot without it?
 

Zarapho

Member
Oct 4, 2018
11
0
I never had that, can you flash a more up to date vendor?

Or does it boot without it?

I did them with the IMG File in this ZIP.
My phone blacked out while OTA Update to 9.0 .. but I cann fastboot device
(WRN123456789) fastboot

but still somehow not overwrite Vendor.

By Up to date you lean the newest IMG / Firmware of EMUI? I have a C432 B152

---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------

@Zarapho

Your phone is OEM Unlocked?

OEM and Bootloader Unlocked :)
 

Priste459

New member
Apr 8, 2020
1
0
I never had that, can you flash a more up to date vendor?

Or does it boot without it?


Hi @dladz, I followed all the steps of your guide. Until the kernel flash everything is ok. When I enter
fastboot flash vendor VENDOR.img
I get the error "FAILED (remote: Command not allowed) ".
I can no longer continue and therefore recover the phone. Please help me. I have been working on it for 8 hours.
can be solve this problem with an updated version of the firmware ?
Thank you earlier
 

dladz

Senior Member
Aug 24, 2010
13,114
4,165
Liverpool
Huawei Watch 2
OnePlus 8
Hi @dladz, I followed all the steps of your guide. Until the kernel flash everything is ok. When I enter
fastboot flash vendor VENDOR.img
I get the error "FAILED (remote: Command not allowed) ".
I can no longer continue and therefore recover the phone. Please help me. I have been working on it for 8 hours.
can be solve this problem with an updated version of the firmware ?
Thank you earlier

Potentially a newer one for the same model yes, but don't downgrade

You could install hisuite too. Apparently it can also be driver related or so I've read

Have you met all the pre requisites??

OEM unlocked is on?

Is your bootloader locked?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    WARNING

    By doing this you may lose your data, this is intended for when you have nowhere else to turn to.

    Back Story

    Hi All,
    Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
    After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
    After the installation, I tried to install a bunch of ROM's, I messed up a bit.

    Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.

    So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.

    Ton of files in there, the files i just mentioned which are all .img files and some others.
    In the end i needed several to get a perfect restore which has worked every single time without fail.

    As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way :D Yaay, also what to do and where to obtain the firmwares from my experiences.

    Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.

    Good luck, any questions let me know. :good:


    START HERE

    *NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
    The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
    They require an account to be made but besides that they were faster and had more choice.


    Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...

    Anyway, moving on........ :D

    FILES

    At the foot of this guide is a link, inside it is everything you should require in order to complete this guide

    ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)

    IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
    Move all of them after downloading to the ADB folder in C:\ADB

    CACHE.img
    CUST.img
    ERECOVERY_RAMDI.img
    KERNEL.img
    RECOVERY_RAMDIS.img
    USERDATA.img
    VENDOR.img
    SYSTEM.img

    EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.

    Pre-requisites

    - A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
    - A device variant of either L-09 or L-29 (others may work but i have not tested)
    - A device variant of c432 (the 782 may work but i have not tested)
    - Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
    - Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
    - I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
    - A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can


    GUIDE

    On your computer / laptop

    STEP 1 Download all the files from the mega link provided.

    STEP 2 Copy the ADB Folder to the root of C: so it looks like this

    C:\ADB

    STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.

    STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear

    STEP 5 In the black window type the following:

    cd c:\adb then press Enter

    STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows

    On your Phone

    STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.

    On your computer / laptop

    Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img

    *NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
    You could then press the tab key and scroll through the files in the folder.
    eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img


    PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.

    fastboot flash cust CUST.img
    fastboot flash cache CACHE.img
    fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
    fastboot flash userdata USERDATA.img
    fastboot flash kernel KERNEL.img
    fastboot flash vendor VENDOR.img
    fastboot flash system SYSTEM.img


    STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.

    fastboot reboot

    If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190


    You can then root and use your device as you see fit.

    Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN :) )

    NOTE: they actually now have, sorry

    https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg

    Any questions, please ask away and i'll do what i can to help ;)
    1
    @mdda7

    You must have an unlocked bootloader.
    1
    @dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
    1
    Haha no worries fella.

    Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.

    All I've got is a black screen and red flashing LED.
    1
    Thank you, life saver!!