Database Info

[Q] Two major problems combined completely block my phone

Hi,
so yeah... I got two fatal problems that completely block me from doing anything on my phone.
It started when suddenly my phone's screen turned black, and after a restart it keeps taking me to a screen when it asks for a password to decrypt my data, blocking me from reaching my phone.
So I wanted to recover the phone to fix it, but when i enter fastboot and choose recovery, after a few seconds it shows a picture of the android logo with an exclamation mark on it, and I cannot get into the recovery screen.
Each problem prevents me from fixing the other one, any ideas of how can I save my phone?

Download a custom recovery for crespo. Get your phone into fastmode mode and flash the recovery image.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Then select recovery in fastboot menu.
Encrypt problem is reported in this thread earlier. You may have to do a full wipe and flash a new ROM.

I downloaded the google factory image, but when i run fastboot -w update image-soju-jzo54k.zip (tried two different ones), it fails when trying to write to the system partition (FAILED remote: Write fail).
the other partitions work, but something prevents me from updating the system partition no matter what zip i use, tried many.
any ideas?

Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.

_android_ said:
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
Click to expand...
Click to collapse
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?

loliori said:
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
Click to expand...
Click to collapse
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)

_android_ said:
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
Click to expand...
Click to collapse
ok so soju is the right one for me.
I followed your instructions and now, and it fails writing the system image, the cmd window pretty much looks like that:
checking product...
OKAY
...
... (more ok checks)
sending 'boot'
OKAY
more OK sendings
sending 'system'
OKAY
writing 'system'
FAILED (remote: Write Fail)
I also tried using the batch file and although the window closes before i can see if any error happened, i get the same "FAILWrite Fail" error in my fastboot screen status, so I assume the same problem occurs.

What about formatting system partition via cwm? Failed too?

no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)

loliori said:
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
Click to expand...
Click to collapse
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?

_android_ said:
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
Click to expand...
Click to collapse
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.

loliori said:
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
Click to expand...
Click to collapse
You should Install CM then gapps.

_android_ said:
You should Install CM then gapps.
Click to expand...
Click to collapse
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing

loliori said:
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
Click to expand...
Click to collapse
Google factory images are only flashable via fastboot. But there may be CWMed (cooked) versions available in XDA.

It seems like no matter what rom i flash, it either gets stuck while the phone is loading, or the phone loads and i get this "type password to decrypt" window.
Is there a way to like hard-format my phone, or a way to fix my fastboot flashing problems?

[GUIDE] Sucsessful OTA-Update after Rooting + other system changes

Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
There is no need to relock your bootloader.
The reason the OTA-Update fails, is that one of the /boot, /system, /logo or /recovery partitions are changed.
For example the /recovery if you flashed it permanently or the /boot partition for rooting. Also the /system partition when you remove same build-in apps or install xposed and do not reverse the changes.
To restore the partitions you have to flash the stock ROM Images of the partitions.
That's all you have to do!
Most of you have the problem that they can't find the right stock ROM with the correct build-no. (or don't have access to the FileFactory folder).
In desperation you just download any stock ROM that contain "XT16xx" and flash it, without any idea what you are doing.
And that is the reason your phones lost the IMEI no.
There is also another problem with changing /system or /boot after the OTA-Update, because usually Motorola don't release a stock ROM image which include the OTA-Update when the next OTA-Update should be a major update to the next Android Version (6.0.1 -> 7.0). So when you make some changes to /system or /boot (rooting) after the OTA-Update you have no stock ROM image files of the current build-no and you have to flash the hole stock ROM image and erase all your data and take then two OTA-Updates (6.0 -> 6.0.1 -> 7.0) to get Android 7.0.
This is the reason you should make a TWRP backup of /system and /boot to restore it and then take the next OTA-Update, maybe to Android 7.0.
[GUIDE]
ONLY FOLLOW THIS GUIDE IF YOU HAVE THE CORRECT STOCK ROM IMAGE !!!
STOCK ROM IMAGE FILE NAME MUST CONTAIN YOUR CURRENT BUILD-NO AND SKU (e.g. XT162) OF THE PHONE !!!
I am not responsible for any damage or failure on your smartphone.
Requirements:
Correct Stock ROM Image for your phone -> FileFactory Moto G
Minimal ADB & Fastboot
Motorola Drivers
TWRP - Custom Recovery
1a. If you get the OTA-Update notification
If you are rooted and the OTA-Update notification pops up, download the update and hit the "later" button. Go with your fav. Filebrowser to:
Code:
/data/data/com.motorola.ccc.ota/app_download
and copy the OTA-Update "Blur_Version.2....." file to your SD-Card.
Go to 2. ↓
1b. If you don't get the OTA-Update notification because you already try to install it and get "error 7"
First option is to wait and drink some cups of tea till the notification popup again and try 1a. ↑
Second option is to go to 2. ↓, but then you have no root access till the notification popup up again.
2. Restore the stock ROM images
Extract only the boot.img, logo.bin, recovery.img, system.img_sparsechunk.0 to .7 files to the MADB&FB folder.
Connect your phone to your PC and open MADB&FB, check the connection with:
Code:
adb devices
return should include your "serial-no" and "device".
Reboot into bootloader with:
Code:
adb reboot-bootloader
and check again with:
Code:
fastboot devices
return should be "serial-no" and "fastboot".
Flash the partitions with:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
After every command should be a return with "OKAY".
Reboot your Phone with:
Code:
fastboot reboot
After reboot all your data is still there and you can sideload the OTA-Update, if the OTA-Update notification has not already appeared.
3. Sideload from SD-Card
Reboot into recovery:
Code:
adb reboot recovery
After few seconds the dead "Android" should appear with "No command."
HOLD "Power" and then HOLD "VOLUME UP" for 2-1 seconds and release. Now you are in "Android Recovery".
Select "Apply update from SD card" and choose your "Blur_Version.2..." file.
After 20-30 min you get "success" message and select "Reboot system now".
4. Make a backup of /system, /boot, /recovery and /logo
Before you can make some further changes on your /system, /boot, /recovery and /logo, you should backup these partitions for the next OTA-Update.
Follow all steps in the Guide to root systemless -> [ROOT][GUIDE] Systemless Rooting with SuperSU 2.78 , which include the TWRP backup (/system and /boot).
Then come back here and install on your rooted phone -> Partitions Backup & Restore.
Select "LOGO" and "RECOVERY" and change Settings to "Raw partitions image (img)" and save it on your SD-Card.
Now you have all partitions as a backup for the next OTA-Update. So when the next update is coming, you have to flash /logo and /recovery and then restore your TWRP backup and you are able to install the update without issues.
Have Fun and don't pay attention to my writing errors

Bender1987 said:
Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
You can root your phone again with this GUIDE after the update -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
There is no need to relock your bootloader.
Click to expand...
Click to collapse
I used this procedure a couple of days ago and it worked flawlessly. When I rebooted after flashing all of the stock files, my OTA update notification was there waiting for me to select "Install". I did and it installed without issues.
What is surprising to me is how many people try it with the wrong firmware and then are surprised when they screw up their phones.

I was so close!!! lol, didn't realize they checked /logo for modifications. Was about to completely wipe everything to get the update to apply. Glad I checked xda before doing so as all I was missing was flashing stock logo.img (restoring system, recovery and boot I had already tried). Thanks Bender1987 for the easy guide.
I have the 64GIG 4G plus (XT-1644)

Hi @Bender1987,
Thank you for your guides, they are very helpful. I've already unlocked, rooted without flashing twrp, uninstalled some system apps and flashed xposed using Flashfire on my xt1642, and eveything is running fine so far. So, when an OTA update is available (hopefully nougat!) will I receive the notification? Or does the rooting stop even OTA notifications? Thanks!

@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.

Bender1987 said:
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Click to expand...
Click to collapse
I just got my xt1642 a week ago. It already came with build number: MPJ24.139-48 which I think is the latest, so I haven't received any OTA update yet.

@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.

Bender1987 said:
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Click to expand...
Click to collapse
Well, I spent 2 days without touching the phone before unlocking/rooting and didn't receive this ota-update. Maybe it is not available for my version (32gb, 3gb ram, xt1642)...
If I didn't flash twrp, I guess I won't need to restore it, right? Anyway, I made the full backup following your instructions. In which partition is stock twrp included? Boot? Thanks.

Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.

Bender1987 said:
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Click to expand...
Click to collapse
Let me know if I understood it right. I made a TWRP backup of untouched boot, system and data, rooted and installed xposed without flashing TWRP and without changing logo.bin. Then I should be able to install next OTA update if I previously restore my copies of boot and system in TWRP. Right? No need to flash stock images in this case? Thanks!

@pblasi jep you are right

Xt1644 not play nice with adb nor does it go into recovery it just reboots when I hold the buttons...or it stays on no command

All devices have stock recovery on it. I tried it again, when you see the dead Android -> HOLD POWER and then HOLD VOLUME UP for 2-3 sec. -> release VOLUME UP and still HOLD POWER
https://www.youtube.com/watch?v=SuOrl7Q4JY8
at 1:58.

When I flash the files, for the boot and recovery I get a warning that the "image not signed or corrupt". Eventually it is written... but is that normal?
mfastboot flash recovery recovery.img
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
Image not signed or corrupt
OKAY [ 0.153s]
finished. total time: 0.684s
Click to expand...
Click to collapse

@SoNic67
Maybe it is not the correct stock rom?

Hmm, it was DL from the usual place, but true, I am not 100% sure about it. However, it "works" but I don't get the OTA.
I am DL now the newer full FW.
LE: That latest full FW worked. I had to reinstall all my apps from backup but...

Weird thing is that before my imei disappeared I was getting the ota updates
Sent from my 6045X using Tapatalk

@Bender1987 I have a TWRP backup of unmodified Stock ROM XT1643, so now to install OTA do I just have to flash the nandroid backup & then flash stock recovery to get ota updates? If so then how can I go about flashing stock recovery. Thanks in advance mate

@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.

Bender1987 said:
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Click to expand...
Click to collapse
Will try

Bricked stock recovery and no flashable update.zip on Mate8 NXT-TL00 with L29 oeminfo

Hey guys,
I was using a NXT-TL00 with Android 7.0 and EMUI 5.0 and I wanted to change to a international ROM with Nougat and EMUI 5.
My current situation:
I unlocked the bootloader.
I can boot into fastboot and flash twrp-3.0.2-0-next.img
I can boot into that TWRP and flash MATE8-TL00-EMUI5.0_B577.zip. (Thanks again, paulcl!)
I can boot into that ROM and use it.
I changed my oeminfo and custom.bin from TL00 to L29 via SRKToolHuawei. Afterwards I had to unlock the bootloader again.
I tried to:
extract various update.zip (update.app inside of the zip) via HuaweiUpdateExtractor_0.9.9.5.
flash the extracted boot.img, recovery.img, system.img via fastboot manually and SRKToolHuawei.
wipe and format data, dalvik, cache, system in- and excluding reboots in every possible variation.
use different TWRP versions.
However:
I can't boot into stock recovery (even after flashing it).
I can't boot into eRecovery.
I can't flash any update.zip oder other ROM besides the one above. Why?
Using eRecovery or stock recovery won't work since I can't boot into it.
TWRP would print this error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link typ file...
write radio image...
check_write_data_to_partition, write data error
E:unknown command [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NXT-TL00C01B575/update.zip'
I can't flash any system.img via fastboot. I would get this error:
fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (452422 KB)...
OKAY [ 13.007s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 13.045s
What I want:
A fully working TWRP so I can simple flash an update.zip
A working (stock?) L29 ROM with Android 7 or 6 and Emui 5 or 4 and preinstalled GAPPS.
A working stock recovery and erecovery
OTA support
the possibility to lock bootloader when everything else is working
What might help:
A ROM which won't touch the data partition so I can install it trough TWRP.
Maybe there is a way to put the system.img into a flashable zip-file so I can flash the partition via TWRP so there won't be the error message from fastboot. Unfortunately, I have no idea how to do that. An TWRP doesn't allow to flash system.img directly.
BTW:
My current model number is: NXT-L29
My current build number is: "NRD90M test keys"
EMUI-Version 5.0, Android Version 7.0
Thanks for reading through my text. It would be great if there is someone to help me out here!

hello i have the EXACT same problem except i was on a l29C at the beginning..
i m stuck here 2 days now
if somebody have a solution i greatly appreciated

Install stock kernel and the use hisuite

asphaltkiller said:
hello i have the EXACT same problem except i was on a l29C at the beginning..
i m stuck here 2 days now
if somebody have a solution i greatly appreciated
Click to expand...
Click to collapse
I already found a solution which is not perfect yet. First, I tried to follow the instructions from
How to install NXT-L29C432B560 (Official) Stock Firmware. (Guide with download links) by sillanwali.
Very helpful for me was post #49. I recommend to read through the first post and then coming back and follow the instructions below.
First, you need:
TWRP 3.0.3 (...3 is for Nougat)
this update.zip
MATE8-TL00-EMUI5.0_B577.zip
The procedure might be too long with redundant steps, but it worked for me. So give it a try:
Unlock bootloader
Flash twrp via fastboot(3.0.3 is for Nougat)
fastboot flash recovery twrp-3.03.img
fastboot reboot​
Boot into TWRP
Copy update.zip and MATE8-TL00-EMUI5.0_B577.zip to SD.
Wipe>format Data>yes
Wipe>Advance wipe >data, dalvik, cache, system
Install this update.zip linked above.
Try to reboot into system. Mine didn't boot into system, but stock recovery and erecovery are now installed. Go on!
Flash TWRP again (since it's overwritten by stock recovery. No worries - you now can now easily flash back stock recovery).
Boot into TWRP.
Copy MATE8-TL00-EMUI5.0_B577.zip to SD Card.
Again, do a full wipe.
Install MATE8-TL00-EMUI5.0_B577.zip.
Reboot into system. It now should work, however it's the Chinese version.
Extract the update.zip and copy update.app to a new created DLOAD folder on the SD Card.
Do a factory reset.
Flash the stock recovery via fastboot (or TWRP). You will get the image by extracting recovery.img of update.app with HuaweiUpdateExtractor.
Reboot into recovery to install the update.app (automatically).
Now you should be on NXT-L29C432B560.
If you want to use the update_data_full_hw_eu.zip or SuperSu follow the instructions in the How-to-install guide.
To be clear, I still have a few problems:
erecovery would boot but when I am trying to restore via wifi I will get the error: "getting package info failed"
Bluetooth and NFC are not working.
Maybe someone has a solution for that?

sebastjon said:
Bluetooth and NFC are not working.
Click to expand...
Click to collapse
Make the installation again!

Bricked ERROR MODE Func NO : 8 Error NO : 1

Hi,
Yesterday I've tried to rebrand my phone FRD-L09C432 to FRD-L09C10 version. It succeeded and I was in EMUI 4.1.
Then i tried to use hackslash's method to flash android O. While flashing the rom with HuRupdater I've go an error.
Now my phone is bricked in
ERROR MODE
Func NO : 8 (hifi image)
Error NO : 1 (security verify failed)
I've been able to go to fastboot once, and i unlocked bootloader again, but now I can't go back to bootloader anymore.
I've tried every button combination and i left my battery drain to 0% but still no success.
If anyone of you got an idea, I'd be grateful

Did you tried to update your device to Oreo directly from EMUI 4.1. My guide clearly said that you need to flash Nougat package and not Marshmallow one before flashing Oreo.
Regardless, your device is screwed unfortunately and you can't boot your device to fastboot is problematic. I guess you also can't reboot your device to recovery since after you performed the unlock the device has to perform a factory reset and since it's unable to perform it, it has locked you out of fastboot. When I was stuck in this situation, I discharged the battery completely and connected it to PC while holding the volume down button to force it into fastboot. I had to do it several times until it finally worked. After that flash TWRP to your device immediately. Reboot your device to recovery by connecting it to PC and holding the Volume Up button instead. TWRP will allow you to flash a PV package and restore your device.
If you're still unfortunately unable to get your device up and running you have to use DC Phoenix to restore the firmware (it's a paid solution, costs 15 Euros).

hackslash said:
Did you tried to update your device to Oreo directly from EMUI 4.1. My guide clearly said that you need to flash Nougat package and not Marshmallow one before flashing Oreo.
Regardless, your device is screwed unfortunately and you can't boot your device to fastboot is problematic. I guess you also can't reboot your device to recovery since after you performed the unlock the device has to perform a factory reset and since it's unable to perform it, it has locked you out of fastboot. When I was stuck in this situation, I discharged the battery completely and connected it to PC while holding the volume down button to force it into fastboot. I had to do it several times until it finally worked. After that flash TWRP to your device immediately. Reboot your device to recovery by connecting it to PC and holding the Volume Up button instead. TWRP will allow you to flash a PV package and restore your device.
If you're still unfortunately unable to get your device up and running you have to use DC Phoenix to restore the firmware (it's a paid solution, costs 15 Euros).
Click to expand...
Click to collapse
Thank you for the answer.
Btw, can DC Phoenix helps me even when I don't have access to the bootloader? Or do I need first to find a way to go into bootloader

Elyth_ said:
Thank you for the answer.
Btw, can DC Phoenix helps me even when I don't have access to the bootloader? Or do I need first to find a way to go into bootloader
Click to expand...
Click to collapse
DC Phoenix can help you even if the bootloader is not accessible. For that you have to disassemble your device and follow the DC Phoenix Method 3 aka Test point method to flash board software package and then the complete OS.

hackslash said:
After that flash TWRP to your device immediately.
Click to expand...
Click to collapse
HI again, I'm actually in bootloader mode, but flashing TWRP gives me the error FAILED (remote: partition length get error). Do you have any idea on what's causing it ?
EDIT : fastboot flash recovery_ramdisk <your file as usual> worked
EDIT 2 : can't get to reboot in recovery after flashing with that command
EDIT 3 : When I try to reboot to recovery, I get the screen saying "Your device has been unlocked and can't be trusted..." but then I have the error Func NO : 11 (recovery img) Error NO : 2 (load failed!)

Elyth_ said:
HI again, I'm actually in bootloader mode, but flashing TWRP gives me the error FAILED (remote: partition length get error). Do you have any idea on what's causing it ?
EDIT : fastboot flash recovery_ramdisk <your file as usual> worked
EDIT 2 : can't get to reboot in recovery after flashing with that command
EDIT 3 : When I try to reboot to recovery, I get the screen saying "Your device has been unlocked and can't be trusted..." but then I have the error Func NO : 11 (recovery img) Error NO : 2 (load failed!)
Click to expand...
Click to collapse
What TWRP are you trying to flash? I recommend flashing Honor View 10 one from twrp.me. After you install it and you're able to boot to recovery, ping me back.

hackslash said:
What TWRP are you trying to flash? I recommend flashing Honor View 10 one from twrp.me. After you install it and you're able to boot to recovery, ping me back.
Click to expand...
Click to collapse
Unfortunately I tried to use DC Phoenix to flash L09C10 EMUI 4.1 ROM, and this is what I got
Code:
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 73QDU16B03003820
7/15/2018 8:57:52 PM Starting extracting partitions from file UPDATE.APP
Current version: FRDC432B001
Cannot create extract directory: D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\tmp\20180715_205752_UPDATE\
Extract files to directory: D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\
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: CUST OK
Extracting partition: MODEM_DTB OK
7/15/2018 8:58:16 PM Extracting partitions finished OK
7/15/2018 8:58:17 PM Starting to write device in FASTBOOT mode...
Device found: 73QDU16B03003820
IMEI: 861349039027486
Build number: :FRD-L09C10B130
Product model: FRD-L09
Writing XLOADER partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\BOOT.img
BOOT partition UPDATE ...FAILED
Writing RECOVERY partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\RECOVERY.img
RECOVERY partition UPDATE ...FAILED
Writing RECOVERY2 partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\RECOVERY2.img
RECOVERY2 partition UPDATE ...FAILED
Writing DTS partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\DTS.img
DTS partition UPDATE ...FAILED
Writing MODEM partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\SYSTEM.img
SYSTEM partition UPDATE ...FAILED
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\CUST.img
CUST partition UPDATE ...FAILED
Writing MODEM_DTB partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
7/15/2018 8:59:35 PM Writing device finished - INCOMPLETE
Waiting for fastboot device...
Device found: 73QDU16B03003820
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
Process was cancelled by user
Then my phone shutdowned and doesn't turn off anymore

Elyth_ said:
Unfortunately I tried to use DC Phoenix to flash L09C10 EMUI 4.1 ROM, and this is what I got
Then my phone shutdowned and doesn't turn off anymore
Click to expand...
Click to collapse
Well I won't lie, you're in the exact same situation I was in. However even if your phone doesn't turns on, it's still in fastboot mode. Connect it to PC and check fastboot if it is connected. If not hold down the power button to force a restart and then hold volume down button and reconnect the phone to PC. As soon as fastboot detects your device, use DC Phoenix to again flash the EMUI 401 firmware. This time it will flash successfully.

nothing

hackslash said:
Connect it to PC and check fastboot if it is connected. If not hold down the power button to force a restart and then hold volume down button and reconnect the phone to PC. As soon as fastboot detects your device, use DC Phoenix to again flash the EMUI 401 firmware. This time it will flash successfully.
Click to expand...
Click to collapse
Idk, I try every button combination but the screen stays black and fastboot isn't connected

Screen didn't turned on for me too. But I guess I was lucky enough that the device was in fastboot mode and I was able to flash the firmware.
Your only choice is the Method 3 now, the Testpoint method.

hackslash said:
Screen didn't turned on for me too. But I guess I was lucky enough that the device was in fastboot mode and I was able to flash the firmware.
Your only choice is the Method 3 now, the Testpoint method.
Click to expand...
Click to collapse
I simply don't know how to thank you enough. Changed the USB port and my phone is now connected in fastboot mode.
I flashed again with DC Pheonix, it failed again, but my phone restarted and screen turned on. Bootloader was again locked, I unlocked it again and then flashed TWRP from the TWRP Honor 8 Guide.
Now I'm finally back in TWRP, which firmware should I flash ? I'll follow exactly your instructions ahah :laugh:

Elyth_ said:
I simply don't know how to thank you enough. Changed the USB port and my phone is now connected in fastboot mode.
I flashed again with DC Pheonix, it failed again, but my phone restarted and screen turned on. Bootloader was again locked, I unlocked it again and then flashed TWRP from the TWRP Honor 8 Guide.
Now I'm finally back in TWRP, which firmware should I flash ? I'll follow exactly your instructions ahah :laugh:
Click to expand...
Click to collapse
That's excellent. Before I tell you which firmware to flash, what was your device region before all of this happened.

hackslash said:
That's excellent. Before I tell you which firmware to flash, what was your device region before all of this happened.
Click to expand...
Click to collapse
L09C432, European/French

Elyth_ said:
L09C432, European/French
Click to expand...
Click to collapse
Okay, what you should do is, flash L09C432 oeminfo.img from TWRP (you can check Huawei MultiTool for the image). After that perform a complete factory from TWRP. Don't reboot your device yet.
Then, flash B394 firmware (FullOTA-MF-PV one) and ensure you flash all the files available for that firmware (two files). Once the flash is complete reboot your device and you're on EMUI 5. You can then use Firmware Finder to update your device to latest package authorised for your device.

hackslash said:
Okay, what you should do is, flash L09C432 oeminfo.img from TWRP (you can check Huawei MultiTool for the image). After that perform a complete factory from TWRP. Don't reboot your device yet.
Then, flash B394 firmware (FullOTA-MF-PV one) and ensure you flash all the files available for that firmware (two files). Once the flash is complete reboot your device and you're on EMUI 5. You can then use Firmware Finder to update your device to latest package authorised for your device.
Click to expand...
Click to collapse
Thanks i'll sure try this out ! Just in case, "complete factory," means factory reset not format data right ?

Elyth_ said:
Thanks i'll sure try this out ! Just in case, "complete factory," means factory reset not format data right ?
Click to expand...
Click to collapse
Yep!

hackslash said:
Okay, what you should do is, flash L09C432 oeminfo.img from TWRP (you can check Huawei MultiTool for the image).
Click to expand...
Click to collapse
Another question, Huawei Multitool is mainly in russian and i don't understand a single word of it so I'm kind of lost. How should I get the image with that software ?

Elyth_ said:
Another question, Huawei Multitool is mainly in russian and i don't understand a single word of it so I'm kind of lost. How should I get the image with that software ?
Click to expand...
Click to collapse
Try this version http://pro-teammt.ru/projects/hwmt/release/Multi-Tool 8.msi
It's GUI and should prompt you to select language or atleast changing language would be easy.

hackslash said:
Try this version http://pro-teammt.ru/projects/hwmt/release/Multi-Tool 8.msi
It's GUI and should prompt you to select language or atleast changing language would be easy.
Click to expand...
Click to collapse
It seems to be the one I had, anyway i'll do some research bc the GUI is still almost only in Russian even when I select English.
When i click Launch Huawei MultiTool the CMD is in Russian even tho English is selected
EDIT : Nevermind, I found a tutorial I did it.

Nexus 5 deleted data partition

Hi there,
So I wanted to resize the system partition so I could install GApps. I accidentally deleted the data partition somehow (deleted not corrupted). I can go into bootloader and recovery, my bootloader is unlocked so I can flash any recovery I need to but I can't boot Android. Any ways to redo the partition table or manually add the userdata partition?
Thanks in advance.
Edit: I was able to fix the partition by creating a partition called "userdata" with parted, but now my phone is constantly rebooting and it cant be the power button because when powered off or in bootloader, it doesnt automatically turn on. Any help?

KevinKraze said:
Hi there,
So I wanted to resize the system partition so I could install GApps. I accidentally deleted the data partition somehow (deleted not corrupted). I can go into bootloader and recovery, my bootloader is unlocked so I can flash any recovery I need to but I can't boot Android. Any ways to redo the partition table or manually add the userdata partition?
Thanks in advance.
Click to expand...
Click to collapse
I would start fresh and flash the last factory image using fastboot
Then follow this guide for repartitioning... https://forum.xda-developers.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/

Lughnasadh said:
I would start fresh and flash the last factory image using fastboot
Then follow this guide for repartitioning... https://forum.xda-developers.com/t/recovery-unofficial-twrp-hh-for-nexus-5-hammerhead.4047653/
Click to expand...
Click to collapse
I have tried to flash the factory image, but as I said, the data partition is deleted so nothing works

I got it to work by manually creating a partition with parted and called it "userdata" After I just flashed the userdata.img file and everything seemed to work!