DC-Phoenix

[icsiszer]

If your device has board software, you could try flashing with it from scratch, otherwise not much to do regarding this.

Solved, via Fastboot using ADB... spent 19 euros for nothing... :-/

[Valdemaras]

On device I had this ags-w09c100b278 as I see, but it was wiped via TWRP.

Is there anything that I can do? Please let me know. Than you.

If your device has board software, you could try flashing with it from scratch, otherwise not much to do regarding this.

[icsiszer]

If installation stops at 5% means firmware is not suitable, probably android or security patch mismatch.

On device I had this ags-w09c100b278 as I see, but it was wiped via TWRP.

Is there anything that I can do? Please let me know. Than you.

[Valdemaras]

Yes, the device restarts in Upgrade mode, then I see that the DC-Phoenix is also communicating via COM4. On the device screen installation starts, but suddenly stop at 5%.

If installation stops at 5% means firmware is not suitable, probably android or security patch mismatch.

[icsiszer]

Does the device switch to upgrade mode during this as it is necessary to proceed with flash? You should monitor the device manager on your computer to see what exactly happens to the device.

Yes, the device restarts in Upgrade mode, than I see that the DC-Phoenix is also communicating via COM4. On the device screen installation starts, but suddenly stop at 5%.

[Valdemaras]

Does the device switch to upgrade mode during this as it is necessary to proceed with flash? You should monitor the device manager on your computer to see what exactly happens to the device.

[icsiszer]

Hi,

I tried to use DC-Phoenix on a Huawei Mediapad T3 10, without success. The tablet is soft bricked... ROM wiped. Not accessible via USB (device manager don't see in COM port)

Please advice me what I am doing wrong... I don't want to lose my credits without fixing my tablet.

DC Phoenix 0.0.0.173
user:icsiszer

Looking for a device in upgrade mode
No devices detected in upgrade mode
Device found: 4JPNU19124108912


Standard update
Not Reboot NOT checked
Update Verlist to server on file load NOT checked
Enable testpoint NOT checked
Disable testpoint NOT checked
Try Rescue Recovery checked
Bypass version check checked
Old slow algo NOT checked

Extracting recovery partition

Extracting partition: RECOVERY
RECOVERY partition extracted

Extracting partition: ERECOVERY
ERECOVERY partition extracted

21.01.2024 23:28:39 Starting to try Rescue Recovery...


Looking for a device in fastboot mode
Device found: 4JPNU19124108912


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

SN:4JPNU19124108912
IMEI:4JPNU19124108912
Build number: AGS-W09C100B278
Model: AGS-W09
Vendor/Country: hw/eu
Battery state: 3675mv
OEM lock state info:
user Lock state is unlock

fbLock state is lock

OEM get bootinfo:
*******************************************

Image is origin

Verify mode is enforcing

Check root info is safe

Lock state is unlock

Root State: ROOT

*******************************************



Process identifier:72414895


Erasing ver .. .
Getting lock state info...
Cannot get FBlock info from device
Trying to unlock device...

Signing process may take few minutes

Trying to get data from server

Erasing ver .. .
Writing rescue_recovery partition
RESCUE_RECOVERY partition update ...OK
Update recovery parttion OK

USB Device REMOVAL
Type: @oem15.inf,%hwfastboot%;Android Sooner Single ADB Interface
VidPid: VID_18D1&PID_D00D
Instance id: 4JPNU19124108912
Looking for device in upgrade mode...

USB Device INSERTION
Type: @oem19.inf,%busfilter.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_107D
Instance id: 4JPNU19124108912
Enter recovery mode OK

21.01.2024 23:29:16 Starting to write device in UPGRADE mode...
Cannot detect device, try again
21.01.2024 23:29:24 Writing device finished with ERROR

[Valdemaras]

but as i said, after downgrade to 9 the pc doesn't "see" the phone, not even a sign for connected device in Device Manager

Sadly we can not help with such a problem.

[drakulaboy]

No standard USB cable should work on Android 9.

but as i said, after downgrade to 9 the pc doesn't "see" the phone, not even a sign for connected device in Device Manager

[Valdemaras]

i downgraded to 9 a few times but after downgrade PC can't find the phone, need the Harmony TP cable?

No standard USB cable should work on Android 9.

[drakulaboy]

device must be on Android 9 for unlock to be permanent.

i downgraded to 9 a few times but after downgrade PC can't find the phone, need the Harmony TP cable?

[Valdemaras]

hello, is DC-unlocker able to unlock Huawei P30 Pro bootloader, Kirin 980? it unlocks temporary or full unlock?

DC-unlocker isn't able to do it, only HCU is and device must be on Android 9 for unlock to be permanent.

[drakulaboy]

hello, is DC-unlocker able to unlock Huawei P30 Pro bootloader, Kirin 980? it unlocks temporary or full unlock?

[Valdemaras]

where can i get the XML file?

it usually is in the raw pack of board software if you find any.

[uradryct]

Refund for time license is unavailable. The code you see is the bootloader code that you can use on cmd. If you bricked your phone by writing random incorrect CPU data as visible from your logs you may need to reflash it from scratch with board software if reset, clear data/cache from the recovery menu and reflashing stock ROM does not help.

where can i get the XML file?