Database Info

Moto G (India) - XT1033 - can't FLASH anything (bootloop)

Hi All,
Phone - Moto G 1st Gen (India)
Model - XT1033 (falcon)
data backup - not required. Trying to bring phone to life is only objective. So anyone has any suggestion other than what I am trying below and will make phone alive I do not mind trying.
Phone was working very well before three days . After I did soft reset, it is going in bootloop only.
1. I can access bootloader and recovery menu.
2. I wiped cache, data/factory reset but did not help
3. after reading many threads on xda, so far i did following,
a. unlocking bootloader - done successfully, i can see status code -3 on reboot
b. flashing custom recovery TWRP - shows success on command line but neither i see teamwin logo nor twp recovery (goes back to stock recovery or shows black screen). I also tried CWM but same result!!!
mfastboot.exe flash recovery twrp-3.0.2-0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9330 KB)...
OKAY [ 0.377s]
writing 'recovery'...
OKAY [ 0.185s]
finished. total time: 0.577s​
c. tried booting in twrp successfully, i can access TWRP
mfastboot.exe boot twrp-3.0.2-0-falcon.img
d. flash custom rom
- MTP is enabled by TWRP so moto g is detected in windows so copied Android6.0.1_NX_R10.3.3_MotoG2013.zip
- used TWRP to install it but gets stuck in "patching system image unconditionally" forever...
- Tried other ROMs such as XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml with following steps, shows success but after rebooting I dont see anything happened.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​​
It seems as all the tools/commands are executed successfully but not able to make changes in flash.
can anyone pls. point me or guide me for the solution ahead?
Appreciate your support in advance.
Best Regards,
Jignesh Shah

jignesh_shah said:
Hi All,
Phone - Moto G 1st Gen (India)
Model - XT1033 (falcon)
data backup - not required. Trying to bring phone to life is only objective. So anyone has any suggestion other than what I am trying below and will make phone alive I do not mind trying.
Phone was working very well before three days . After I did soft reset, it is going in bootloop only.
1. I can access bootloader and recovery menu.
2. I wiped cache, data/factory reset but did not help
3. after reading many threads on xda, so far i did following,
a. unlocking bootloader - done successfully, i can see status code -3 on reboot
b. flashing custom recovery TWRP - shows success on command line but neither i see teamwin logo nor twp recovery (goes back to stock recovery or shows black screen). I also tried CWM but same result!!!
mfastboot.exe flash recovery twrp-3.0.2-0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9330 KB)...
OKAY [ 0.377s]
writing 'recovery'...
OKAY [ 0.185s]
finished. total time: 0.577s
c. tried booting in twrp successfully, i can access TWRP
mfastboot.exe boot twrp-3.0.2-0-falcon.img
d. flash custom rom
- MTP is enabled by TWRP so moto g is detected in windows so copied Android6.0.1_NX_R10.3.3_MotoG2013.zip
- used TWRP to install it but gets stuck in "patching system image unconditionally" forever...
- Tried other ROMs such as XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml with following steps, shows success but after rebooting I dont see anything happened.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
It seems as all the tools/commands are executed successfully but not able to make changes in flash.
can anyone pls. point me or guide me for the solution ahead?
Appreciate your support in advance.
Best Regards,
Jignesh Shah
Click to expand...
Click to collapse
Which android version u have in your mobile before bootloop.....?

skyrajparmar said:
Which android version u have in your mobile before bootloop.....?
Click to expand...
Click to collapse
It was android lollipop...

skyrajparmar said:
Which android version u have in your mobile before bootloop.....?
Click to expand...
Click to collapse
It was android lollipop...

jignesh_shah said:
It was android lollipop...
Click to expand...
Click to collapse
1-Reboot into recovery (twrp)
2-Wipe data system cache
3-Flash cm13 zip file.....
4-reboot system
Enjoy

@skyrajparmar, appreciate your response.
I tried your suggestion but result is same.
details:
1-Reboot into recovery (twrp) - success
2-Wipe data system cache - cleaned data/dalvik cache/cache/system successfully using TWRP
3-Flash cm13 zip file..... - using TWRP copied cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip to internal storage (over MTP) and installing using TWRP. It stays in "patching system image unconditionally" forever... I waited for more than 30 minutes and still its going on...
4-reboot system - not done as it does not come out from previous step
Can you suggest if I have missed anything or doing something incorrect or any thing else?

jignesh_shah said:
@skyrajparmar, appreciate your response.
I tried your suggestion but result is same.
details:
1-Reboot into recovery (twrp) - success
2-Wipe data system cache - cleaned data/dalvik cache/cache/system successfully using TWRP
3-Flash cm13 zip file..... - using TWRP copied cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip to internal storage (over MTP) and installing using TWRP. It stays in "patching system image unconditionally" forever... I waited for more than 30 minutes and still its going on...
4-reboot system - not done as it does not come out from previous step
Can you suggest if I have missed anything or doing something incorrect or any thing else?
Click to expand...
Click to collapse
reasons
1-may be your cm12.1 zip file is bad..... try with cm13
2-your system partition may be damaged (fix-repair system n data partition in twrp )

@skyrajparmar,
1. cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip is a snapshot and all CM13 are nightly. since i wanted to use stable than beta, i tried CM12.1
2. as you suggested, i tried wipe ->advanced wipe -> data - success
3. as you suggested, i tried wipe ->advanced wipe -> system - fail with error 4 - unable to repair system (pls see attached image)

jignesh_shah said:
@skyrajparmar,
1. cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip is a snapshot and all CM13 are nightly. since i wanted to use stable than beta, i tried CM12.1
2. as you suggested, i tried wipe ->advanced wipe -> data - success
3. as you suggested, i tried wipe ->advanced wipe -> system - fail with error 4 - unable to repair system (pls see attached image)
Click to expand...
Click to collapse
1-First convert system into f2fs format 2-now convert system into e4ft
3-try again repair function
Q had u tried cm13.....?

@skyrajparmar, as suggested,
1. converting to f2fs - on phone it shows success but when I press back it shows /system as ext4 only. should not it change to f2fs? pls. refer images...
2. converting to ext4 ( i assume there is a typo in your reply where you mentioned e4ft)
3. trying to repair - same error
I am downloading CM13, it will take few more minutes before I can try it...

jignesh_shah said:
@skyrajparmar, as suggested,
1. converting to f2fs - on phone it shows success but when I press back it shows /system as ext4 only. should not it change to f2fs? pls. refer images...
2. converting to ext4 ( i assume there is a typo in your reply where you mentioned e4ft)
3. trying to repair - same error
I am downloading CM13, it will take few more minutes before I can try it...
Click to expand...
Click to collapse
Okay.... try cm13... then reply me..... i m waiting

@skyrajparmar, as suggested, trying cm-13.0-20160617-NIGHTLY-falcon.zip and its stuck into 'patching system image unconditionally...'
FYI- before this, i booted with TWRP and cleaned cache/dalvik/data etc. as usual...

jignesh_shah said:
@skyrajparmar, as suggested, trying cm-13.0-20160617-NIGHTLY-falcon.zip and its stuck into 'patching system image unconditionally...'
FYI- before this, i booted with TWRP and cleaned cache/dalvik/data etc. as usual...
Click to expand...
Click to collapse
Now i m understand whole situation......
System partition of your mobile damaged........ if mobile is still on warranty then send it to service centre
R u living in gujarat.....?

hmmm, thats what i feared.... Not in warranty as its been 2 yrs now.
btw, i m from ahmd but in pune...
thanks for all your support and help....
is there anything else can be done?

jignesh_shah said:
hmmm, thats what i feared.... Not in warranty as its been 2 yrs now.
btw, i m from ahmd but in pune...
thanks for all your support and help....
is there anything else can be done?
Click to expand...
Click to collapse
May be someone's moto g system partition backup help u......

I think i can manage to get /system partition from working motog from someone.
would it be possible for you to provide working steps to do after that?
thanks in advance...

jignesh_shah said:
I think i can manage to get /system partition from working motog from someone.
would it be possible for you to provide working steps to do after that?
thanks in advance...
Click to expand...
Click to collapse
Copy that backup in pendrive(twrp>backups).... n connect pendrive to your moto g .... n restore backup....... but before backup check md5 create box (don't create md5)
if u want it in other moto g Backup must be without md5
Don't say thanks...hit thanks

@skyrajparmar,
is there any difference between using someone's system folder and following commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
would not above list of commands will overwrite /system partition?
I am asking because I have already tried above commands with much of the help!!!

jignesh_shah said:
@skyrajparmar,
is there any difference between using someone's system folder and following commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
would not above list of commands will overwrite /system partition?
I am asking because I have already tried above commands with much of the help!!!
Click to expand...
Click to collapse
Did u tried restore system partition of other moto g......?

No, I am still trying to get /system. I have not got succeeded with getting /system partition as most of the people I know have unrooted device.

Stock xt 1572, RetEu, 7.0 DDumped files.

I was long time at MM sources.
Yesterday, Luis Gonzales created Resurrection Remix 5.8.5 working on Nougat baseband.
https://forum.xda-developers.com/mo...mix-v5-8-3-t3637204/post74686456#post74686456
So I updated my MXS to last N: 25.200-15-3
Before flashing custom I made DD backup of all needed partitions. I didn't try it but I think they are safe.
All can be flashed with fastboot.
System, boot, recovery with twrp too(flash from image).
All without root.
Kernel(boot) is untouched - without root - extracted from supersu backup.
https://mega.nz/#F!814XxZQK!g_INQT-O8ClpNttPc-wg6w
Flashing method:
fastboot oem fb_mode_set
fastboot flash logo logo.bin (unlocked BL warning!!!)
fastboot flash boot boot.img (rename downloaded file)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Only for phones with unlocked BL and N version of BL & gpt.
Fastboot should sparse system.img itself.
Modems only(MM&N):
https://mega.nz/#F!FlxxUZxQ!M9kqWei99LXatwc4LgJORw
Mirror and instructions with comments - post #25
https://forum.xda-developers.com/showpost.php?p=74993383&postcount=25
MM recovery tool post #28
https://forum.xda-developers.com/showpost.php?p=75001459&postcount=28
Big thanks to @Prazaar

valerio32 said:
Modem is EU?
Click to expand...
Click to collapse
"Stock xt 1572, RetEu, 7.0 DDumped files."

valerio32 said:
you can do the ota updates and the recovery is original or is twrp?
---------- Post added at 03:34 PM ---------- Previous post was at 03:16 PM ----------
is normal "Invalid sparse file format at header magi"?
:crying::crying::crying::crying:
Click to expand...
Click to collapse
I don't understand. Upload screenshots somewhere.

valerio32 said:
the phone works, but how can I block the bootloader?
thank you
:crying::crying::crying::crying:
Click to expand...
Click to collapse
You can't untill will be flashable original stock for fastboot.
The same version or upper.
OTA - I don't think will be any more. But If you have last BL version shouldn't be any problems.
Btw
Did you flashed all partitions I uploaded? Only modem, fsg?

CAN NOT.

Hi,brother.could you please backup the bootloader file?

zi_mo said:
Hi,brother.could you please backup the bootloader file?
Click to expand...
Click to collapse
Only with flashfire app(rpm, sbl1, aboot, utags).
Flashfire says - restoring is most dangerous.

Thanks for replying.
My friend has a broken xs_EU with blocked BL by flashing stock_7.0BR,I thought that it would be rescued by flashing you files with gpt of the ota_patches if we got the file bl.
so, we must wait for the stock_7.0EU.

Will this work if I flash these files on my recently debricked (from downgrade) XS on MM 6.01?

Bootloader is still unlocked from the initial install of a custom ROM. But then I bricked it after downgrading from N to stock MM and installing OTA updates.
So just flash these files in fastboot and it should be on Nougat again unbricked?

I don't know.
There isn't bootloader & gpt into these files.
If your BL & gpt are Nougat you can flash it and later install ota updates @Murugan78

BL and GPT should still be N after the downgrade no? It went from MM to N with OTA when I bought it. Last month I installed Lineage ROM but decided to go stock again (and got bricked due to the N bootloader and gpt?). I get the prevalidation error when flashing BL and GPT from the official MM ROM so these must still be N if I am correct. This is my first moto device and I have done some custom things in the past with my S1, S2 and my OPO but never had these issues.
The sparsechunks are not necessary for trying to upgrade?

BL, gpt should be N. @Murugan78

And I can flash the system.img as 1 file instead of all the chunks?

Yes
fastboot flash system system.img

Flashed the files and so far so good! Got an OTA update without problems. Tomorrow I'm gonna test if my SIM works and maybe remove the unlocked bootloader message.
Thanks a LOT!

dzidexx said:
I was long time at MM sources.
Yesterday, Luis Gonzales created Resurrection Remix 5.8.5 working on Nougat baseband.
https://forum.xda-developers.com/mo...mix-v5-8-3-t3637204/post74686456#post74686456
So I updated my MXS to last N: 25.200-15-3
Before flashing custom I made DD backup of all needed partitions. I didn't try it but I think they are safe.
All can be flashed with fastboot.
System, boot, recovery with twrp too(flash from image).
All without root.
Kernel(boot) is untouched - without root - extracted from supersu backup.
https://mega.nz/#F!814XxZQK!g_INQT-O8ClpNttPc-wg6w
Flashing method:
fastboot oem fb_mode_set
fastboot flash logo logo.bin (unlocked BL warning!!!)
fastboot flash boot boot.img (rename downloaded file)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Only for phones with unlocked BL and N version of BL & gpt.
Fastboot should sparse system.img itself.
Modems only(MM&N):
https://mega.nz/#F!FlxxUZxQ!M9kqWei99LXatwc4LgJORw
Click to expand...
Click to collapse
If i flash all with fastboot, i turn back my phone to the lastest N stock version.
I guess that it format internal storage too.

thi3um said:
If i flash all with fastboot, i turn back my phone to the lastest N stock version.
I guess that it format internal storage too.
Click to expand...
Click to collapse
This will format:
fastboot erase cache
fastboot erase userdata
You need it if you was on another version - 6.x or 7.1.2.

mirror online: https://dl.prazaar.de/?dir=Android/Motorola/XT1572/Dumped_Files
edit: The gpt.bin can be easily pulled from an OTA file
and the single bootloader files in: Blur_Version.24.231.13.clark_reteu.reteu.en.EU.zip:
tz.mbn, sdi.mbn, sbl1.mbn, pmic.mbn, rpm.mbn, hyp.mbn, fsg.mbn (but it "about.mbn" is missing)
I working on a Recovery Tool for Moto X Style (EU) XT1572 from 7.0 back to 6.0.1 with working OTAs
No other factory img is needed anymore. you want to be up to date? only OTAs needet for this
bootloader after this up to date!
The Recovery Tool bring you up to 6.0.1 without restriction.
https://dl.prazaar.de/?dir=Android/Motorola/XT1572/Factory/Recovery-Tool / for news prazaar.de

Just a question, I already have my xt 1572 reteu with the build version NPHS 25.200-15-3 like this dumped files, but I miss the October update, can I just flash recovery and boot.img from the dumped files in order to install the security patch? Thanks!!

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.

Bringing volte back to stock based roms -z5 dual e6683

GUYS THIS WORKS REAL DEAL
requirement
1 ) Z5 DUAL with unlock bootlooder
2 ) stock rom ftf E6683_32.4.A.1.54_R2E_India Generic_1298-7547
3 ) twrp recovery
tutorial
1 ) first of all flash stock rom E6683_32.4.A.1.54_R2E_India Generic_1298-7547
2 ) boot and check volte it should working fine
3 ) boot in fastboot volume up key and insert usb cable
4 ) flash twrp recovery
5 ) boot in twrp
6 ) backup TA"trim-area"
Firmware
OEM
LTALabel
modemst1 "baseband"
modemst2 "baseband"
7 ) flash custom rom (I flashed [MROM] [Plus version_v3 .3.9 NEW )
8 ) boot and check everything
9 ) boot into recovery
10 ) restore TA"trim-area"
Firmware
OEM
LTALabel
modemst1 "baseband"
modemst2 "baseband"
FROM BACK UP YOU HAVE TAKEN FROM STOCK ROM.
enjoy folKs AND THANK YOU bhupender kaushik4444 FROM Z5 PREMIUM XDA
SOURCE---https://forum.xda-developers.com/z5-premium/help/z5p-volte-fix-custom-rom-t3882387

[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)

T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.​I have temporarily removed instructions for flashing this firmware until I can test it further.
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!

weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.​Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?

Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update

mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
that's strange, I am able to flash abl fine.

I'm also having this issue.
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing

weakNPCdotCom said:
that's strange, I am able to flash abl fine.
Click to expand...
Click to collapse
Strange it wouldn't work for me my bootloader plus my device have been carrier unlocked for almost two years and I'm converted to the international variant as well I've never had a problem with flashing I guess it's not for me I'll probably convert back to TMobile just to test there update

mjb337 said:
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Click to expand...
Click to collapse
If you have converted to international for all intents and purposes you now have a GSM1917 international. You can install Derpfest and all the other "regular roms". If you do the "manual method" where you flash each partition you should be good to go.
greytheVIIth said:
I'm also having this issue.
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
Click to expand...
Click to collapse
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.

weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.​Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Thank you very much!!!
saved my phone <3

Hi. This rom supports dual sim?

kobebryant said:
Hi. This rom supports dual sim?
Click to expand...
Click to collapse
This is a stock firmware package. Also, it is NOT a TRWP flashable zip. I can make one of those if twrp actually works now.

famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
Would it be possible for you to link me to the source of that TWRP build? I would like to get it on my phone.
Also, that would allow me to build a flashable zip of this firmware.

famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.

weakNPCdotCom said:
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
Click to expand...
Click to collapse
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
TWRP-3.5.1-guacamole-FBEv2-Nebrassy-3.img | by Nebrassy for OnePlus 7 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

famewolf said:
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
Click to expand...
Click to collapse
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD

weakNPCdotCom said:
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
Click to expand...
Click to collapse
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387

famewolf said:
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
Click to expand...
Click to collapse
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone

weakNPCdotCom said:
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
Click to expand...
Click to collapse
Both Derpfest and Yaap work well with fbev2 and are Android 11 based on AOSP. I'm sorry that happened to you. In future you should use "Fastboot BOOT twrp.img" to boot recovery without replacing the existing recovery...then if it didn't work all you'd need to do if force the phone to power off via holding down vol up and power for several seconds. Still not sure how you soft bricked because I tried installing it in recovery on a non compatible rom and all it did was startup and show available storage as 0. It showed no files...once i upgraded the rom then it worked fine.

If you pay attention to with slot you are booting to and flashing to ,it will help out slot. This will always leave you a option to repair. By just switching to the opposite slot to boot to recovery. If you don't know the command then you should really learn fastboot --help. It's all the same as Python.

Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...

Pluginbaby00 said:
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Click to expand...
Click to collapse
I have the extracted payload, but im not sure if it's actually usable on the GM1915. I can upload it if you need it, but there are several partitions you cant flash and the system image is not in the proper sparse format.