Database Develop

[EOL] [Rom/Kernel] SM-G935D/SC-02H Marshmallow (May/06/17)

This will be for the SM-G935D/SC-02H Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (Marshmallow)
TWRP 3.0.3-0: https://www.androidfilehost.com/?fid=817550096634747128
Rooted Rom: https://www.androidfilehost.com/?fid=385035244224413763
HKernel for hero2qltedcm:https://www.androidfilehost.com/?fid=745425885120706416
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/android_kernel_samsung_msm8996/commits/tw-6.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969

Reserved

travis82 said:
This will be for the Japanese variant of the s7 edge this is an unlocked model also.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (SC02HOMU1APL2)
TWRP: Coming soon
Debloated Rom: Coming soon
Kernel: Coming soon
Click to expand...
Click to collapse
Can this be used for sm g9350 hongkong?
Sent from my SM-G9350 using Tapatalk

Please use common sense and read ITS FOR THE JAPANESE VARIANT.. READ THE MODEL #. Good gosh stop posting stupid questions dude.

Thanks I'll try this when I get to work.
I can't seem to unlock my bootloader, I'm unable to flash TWRP and enter the recovery. It just says Recovery mode -> Warranty bit set: Recovery and enters into a normal boot after trying it a few times.
Edit:
used the official TWRP and recovery now works. Now trying to install the rom
Edit2:
When trying to install it keeps giving me the following error:
This package is for "SC-02h,hero2qledcm" devices; this is a "hero2qltedcm"
Update process ended with ERROR: 7
Error installing zip file '/sdcard/TWRP/SC-02H_Debloated.zip'
Edit3:
I edited the update-script and removed the assert.
However I don't notice any changes in the rom itself. It still has some bloatware (docomo stuff)

ahh ok i thought it would use sco2h not dcm I can fix that sorry, and I assume twrp is doing the same. I will use a dcm kernel in twrp, let me know if that kernel boots please I dont have the device in hand so I am relying on you all to let me know.
USE crom.apk to unlock bootloader you should find it in galaxy apps store. I'm pretty sure others have unlocked their bootloader doing the same thing. I also used to have someone install my hkroms and kernels on the jap variant so I know you can unlock the bootloader.
CROM: https://www.androidfilehost.com/?fid=385035244224394932
can you unlock the bootloader with that, its a link to what we used to unlock ours.
I need you to unlock your bootloader first please. Sounds like that is the issue.

If I run that app it just exits with Crom Service has stopped working.
Your rom works fine, it has root which is what I needed the most.
Just wish there was a way to remove the sim lock from the device without having to beg Docomo.

I bet I have my asserts all messed up here man I'm sorry. I see SC-02H than hero2qltedcm, than SM-G935D soo I need to get this in the correct order. Would you mind shooting me a pm so I can hangouts you so we can knocks this out quickly?

updated op with twrp recovery and kernel.

This works, root and most of the bloated software is gone

Off topic question (need some insight)
You have started to make a working TWRP for the Docomo variant - thank you for your work (hopefully people in JP using the Docomo version find success).
I know this is off topic but I thought you could provide me with a better understanding.
I am currently using the au KDDI variant (SCV33-Snapdragon) and have successfully installed TWRP (3.0.2-0) with ability to mount /data following xda, youtube, and a Vietnamese forum using google translate; BUT I am unable to keep TWRP ability to mount /data after flashing re-engineered boot file via odin to apply root (Snapdragon Variant Root). TWRP can still be used to go into recovery, mount /ext sdcard, and reboot. I've tried many different styles of rooting after and before installing TWRP, in addition to flashing in different ways - but I still failed. It's either have full working TWRP that can mount /data but without root; or, have root but TWRP that can't mount /data (basically useless as it cannot install anything nor, make backups).
I apologize for such long response, any insight or somewhere you can point me to where I can do more research, as this is how far I have come so far, but still fail to acquire both (Yes I have watched numerous YT vids and read countless post stating devs have not yet found a way on the US-Snapdragon variants, which I understand this may apply to the JP variant too) . Thank you.

With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?

SCV33 looks exactly the same as SC-02H. What's the difference? single sim dual sim? Can you use sc-02h roms for it? I need more information unless you guys want to start donating me devices.

bu06034 said:
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
Click to expand...
Click to collapse
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.

travis82 said:
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
Click to expand...
Click to collapse
First, I really apprecate the work you have put in on bringing ROOT and TWRP to users in Japan. If I can help by doing some testing for you with my DoCoMo model, I'd be happy to do so!
Regarding my original question, I was not talking about an engineering kernel. I was thinking that if I flashed a custom ROM for the SG-935F Hong Kong (Exynos) model, and then flashed your kernel over it, would it work?
As I understand it, the kernel is the interface between the OS and the hardware. Maybe that is ignorant? The reason I ask is because this process was quite common for Japanese S4 users to employ custom ROMs for US S4s; i.e. Flash the US custom ROM (e.g. Mokee or Albee95) and then flash the Japanese S4 kernel onto it.
I understand the question might seem silly to you, but I don't have the hundreds of hours required to reach your level of expertise. I have invested sufficient time to understand much of the jargon; and the tools and methods employed to get root and flash ROMs. More than that, I rely on asking the experts, like you. :good:

you would have to port firmware framework and a bit of other things, secondly hong kong does not self exynos versions here. It's all Qualcomm.

SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82

SCV33 test 1
travis82 said:
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
Click to expand...
Click to collapse
Travis,
TESTED (Semi-working)
I've done some testing on my SCV33 variant using what you've made for the SC-02H.
[Kernel]
I flashed the HKernal Beta 2, using the SC-02H FW, and TWRP Unofficial you've provided onto my SCV33 Galaxy S7e and it is really snappy and fast. Very nice kernel. Any DoCoMo users out there should flash this - though still beta it does the job. I had no problems flashing this in TWRP.
[TWRP Unofficial]
I was able to mount all partitions - works. I had no problem flashing this using Odin.
[Problems I've Encountered]
* After rebooting into TWRP Unofficial many times. My log reads "Unable to mount /steady." I have no idea what this is or what partition it belongs too; but, TWRP is still able to do everything else such as mount /data, wipe /system, etc. - I don't think its a big issue to be honest. Just wanted to let you know.
* After installing everything and everything working fine. I do not/cannot communicate with networks (cannot connect to wifi, cannot call, and no data). I had check SIM status = not available, IMEI = Unknown, SN = Unknown. I had made an EFS back up of my KDDI rom with working network communication and restored with with TWRP Unofficial. Installation via TWRP log has stated successful, but upon reboot problem has not been fixed. Any ideas I should try? I also believe the software from the SC-02H OS handles how im about to connect to data towers and catch frequencies. Putting in my own APN does not work.
* Crom Service.apk you've provided at an earlier comment to unlock bootloader, which I've installed, does not work. All it does is FC when trying to open the app - installation is fine. I had also tried getting one from the internet, and looking for it at the Samsung Galaxy App Store - the internet one does the same, FC. Samsung Galaxy App Store does not have Crom Service available. I am assuming SCV33 wont ever be able to unlock bootloader.
* Debloated Rom Zip does not work, after doing a clean install to Stock Odin, installing TWRP Unofficial, system ext4 format, wiping /system /data /internal storage /dalvikArt /cache, and flashing Debloated Rom Zip with TWRP - states installed successful and boots up. Though upon booting I still have all the bloat there. In addition, many FCs from many different apps, even after reboot (e.g. tap and play, google play store, google services). The rom still functions after a couple more reboots after a /dalvikART cache wipe, but it just doesn't seem as fast as the stock one though. I believe this maybe a conflict due to my device, and myself as well.
----
Oh BTW the SCV33 is:
*SM-G935J
*OS 6.0.1
*Single SIM only
I will try my best do to other methods on trying to get this to fully work, but the Network Communication thing always halts my progress. I really dig this kernel man.
Again, thank you for your hard work and dedication to the Snapdragon Variant its very much appreciated :highfive:. Looking at the Exynos sub-forum I get so jelly at times.

OK is yours has a different modem then the rest. Also your partitions might be a bit different, I really need that device in my hands to look at the partition layout. If you can find SCV33 kernel source I will be more than happy to make a kernel for this variant also. I call my kernels beta because it's just how I do it.
Ok found your source for the kernel I'll check out the configs and maybe make a kernel later on this week.

SM-G935J (SCV33)
Here is a test kernel: https://www.androidfilehost.com/?fid=529152257862698452
Rooted rom: https://www.androidfilehost.com/?fid=529152257862698453
Let me know if there is any issues.

[ROM][UNOFFICIAL][6.0.1][2017/07/06] LineageOS 13.0 XT926 KKBL

Because having my old reliable daily driver gathering dust really bothered me for too long...
This is a plain build of LineageOS 13.0 with the xt926 target. Pretty much everything necessary to build it is already in git, it just doesn't have any official builds or any official LineageOS maintainers. It's an opportunity for someone who still loves this device... I'm going to try to get 14.1 working and hopefully turn this over to someone who has the time to become a LineageOS maintainer for the device.
It requires KitKat bootloader. Your bootloader should also be unlocked (e.g. with Motopocalypse).
This is also my first time building Android and actually using it, so if you think I should have done something differently, feel free to let me know! I've been lurking on XDA for many years and I've learned a lot. This is the first chance I've had to start giving something back.
How I built it
I built this using LineageOS build instructions, just substituted xt926 as the build target and cm-13.0 as the branch. I had to replace external/tinycompress/ because it wouldn't compile; I used upstream Google sources, then it compiled properly.
I pulled missing proprietary blobs from https://github.com/TheMuppets/proprietary_vendor_motorola from the cm-13.0 branch.
Questions
What about LineageOS 14.1?
I plan to attempt to build 14.1 next. But unlike 13.0 it doesn't already have an xt926 build target defined so it's going to take some extra work. If all goes well, I'll be able to post builds in the next few days. If not...
Why don't you support JBBL?
Because it would be a lot of extra work. And from the preliminary look I've taken, it seems that 14.1 will probably require KKBL anyway, and not work at all with JBBL.
Does it work on xt907/xt925?
It should do. I don't have either of these devices so I can't test it and I can't guarantee it. But you can always try it!
Does it work on other phones?
If it's msm8960, then maybe. Otherwise, probably not. But feel free to brick your phone if you really want.
Download
System: lineage-13.0-20170706-UNOFFICIAL-xt926.zip
Recovery: lineage-13.0-20170706-UNOFFICIAL-xt926-recovery.img
Instructions:
Flash recovery from fastboot (optional). You can use the included recovery or some other recovery you already have.
Flash system ZIP from recovery. Flash gapps at the same time before rebooting out of recovery.
Wipe data/cache.
Reboot system and Enjoy!

I'm really interested in flashing lineageOS to my Droid RAZR HD devices. Unfortunately, I think these specs are incompatible:
* System Version: 182.46.15 XT926 Verizon.en.US
* Model Number: DROID RAZR HD
* Android Version: 4.4.2
* Baseband Version: VANQUINSH_BP_100731_020.64.21P
* Kernel Version: 3.4.42-gbd361ac
* Build Number: KDA20.62-15
* Build Date: Tue Jul 29 02:51:09 PDT 2014
Without going through all the tr.apk/motopacalypse.apk stuff, do you know of any way to make this happen? thanks.

I'm really interested in flashing lineageOS to my Droid RAZR HD . Any bugs? thx

Thanks for posting this! I tried installing it on my unlocked Verizon XT926, and got stuck at the animated logo in the boot sequence. I had the same problem with the CM11 M2 snapshot, but CM 12.1 works.
In both cases, I tried wiping data, cache, Dalvik cache, and system multiple times; I reinstalled and re-wiped in different sequences and combinations. (All operations were in TWRP.) I also tried cold booting and booting with and without SIM and SD card. I did not attempt to install GApps.
Bootloader version: 10.9B
Baseband version: VANQUINSH_BP_100731_020.64.21P

pentaflox said:
Thanks for posting this! I tried installing it on my unlocked Verizon XT926, and got stuck at the animated logo in the boot sequence. I had the same problem with the CM11 M2 snapshot, but CM 12.1 works.
In both cases, I tried wiping data, cache, Dalvik cache, and system multiple times; I reinstalled and re-wiped in different sequences and combinations. (All operations were in TWRP.) I also tried cold booting and booting with and without SIM and SD card. I did not attempt to install GApps.
Bootloader version: 10.9B
Baseband version: VANQUINSH_BP_100731_020.64.21P
Click to expand...
Click to collapse
I've had this issue in the past. First wipe your system, I usually do a format data as well (you will lose everything on your internal SD if you do this, external SD should be fine). Install CM 11, reboot to recovery, don't wipe and dirty flash whatever CM/LOS rom you want.

Ok, so I said all of that, and then got stuck for forever. I couldn't use my copy of TWRP 2.8.6.0, I had to use the recovery posted in this thread. I then did a factory reset (full wipe) and was able to install this build and get it to load.
I'd love to see an updated TWRP for KBBL, but I don't think we'll ever get that.
---------- Post added at 01:38 PM ---------- Previous post was at 12:58 PM ----------
Triple posting here:
I got into the system and things ran...ok. I rebooted to recovery and installed the latest opengapps pico package and everything went wrong. The device is now running very slowly and I can't log in to Google. It looks like it's going to work, but sits at "Checking info" for a long time before saying I can't log in. Comparatively, running the JBBL, Photon Q recovery, and latest official Lineage build for the Photon Q works much faster and without issue. I don't like running JBBL, and would rather have a build for my device and not a similar one, but that may be what I need to go back to.
I just tried another flash without rebooting between rom and Gapps and I'm getting stuck at the same point.
Another update:
Just tried opengapps nano package, I was able to get through the sign-in process with this one, but it's running slower with this package than with the pico. I'll give it a try for a couple of days and will try to remember to stop back to leave more feedback. I still need to test voice calls, since they don't work with the photon q (speakerphone works but not the built-in mic)

Well, no audio works. I can't play back local audio, both mic and earpiece are dead, no loudspeaker or speaker phone mic either. Back to 12.1 for now. I'll keep an eye on this thread too. Thanks!

why dont use the LOS13 for de xt 907? that rom runs very well in xt925 with jbbl. All is functional.

@error28, can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that @thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Related thread: https://forum.xda-developers.com/droid-razr-hd/help/xt926-4-1-1-to-lineageos-14-1-t3636103

pentaflox said:
@error28, can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that @thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Related thread: https://forum.xda-developers.com/droid-razr-hd/help/xt926-4-1-1-to-lineageos-14-1-t3636103
Click to expand...
Click to collapse
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat

|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
Click to expand...
Click to collapse
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.

pentaflox said:
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
Click to expand...
Click to collapse
I don´t now another method to downgrade...only with install stock...
But i think it´s relative simple...
In the original JB-Rom edit the "XML" and remove the 2 Lines with "partition_signed" and "tz_signed"...
And flash with RSD
Maybe you should then turn on Wlan, GPS, NFC and Bluetooth before flashing the Nougat-Rom...in the past there were problems when flashing with turn off...especially with Wlan....go´s after that never on
Because of CDMA...I don´t now ...must you test...in the build.prob are lines with CDMA config...but i don´t now the meaning...
konrat

error28 said:
What about LineageOS 14.1?
I plan to attempt to build 14.1 next. But unlike 13.0 it doesn't already have an xt926 build target defined so it's going to take some extra work. If all goes well, I'll be able to post builds in the next few days. If not...
Click to expand...
Click to collapse
Have you had the time and opportunity to try a LOS 14.1 build? I am interested in this as I have an XT905 (basically an xt907 with a different radio) and my build for the KKBL for LOS 14.1 does not successfully boot. I think that maybe/possibly when we go to Oreo that only the KKBL version will work.
error28 said:
Why don't you support JBBL?
Because it would be a lot of extra work. And from the preliminary look I've taken, it seems that 14.1 will probably require KKBL anyway, and not work at all with JBBL.
Click to expand...
Click to collapse
FYI: The fact that people are using my JBBL builds for an XT907/XT905 I think proves LOS 14.1 can run on the JBBL. Its actually one of the most stable ROMs I have personally used.
error28 said:
Does it work on xt907/xt925?
It should do. I don't have either of these devices so I can't test it and I can't guarantee it. But you can always try it!
Click to expand...
Click to collapse
Can someone document the steps they take to convert an XT907 ROM to that of an XT925/XT926?
error28 said:
Recovery: lineage-13.0-20170706-UNOFFICIAL-xt926-recovery.img
Click to expand...
Click to collapse
If someone documents the conversion of an XT907 ROM, maybe I could try and compile TWRP 3.1.1 for the xt925/xt926. Maybe.
error28 said:
Instructions:
Flash recovery from fastboot (optional). You can use the included recovery or some other recovery you already have.
Flash system ZIP from recovery. Flash gapps at the same time before rebooting out of recovery.
Wipe data/cache.
Reboot system and Enjoy!
Click to expand...
Click to collapse
thunder2132 said:
I've had this issue in the past. First wipe your system, I usually do a format data as well (you will lose everything on your internal SD if you do this, external SD should be fine). Install CM 11, reboot to recovery, don't wipe and dirty flash whatever CM/LOS rom you want.
Click to expand...
Click to collapse
FYI: Although its a different phone with a different Kernel, for the XT907 JBBL Nougat ROM's (not Marshmallow) we also had to reformat the Data partition as F2FS.
pentaflox said:
can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
Click to expand...
Click to collapse
And thats the problem, contributors for our aging phones are hard to find, and extending beyond your own computer takes extra work & time. I know I have not placed my work onto GITHUB. I built personally just to get Nougat ResurrectionRemix for me personally, not for the betterment of the world
pentaflox said:
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Click to expand...
Click to collapse
Have you tried taking a Logcat and lookiung at the results? or maybe even posting them on www.hastebin.com in case someone is interested enough to look for you?
pentaflox said:
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Click to expand...
Click to collapse
My brief look at the source code shows that the xt897 and the XT925/XT926 use different touch/display drivers.
---------- Post added at 10:43 AM ---------- Previous post was at 10:42 AM ----------
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
Click to expand...
Click to collapse
Again, any chance you could document what you change to get it to run?
pentaflox said:
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
Click to expand...
Click to collapse
|Konrat| said:
I don´t now another method to downgrade...only with install stock...
But i think it´s relative simple...
In the original JB-Rom edit the "XML" and remove the 2 Lines with "partition_signed" and "tz_signed"...
And flash with RSD
Maybe you should then turn on Wlan, GPS, NFC and Bluetooth before flashing the Nougat-Rom...in the past there were problems when flashing with turn off
Click to expand...
Click to collapse
I personally never use RSD, I explicitly use fastboot to manually upgrade/downgrade my bootloader and recovery etc. The below is expoicitly for an xt905, but should be pretty easy to convert for your device
Code:
mfastboot flash partition "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\partition_signed"
mfastboot flash sbl1 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl1_signed"
mfastboot flash sbl2 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl2_signed"
mfastboot flash sbl3 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl3_signed"
mfastboot flash rpm "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\rpm_signed"
mfastboot flash tz "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\tz_signed"
mfastboot flash aboot "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\aboot_signed"
mfastboot reboot-bootloader
mfastboot flash modem "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\modem_signed"
mfastboot flash fsg "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\fsg_signed"
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash logo "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\logo"
mfastboot flash devtree "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\devtree_signed"
mfastboot flash boot "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\boot_signed"
mfastboot flash recovery "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\recovery_signed"
mfastboot flash system "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\system_signed"
mfastboot flash cdrom "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\cdrom_signed"
mfastboot erase tombstones
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot-recovery
Your partitions may be different, and your files and locations will definitely! be different
|Konrat| said:
Because of CDMA...I don´t now ...must you test...in the build.prob are lines with CDMA config...but i don´t now the meaning...
Click to expand...
Click to collapse
Yeah, hmmm.. we dont have CDMA in Aus either, so I didnt test it. However, I did not remove any explicit CDMA code, but did change the "labelling" of CDMA stuff to remove company names/branding, so maybe that would of broke something

Again, any chance you could document what you change to get it to run?
Click to expand...
Click to collapse
I have nothing changed.
I was on kitkat and flashback to JB with an "JB-O2DE-ROM"..."O2" Is an Provider in Germany
(changed before the xml).
And flash with RSD-light.(it´s btw. only a Gui for Fastboot)
Than i flash your TWRP with Fastboot and than wiped all and reformat DATA and CACHE Partition to F2FS
After that i flash your ROM and Open GApps...booting...
Than i tweak a little bit the build.prob...Display Density to 320... Model Name...Country Code
And Viola... ready
WfG Konrat

|Konrat| said:
I have nothing changed.
I was on kitkat and flashback to JB with an "JB-O2DE-ROM"..."O2" Is an Provider in Germany
(changed before the xml).
And flash with RSD-light.(it´s btw. only a Gui for Fastboot)
Than i flash your TWRP with Fastboot and than wiped all and reformat DATA and CACHE Partition to F2FS
After that i flash your ROM and Open GApps...booting...
Than i tweak a little bit the build.prob...Display Density to 320... Model Name...Country Code
Click to expand...
Click to collapse
I am suprised that TWRP works, as there is explicit code for the screen resolution. The xt907 being 540x960 while yours is 720x1280
As for the ROM, the zip file explicitly checks for specific model no's. Admittedly I do have a couple in there I wasn't too sure of, but I wouldn't of expected them to have worked on your phone.
From whaqt you are saying above, there is no definitive need to actually compile a ROM or TWRP if you stay on JBBL. Its only maybe a KKBL ROM that is "missing"? as the KKBL TWRP works as-is.
PS: No-one as yet has actually given me a good reason to upgrade to KKBL. The only reason I have heard is that it removes the random flash of
the screen when turning on.

Thanks for the help, @DiamondJohn. I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL, and I've learned a lot more about AOSP. I'm running Mokee OS 5.1 at the moment.

pentaflox said:
Thanks for the help, @DiamondJohn. I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL, and I've learned a lot more about AOSP. I'm running Mokee OS 5.1 at the moment.
Click to expand...
Click to collapse
I would really question @|Konrat|, he appears pretty confident in what he does.
As for simply changing the build.prop, I know there are a number of items that cannot be changed except through the source code at compile time. build.prop mainly does visual things in renaming a device. What is really suprising is that the xt907 has different touch/display drivers
As for 5.1, I personally found Lollipop very problematic on my phone. With random reboots and not being able to run my custom live wallpaper.

DiamondJohn said:
As for 5.1, I personally found Lollipop very problematic on my phone. With random reboots and not being able to run my custom live wallpaper.
Click to expand...
Click to collapse
Thanks for the advice. Did you have those issues with Mokee specifically? It's only been two days but Mokee had serious enough problems that I went back to CM.

pentaflox said:
Thanks for the advice. Did you have those issues with Mokee specifically? It's only been two days but Mokee had serious enough problems that I went back to CM.
Click to expand...
Click to collapse
No, from memory, I used to run BlissPop, Carbon and maybe RR. Mokee seemed too close to CM at the time to really get into it.
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
pentaflox said:
I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL
Click to expand...
Click to collapse
One of the surprises I had with people cross flashing my XT907/XT905 buiulds onto other phones is that the first line of the install script/zip checks that the device is an XT907/XT905, It occurred to me if they flash the XT907 TWRP, then it will probably report itself as an XT907, and thereby pass that test/check.
But I am still surprised that the XT907 TWRP works:silly:

|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
Click to expand...
Click to collapse
Can second and confirm this. Both ROM's run great on my RAZR HD MAXX XT926.
RR was too laggy for me personally, it kept rebooting so i decided on crDroid as my daily which so far has been the best ROM i've ever used on this ageing device.
So if anyone is out there still using the RAZR HD as their daily phone give the above a try. They've really given my device a new lease of life and i feel like i'll get another year or two out of it as a result.
Oh and a big thanks for DiamondJohn and the creators behind these ROMs. Thanks!

[ROM][XZ][P][9.0][WEEKLY]OmniROM

XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31

Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs

I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.

Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)

XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.

sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad

opps

I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?

Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.

KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p

Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.

oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.

Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx

Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving

KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread

Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.

XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/

KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated

Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official

anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem

[ROM] TMO Z2 Force 27.1.5 / 27.1.7 FlashAll (Mar/Aug 2019)

This is a Motorola Z2 Flash T-Mobile FlashAll. It is based on @texasaggie1's October 2018 version and does not wipe user data.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Similarities to @texasaggie1's:
The image was downloaded from https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/,
ADB + Fastboot are included
Windows Only (FOR NOW)
Differences:
Updated for 27.1.5 / 27.1.7
Updated included TWRP
Cleaned up batch files
Upcoming Changes:
Bash script version for Linux/Mac
Include TWRP 3.3.1-0 instead of TWRP 3.2.3-2
Batch prompt to install black logo fix
Prerequisites:
Windows
Oreo or newer
Unlocked bootloader
(bootloader) _______: not found OR FAILED (remote: unknown command):
This is a known issue with Motorola devices. Here are some steps you should try:
Try another USB port
Use another ADB version
Try another USB cable
Use Windows 7
How To:
Unzip the Flashall
Open a command prompt in the folder it created
Connect the phone with ADB debugging enabled
Follow the section below based on what you would like to do
Return to Stock
Run flashall.bat
Return to Stock with Root
Run flashall_then_recovery.bat
Choose Install, then select the TWRP installer .zip
Choose Reboot, then Recovery
Choose Install, then the Magisk (recommended), or another SU .zip
Choose Reboot, then System
Return to Stock and Wipe All Data
Run flashall_erase.bat
Downloads
27.1.5 March Flashall
27.1.7 August Flashall - WARNING: USE 27.1.7 AT OWN RISK. Reports of WIFI+DATA bricking on LineageOS
Updated Flashall scripts - Updated 8/28/19, drop into an existing flashall above.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.

Can't Wait to Try It
I will download it later and attempt to update my Z2 (now my wifes )
Thanks for doing this!
What command do I run if I just want to update the phone, but keep all of my data?

texasaggie1 said:
I will download it later and attempt to update my Z2 (now my wifes )
Thanks for doing this!
What command do I run if I just want to update the phone, but keep all of my data?
Click to expand...
Click to collapse
Assuming your on an older build of stock (e.g. 27.1.3) and want to update to this version, flashall.bat will update you. flashall_then_recovery.bat will also upgrade and also setup for installing root. For non-stock builds and newer android versions (Pie) there may be some issues with database versions and other niche issues (e.g. Camera and root based apps storing files in different locations because of new Pie limitations). I always back up all my apps+data using Titanium backup before any changes, helps prevent a lot of hassle.
Edit: Additionally, if you've checked for updates before the updater may still think you have an update. It's best to clear the updater's appdata once the flashall completes. (I may add this to a future version)

rcmaehl said:
Assuming your on an older build of stock (e.g. 27.1.3) and want to update to this version, flashall.bat will update you. flashall_then_recovery.bat will also upgrade and also setup for installing root. For non-stock builds and newer android versions (Pie) there may be some issues with database versions and other niche issues (e.g. Camera and root based apps storing files in different locations because of new Pie limitations). I always back up all my apps+data using Titanium backup before any changes, helps prevent a lot of hassle.
Edit: Additionally, if you've checked for updates before the updater may still think you have an update. It's best to clear the updater's appdata once the flashall completes. (I may add this to a future version)
Click to expand...
Click to collapse
Didn't work for me....it hangs and fails to flash. Here is a screenshot showing how far it gets for me. Ideas?

tr4sh80 said:
Didn't work for me....it hangs and fails to flash. Here is a screenshot showing how far it gets for me. Ideas?
Click to expand...
Click to collapse
I've replied to you in the Z2 discord. I may need to make the file a bit more verbose. I'll update it after work today.

Worked for me, thank you OP. Said update unsuccessful after booting, but the build number shows 27.1.5 now.

Hi, isn't there Screenshot of the rom ?

mf2fx said:
Hi, isn't there Screenshot of the rom ?
Click to expand...
Click to collapse
Define screenshot? A screenshot of the version info? Or are you referring to a system image?

stuck
Mine is stuck like this. Any ideas?

I know this is for T-Mobile, but does anyone have the Verizon one? I am running a Sprint Z2 with Verizon and the update is failing for me :|

Same here
pacotort said:
Mine is stuck like this. Any ideas?
Click to expand...
Click to collapse
I get the exact same. On 27.1.3

How would I install this coming from Lineage 16.0

Thanks so much for this!!

pacotort said:
Mine is stuck like this. Any ideas?
Click to expand...
Click to collapse
Commands aren't being fully sent to the device and are being cut off past a certain point. You can tell because of things like
slot-suffi: not found
partition-typ: not found
Click to expand...
Click to collapse
Do you have another version of fastboot and ADB installed somewhere? Additionally try another cable/USB port.

I was trying to go with LineageOS 16.0 (to get me some PIE!!!) but it kept borking on me... and then I was in boot-loop hell!!! This FlashAll got me back to functional and I may just stick with it. Pie might be newer, but stable & reliable are most important for me. Thanks so much for putting this package together! Maybe T-mobile/ATT/Sprint should hire the devs from this forum to help them 1) get Pie out for the Z2 Force and 2) honor their commitments. Boohoo... it's too much work for them to build & test the package.... but it wasn't too much for them to hold our their hand and take hundreds of $$$ from each of us, was it?

papadelogan said:
I was trying to go with LineageOS 16.0 (to get me some PIE!!!) but it kept borking on me... and then I was in boot-loop hell!!! This FlashAll got me back to functional and I may just stick with it. Pie might be newer, but stable & reliable are most important for me. Thanks so much for putting this package together! Maybe T-mobile/ATT/Sprint should hire the devs from this forum to help them 1) get Pie out for the Z2 Force and 2) honor their commitments. Boohoo... it's too much work for them to build & test the package.... but it wasn't too much for them to hold our their hand and take hundreds of $$$ from each of us, was it?
Click to expand...
Click to collapse
Thanks for the feedback! I do agree that it's extremely disappointing only the Verizon variants are getting Pie, but hey, they gotta upsell that 5G mod somehow...

I am aware of the 27.1.7 update and will be creating an flashall for it soon

Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed

rcmaehl said:
Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed
Click to expand...
Click to collapse
What sort of networking issues? WiFi or issues with service?

rcmaehl said:
Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed
Click to expand...
Click to collapse
Can you post the link to 27.1.7?
I looked on mirrors.lolinet.com and it is not posted there yet.
I will try my own flashall and report back

[Important] Read this before FLASHING/Updating to Stock PIE 9 {SPRINT,TMO AT&T ETC}

[Important] Read this before FLASHING/Updating to Stock PIE 9 {SPRINT,TMO AT&T ETC}
Mates! for newbies specially Sprint,TMO and Atn&t users I know you are sad to hear that you won't get stock Pie update and you have been watching threads here on XDA showing how to flash captured Stock Pie of Verizon/Brazil variant on your Sprint ,at&t TMO variants this very important to know that DO NOT UPDATE/FLASH 9.0 Pie update of Verizon/Brazil variants. Otherwise you will loose your IMEI, Baseband N, modem. AND definitely NO WIFI and there is turning back
That update only works for Verizon/brazil variant devices which are getting updates by Motorola it's not for sprint at&t tmo etc THIS ONLY WORKS FOR VARIANTS WHICH ARE ANNOUNCED BY MOTO.
Reasons: when you flash stock pie your Oreo modem is replaced with Pie modem which doesn't matches to your variant which results in loosing of imei,base band and wifi.
Even if you try to flash back oreo with a clean flash you may be able to use your stock oreo but due to pie modem you won't be able to downgrade to your oreo modem and in result your imei baseband will still be gone with pie and there is no solution haven't been found yet.
Please if you really want to use pie there are other custom roms like Dirty Unicorns, CR Droid,Havoc and Lineage OS use them till the developers found an solution for this problem. Thank you!

just don't flash modem,see no problems.sprint - pie

Can at&t ariants flash it?
As it is locked...

Dreamerok said:
just don't flash modem,see no problems.sprint - pie
Click to expand...
Click to collapse
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?

KOAO said:
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
Click to expand...
Click to collapse
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.

found this
Found this forum:
bbs.ixmoe.com/t/topic/22171
Could be a solution to unbrick ?

Dreamerok said:
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
Click to expand...
Click to collapse
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated ??

gokart2 said:
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated
Click to expand...
Click to collapse
work fine for me. some bugs with wifi (quick connect disconect sometimes)
battery better. twrp * magisk + gpay ) gcam last works perfect. motocamera & motoprojector ? moto verve buds work

Just came to me....there might be a way to revert back firmware. Way back in 3vo 3d days there was a Boost mobile update that had a newer Android version then what the Sprint people got. So many of us flashed it and had problems. And couldn't revert back.
The best kernel dev I've seen to date (name cannot be given due to settlement between him an xda) found he could hex edit the previous bootloaders version number to be post the Boost version, which then allowed it to flash. And we could then revert back to the Sprint firmware/ROM. I don't know how Moto checks or limits firmware flashing, but just an idea?

I have same problem but i had Lineage OS Backup and flashed it. Now I have normal Lineage OS on Partition B and Lineage OS with Problem on Partition A. (Official Rom only uses A partition, Lineage OS supports A/B partition update). I don't know if there is any way to copy B partition IMEI and Baseband on Partition A.

Moto z2 force sprint
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue

Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
can you update what have you done?

Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
I have the same problem. Can I fix it somehow?