DC-Phoenix

[Valdemaras]

what is the 2/3 method?

There is DC-phoenix guide that launches along with software (if you read any messages that pop up) It has 3 different methods of repair.

[juliog]

Then can only use method 2/3 to flash it.

what is the 2/3 method?

[Valdemaras]

do not explain me well, I have tried to flash it of all possible combinations several times, and in all I get the same result

Then can only use method 2/3 to flash it.

[juliog]

Make sure you are using same android version to flash it with, also use bypass version option.

do not explain me well, I have tried to flash it of all possible combinations several times, and in all I get the same result

[juliog]

Make sure you are using same android version to flash it with, also use bypass version option.

I'm using a lower version, to downgrade, and the bypass option is checked

[juliog]

I'm using a lower version, to downgrade, and the bypass option is checked

[Valdemaras]

DC Phoenix 0.0.0.132

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

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

Extracting recovery partition

Extracting partition: RECOVERY
RECOVERY partition extracted

30/09/2020 12:45:49 Starting to try Rescue Recovery...


Looking for a device in fastboot mode
Device found: FFY5T17C11024874


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

SN:FFY5T17C11024874
IMEI:867973038207411
IMEI1:867973038227427
MEID:00000000000000
Build number: :RNE-L21 8.0.0.346(C432)
Model: RNE-L21
Vendor/Country: hw/eu
Battery state: 4263mv
OEM lock state info:
FB LockState: LOCKED
USER LockState: LOCKED
OEM get bootinfo:
locked

Getting base version...
Getting cust version...
Getting preload version...
Preload Version is EMPTY

Process identifier:27761411


Erasing ver .. .
Writing rescue_recovery partition
RESCUE_RECOVERY partition update :FAIL partition length get error
Uptade recovery parttion FAIL

Cannot enter in Recovery mode

Make sure you are using same android version to flash it with, also use bypass version option.

[juliog]

DC Phoenix 0.0.0.132

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

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

Extracting recovery partition

Extracting partition: RECOVERY
RECOVERY partition extracted

30/09/2020 12:45:49 Starting to try Rescue Recovery...


Looking for a device in fastboot mode
Device found: FFY5T17C11024874


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

SN:FFY5T17C11024874
IMEI:867973038207411
IMEI1:867973038227427
MEID:00000000000000
Build number: :RNE-L21 8.0.0.346(C432)
Model: RNE-L21
Vendor/Country: hw/eu
Battery state: 4263mv
OEM lock state info:
FB LockState: LOCKED
USER LockState: LOCKED
OEM get bootinfo:
locked

Getting base version...
Getting cust version...
Getting preload version...
Preload Version is EMPTY

Process identifier:27761411


Erasing ver .. .
Writing rescue_recovery partition
RESCUE_RECOVERY partition update :FAIL partition length get error
Uptade recovery parttion FAIL

Cannot enter in Recovery mode

[hinterland99]

thx
it happened after flashing openkirin (apex 10 beta) in testpoint fastboot mode
i don't think it's actually physical broken but the android 10(openkirin) did something during the install process or in the boot process afterwards(then with locked bootloader cause i never made it to the downgrade android 8 version for dc unlocker to work - but paid you already of course)
maybe something with the AB Partition change

the reason why im posting this here besides you maybe knowing a way around is that in case i get it done - All the other Kirin 960 Emui 9 - past security patch 2020 could be unlocked and upgraded to android 10( via treble or open kirin)
And that would be helpful for a lot of devices out there - i'lll keep on trying - and report if i make it - so you could write a one click solution for everyone


thank you for your help Valdemaras

[Valdemaras]

Hisuite not supposed to detect it in this mode, hisuite only gives drivers. I think your device's memory/board dead or damaged beyond software capability to repair it.

[hinterland99]

Thx for Answer
no hi suite does not recognize tablet/phone at all(not in recovery mode as well)
uninstalled windows USB-SER driver and did the "scan for new hardware thing" -> SB-SER device reapers hisuite doesn't detect it


Phone/Tablet doesn't boot at all - not in fastboot(which is the usual - fixable behavior - not in edl or recovery mode
tried to flash board software vie phoenix but - no success
maybe some partition table bug? maybe some wrong odm/oem(odm.img) file??
but after runninge
./hikey_idt -c config -p /dev/ttyUSB0
on ubuntu and flashing


0: Image: ./hisi-sec_usb_xloader.img Downalod Address: 0x20000
1: Image: ./hisi-sec_uce_boot.img Downalod Address: 0x6a908000
2: Image: ./hisi-sec_fastboot.img Downalod Address: 0x1ac00000
i get fastboot mode with temporary open bootloader (testpoint one time open bootloader mode)
this is where i hope i could install board software vie cd phoenix
thx

[Valdemaras]

First try to uninstall mobile and then reinstall hisuite on pc for correct drivers. After flashing board phone does not boot up normally as i understand, is that correct?

[hinterland99]

Hello
Mediapad m5 Wifi model
cmr-w09
im desperate after 35 hours of trying(no Exaggeration) can DC Phoenix help?


I partly succesfully downgraded from emui 9 for dc bootloader unlocker to work -------- via testpoint method (tablet is opened)
flashing board software in edl mode(edl and fastboot)

My Problem - pls help
whenever i boot the tablet boots into edl mode --- without having the test point pressed
no fastboot --- via vol down button
no emregency rescue----- via vol up button
just the edl mode :

-----------------------------------------------------------------
Manufacturer: HISILICON

GSM modem (1-port) converter detected
usb 3-3: GSM modem (1-port) converter now attached to ttyUSB0
------------------------------------------------------------------------------------

BUT i get a full working fastboot with HiKey_IDT tools --> stable

-------------------------------------------------------------------------
C:\adb\Minimal ADB and Fastboot>fastboot devices
0123456789ABCDEF fastboot

C:\adb\Minimal ADB and Fastboot>
-----------------------------------------------------------

fastboot.jpg

whenever i disconnect the usb cable and reboot i get a black screen on Tablet and "land" in edl mode(not edl fastboot)

do i have am expensive doorstoper? or is there hope?

[Vincentas]

Can you help me with an account? I need it urgently. My cell phone died and I need to revive it. I only want the account for about three hours and you can change the password, please!

Please read my previous message.

[juanN12]

Can you help me with an account? I need it urgently. My cell phone died and I need to revive it. I only want the account for about three hours and you can change the password, please!