Database Develop

Partition information / Unbricking

This is the place for various bits and pieces of information/facts/wtf collected whilst digging around in our TF701.
Use at your own peril.
UPDATE: I know the staging partition is where to blob (bootloader) goes, but as I found out, that's only half of the story.
It seems like the bootloader takes the contents of staging at boot time and puts them where they belong.
Now if anybody has more details about this, that would be great.
Partitions
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
recovery.fstab
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
Blob
Code:
name size description status
[U]10.14.1.47:[/U] [ATTACH]2435244._xfImport[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246._xfImport[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245._xfImport[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247._xfImport[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248._xfImport[/ATTACH]
[U]10.26.1.7:[/U] [ATTACH]2435238._xfImport[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241._xfImport[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240._xfImport[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242._xfImport[/ATTACH]
Unbrick
How to unbrick a TF701 that still has fastboot running (possibly partially redundant):
WARNING: Any damage caused by following these instructions...
Yeah, right... Nevermind that... If your fastboot works, this will save your tablet
Required tools: I assume you have them already
Required files:
UL-K00C-xx-10.14.1.47-user.zip (on micro SD card in TF701)
10.14.1.47 blob and boot.img (unpacked from UL-K00C-xx-10.14.1.47-user.zip)
drgravy's recovery.img
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
check the version displayed. Is it 10.14.1.47? if not, hard reset to bootloader ([vol-] + [power])
boot recovery kernel (RCK)
install zip
choose zip from sdcard
UL-K00C-xx-10.14.1.47-user.zip
Yes
wait and pray to odin
+++ go back +++
reboot system now
Yes - Disable recovery flash (doesn't actually matter)
Yes - Root device (/system/xbin/su) (just kidding, this doesn't work)
Please consider clicking thanks
Sources:
Lots of own work
http://forum.xda-developers.com/showpost.php?p=47767352&postcount=71
https://github.com/AndroidRoot/BlobTools

im trying to find pretty much the same info
mmcblk0p? for boot and external_sd
This helped alot thanks!
nevermind find both
LNX = boot
/dev/block/mmcblk1p1 is external_sd

schmeggy929 said:
im trying to find pretty much the same info
mmcblk0p? for boot and external_sd
This helped alot thanks!
nevermind find both
LNX = boot
/dev/block/mmcblk1p1 is external_sd
Click to expand...
Click to collapse
things that will appear here tomorrow:
by name symlinks
recovery fstab info
unpacked blob contents
more detailed bootloader related stuff
anything fun I'll find on the way
for the next 12 hours that's it...

lpdunwell said:
This is the place for various bits and pieces of information/facts/wtf collected whilst digging around in our TF701.
Use at your own peril.
UPDATE: I know the staging partition is where to blob (bootloader) goes, but as I found out, that's only half of the story.
It seems like the bootloader takes the contents of staging at boot time and puts them where they belong.
Now if anybody has more details about this, that would be great.
Partitions
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
recovery.fstab
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
Blob
Code:
name size description status
[U]10.14.1.47:[/U] [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
[U]10.26.1.7:[/U] [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
Unbrick
How to unbrick a TF701 that still has fastboot running (possibly partially redundant):
WARNING: Any damage caused by following these instructions...
Yeah, right... Nevermind that... If your fastboot works, this will save your tablet
Required tools: I assume you have them already
Required files:
UL-K00C-xx-10.14.1.47-user.zip (on micro SD card in TF701)
10.14.1.47 blob and boot.img (unpacked from UL-K00C-xx-10.14.1.47-user.zip)
drgravy's recovery.img
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
check the version displayed. Is it 10.14.1.47? if not, hard reset to bootloader ([vol-] + [power])
boot recovery kernel (RCK)
install zip
choose zip from sdcard
UL-K00C-xx-10.14.1.47-user.zip
Yes
wait and pray to odin
+++ go back +++
reboot system now
Yes - Disable recovery flash (doesn't actually matter)
Yes - Root device (/system/xbin/su) (just kidding, this doesn't work)
Please consider clicking thanks
Sources:
Lots of own work
http://forum.xda-developers.com/showpost.php?p=47767352&postcount=71
https://github.com/AndroidRoot/BlobTools
Click to expand...
Click to collapse
Sorry, how should I extract the recovery.img from the OTA zip file?
I can only find several files: install-recovery.sh recovery-from-boot.p recovery-resource. dat
Or if I can extract it anywhere else?

lpdunwell said:
Code:
[U]10.26.1.7:[/U] [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
Click to expand...
Click to collapse
@lpdunwell
Any ideas what BC1 is for? Also there is no SOS file inside the BLOB. I have repacked the BLOB as I wanted to make a bootloader and recovery flash package but not sure how to flash a recovery.
On the TF700 you could just pack it back into the BLOB using the below and it would flash to staging fine. Any ideas?
Code:
blobpack -s blob EBT blob.EBT SOS blob.SOS
I wonder if the same can be done like this?
Code:
blobpack -s blob BCT blob.BCT BC1 blob.BC1 EBT blob.EBT SOS blob.SOS

sbdags said:
@lpdunwell
Any ideas what BC1 is for? Also there is no SOS file inside the BLOB. I have repacked the BLOB as I wanted to make a bootloader and recovery flash package but not sure how to flash a recovery.
On the TF700 you could just pack it back into the BLOB using the below and it would flash to staging fine. Any ideas?
Code:
blobpack -s blob EBT blob.EBT SOS blob.SOS
I wonder if the same can be done like this?
Code:
blobpack -s blob BCT blob.BCT BC1 blob.BC1 EBT blob.EBT SOS blob.SOS
Click to expand...
Click to collapse
TBCH, I'm not sure about the BC1.
The recovery is not part of the blob (anymore?). And the exact way an official update flashes it is probably not the best way to go when flashing manually. My advice for the moment probably is: Keep flashing the bootloader to a minimum, and flash recoveries via fastboot.

lpdunwell said:
TBCH, I'm not sure about the BC1.
The recovery is not part of the blob (anymore?). And the exact way an official update flashes it is probably not the best way to go when flashing manually. My advice for the moment probably is: Keep flashing the bootloader to a minimum, and flash recoveries via fastboot.
Click to expand...
Click to collapse
Yeah I tried a number of ways to get it to flash but it looks like the nvcopy tool that Asus use doesn't work outside the stock recovery.

Search the UL-K00C-WW-10.14.1.47-user.zip file
Hi,
And thank you. But Do you know where I can download the UL-K00C-WW-10.14.1.47-user.zip ?
On ASUS and can find only WW_epaduser_10_14_1_47_UpdateLauncher.zip.
Oups UL-K00C-WW-10.14.1.47-user.zip is in WW_epaduser_10_14_1_47_UpdateLauncher.zip.

Question
Hi
A question : Is it possible to use the same procedure with UL-K00C-WW-10.26.1.7-user.zip or UL-K00C-WW-10.26.1.18-user.zip ?
Best regards

Bumping this as it should be stickied

Xstof said:
Hi,
And thank you. But Do you know where I can download the UL-K00C-WW-10.14.1.47-user.zip ?
On ASUS and can find only WW_epaduser_10_14_1_47_UpdateLauncher.zip.
Oups UL-K00C-WW-10.14.1.47-user.zip is in WW_epaduser_10_14_1_47_UpdateLauncher.zip.
Click to expand...
Click to collapse
Did you ever find out where to get this file? I've been looking everywhere and I fear my device is hosed without it. HELP!

SgtMac02 said:
Did you ever find out where to get this file? I've been looking everywhere and I fear my device is hosed without it. HELP!
Click to expand...
Click to collapse
Google "Asus support downloads", click on the first link....

lpdunwell said:
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ok, so I'm trying to get through this and having some trouble...
I've been having to go back and forth on a few things and I fear I've managed to hose thing up pretty good. But at this point, I have the files you state, and in following these instructions, was able to successfully erase the partitions mentioned, then when I tried to flash the first time, I actually screwed up and didn't have the blob file I needed, so now I go back, and obviously I can't re-erase the other files, but formatting system still works, so I know I'm getting good communication with the device. Then trying to flash the blob to staging, I get:
sending 'staging' (1379 KB)...
FAILED (command write failed (No such device or address))
Any thoughts or suggestions would be greatly appreciated.

Am I completely bricked?
I'm stuck in a boot loop with Asus / Unlocked appearing and unable to get to recovery. I've tried connecting with win 8.1 via usb but adb does not see devices. i assume running fastboot is the same situation. I can see the device listed APX and understand that Nvflash can help with that but there is no nvflash for Tegra 4.
I'm not sure how it got to this state - could be me or device. it is new and i considered returning save for the Device is Unlocked message
Ironically, this is my second Tf701t as the first cracked the screen. Considering taking motherboard out of old and putting in new (or visa vera) but I'm really bad with hardware.
Do I really have 2 broken devices I'll try anything.
Thanks for any (emotional) support ...

sonicthoughts said:
I'm stuck in a boot loop with Asus / Unlocked appearing and unable to get to recovery. I've tried connecting with win 8.1 via usb but adb does not see devices. i assume running fastboot is the same situation. I can see the device listed APX and understand that Nvflash can help with that but there is no nvflash for Tegra 4.
I'm not sure how it got to this state - could be me or device. it is new and i considered returning save for the Device is Unlocked message
Ironically, this is my second Tf701t as the first cracked the screen. Considering taking motherboard out of old and putting in new (or visa vera) but I'm really bad with hardware.
Do I really have 2 broken devices I'll try anything.
Thanks for any (emotional) support ...
Click to expand...
Click to collapse
This happened in my TF300T, yes is a hard brick.
Nvflash only works if you did work before.
Here is a guide to ifixit a TF700 perhaps help you. :good:

Would it not make more sense to swap the screens over?
Sent from my HTC Desire 610 using XDA Free mobile app

lpdunwell said:
This is the place for various bits and pieces of information/facts/wtf collected whilst digging around in our TF701.
Use at your own peril.
UPDATE: I know the staging partition is where to blob (bootloader) goes, but as I found out, that's only half of the story.
It seems like the bootloader takes the contents of staging at boot time and puts them where they belong.
Now if anybody has more details about this, that would be great.
Sources:
Lots of own work
http://forum.xda-developers.com/showpost.php?p=47767352&postcount=71
https://github.com/AndroidRoot/BlobTools
Click to expand...
Click to collapse
Thank you for your analysis! I wonder does the "staging" partition contain temporary updates, and the blob flashed to it will automatically decompress to the correct partitions in the next boot?
In other words, in order to update the bootloader and the recovery system, I could do either:
1.
Code:
fastboot flash staging bootloader
fastboot flash recovery TWRP.img
Or:
Code:
blobpack -s bootloader-TWRP.blob EBT bootloader.EBT SOS TWRP.img
fastboot flash staging bootloader-TWRP.blob
Are they equivalent?

Stuck with the old bootloader
[CODE said:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader[/CODE]
check the version displayed. Is it 10.14.1.47? if not, hard reset to bootloader ([vol-] + [power])
boot recovery kernel (RCK)
install zip
choose zip from sdcard
UL-K00C-xx-10.14.1.47-user.zip
Yes
wait and pray to odin
+++ go back +++
reboot system now
Yes - Disable recovery flash (doesn't actually matter)
Yes - Root device (/system/xbin/su) (just kidding, this doesn't work)
Please consider clicking thanks
Sources:
Lots of own work
http://forum.xda-developers.com/showpost.php?p=47767352&postcount=71
https://github.com/AndroidRoot/BlobTools
Click to expand...
Click to collapse
I am stuck, for some reason after following these steps when the device reboots it is still with the old recovery and bootloader. Can anybody help please?

xabier87 said:
I am stuck, for some reason after following these steps when the device reboots it is still with the old recovery and bootloader. Can anybody help please?
Click to expand...
Click to collapse
What are you trying to do? Which BL and recovery do you currently have?
Flashable zips for the last bootloaders are here: http://forum.xda-developers.com/showpost.php?p=61045480&postcount=2

berndblb said:
What are you trying to do? Which BL and recovery do you currently have?
Flashable zips for the last bootloaders are here: http://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
Click to expand...
Click to collapse
Thanks for the info! I might try with these zips and bootloaders. I am trying to reset my tablet or make it work. Had cm-12.1-20160711-NIGHTLY-tf701t.zip on it with TWRP recovery and US_epad-10.26.1.18-20131217 bootloader but it recently stoppped working. I do have access to the bootloader and recovery but after following the fastboot instructions and rebooting nothing is changed on the tablet.

How to recover my encrypted userdata ?

Hi all,
I have a Nexus 6 phone with disk encryption enabled. I am trying to recover my userdata, could someone help me with this?
Following is what I did.
Backed up encrypted user data:
HTML:
$sudo adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata myencrypted_userdata
while flashing the new firmware images I accidentally flashed the userdata image that came with factory images too.
I remember the the password I used to encrypt the disk. So I thought I can flash the myencrypted_userdata back, in order to recover the my old data.
I used following command to do that:
HTML:
$ sudo fastboot flash userdata+userdata1 myencrypted_userdata
Unfortunately, that didn't work so how do I flash my backed up "myencrypted_userdata" to my device? and recover it using the the password I know?
Thank you so much for your time
Post note:
Following is the error I am getting:
HTML:
$ sudo fastboot flash userdata+userdata1 myencrypted_userdata
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
and size of backed up "myencrypted_userdata" is huge :
HTML:
$ ls -alh myencrypted_userdata
-rw-rw-r-- 1 kar kar 56G mrt 3 13:03

karthik9;71266527
while flashing the new firmware images I accidentally flashed the userdata image that came with factory images.......[/QUOTE said:
It looks like dirty flashing.
New firmware and data from previous version.
That doesn't work in many cases.
Click to expand...
Click to collapse

NLBeev said:
It looks like dirty flashing.
New firmware and data from previous version.
That doesn't work in many cases.
Click to expand...
Click to collapse
Okay, I tried to use the same firmware image version I had, just to recover the data. That is also not working.
I followed the same steps I mentioned earlier:
HTML:
$sudo fastboot flash userdata+userdata1 myencrypted_userdata
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Is there there any other way to recover the data? (I remember the password though)

karthik9 said:
...
Is there there any other way to recover the data? (I remember the password though)
Click to expand...
Click to collapse
Are you sure the data partition is wiped/formatted before restoring your data?
(Assumed, but did not see that in the steps you wrote.)

NLBeev said:
Are you sure the data partition is wiped/formatted before restoring your data?
(Assumed, but did not see that in the steps you wrote.)
Click to expand...
Click to collapse
Thank you for you response.
So I did wipe out the old userdata with new firmware image (userdata.img) using following command .
HTML:
$sudo fastboot flash userdata userdata.img
Then now I am trying to restore my old userdata partition using following command:
HTML:
$sudo fastboot flash userdata+userdata1 myencrypted_userdata
No I didn't do anything else in between. Am I missing something in between? if so, how do I format the data partition? Also, the encrypted image size is huge "56G". Is that a problem?

karthik9 said:
No I didn't do anything else in between. Am I missing something in between? if so, how do I format the data partition? Also, the encrypted image size is huge "56G". Is that a problem?
Click to expand...
Click to collapse
Don't know about the size, try it. But you have to fastboot erase the data partition first.
Try fastboot erase userdata and fastboot erase cache before restoring.
EDIT the format command is
Fastboot format <partition>

NLBeev said:
Don't know about the size, try it. But you have to fastboot erase the data partition first.
Try fastboot erase userdata and fastboot erase cache before restoring.
EDIT the format command is
Fastboot format <partition>
Click to expand...
Click to collapse
Still getting same error:
HTML:
[email protected]:~ $ sudo fastboot erase userdata [134]
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.649s]
finished. total time: 1.649s
[email protected]:~ $ sudo fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.024s
[email protected]:~ $ sudo fastboot flash userdata+userdata1 myencrypted_userdata
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.

Last idea:
Fastboot erase userdata
Fastboot format userdata
<Restore>

[SOLVED] Softbricked Huawei P9Plus

[SOLVED] Solution in post 7
After about 7 seven years without bricking a phone I finally managed to do so.
I was on VIE-L09C432B360 and tried to update to B370 via FF and proxy.
All seemed to be good, but on reboot only an error message appeared. I only have the option to go to the erecovery or the fastboot&rescue mode.
In erecovery I'm connected to my WiFi but restore fails.
In Fastboot&Resuce mode I see following text:
"AP_S_COLDBOOT
NA
volumnkey_down_press_process_func
PHONE LOCKED
FRP Lock
rescue mode enter"
In this mode I have a contact to the device in fastboot but I'm not able to flash something (says: Command not allowed)
I also tried DC-Unlocker (as it seems to have an unbrick option) but it won't find the phone. And I tried SRK-Tool, but this is using the same method as if I try to flash via fastboot.
Any options?
Checked a few things via fastboot:
fastboot getvar rescue_version
rescue_version: rescue0.5
finished. total time: 0.064s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VIE-L09C432B360
finished. total time: 0.003s
fastboot oem get-product-model
...
(bootloader) VIE-L09
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot oem get-psid
...
(bootloader) SN:N9Q7N1651(...)
(bootloader) IMEI:86086(...)
(bootloader) IMEI:86086(...)
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot oem get-build-number
...
(bootloader) :VIE-L09C432B360
OKAY [ 0.003s]
finished. total time: 0.004s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.007s

did u try t unlock? via fastboot?
If you get command not allowed i recommend you DC Pheonix not DC Unlocker....

I tried to unlock. No success.
Using DC-Phoenix I get this:
Current version: VIE_Global_5.0_oversea_channel
Extracting partitions
Cannot create extract directory: F:\Programme\DC_Phoenix\tmp\20170418_175324_UPDATE\
Extract files to directory: F:\Programme\DC_Phoenix\
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: MODEM_DTB OK
Extracting partition: XLOADER OK
Extracting partition: FASTBOOT OK
Extracting partition: DTS OK
Extracting partition: FW_LPM3 OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Device found: N9Q7N16513XXXXXXXX
IMEI: 8608650XXXXXXXX
Build number: :VIE-L09C432B360
Product model: VIE-L09
Writing MODEMNVM_UPDATE partition with file F:\Programme\DC_Phoenix\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing MODEMNVM_UPDATE partition with file F:\Programme\DC_Phoenix\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing SENSORHUB partition with file F:\Programme\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file F:\Programme\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file F:\Programme\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing MODEM partition with file F:\Programme\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file F:\Programme\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file F:\Programme\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file F:\Programme\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing MODEM_DTB partition with file F:\Programme\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Writing XLOADER partition with file F:\Programme\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FASTBOOT partition with file F:\Programme\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing DTS partition with file F:\Programme\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing FW_LPM3 partition with file F:\Programme\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing TEEOS partition with file F:\Programme\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file F:\Programme\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing RECOVERY partition with file F:\Programme\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file F:\Programme\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Software written
18.04.2017 17:55:34 Writing device finished OK
Second attempt:
Current version: VIE_C900B000
Extracting partitions
Cannot create extract directory: F:\Programme\DC_Phoenix\tmp\20170418_180047_UPDATE\
Extract files to directory: F:\Programme\DC_Phoenix\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
Extracting partition: RECOVERY OK
Device found: N9Q7N16513XXXXXXX
IMEI: 860865030XXXXXXX
Build number: :VIE-L09C432B360
Product model: VIE-L09
Writing XLOADER partition with file F:\Programme\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file F:\Programme\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file F:\Programme\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file F:\Programme\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file F:\Programme\DC_Phoenix\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file F:\Programme\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file F:\Programme\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file F:\Programme\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file F:\Programme\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file F:\Programme\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY2 partition with file F:\Programme\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file F:\Programme\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file F:\Programme\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file F:\Programme\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file F:\Programme\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file F:\Programme\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...FAILED
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file F:\Programme\DC_Phoenix\CUST.img
CUST partition UPDATE ...FAILED
Writing MODEM_DTB partition with file F:\Programme\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Writing RECOVERY partition with file F:\Programme\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Software written
18.04.2017 18:02:33 Writing device finished - INCOMPLETE
Third attempt:
Current version: VIE_Global_5.0_oversea_channel
Extracting partitions
Cannot create extract directory: F:\Programme\DC_Phoenix\tmp\20170418_180519_UPDATE\
Extract files to directory: F:\Programme\DC_Phoenix\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: MODEM_DTB OK
Device found: N9Q7N165130XXXXXX
IMEI: 8608650302XXXXXXXX
Build number: :VIE-L09C432B360
Product model: VIE-L09
Writing XLOADER partition with file F:\Programme\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file F:\Programme\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file F:\Programme\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file F:\Programme\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file F:\Programme\DC_Phoenix\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file F:\Programme\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file F:\Programme\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file F:\Programme\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file F:\Programme\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file F:\Programme\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file F:\Programme\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file F:\Programme\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file F:\Programme\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file F:\Programme\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file F:\Programme\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file F:\Programme\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file F:\Programme\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing MODEM_DTB partition with file F:\Programme\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
18.04.2017 18:07:29 Writing device finished OK
Fourth attempt:
Current version: VIE_Global_5.0_oversea_channel
Extracting partitions
Cannot create extract directory: F:\Programme\DC_Phoenix\tmp\20170418_181719_UPDATE\
Extract files to directory: F:\Programme\DC_Phoenix\
Extracting partition: CUST OK
Extracting partition: VERSION OK
Device found: N9Q7N165130XXXXXX
IMEI: 8608650302XXXXXXXX
Build number: :VIE-L09C432B360
Product model: VIE-L09
Erasing CUST partition
ERASE partition CUST ...FAILED
Writing CUST partition with file F:\Programme\DC_Phoenix\CUST.img
CUST partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file F:\Programme\DC_Phoenix\CUST.img
CUST partition UPDATE ...OK
Writing VERSION partition with file F:\Programme\DC_Phoenix\VERSION.img
VERSION partition UPDATE ...OK
Software written
18.04.2017 18:17:39 Writing device finished OK
But still the device won't boot.

Try rolling back by putting the rollback update.zip file in dload folder on an SD card. If that loads successfully, load a 202 or below firmware using the same method (SD card) and then you should be able to update to 370.

use rollback from N to M in DC Pheonix amd after restart enter in fastboot again and flash with DC Pheonix B180.
---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------
Also after you install what i said bellow try to get into recovery and wipe data and cache

zubyro said:
use rollback from N to M in DC Pheonix amd after restart enter in fastboot again and flash with DC Pheonix B180.
---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------
Also after you install what i said bellow try to get into recovery and wipe data and cache
Click to expand...
Click to collapse
I tried the rollback from SD-Card and and via DC-Phoenix. Both time no success.
No I will try to get into Recovery before it reboots and try to clear everything.

Ok, I finally managed to bring it back to life. Here is, what I did (Don't know if all is necessary, but thats what I did):
First: The phone was in a bootloop, Bootloader locked and FRP locked. eRecovery didn't work, wipe cache and factory reset won't work.
So I found a Firmware VIE-L09C432B170 which also contains the userdata.img and cache.img (note that most of the UPDATE.APP won't have them). After flashing this with DC-Phoenix I was still in a bootloop. I than flashed the UPDATE.APP of VIE-L09C02B131 (which was the version the phone came with).
And here we go: The phone is back alive and on VIE-L09C432B131.

good job. next time pay attention on what you flash...

zubyro said:
good job. next time pay attention on what you flash...
Click to expand...
Click to collapse
I payed a lot attention. I had at least two looks at the CUST and Build and also had a look into VERLIST.img. But something went completely wrong.
I found out, that the vendor and vendor country were missing. And now I'm not able to update.
So next time I pay attention which phone I buy. Either a Nexus (Pixel) or a OnePlus. Or the next Nokia, which seems to be very promising.

agree!

Further request
Rocksau said:
Ok, I finally managed to bring it back to life. Here is, what I did (Don't know if all is necessary, but thats what I did):
First: The phone was in a bootloop, Bootloader locked and FRP locked. eRecovery didn't work, wipe cache and factory reset won't work.
So I found a Firmware VIE-L09C432B170 which also contains the userdata.img and cache.img (note that most of the UPDATE.APP won't have them). After flashing this with DC-Phoenix I was still in a bootloop. I than flashed the UPDATE.APP of VIE-L09C02B131 (which was the version the phone came with).
And here we go: The phone is back alive and on VIE-L09C432B131.
Click to expand...
Click to collapse
Hi! Is it possible to flash UPDATE.APP directly from fastboot?

do you still have a copy of VIE-L09C432B131 that i can download directly from you?
Rocksau said:
Ok, I finally managed to bring it back to life. Here is, what I did (Don't know if all is necessary, but thats what I did):
First: The phone was in a bootloop, Bootloader locked and FRP locked. eRecovery didn't work, wipe cache and factory reset won't work.
So I found a Firmware VIE-L09C432B170 which also contains the userdata.img and cache.img (note that most of the UPDATE.APP won't have them). After flashing this with DC-Phoenix I was still in a bootloop. I than flashed the UPDATE.APP of VIE-L09C02B131 (which was the version the phone came with).
And here we go: The phone is back alive and on VIE-L09C432B131.
Click to expand...
Click to collapse
Huawei has no firmware AT ALL on their websites for the P9 Plus and without the firmware, I don't know how to navigate through this. I done the exact same thing to my P9 Plus

VTR-L09 8.0.0.360(C432) Func NO: 11 (recovery image) Error NO: 2 (load failed!)

Hey there,
like the title says i have managed it to break my phone -.-:crying:
here are the stats:
Selected Applications port COM10
Selected Diagnostics port COM10
Found Phone : VTR-L09
Model : Huawei phone in fastboot mode
IMEI : 862789034425897
Serial NR. : 6PQ0217406000752
Firmware : VTR-L09 8.0.0.360(C432
IMEI1:862789034425897
MEID:86278903442589
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3523mv
Dload:
doesnt work )=
Service_Full_Repair_Vicky-L29_C10B151_Firmware_Russian_Federation_Belarus_Georgia_Mongolia_androidhost.ru
I have tried:
from update zip :
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash ramdisk ramdisk.img
and tried:
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash erecovery_kernel erecovery_kerne.img
fastboot flash erecovery_ramdis erecovery_ramdi.img
fastboot flash erecovery_vbmeta erecovery_vbmet.img
fastboot flash erecovery_vendor erecovery_vendo.img
also tried hwota...
but Nothing Works for me )=
Still only have fastboot and error mode, no acces to twrp or erecovery )=
have no idea left right now.... :silly: sitting the last 2 days on this -.- just want my phone back :crying:
I have a complete recovery from twrp, the one file full ota, and the 3 part full ota
please help me to get back to full funktion or to twrp from where i could manage the rest (=
sry for my bad englisch to less slep these days

Okay invested 20 bucks in dcphonix for 3 day licence
but my phone is back even my datas are restored
now it is loading at 10% when akku is charged i will again try to install twrp which killed my system because i flashed it via fastboot flash recovery instead of fastboot flash recovery_ramdisk
Hope it will work now with the right command and the newest twrp (=
will try the 3.2.1 oreo v2 (= or should i use another?
and i see magisk is gone (what was clear) wich Version best for reinstall?
have to take a look if i give my akkount free so you have all a chance to unbrick
Edd: will give it free after fin and saved my phone since it is a 3 day acc and no option that you buy things on my card (=

dt92 said:
Okay invested 20 bucks in dcphonix for 3 day licence
but my phone is back even my datas are restored
now it is loading at 10% when akku is charged i will again try to install twrp which killed my system because i flashed it via fastboot flash recovery instead of fastboot flash recovery_ramdisk
Hope it will work now with the right command and the newest twrp (=
will try the 3.2.1 oreo v2 (= or should i use another?
and i see magisk is gone (what was clear) wich Version best for reinstall?
have to take a look if i give my akkount free so you have all a chance to unbrick
Edd: will give it free after fin and saved my phone since it is a 3 day acc and no option that you buy things on my card (=
Click to expand...
Click to collapse
Hi dt92! I'm in the same place as you after accidentally killing my Oreo with flashing TWRP, how did this program work?
And I know this is too much, but could I use what you used since i'm just a student without a credit card right now?
I'm so sorry, I'm so nervous right now since my parents would kill me if they figured out that I broke the phone they gave to me as a gift (

uzernamezz said:
Hi dt92! I'm in the same place as you after accidentally killing my Oreo with flashing TWRP, how did this program work?
And I know this is too much, but could I use what you used since i'm just a student without a credit card right now?
I'm so sorry, I'm so nervous right now since my parents would kill me if they figured out that I broke the phone they gave to me as a gift (
Click to expand...
Click to collapse
hey here (= accidentally killing my system again and stuck now between bootloader, e recovery, twrp, and download but thiks there is a chance out of it (= (if someone know please help)
Tryed to share the software at a friend with boken phone yesterday but its ip based )=
so yes i think the software could help you and you can pay per pay pal
don`t panic think we will manage to get our vtr`s back on Oreo (=
Code:
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 6PQ0217406000752
07.03.2018 22:16:53 Starting extracting partitions from file UPDATE.APP
Current version: VTR_C900_EMUI8.0
Cannot create extract directory: C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\tmp\20180307_221653_UPDATE\
Extract files to directory: C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: VECTOR OK
Extracting partition: VBMETA OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: DTS OK
Extracting partition: KERNEL OK
Extracting partition: RECOVERY_RAMDISK OK
Extracting partition: RECOVERY_VENDOR OK
Extracting partition: RECOVERY_VBMETA OK
Extracting partition: ERECOVERY_KERNEL OK
Extracting partition: ERECOVERY_RAMDISK OK
Extracting partition: ERECOVERY_VENDOR OK
Extracting partition: ERECOVERY_VBMETA OK
Extracting partition: RAMDISK OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: ISP_FIRMWARE OK
Extracting partition: MODEM_FW OK
Extracting partition: HISEE_IMG OK
Extracting partition: HISEE_FS OK
Extracting partition: ODM OK
07.03.2018 22:20:50 Extracting partitions finished OK
07.03.2018 22:20:50 Starting to write device in FASTBOOT mode...
Device found: 6PQ0217406000752
IMEI: 862789034425897
Build number: :VTR-L09 8.0.0.360(C432)
Product model: VTR-L09
Writing XLOADER partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing VECTOR partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\VECTOR.img
VECTOR partition UPDATE ...OK
Writing VBMETA partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\VBMETA.img
VBMETA partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing DTS partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\DTS.img
DTS partition UPDATE ...OK
Writing KERNEL partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\KERNEL.img
KERNEL partition UPDATE ...OK
Writing RECOVERY_RAMDISK partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RECOVERY_RAMDISK.img
RECOVERY_RAMDISK partition UPDATE ...OK
Writing RECOVERY_VENDOR partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RECOVERY_VENDOR.img
RECOVERY_VENDOR partition UPDATE ...OK
Writing RECOVERY_VBMETA partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RECOVERY_VBMETA.img
RECOVERY_VBMETA partition UPDATE ...OK
Writing ERECOVERY_KERNEL partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_KERNEL.img
ERECOVERY_KERNEL partition UPDATE ...OK
Writing ERECOVERY_RAMDISK partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_RAMDISK.img
ERECOVERY_RAMDISK partition UPDATE ...OK
Writing ERECOVERY_VENDOR partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_VENDOR.img
ERECOVERY_VENDOR partition UPDATE ...OK
Writing ERECOVERY_VBMETA partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_VBMETA.img
ERECOVERY_VBMETA partition UPDATE ...OK
Writing RAMDISK partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RAMDISK.img
RAMDISK partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing ISP_FIRMWARE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ISP_FIRMWARE.img
ISP_FIRMWARE partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Writing HISEE_IMG partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\HISEE_IMG.img
HISEE_IMG partition UPDATE ...OK
Writing HISEE_FS partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\HISEE_FS.img
HISEE_FS partition UPDATE ...OK
Writing ODM partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ODM.img
ODM partition UPDATE ...OK
Software written
07.03.2018 22:28:01 Writing device finished OK
thats the output of DC- phoenix...
think the software unzips the update files, open backdoor, load them one by one....
but don´t know how they managed the backdoor
hope to get my phone back to work today or tomorrow otherwise 20 bucks for nothing
but have some problems i do not understand have a full recovery backup but cant start phone when i load it via twrp, it is like some part is missing

dt92 said:
hey here (= accidentally killing my system again and stuck now between bootloader, e recovery, twrp, and download but thiks there is a chance out of it (= (if someone know please help)
Tryed to share the software at a friend with boken phone yesterday but its ip based )=
so yes i think the software could help you and you can pay per pay pal
don`t panic think we will manage to get our vtr`s back on Oreo (=
Code:
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 6PQ0217406000752
07.03.2018 22:16:53 Starting extracting partitions from file UPDATE.APP
Current version: VTR_C900_EMUI8.0
Cannot create extract directory: C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\tmp\20180307_221653_UPDATE\
Extract files to directory: C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: VECTOR OK
Extracting partition: VBMETA OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: DTS OK
Extracting partition: KERNEL OK
Extracting partition: RECOVERY_RAMDISK OK
Extracting partition: RECOVERY_VENDOR OK
Extracting partition: RECOVERY_VBMETA OK
Extracting partition: ERECOVERY_KERNEL OK
Extracting partition: ERECOVERY_RAMDISK OK
Extracting partition: ERECOVERY_VENDOR OK
Extracting partition: ERECOVERY_VBMETA OK
Extracting partition: RAMDISK OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: ISP_FIRMWARE OK
Extracting partition: MODEM_FW OK
Extracting partition: HISEE_IMG OK
Extracting partition: HISEE_FS OK
Extracting partition: ODM OK
07.03.2018 22:20:50 Extracting partitions finished OK
07.03.2018 22:20:50 Starting to write device in FASTBOOT mode...
Device found: 6PQ0217406000752
IMEI: 862789034425897
Build number: :VTR-L09 8.0.0.360(C432)
Product model: VTR-L09
Writing XLOADER partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing VECTOR partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\VECTOR.img
VECTOR partition UPDATE ...OK
Writing VBMETA partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\VBMETA.img
VBMETA partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing DTS partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\DTS.img
DTS partition UPDATE ...OK
Writing KERNEL partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\KERNEL.img
KERNEL partition UPDATE ...OK
Writing RECOVERY_RAMDISK partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RECOVERY_RAMDISK.img
RECOVERY_RAMDISK partition UPDATE ...OK
Writing RECOVERY_VENDOR partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RECOVERY_VENDOR.img
RECOVERY_VENDOR partition UPDATE ...OK
Writing RECOVERY_VBMETA partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RECOVERY_VBMETA.img
RECOVERY_VBMETA partition UPDATE ...OK
Writing ERECOVERY_KERNEL partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_KERNEL.img
ERECOVERY_KERNEL partition UPDATE ...OK
Writing ERECOVERY_RAMDISK partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_RAMDISK.img
ERECOVERY_RAMDISK partition UPDATE ...OK
Writing ERECOVERY_VENDOR partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_VENDOR.img
ERECOVERY_VENDOR partition UPDATE ...OK
Writing ERECOVERY_VBMETA partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ERECOVERY_VBMETA.img
ERECOVERY_VBMETA partition UPDATE ...OK
Writing RAMDISK partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\RAMDISK.img
RAMDISK partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing ISP_FIRMWARE partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ISP_FIRMWARE.img
ISP_FIRMWARE partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Writing HISEE_IMG partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\HISEE_IMG.img
HISEE_IMG partition UPDATE ...OK
Writing HISEE_FS partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\HISEE_FS.img
HISEE_FS partition UPDATE ...OK
Writing ODM partition with file C:\Users\Dennis\Desktop\Huawai\DC_Phoenix_v50\ODM.img
ODM partition UPDATE ...OK
Software written
07.03.2018 22:28:01 Writing device finished OK
thats the output of DC- phoenix...
think the software unzips the update files, open backdoor, load them one by one....
but don´t know how they managed the backdoor
hope to get my phone back to work today or tomorrow otherwise 20 bucks for nothing
but have some problems i do not understand have a full recovery backup but cant start phone when i load it via twrp, it is like some part is missing
Click to expand...
Click to collapse
I see!
I'm so sorry for sending you a PM, haha.. but that means I'm out of luck then :/ since I'm not allowed to have one..
But hopefully we find other free alternatives for this, yeah?
Cheers mate! Good luck on fixing your phone!

uzernamezz said:
I see!
I'm so sorry for sending you a PM, haha.. but that means I'm out of luck then :/ since I'm not allowed to have one..
But hopefully we find other free alternatives for this, yeah?
Cheers mate! Congrats on fixing your phone!
Click to expand...
Click to collapse
right now its blackscreen/ dead :crying:
hope to get it back running

dt92 said:
right now its blackscreen/ dead :crying:
hope to get it back running
Click to expand...
Click to collapse
Keep us posted! Maybe we'll be able to find something that can apply to all of our phones?

If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm

cesedy said:
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
Click to expand...
Click to collapse
Bless you, mate! Unfortunately, it says that the software is locked to another PC..
Doesn't this have something to do with IP addresses or something?

That would suck, as I have Dynamic IP.
But, in Task manager I saw processes adb.exe and fastboot.exe which I am not running.
As i have nothing like that opened, maybe those were diversion processes to stay connected only to my PC.
I have closed them now, can you try again?
And, if you succeed, then, maybe, close those on your Task Manager aswell.

you cant use it because it is not ip based its mac based you can only use the tool where you make the first install )=
now since i hang on blackscreen of death -.- i found a way wich i will try tomorrow (=
take a look :
pic of testpoint vtr-l09
https://drive.google.com/file/d/1uGl...RQNxSZhgm/view
then you can reinstall factory firmware
https://www.dc-unlocker.com/file-lis...with_Testpoint
think this is the last way /=
in att is the testpoint reset data for vtr-l09 but now i go to bed
tommor i will upload a full rom vtr-l09c432-b171 ink dtwork file and vtr-l29 if i find i frind where i can make the upload because i pay per 30 GB

cesedy said:
That would suck, as I have Dynamic IP.
But, in Task manager I saw processes adb.exe and fastboot.exe which I am not running.
As i have nothing like that opened, maybe those were diversion processes to stay connected only to my PC.
I have closed them now, can you try again?
And, if you succeed, then, maybe, close those on your Task Manager aswell.
Click to expand...
Click to collapse
Hey, I checked for those two, unfortunately nothing else seemed to work just as well. Is there any hope left?

dt92 said:
here are the stats:
Selected Applications port COM10
Selected Diagnostics port COM10
Found Phone : VTR-L09
Model : Huawei phone in fastboot mode
IMEI : 862789034425897
Serial NR. : 6PQ0217406000752
Firmware : VTR-L09 8.0.0.360(C432
IMEI1:862789034425897
MEID:86278903442589
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3523mv
Click to expand...
Click to collapse
Hello, please how you manage to see this info on your PC?

used hcu witch is part of dc phonix i think (=
ot oem info in fastboot would also do it (=
after a little talk with my handy distributor i will send it back and get a new one thanks god for insurance
so now i have just to way a few days and should then do it a little more slow step by step...
but will stand by your sites
even at my state the phone could be repaired but i don´t want to open it (=

-

-

jeanbono67 said:
Hey folks !
I've tried to restore stock firmware on my P9 Plus (VIE-L09C432B370) through erecovery but I keep getting the "getting package info failed" after connecting to the wifi.
Tried flashing TWRP, ended up having the "Your device is now booting" message forever.
Normal boot ends up in a bootloop.
Can't restore it via HiSuite.
The bootloader and the FRP are unlocked.
Oh and I lost the sim/sd card tray, so no dload possible for me *kill me please*
I can't download any stock rom since Huawei made it impossible through the hicloud links.
Is there any soul who can help me with this ?
Thank you in advance !
Click to expand...
Click to collapse
same problem, from oreo vie-al10...
I have erased with command fastboot erase ... this partitions:
recovery_vendor
dts
dto
recovery_vbmeta
erecovery_vbmeta
vbmeta
modem
modem_dsp
modem_dtb
dfx
3rdmodem
cache
odm
hisitest0
hisitest1
patch
bootfail_info
rrecord
reserved3
system
cust
version
vendor
product
hisitest2
userdata
now the phone don't start and I'm trying to repair with hisuite.