Database Info

Help with cm11s!

How to return back to cm11s from Nougat without losing my internal?
Maybe some radio or frimware can help flashing it directly from twrp.
Thanks.

Mr.Ak said:
How to return back to cm11s from Nougat without losing my internal?
Maybe some radio or frimware can help flashing it directly from twrp.
Thanks.
Click to expand...
Click to collapse
Don't wipe internal. Use a flashable zip (search for your preferred build). Nothing else.

Gawd said:
Don't wipe internal. Use a flashable zip (search for your preferred build). Nothing else.
Click to expand...
Click to collapse
But what radio/frimware/modem I should flash first?
I mean I can't directly flash KK over N..

Mr.Ak said:
But what radio/frimware/modem I should flash first?
I mean I can't directly flash KK over N..
Click to expand...
Click to collapse
You can. Just clean flash, I'm not talking about dirty here. If you want the modem that came with CM11S, then you can find it in the respective thread. Otherwise no problem. Happy flashing.

Mr.Ak said:
How to return back to cm11s from Nougat without losing my internal?
Maybe some radio or frimware can help flashing it directly from twrp.
Thanks.
Click to expand...
Click to collapse
You can just flash the fastboot image of CM11S from here: https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Fastboot image includes the firmware.
Use the following commands and you won't lose your internal storage:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Also, if you are not comfortable with fastboot method, you will find the flashable zip in the same thread mentioned above. You can flash that via TWRP.
Here's the modem collection for CM11: https://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
PS: I don't guarantee that this will work, because jumping back from nougat to kitkat is something I never tried myself. Good Luck!

ninjasumit said:
You can just flash the fastboot image of CM11S from here: https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Fastboot image includes the firmware.
Use the following commands and you won't lose your internal storage:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Also, if you are not comfortable with fastboot method, you will find the flashable zip in the same thread mentioned above. You can flash that via TWRP.
Here's the modem collection for CM11: https://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
PS: I don't guarantee that this will work, because jumping back from nougat to kitkat is something I never tried myself. Good Luck!
Click to expand...
Click to collapse
So I have downloaded the fastboot package.
Is there any chance that KK would boot without flashing userdata,as you mentioned?

Mr.Ak said:
So I have downloaded the fastboot package.
Is there any chance that KK would boot without flashing userdata,as you mentioned?
Click to expand...
Click to collapse
It should. But if it doesn't then you can always flash a nougat ROM via twrp.
Also, don't forget to backup your EFS partition.

Mi4 bricked after flashing with fastboot

Hello everybody,
I did a mistake :crying:
On my Mi4 was installed a CyanogenMod 13 ROM. To do this, I resize the phone partitions in the past.
Now I want to update to LineageOS 14.1 but at the installation I got the error: "assert failed cancro.verify baseband mpss.di.4.0 == 1".
At the Lineage Community I found the solution, to install first a newer Stock OS and then the Lineage Rom.
But to install the Stock OS I had to resize the system partitions to the original size.
This article was helping me:
http://en.miui.com/thread-93248-1-1.html
After the successfully resizing, I wanted to flash the cancro_global_images_V8.1.6.0.MXDMIDI_20161230.0000.00_6.0_global
with the FLASHING FASTBOOT MiUI ROMS Guide from xda:
https://forum.xda-developers.com/xiaomi-mi-3/general/guide-flashing-fastboot-miui-roms-t2938279
To flash following parts was successfully:
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
The error was displayed by the "fastboot flash system system.img" command:
I think the resizing zip was wrong.
Now my Phone doesn't display anything. Not fastboot with power+volume down or cwm with power+volume up.
Only my PC is showing me a lot of partitions and two images folders:
Please help me!

everything ok
I found a possibility, to restore the phone
with the old MiFlash Tool. The newer one does not work.
I'm not able to post the link.
It's the link inside this thread:
https://forum.xda-developers.com/mi-4/help/hard-bricked-mi-4s-black-screen-t3512501

Almost everything possible with the tools provided at MIUI forums. Let us know if your device booted up. Good luck!

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!!

I cant flash userdata.img?

Im reverting back to android 6.0 for my k1
But when i go to flash userdata its says userdata isnt found
And i look in the zip and it wasnt there so i downloaded again and it still wasnt there any suggestions
1 more thing nvidias instrucrions say to
Fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
And rhats it do i reboot after blob?
Cause someone elses tutorial says to
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
Tjeres an extra command?
Which do i use?
Thx

Iceek1 said:
Im reverting back to android 6.0 for my k1
But when i go to flash userdata its says userdata isnt found
And i look in the zip and it wasnt there so i downloaded again and it still wasnt there any suggestions
1 more thing nvidias instrucrions say to
Fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
And rhats it do i reboot after blob?
Cause someone elses tutorial says to
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
Tjeres an extra command?
Which do i use?
Thx
Click to expand...
Click to collapse
Don't worry, that one isn't included in the latest Nougat builds as well and they still flash normally.
Just proceed without that

[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.