Related
After a wrong Downgrade from Android 7 , used a OTA File after Downgrade file from Huawei, i stuck on Huawei Logo, i just can enter Fastboot Mode.
How can i install the Full Firmware via Fastboot Mode???
Phone is not rooted or unlocked.
Thank you for Help!!!!
I'm in a similar position, so subscribing to this thread in the hopes we can get some advice!
ConfusedTA said:
I'm in a similar position, so subscribing to this thread in the hopes we can get some advice!
Click to expand...
Click to collapse
I will try tomorrow with empty Batterie , hope i can enter to dload
No chance, as soon enough power is in the Bat. Phone restart to Huawei Logo.
I think, now i have a expensive piece of cr..
I managed to get to eRecovery and dload, by using DC-Phoenix and one of the various UPDATE.APP files from here on the forum. It still doesn't boot, but it's 1 step further...
Which File did you used?
My Phone is working!!!!!!!!!!!!!!!!!
I used EVA L09C432B136 with DC-Phoenix, after start i got Update to L19C432B166
Good Luck ConfusedTA hope you also get you Phone back to life!
Edit: Fingerprint isnt working at the moment
I'm sure I've tried a version of that - can you let me know where you got it from?
ConfusedTA said:
I'm sure I've tried a version of that - can you let me know where you got it from?
Click to expand...
Click to collapse
Pm send!
Thanks - same version as I've already tried
Glad you got yours fixed, though!
How did you done the flash with DC-Phoenix, acc Text Guide? Did you marked all items in the Upade.APP?
On the Pictures are not all items marked, but the should be!!!
Yes, all items were ticked in DC-Phoenix.
Here's my log, just in anyone spots anything!
Code:
Current version: EVA_C900B000
Extracting partitions
Cannot create extract directory: C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\tmp\20170129_125948_UPDATE\
Extract files to directory: C:\Users\Garry\Desktop\DC_Phoenix_v24\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: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
Extracting partition: USERDATA OK
Device found: MWS0216A16000685
IMEI: ***************
Build number: :EVA-L09C432B182
Product model: EVA-L09
Writing XLOADER partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\CUST.img
CUST partition UPDATE ...OK
Writing MODEM_DTB partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Erasing USERDATA partition
Partition USERDATA erased
Writing USERDATA partition with file C:\Users\Garry\Desktop\DC_Phoenix_v24\DC_Phoenix\USERDATA.img
USERDATA partition UPDATE ...OK
Software written
29/01/2017 13:02:41 Writing device finished OK
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
I've also tried to do the 3-button dload mode following this - it gets to 4%, then starts the update, then immediately fails.
Have you extracted the complete dload folder on your external SD? (root directory)
Gesendet von meinem EVA-L19 mit Tapatalk
Yep, I have
Hmm ok, that's strange, should work normally.
That's what I've been reading elsewhere should happen.
Just my luck that I get something not working right
Is your bootloader unlocked?
No, it is locked, as is FRP.
Last idea, try another firmware.
I've tried B136, B166, B182, B360 and B361!
But thanks for the suggestions!
[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
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 (=
Another method for unbricking EMUI 9 devices. For advanced users (not mentioning links to TWRP, to FullOTA factory images... there are other threads dedicated to that). Tested on Mate 20 Pro.
This method should help when:
1. Device has bootloader unlocked (unusable for locked bootloaders)
2. System fails to boot. HiSuite (HSTool) restore method does not work (fails in stage "Install recovery") nor does DLOAD method work (after VolUp+VolDn+Pwr action system continues booting or ends in 5% Installation and bootloops).
3. Fastboot mode is working
The reason might be wiped/corrupted eRecovery paritition.
Huge credits and thanks to @OldDroid for having educated me about eRecovery and about flashing it.
Steps:
1. Download FullOTA factory image
2. Extract UPDATE. APP file
3. Extract ERECOVERY_KERNE.img, ERECOVERY_RAMDI.img, ERECOVERY_VENDO.img, ERECOVERY_VBMET.img (guide:
OpenKirin - guide to extract partition images)
4. Boot into fastboot
5. Install and boot TWRP (
Code:
fastboot flash recovery_ramdisk twrp.img
)
6. Copy (e.g. via MTP, while connected to the computer) the 4 previously extracted images to internal storage or SD
7. Enter TWRP shell and execute:
Code:
ls -l /dev/block/bootdevice/by-name/
8. Check partition names, in case of Mate 20 Pro they are:
Code:
erecovery_kernel /dev/block/sdd37
erecovery_ramdisk /dev/block/sdd38
erecovery_vbmeta /dev/block/sdd53
erecovery_vendor /dev/block/sdd39
9. Copy the extracted files into corresponding partitions:
Code:
dd if=./ERECOVERY_KERNE.img of=/dev/blck/sdd37
dd if=./ERECOVERY_RAMDI.img of=/dev/blck/sdd38
dd if=./ERECOVERY_VENDO.img of=/dev/blck/sdd39
dd if=./ERECOVERY_VBMET.img of=/dev/blck/sdd53
10. Reboot to fastboot and flash stock recovery via
Code:
fastboot flash recovery_ramdisk stock_recovery.img
Now you should be good to go for DLOAD (recommended for soft-brick recovery) and HSTool methods.
Would this be for Error mode?
func no : 11 (recovery image)
error no : 2 (load failed!)
This error is what happens when I try Dload.
ReyneBow said:
Would this be for Error mode?
func no : 11 (recovery image)
error no : 2 (load failed!)
This error is what happens when I try Dload.
Click to expand...
Click to collapse
Depends on what is actually broken. If the error is caused by a broken eRecovery image, than this could help. I can't tell, the error codes displayed tell me nothing. One can also update eRecovery if it is extracted from a more recent firmware - e.g. EMUI 9.1.
How to unlock the Realme 8 Pro bootloader?
1. you'd better write in english, to get a broader range of people who understand you question ;-).
2. Also waiting for that ... it's a shame.
Greetz
Kurt
How to unlock bootloader realme 8 5G
Answer from [email protected] from today :
Unlock Bootloader tutorial for Realme 8 Pro RMX3081 is not available as of now.Further, keep following our social media handles and official community portal for the latest updates,
Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
StratOS_HTC said:
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Click to expand...
Click to collapse
Here is my id : RMX3081export_11_A.44_2021110921030235
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Oh bro, this is not GDPR version.. After I unlocked my bootloader, i tried to root realme 8 pro with patched boot image from OFP Rom but it's doesn't work for me..
Any thing to say about this?
StratOS_HTC said:
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Click to expand...
Click to collapse
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Since jour project id is 20711
Guess your PCB shows 0020711*
dial : *#899#
press the PCB num
StratOS_HTC said:
Well let me guide you throught it :
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah , tried but nothing seems to be work.
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_sys
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah i tried the steps that u said above to ROOT realme 8 pro, but it doesn't work for me... here are the steps that i did.
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
*Fastboot flash boot (magisk patched) boot.img
Result : Device went to bootloop. Retrieved from
bootloop by flashing stock boot image that previously extracted from OFP file and now the device is fine.
Also tried this step
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
* Fastboot --disable-verity --disable-verification
flash vbmeta_system vbmeta_system.img
*Fastboot --disable-verity --disable-verification
flash vbmeta_vendor vbmeta_vendor.img
*Fastboot flash boot (magisk patched) boot.img
Result : Bootlooped. Retrieved by flashing stock boot image..
And also, i tried to BOOT patched boot image... and it shows
FAILED <remote: unknown command>
ABV is still active.
THX @Shibu Shaji
For showing us the 20711 EXPORT .44 ROM fastboot getvar all infos.
I have also the 20713 GDPR .44 ROM fastboot getvar all infos.
The bootloader in EXPORT is unlocked and is not userspaced.
From green to orange state ... some progress after all ...
It seems your bootloader unlocked? actually how? I think ur AVB is now disabled
StratOS_HTC said:
View attachment 5505451
From green to orange state ... some progress after all ...
Click to expand...
Click to collapse
Wow, how did you do it?
currently via isp ufs access and help of a reversing from a friend.
On bootloop also ...
Oh bro, So what to do next? Is there any other problems with ur partitions after this?
Since EDL is not configured correctly (No kernel driver supported: Operation not supported or unimplemented on this platform) after the firehose programmer sucessfully boot ...
Also QFIL and unimplemented <CONFIGURE> or <SIG> and signed and certed things the only thing to do is via ISP UFS control.
OR possible USB port communication debug via MSM flash.
For EXPORT version have prepared seen action on the screen for this ROM
Code:
Project 20711
RMX3081
Version Flash MSM download tool v.2.0.51 for eMMC/UFS
Rom ofp : RMX3081export_11_A.28_202104090210
Server : India
Use default NV=yes
Reboot on finish=yes
Download Firehose protocol file
Sahara communication succeeded
Boot via firehose
Trying to handshake
Get sign data
Verify data
Getting NV code from server
Failed to get NV code. Default NV code would be used
Firehose GetUfsInfo
Erasing the partition Primarly GPT
Erasing the partition BackupGPT
Erasing the partition userdata
Downloading cdt_engineering_release.img
Erasing partition keystore
Downloading cache.img
Downloading recovery.img
Downloading metadata.img
Downloading userdata.img
Downloading gpt_main0.bin
Downloading xbl.elf
Downloading gpt_main1.bin
Downloading gpt_main2.bin
Downloading aop.mbn
Downloading tz.mbn
Downloading NON-HLOS.bin
Erasing the partition mdtpsecapp
Erasing the partition mdtp
Downloading abl.elf
Downloading dspso.bin
Downloading boot.img
Downloading devcfg.mbn
Downloading vbmeta_vendor.img
Downloading dtbo.img
Downloading imagefv.elf
Downloading oppo_sec.mbn
Downloading dpAP.mbn
Erasing the partition spunvm
Downloading splash.img
Downloading logfs_ufs_8mb.bin
Erasing the partition cateloader
Erasing the partition rawdump
Erasing the partition logdump
Download multi_image.mbn
Erasing the partition catefv
Downloading gpt_main4.bin
Download static_nvbk.bin
Erasing the partition opporeserve1
Downloading emmc_fw.bin
Downloading DRIVER.ISO
Downloading gpt_main5.bin
Restarting
Downloading Firehose protocol file
Sahara communication succeeded
Trying to handshake via Firehose
Configure the settings of Firehose
Get sign data
Verify data
Downloading super partsuper.0
Downloading super partsuper.1
Downloading super partsuper.2
Get basic data
Write patch image to user partition
Restarting
Download succeeded
Get sign data
Verify data
Currently non-implemented/documented also by MSM7125 ?