[Solved] Soft brick reparieren

[Mordor]

Hey Leute

Ich muss jetzt doch mal fragen.

Auf meinem p20p war android 8.1 auf das ich Android 9 installiert hatte.
Dann wollte data encryption ausschalten und rooten.

Nun habe ich aber folgende Situation:
Ich habe zwar TWRP drauf aber kein OS. Ich kann auch kein OS installieren. Der HurUpdater läuft z.B. an sich durch. Zeigt aber 4 mal Command unkown...am Ende ist die "installation" nach 30 Sekunden beendet. Das kann nicht klappen.

Per HiSuite kann ich nichts wiederherstellen, weil mein Gerät nicht unterstützt wird.

Im Erecovery kann ich ein Factor Reset machen aber lande logischer weise im twrp. Da geht ein Factory Reset.

Format Data geht auch.

Lineage os bekomme ich nicht drauf, weil kein Stock os drauf ist. Ein Stock os bekomme ich nicht installiert.

das hier
HELP: Bricked P20 Pro - "Getting package info failed"

habe ich gemacht:
UPDATE.zip entpackt und alle isos installiert:

finished. total time: 0.016s
PS C:\adb> fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [  0.734s]
writing 'recovery_ramdisk'...
OKAY [  0.156s]
finished. total time: 0.906s
PS C:\adb> fastboot reboot
rebooting...

finished. total time: 0.016s
PS C:\adb> fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 12.071s]
writing 'system'...
OKAY [  2.094s]
sending sparse 'system' (449804 KB)...
OKAY [ 11.813s]
writing 'system'...
OKAY [  2.016s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.495s]
writing 'system'...
OKAY [  1.791s]
sending sparse 'system' (460796 KB)...
OKAY [ 18.297s]
writing 'system'...
OKAY [  1.908s]
sending sparse 'system' (460796 KB)...
OKAY [ 15.948s]
writing 'system'...
OKAY [  2.049s]
sending sparse 'system' (460796 KB)...
OKAY [ 21.016s]
writing 'system'...
OKAY [  1.997s]
sending sparse 'system' (460796 KB)...
OKAY [ 18.184s]
writing 'system'...
OKAY [  2.060s]
sending sparse 'system' (460796 KB)...
OKAY [ 16.232s]
writing 'system'...
OKAY [  1.848s]
sending sparse 'system' (313552 KB)...
OKAY [ 11.292s]
writing 'system'...
OKAY [  1.420s]
finished. total time: 154.806s
PS C:\adb> fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [  0.720s]
writing 'recovery_ramdisk'...
OKAY [  0.172s]
finished. total time: 0.892s
PS C:\adb> fastboot reboot
rebooting...

finished. total time: 0.000s
PS C:\adb> fastboot erase -w
usage: fastboot [ <option> ] <command>

commands:
  update <filename>                        reflash device from update.zip
  flashall                                 flash boot, system, vendor and if found,
                                           recovery
  flash <partition> [ <filename> ]         write a file to a flash partition
  flashing lock                            locks the device. Prevents flashing                                           partitions
  flashing unlock                          unlocks the device. Allows user to                                           flash any partition except the ones                                           that are related to bootloader
  flashing lock_critical                   Prevents flashing bootloader related                                           partitions
  flashing unlock_critical                 Enables flashing bootloader related                                           partitions
  flashing get_unlock_ability              Queries bootloader to see if the                                           device is unlocked
  erase <partition>                        erase a flash partition
  format[:[<fs type>][:[<size>]] <partition> format a flash partition.
                                           Can override the fs type and/or
                                           size the bootloader reports.
  getvar <variable>                        display a bootloader variable
  boot <kernel> [ <ramdisk> ]              download and boot kernel
  flash:raw boot <kernel> [ <ramdisk> ]    create bootimage and flash it
  devices                                  list all connected devices
  continue                                 continue with autoboot
  reboot [bootloader]                      reboot device, optionally into bootloader
  reboot-bootloader                        reboot device into bootloader
  help                                     show this help message

options:
  -w                                       erase userdata and cache (and format
                                           if supported by partition type)
  -u                                       do not first erase partition before
                                           formatting
  -s <specific device>                     specify device serial number
                                           or path to device port
  -l                                       with "devices", lists device paths
  -p <product>                             specify product name
  -c <cmdline>                             override kernel commandline
  -i <vendor id>                           specify a custom USB vendor id
  -b <base_addr>                           specify a custom kernel base address.
                                           default: 0x10000000
  -n <page size>                           specify the nand page size.
                                           default: 2048
  -S <size>[K|M|G]                         automatically sparse files greater
                                           than size.  0 to disable
PS C:\adb> fastboot erase -w
usage: fastboot [ <option> ] <command>

commands:
  update <filename>                        reflash device from update.zip
  flashall                                 flash boot, system, vendor and if found,
                                           recovery
  flash <partition> [ <filename> ]         write a file to a flash partition
  flashing lock                            locks the device. Prevents flashing                                           partitions
  flashing unlock                          unlocks the device. Allows user to                                           flash any partition except the ones                                           that are related to bootloader
  flashing lock_critical                   Prevents flashing bootloader related                                           partitions
  flashing unlock_critical                 Enables flashing bootloader related                                           partitions
  flashing get_unlock_ability              Queries bootloader to see if the                                           device is unlocked
  erase <partition>                        erase a flash partition
  format[:[<fs type>][:[<size>]] <partition> format a flash partition.
                                           Can override the fs type and/or
                                           size the bootloader reports.
  getvar <variable>                        display a bootloader variable
  boot <kernel> [ <ramdisk> ]              download and boot kernel
  flash:raw boot <kernel> [ <ramdisk> ]    create bootimage and flash it
  devices                                  list all connected devices
  continue                                 continue with autoboot
  reboot [bootloader]                      reboot device, optionally into bootloader
  reboot-bootloader                        reboot device into bootloader
  help                                     show this help message

options:
  -w                                       erase userdata and cache (and format
                                           if supported by partition type)
  -u                                       do not first erase partition before
                                           formatting
  -s <specific device>                     specify device serial number
                                           or path to device port
  -l                                       with "devices", lists device paths
  -p <product>                             specify product name
  -c <cmdline>                             override kernel commandline
  -i <vendor id>                           specify a custom USB vendor id
  -b <base_addr>                           specify a custom kernel base address.
                                           default: 0x10000000
  -n <page size>                           specify the nand page size.
                                           default: 2048
  -S <size>[K|M|G]                         automatically sparse files greater
                                           than size.  0 to disable
PS C:\adb> fastboot erase -W
C:\adb\fastboot.exe: unknown option -- W
PS C:\adb> fastboot erase -w
usage: fastboot [ <option> ] <command>

commands:
  update <filename>                        reflash device from update.zip
  flashall                                 flash boot, system, vendor and if found,
                                           recovery
  flash <partition> [ <filename> ]         write a file to a flash partition
  flashing lock                            locks the device. Prevents flashing                                           partitions
  flashing unlock                          unlocks the device. Allows user to                                           flash any partition except the ones                                           that are related to bootloader
  flashing lock_critical                   Prevents flashing bootloader related                                           partitions
  flashing unlock_critical                 Enables flashing bootloader related                                           partitions
  flashing get_unlock_ability              Queries bootloader to see if the                                           device is unlocked
  erase <partition>                        erase a flash partition
  format[:[<fs type>][:[<size>]] <partition> format a flash partition.
                                           Can override the fs type and/or
                                           size the bootloader reports.
  getvar <variable>                        display a bootloader variable
  boot <kernel> [ <ramdisk> ]              download and boot kernel
  flash:raw boot <kernel> [ <ramdisk> ]    create bootimage and flash it
  devices                                  list all connected devices
  continue                                 continue with autoboot
  reboot [bootloader]                      reboot device, optionally into bootloader
  reboot-bootloader                        reboot device into bootloader
  help                                     show this help message

options:
  -w                                       erase userdata and cache (and format
                                           if supported by partition type)
  -u                                       do not first erase partition before
                                           formatting
  -s <specific device>                     specify device serial number
                                           or path to device port
  -l                                       with "devices", lists device paths
  -p <product>                             specify product name
  -c <cmdline>                             override kernel commandline
  -i <vendor id>                           specify a custom USB vendor id
  -b <base_addr>                           specify a custom kernel base address.
                                           default: 0x10000000
  -n <page size>                           specify the nand page size.
                                           default: 2048
  -S <size>[K|M|G]                         automatically sparse files greater
                                           than size.  0 to disable
PS C:\adb> fastboot flash recovery_ramdisk twrp-3.2.1-0-charlotte-mod-emui-nine.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24954 KB)...
OKAY [  0.546s]
writing 'recovery_ramdisk'...
OKAY [  0.187s]
finished. total time: 0.764s
PS C:\adb> fastboot reboot
rebooting...

finished. total time: 0.031s
PS C:\adb> fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [  0.797s]
writing 'recovery_ramdisk'...
OKAY [  0.156s]
finished. total time: 0.953s
PS C:\adb> fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 12.218s]
writing 'system'...
OKAY [  2.187s]
sending sparse 'system' (449804 KB)...
OKAY [ 12.098s]
writing 'system'...
OKAY [  2.031s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.747s]
writing 'system'...
OKAY [  1.781s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.557s]
writing 'system'...
OKAY [  1.953s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.141s]
writing 'system'...
OKAY [  2.094s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.491s]
writing 'system'...
OKAY [  2.031s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.500s]
writing 'system'...
OKAY [  2.094s]
sending sparse 'system' (460796 KB)...
OKAY [ 12.316s]
writing 'system'...
OKAY [  1.859s]
sending sparse 'system' (313552 KB)...
OKAY [  8.172s]
writing 'system'...
OKAY [  1.437s]
finished. total time: 124.771s
PS C:\adb> fastboot flash system CRC.img
target reported max download size of 471859200 bytes
sending 'system' (353 KB)...
OKAY [  0.016s]
writing 'system'...
OKAY [  0.016s]
finished. total time: 0.031s
PS C:\adb> fastboot flash system CURVER.img
target reported max download size of 471859200 bytes
sending 'system' (0 KB)...
OKAY [ -0.000s]
writing 'system'...
OKAY [  0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot flash system DTO.img
target reported max download size of 471859200 bytes
sending 'system' (3315 KB)...
OKAY [  0.078s]
writing 'system'...
OKAY [  0.062s]
finished. total time: 0.141s
PS C:\adb> fastboot flash system DTS.img
target reported max download size of 471859200 bytes
sending 'system' (20958 KB)...
OKAY [  0.469s]
writing 'system'...
OKAY [  0.125s]
finished. total time: 0.594s
PS C:\adb> fastboot flash system FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'system' (3351 KB)...
OKAY [  0.078s]
writing 'system'...
OKAY [  0.062s]
finished. total time: 0.141s
PS C:\adb> fastboot flash system FW_HIFI.img
target reported max download size of 471859200 bytes
sending 'system' (5876 KB)...
OKAY [  0.141s]
writing 'system'...
OKAY [  0.062s]
finished. total time: 0.203s
PS C:\adb> fastboot flash system FW_LPM3.img
target reported max download size of 471859200 bytes
sending 'system' (220 KB)...
OKAY [ -0.000s]
writing 'system'...
OKAY [  0.047s]
finished. total time: 0.047s
PS C:\adb> fastboot flash system HHEE.img
target reported max download size of 471859200 bytes
sending 'system' (68 KB)...
OKAY [  0.016s]
writing 'system'...
OKAY [  0.031s]
finished. total time: 0.062s
PS C:\adb> fastboot flash system HISIUFS_GPT.img
target reported max download size of 471859200 bytes
sending 'system' (196 KB)...
OKAY [  0.016s]
writing 'system'...
OKAY [  0.016s]
finished. total time: 0.031s
PS C:\adb> fastboot flash system KERNEL.img
target reported max download size of 471859200 bytes
sending 'system' (24576 KB)...
OKAY [  0.531s]
writing 'system'...
OKAY [  0.297s]
finished. total time: 0.844s
PS C:\adb> fastboot flash system PACKAGE_TYPE.img
target reported max download size of 471859200 bytes
sending 'system' (0 KB)...
OKAY [ -0.000s]
writing 'system'...
OKAY [  0.031s]
finished. total time: 0.062s
PS C:\adb> fastboot flash system SENSORHUB.img
target reported max download size of 471859200 bytes
sending 'system' (2471 KB)...
OKAY [  0.062s]
writing 'system'...
OKAY [  0.047s]
finished. total time: 0.109s
PS C:\adb> fastboot flash system SHA256RSA.img
target reported max download size of 471859200 bytes
sending 'system' (0 KB)...
OKAY [  0.000s]
writing 'system'...
OKAY [  0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot flash system TEEOS.img
target reported max download size of 471859200 bytes
sending 'system' (3124 KB)...
OKAY [  0.078s]
writing 'system'...
OKAY [  0.047s]
finished. total time: 0.125s
PS C:\adb> fastboot flash system TRUSTFIRMWARE.img
target reported max download size of 471859200 bytes
sending 'system' (175 KB)...
OKAY [  0.016s]
writing 'system'...
OKAY [  0.047s]
finished. total time: 0.062s
PS C:\adb> fastboot flash system VECTOR.img
target reported max download size of 471859200 bytes
sending 'system' (1190 KB)...
OKAY [  0.031s]
writing 'system'...
OKAY [  0.047s]
finished. total time: 0.078s
PS C:\adb> fastboot flash system VERLIST.img
target reported max download size of 471859200 bytes
sending 'system' (0 KB)...
OKAY [  0.000s]
writing 'system'...
OKAY [  0.016s]
finished. total time: 0.031s
PS C:\adb> fastboot flash system XLOADER.img
target reported max download size of 471859200 bytes
sending 'system' (172 KB)...
OKAY [  0.016s]
writing 'system'...
OKAY [  0.047s]
finished. total time: 0.062s
PS C:\adb> fastboot flash system MODEMNVM_CUST.img
target reported max download size of 471859200 bytes
sending 'system' (1373 KB)...
OKAY [  0.031s]
writing 'system'...
OKAY [  0.000s]
finished. total time: 0.047s
PS C:\adb> fastboot flash system MODEMNVM_UPDATE.img
target reported max download size of 471859200 bytes
sending 'system' (7892 KB)...
OKAY [  0.268s]
writing 'system'...
OKAY [  0.067s]
finished. total time: 0.356s
PS C:\adb> fastboot flash system RECOVERY_RAMDIS.img
target reported max download size of 471859200 bytes
sending 'system' (32768 KB)...
OKAY [  0.730s]
writing 'system'...
OKAY [  0.169s]
finished. total time: 0.903s
PS C:\adb> fastboot flash system VBMETA.img
target reported max download size of 471859200 bytes
sending 'system' (12 KB)...
OKAY [  0.009s]
writing 'system'...
OKAY [  0.048s]
finished. total time: 0.070s
PS C:\adb> fastboot flash system CACHE.img
target reported max download size of 471859200 bytes
sending 'system' (76 KB)...
OKAY [  0.022s]
writing 'system'...
OKAY [  0.224s]
finished. total time: 0.285s
PS C:\adb> fastboot flash system ENG_SYSTEM.img
target reported max download size of 471859200 bytes
sending 'system' (12288 KB)...
OKAY [  0.281s]
writing 'system'...
OKAY [  0.056s]
finished. total time: 0.352s
PS C:\adb> fastboot flash system ENG_VENDOR.img
target reported max download size of 471859200 bytes
sending 'system' (12288 KB)...
OKAY [  0.318s]
writing 'system'...
OKAY [  0.105s]
finished. total time: 0.552s
PS C:\adb> fastboot flash system HDCP.img
target reported max download size of 471859200 bytes
sending 'system' (216 KB)...
OKAY [  0.011s]
writing 'system'...
OKAY [  0.043s]
finished. total time: 0.063s
PS C:\adb> fastboot flash system RECOVERY_VBMETA.img
target reported max download size of 471859200 bytes
sending 'system' (6 KB)...
OKAY [  0.006s]
writing 'system'...
OKAY [  0.055s]
finished. total time: 0.069s
PS C:\adb> fastboot flash system RECOVERY_VENDOR.img
target reported max download size of 471859200 bytes
sending 'system' (16384 KB)...
OKAY [  0.474s]
writing 'system'...
OKAY [  0.142s]
finished. total time: 0.635s
PS C:\adb> fastboot flash system CUST.img
target reported max download size of 471859200 bytes
sending 'system' (176429 KB)...
OKAY [  4.303s]
writing 'system'...
OKAY [  4.006s]
finished. total time: 8.316s
PS C:\adb> fastboot flash system ISP_FIRMWARE.img
target reported max download size of 471859200 bytes
sending 'system' (9789 KB)...
OKAY [  0.233s]
writing 'system'...
OKAY [  0.105s]
finished. total time: 0.377s
PS C:\adb> fastboot flash system MODEM_FW.img
target reported max download size of 471859200 bytes
sending 'system' (57344 KB)...
OKAY [  1.507s]
writing 'system'...
OKAY [  0.304s]
finished. total time: 1.859s
PS C:\adb> fastboot flash system HISEE_FS.img
target reported max download size of 471859200 bytes
sending 'system' (56 KB)...
OKAY [  0.010s]
writing 'system'...
OKAY [  0.066s]
finished. total time: 0.081s
PS C:\adb> fastboot flash system HISEE_IMG.img
target reported max download size of 471859200 bytes
sending 'system' (572 KB)...
OKAY [  0.021s]
writing 'system'...
OKAY [  0.019s]
finished. total time: 0.048s
PS C:\adb> fastboot flash system VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 13.634s]
writing 'system'...
OKAY [  2.072s]
sending sparse 'system' (367348 KB)...
OKAY [ 10.426s]
writing 'system'...
OKAY [  1.714s]
finished. total time: 27.866s
PS C:\adb> fastboot flash system ODM.img
target reported max download size of 471859200 bytes
sending 'system' (117912 KB)...
OKAY [  2.807s]
writing 'system'...
OKAY [  0.663s]
finished. total time: 3.490s
PS C:\adb> fastboot flash system PRODUCT.img
target reported max download size of 471859200 bytes
sending 'system' (388291 KB)...
OKAY [  8.835s]
writing 'system'...
OKAY [  2.967s]
finished. total time: 11.809s
PS C:\adb> fastboot flash system ERECOVERY_KERNE.img
target reported max download size of 471859200 bytes
sending 'system' (24576 KB)...
OKAY [  0.767s]
writing 'system'...
OKAY [  0.158s]
finished. total time: 0.934s
PS C:\adb> fastboot flash system ERECOVERY_RAMDI.img
target reported max download size of 471859200 bytes
sending 'system' (32768 KB)...
OKAY [  0.875s]
writing 'system'...
OKAY [  0.179s]
finished. total time: 1.088s
PS C:\adb> fastboot flash system ERECOVERY_VENDO.img
target reported max download size of 471859200 bytes
sending 'system' (16384 KB)...
OKAY [  0.398s]
writing 'system'...
OKAY [  0.160s]
finished. total time: 0.621s
PS C:\adb> fastboot flash system ERECOVERY_VBMET.img
target reported max download size of 471859200 bytes
sending 'system' (6 KB)...
OKAY [  0.016s]
writing 'system'...
OKAY [  0.048s]
finished. total time: 0.070s
PS C:\adb> fastboot erase -w
usage: fastboot [ <option> ] <command>

commands:
  update <filename>                        reflash device from update.zip
  flashall                                 flash boot, system, vendor and if found,
                                           recovery
  flash <partition> [ <filename> ]         write a file to a flash partition
  flashing lock                            locks the device. Prevents flashing                                           partitions
  flashing unlock                          unlocks the device. Allows user to                                           flash any partition except the ones                                           that are related to bootloader
  flashing lock_critical                   Prevents flashing bootloader related                                           partitions
  flashing unlock_critical                 Enables flashing bootloader related                                           partitions
  flashing get_unlock_ability              Queries bootloader to see if the                                           device is unlocked
  erase <partition>                        erase a flash partition
  format[:[<fs type>][:[<size>]] <partition> format a flash partition.
                                           Can override the fs type and/or
                                           size the bootloader reports.
  getvar <variable>                        display a bootloader variable
  boot <kernel> [ <ramdisk> ]              download and boot kernel
  flash:raw boot <kernel> [ <ramdisk> ]    create bootimage and flash it
  devices                                  list all connected devices
  continue                                 continue with autoboot
  reboot [bootloader]                      reboot device, optionally into bootloader
  reboot-bootloader                        reboot device into bootloader
  help                                     show this help message

options:
  -w                                       erase userdata and cache (and format
                                           if supported by partition type)
  -u                                       do not first erase partition before
                                           formatting
  -s <specific device>                     specify device serial number
                                           or path to device port
  -l                                       with "devices", lists device paths
  -p <product>                             specify product name
  -c <cmdline>                             override kernel commandline
  -i <vendor id>                           specify a custom USB vendor id
  -b <base_addr>                           specify a custom kernel base address.
                                           default: 0x10000000
  -n <page size>                           specify the nand page size.
                                           default: 2048
  -S <size>[K|M|G]                         automatically sparse files greater
                                           than size.  0 to disable
PS C:\adb> fastboot reboot
rebooting...

finished. total time: 0.030s
PS C:\adb>

nun habe ich aber nur bootloop- Erecovery sagt immer wieder getting package information failed

Jemand eine Idee?

 

[d3rb]

Moin moin, ich bin mal so frei und helfe dir hatte das selbe Problem nur leider hat sich hier keiner dazu gemeldet weswegen, ich meine Post wieder gelöscht habe .

Ich hatte es nach der Anleitung von ubr first ever gemacht Anleitung auf seiner Seite ganz unten.
Soweit ich mich erinnere, hatte ich das selbe Problem wie du, hab aber alles neu geflasht bzw was in welche Partition gehört Kernel etc.. Binmmir nicht ganz sicher ob es dann gelöst war.evtl.habe ich dann im twrp die offizielle pie trotz Fehler geflasht, danach hat er sauber durch gebootet Ansonsten pm an mich.



MfG

 

[Mordor]

Super, vielen Dank. War wohl gestern zu spät. War schon 3 mal auf seiner Seite aber das hatte ich völlig übersehen.

(Optional) Step 10 - How to fix a "Bricked" phone
Some CLT-L29 users raported that this ROM can soft “brick” your phone.
If your phone is stuck in EMUI eRecovery, this is how you can fix it,
(Source: XDA by smohanv)

Getting the device ready

1. Download EMUI 9.0 from: here
2. Unzip the file UPDATE.APP from Update.zip
3. Using EMUI extraction tool extract following image files from UPDATE.APP. Download tool from: here
4. Extract, CUST.img, KERNEL.img, RECOVERY_RAMDIS.img and System.imgand copy these files in the same folder where you have ADB tools Download ADB tools from: here. Unzip files. You will find a file cmd-here.exe. Run this file to get to open command prompt in your PC to the same folder where you have this ADB tools extracted.
5. Put your phone in to Fastboot mode (Switch off your phone, Press and hold volumn down button and connect USB with PC)
6. Flash the image files in the same order with fastboot commands as below:
   fastboot flash cust cust.img
   fastboot flash kernel kernel.img
   fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
   fastboot flash system system.img
   
   
7. Now flash custom recovery. Download custom recovery from: here
   fastboot flash recovery_ramdisk twrp-3.2.1-0-charlotte-mod.img
   
   
8. Now restart your device with command below:
   fastboot reboot
   
   As soon issued this command, pull out of USB cable and keep holding volume up button until Huawei logo comes up disappear. It will now boot in to TWRP recovery.

Check file names in TWRP (Advanced > File Manager) are readable under folder sdcard. If file names are appearing as a junk, it means that you need to decrypt your data partition. Follow the steps below:

Wipe > Format data
Hit home button and Reboot > Recovery
Download and copy RemoveEncryption-P20Pro.zip file in to sdcard folder (Internal storage). This file can be downloaded from here.
Flash RemoveEncryption-P20Pro.zip
Hit home button and Reboot > Recovery
Wipe > Format data
Hit home button and Reboot > Recovery

NOW YOU ARE READY TO FLASH OFFICIAL EMUI 8.1 OR 9.0 (as you like). You have no root exploit available for 9.0 at the moment and also Google Pay will see the device as rooted because of unlocked bootloader.

Follow the steps below:

1. Download the EMUI version that you need from the link.
2. Create a folder ZIPS-HERE in the same folder where you have ADB tools (as explained in the section above) and put both update.zip and update_all_hw.zip in this ZIP-HERE folder.
3. Download update_data_public.zip from this link and copy to the same ZIPS-HERE folder: link
4. Download this nocheck.img file and copy it in to the same folder ZIPS-HERE: link
5. Issue following commands (you can copy and paste in the command window)
   adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
   adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
   adb shell “echo –update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command”
   adb push ZIPS-HERE/nocheck.img /data/update/nocheck.img
   adb shell “echo –update_package=/data/update/HWOTA/update.zip > /cache/recovery/command”
   adb shell “echo –update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command”
   adb shell “echo –update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command”
   adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
   adb reboot recovery

Quelle: First Ever Android 9.0 for Huawei P20 Pro | First Ever

Poste das nur hier, weil man ja nie eiß wie lange solche Seiten bleiben.

Bin aber noch am Ausführen, poste dann das Ergebnis.

Ergebnis:
Device is booting now, da hängt er.

Muss ich jetzt ein factory reset machen? Oder erecovery?

Denn erecovery geht nicht. Nach wie vor der gleiche Fehler:
Getting package info failed

Factory Reset im Recovery geht auch nicht.

Nachtrag 2:
Es geht !
Original Post:
[How to..] How to Unbrick CLT-L29C432... Here is the situation and solution.....

 

[d3rb]

Super das how to im Nachtrag 2 ist glaub das selbe was first ever auf seiner Seite hat.

Dann ist ja jetzt aufatmen angesagt.

MfG d3rb

 

[BTK12]

ICh habe jetzt alles probiert ich komme werder in twrp noch in erecovery rein..

Kann mir jemand helfen

 

[d3rb]

Ohne ein paar Infos, kann man dir sicherlich nicht helfen.

 

[BTK12]

Ja. Ich habe es hinbekommen das alles wieder geht.

 

[Humbug26]

Hallo,

ich wollt heute das Update auf 9.0 machen und hatte ein Problem, dasss es nach der Installation vom JamesDSP (Magisk-Mod) nur noch bis zum HUAWEI-Logo bootete. Nach einem eRecovery-Reset war dann schon Schluss beim "Your device has been..."-Screen. Da ging nichts mehr, auch nicht mehr die eRecovery. Hab dann wie in der Anleitungbeschrieben die Dateien extrahiert und per fastboot installiert -> OK. Beim Punkt in der das Teil aber in die TWRP booten soll, bleibts nun beim TWRP-Screen einfach hängen und macht nichts mehr.
Ich sitz schon den halben Tag dran und mittlerweile seh ich vor lauter Bäume den Wald nicht mehr

Hat jemand netterweise eine Idee, was ich noch machen kann?

Edit:
Ok habs soweit hinbekommen, frag mich aber nur worans liegt. Kam die letzten paar Stunen nicht mal ni die eRec., und plötzlich war ich drinnen und hab alles nichmal formatiert. Oh mann...

 

[Mordor]

Welches twrp hattest du genommen ?

 

[Humbug26]

Hatte immer das aus dem Thread genommen, das direkt mitgeflasht wird. Da das aber komischerweise plötzlich nihct mehr tat, hab ichs mit der charlotte-3.2.1.0-mod versucht, hier kam ich dann wie erwähnt maximal zum TWRP-Logo, wo dann nix mehr ging. HAb dann nochmla die ganzen Schritte gemacht bez. flash CUST.IMG .... SYSTEM.IMG...inklusive der RECOVERY_RAMDI.IMG aus der entpackten UPDATE.APP. Hab dann noch zwischen den beiden hin und her gewechsekt und nach jedem flashen eben versucht in die eRec zu kommen. Nach ein paar minuten hab ichs aber dann immer gelassen (also paar Minuten Vol+ drücken). Und grade vorhin mach ich das wdr und plötzlich komm ich in die eRec, wo was von Low-Level format stand...nachdem ich das gemacht hatte warf er mich beim nächsten Boot wieder in die eRec wo ich dann nen "normalen" Factory-Reset machen konnte. Gesagt getan, dazu noch den Cache (sicher ist sicher) und voila...nun ist es wdr komplett einsatzbereit...derzeit noch ihne Root aber den werd ich alleine wegen adaway schon nochmal installieren. Nur den JamesDSP-Mod werd ich wohl weglassen müssen


Edit:
Bin nun doch wdr auf die 8.1er zurückgegangen, mir ist ein besserer Sound beim Musik hören doch wichtiger. Ausserdem hab ich hier weniger Angst, dass bei einem Reboot eventuell wieder was zickt.
Bin nach der Anleitung vorgegangen, die im selben Thread beschrieben wird und ich hatte null Probleme damit. Lediglich in TWRP hatte ich, trotz ausgeschaltenem Passwort etc., verschlüsselte Ordner, habe deswegen diese Datei hier genommen:

[Recovery][P20/Pro][Unofficial]TWRP 3.2.1-0 [18/04/2018]

Danach alles wie gewohnt wieder raufgespielt, mit TB einen Restore gemacht und tada, alles fertig und auch JamesDSP wurde ohne mucks installiert.