Database Develop

A new Start !!

Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not iirc <71.08 shouldn't be flashed onto 71.08 existing BL right or was it 71.10 ?? (idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all. Heard a few CM roms had BL packed into ROMs and the updte to 5.1.x + lower BL caused hardbrick, a.k.a bootloop + noTWRP with Fastboot lockedout ).
So here's my to-do list sorry to post this long but seems like this is start for me....Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & Nexus 6 information....
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - MultiROM working guide on 5.1.1 plus M latest release anyone, will try the official thread tho, any info on whre to start would be awesome !!
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful posts/threads that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!

Ashtrix said:
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not(idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all). So here's my to-do list sorry to post this here but seems like this is start for me.Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & a few Nexus 6 information, any useful links would do the job.
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - Does MultiROM work on 5.1.1 plus M latest release ?
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful links that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Click to expand...
Click to collapse
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use

AlkaliV2 said:
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
Click to expand...
Click to collapse
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..

Ashtrix said:
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Click to expand...
Click to collapse
I'm pretty sure mFastboot is made directly for a Verizon variant, but since the Nexus 6 is unlocked and your Verizon SIM card dictates the network you are on, I would say stick with normal Fastboot for your flashing endeavors. Good luck and read twice, flash once :good:
Edit: Quick side note, love the avatar. Good choice.

Thankyou :highfive:
Just did an OEM unlock and wierdly after that, the bugdroid loading doesn't end at all. Did an factory img flash of 5.1.1 Shamu-LMY48Y and booted in less than a min Lol.
And yes the fastboot is working, wow things are definitely wierd with Shamu (volume normalization, mFastboot previous xperience, bootloader bricks...seems like Qcom fixed that after CM brickbug and no one can help the manual bricking) but I'm ok with all these , just love this device, massive, powerful and sexy looking piece
EDIT :
Well everything's going fine but this bugdroid loading doesn't seem to be fixed at all, after bootup 23Gb was there so I did a format and again stuck, this time around I tried using TWRP to flash (CM12.1)after doing fastboot commands - fastboot format userdata, cache. Now it says unable to flash on so&so data partition, So formatted from the OS and now MTP says generical heirarchial. I don't remember any device with that format...
EDIT 2 : Device won't boot with that bugdroid formatting the Data partition. Needs to be fastboot flashed else stuck there forever again same 23Gb bootissue if I do that & Using fastboot format userdata command it formats into the 64GB - 54Gb available space but with TWRP It fails to flash - the same error, can't flash on data parition. So repeat fastboot and it's a damn cycle. Will try to flash MM if it won't then. I may have to return again...OMG
EDIT 3 : http://forums.androidcentral.com/go...ys-formatting-data-yellow-text-any-ideas.html
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-formatting-data-t2737793

EDIT : Tried MM and after 10 mins formatted succesfully now gotta try a ROM or any, hope its fine !!

Again the GH FS is back with MTP and doesn't flash at all with TWRP. If I go for a re-lock and it it fails to boot with formatting properly...then bam nothing but a bricked Nexus !!
TWRP did the format but the device is messed up, sliptscreen issue..
I'm going to return this, enough of the hassle had me messed up totally :crying:
Seems like 6P seems better than having all these issues. Or wait for the 2016 device...
EDIT : Sorry for the GH format seems like it's normal, but the flashing issue is too wierd..

I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.

scryan said:
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
Click to expand...
Click to collapse
I know this issue, just a factory reset fixed this thing on my old N6 that I had for 2 days, but this takes too much of time to format....Just had TWRP do the job and flashed the Temasek but ALAS !! Splitscreen issue.

Progress towards Root/Twrp/Roms

This thread is strictly for info regarding Root/Twrp/Roms
If you have any ideas or have tried anything please post here
I AM IN NO WAY A DEV ,i am using google and common sense
Here is the link to the sprint boot.img (https://drive.google.com/file/d/0B9Vkl8ldvnNdOGlyLW4wOXNDRUk/view?usp=drivesd)-Thanks to @XirXes
Heres what i have tried
-So far i have tried signing the sprint boot.img to magisk with no luck,it gives me files are read only errors.I was able to get past the the first two steps of this post for systemless root via adb (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
-Flashing the stock sprint boot.img to confirm compatibility hint hint its compatible
ROOT HAS BEEN ACHEIVED!!
UPDATE- As of 9/13/17 we now have root in the form of a patched boot.img thanks to @themustached for patching the boot.img so gracefully for us
To install the boot img you need to reboot to fastboot and run the command "fastboot flash boot (name of boot.img).img
https://drive.google.com/file/d/0B8kodjBRTHoZR2Zob1VLX0xOVkU/view?usp=sharing
Just a update as I have been away from this phone for a bit
We have kernel source now (like 2 months ago) and there are 3 AOSP ROMs that I know about being worked on so far I don't know any details or anything but what I do know is that they completed the build process they are working on getting it running on our phone
joemossjr made the the ncp Rom and got TWRP for us so big thanks to him!
Substratum works on legacy with root and newest version of TWRP just in case anyone was wondering.

https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing

joemossjr said:
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
Click to expand...
Click to collapse
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.

altimax98 said:
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
Click to expand...
Click to collapse
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk

I have insurance and I'm willing to risk my device worst case,it's not a problem,I've noticed if you boot it,it doesn't like to set correctly

joemossjr said:
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
Click to expand...
Click to collapse
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk

Downloaded them all found no recovery

Verified ATT & Sprint boot.img works om Tmobile
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!

bart bart said:
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
Click to expand...
Click to collapse
We are all in this situation. It is likely going to be quite some time before we get root due to the dual partition system.
Based on the Pixel info, we need TWRP first
Sent from my Moto Z (2) using Tapatalk

The recovery is in the boot.img of 7.1 and up devices

Dumper US Cellular Boot.img
altimax98 said:
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Here is dumped boot.img of US Cellular Boot.img. There is a recovery under sbin folder. Hopefully you can make a bootable TWRP from it?
https://www.dropbox.com/s/hjfr8wj2da...ootus.zip?dl=0

If anyone wants to join our efforts the let us know and we can add you in

I want to join your efforts.

Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.

joemossjr said:
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
Click to expand...
Click to collapse
Thank you
Sent from my SM-N930F using XDA-Developers Legacy app

Deleted

Any progress? Anything I can do to help? I have T Mobile variant with unlocked bootloader.

We brought in another guy from the pixel forum who made their twrp recovery he's going to take a look and see what can be done

Question before I delve further.
fastboot -i 0x2b4c flash:raw boot <kernel> [ <ramdisk> ] rather than just flash <partition> [ <filename> ] perhaps for the twrp? Just a spit ball idea as I wrap my head around. Been a few years since I bothered with phones rather than.. other systems. I'm sure this round probably already been tried but curious of the turn before I fry the new toy xD.

joemossjr said:
If anyone wants to join our efforts the let us know and we can add you in
Click to expand...
Click to collapse
I can test stuff when the time comes.

[STOCK] [LG-H872] [Oreo_20a] TWRP Flashable Zips:

LG G6 Oreo 20a​
Note: I know someone created a complete flashable, But I wanted all 3 packages like @autoprime does.
WARNING: Understand my meanings behind, B1,B2 and C1, C2:
B1: Means Bootstock with LAF
B2: Means Bootstock without LAF (Normally H872 users have TWRP on LAF)
C1: Means Complete with LAF
C2: Means Complete without LAF (Normally H872 Users have TWRP on LAF)
All zips check contents with sha1, all zip files are md5hash listed:
LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF) [md5hash:a52e86bd30ca0b4725c1839eb1ad38d3]
LG-H872_Oreo-20a_Bootloader_B2.zip (WO/LAF) [md5hash:7c72ae1f5b82ba54dcc9b7007754ebf9]
LG-H872_Oreo-20a_Modem_Only.zip (Safe Either Way) [md5hash:2f3ad7cd2c468a0d50f52094ad2643f6]
LG-H872_Oreo-20a_Complete_C1.zip (W/LAF) [md5hash:172d01c25cc308a1c2c39def6d13918e]
LG-H872_Oreo-20a_Complete_C2.zip (WO/LAF) [md5hash:7b17a29044d98fe1883ec9fe0e9c9b93]
DOWNLOADS:​
LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF)
LG-H872_Oreo-20a_Bootloader_B2.zip (WO/LAF)
LG-H872_Oreo-20a_Modem_Only.zip (Safe Either Way)
LG-H872_Oreo-20a_Complete_C1.zip (W/LAF)
LG-H872_Oreo-20a_Complete_C2.zip (WO/LAF)
All Future Firmware Updates Will Be listed Here: lg-g6-stock-firmware/H872_T-Mo/

WARNING:​
Complete's have unmolested system images But no Recovery. In other words, make sure you install magisk before rebooting,
or at least delete the recovery restorer in system...

please, can you create an flashable zip to downgrade the version bootloader to 11h?
I want to use your firmware AEX, but without a finger scanner, to live is not so good ....
or should I wait when you add support for 20a?

DmytroPitenko said:
please, can you create an flashable zip to downgrade the version bootloader to 11h?
I want to use your firmware AEX, but without a finger scanner, to live is not so good ....
or should I wait when you add support for 20a?
Click to expand...
Click to collapse
I think @autoprime already created and released a 11h bootstock....... im almost sure he did.........

Eliminater74 said:
I think @autoprime already created and released a 11h bootstock....... im almost sure he did.........
Click to expand...
Click to collapse
I think autoprime's bootstock is for 10h, and sadly I dont think people on ARB01 can't go back to that. I didnt realize that the bootstock is what is needed for the fingerprint issue. I will try to release an 11g bootstock that will do the same thing.

I'm sorry if this is a dumb question, but here goes: I get that the Complete images are unmolested, and I therefore assume, identical to what you get on a G6 from TMobile directly, just in Zip flashable format, but what does "Bootstock" mean? I did try googling the term, but it just defined "Bootlicking" for me, and I didn't find that helpful . I'd imagine that Bootstock means it's just the stock image stripped of all the bloat, but I'm not sure if that's wishful thinking.
Also, my H872 is bootloader unlocked, TWRP flashed to both Recovery and LAF, currently running the AOSP Extended ROM (which seems to be very problematic, at least for me), so if I choose any of the above, will they overwrite my recovery?
Thank you!

Tried flashing the C2 variant, and TWRP reported it failed verification. Also, downloaded the other ones to see. File size tells me what I need to know, LOL. Is there any way to use the complete zip versions as a base and pull out just the bloat, in order to get something more like a clean install? A point in the right direction would be greatly appreciated. I'm working on learning a lot more about Android
Thanks!

jasongw said:
what does "Bootstock" mean?
Click to expand...
Click to collapse
Its the entire bootloader, which normally contains laf and recovery.
I don't believe these include recovery images. just the optional laf.
By the way @Eliminator74 I did notice that the updater-script for the full stock zips tries to do a hash check of boot, modern, system, rct and persist from the /tmp/ directory which they are not extracted to. so the apply patch check fails.

jasongw said:
Tried flashing the C2 variant, and TWRP reported it failed verification. Also, downloaded the other ones to see. File size tells me what I need to know, LOL. Is there any way to use the complete zip versions as a base and pull out just the bloat, in order to get something more like a clean install? A point in the right direction would be greatly appreciated. I'm working on learning a lot more about Android
Thanks!
Click to expand...
Click to collapse
Can confirm this. I tried flashing C2 and it fails verification in TWRP. Then I tried B2 and that worked, but the Modem Only zip also failed verification. Is there any way to resolve this? Thanks.

Hi.
I recently flashed AospEX on my LG G6 H872 and went through the rooting method for this device where you install TWRP on you laf partition and then onto the recovery partition.
I want to get laf back to regular Download Mode.
I want to know if flashing this 20a bootstock (bootloader) with laf will not cause any problems to boot into the Aosp Extended Rom. I guess my question is, are they compatible?
Thanks in advance and thank you all who have contributed to rooting and unlocking this phone.

Links not working - Anyone got mirror ? @Eliminater74, are you able to help send/re-upload?

Same here. Does someone have a copy?

Fixing failed OTAs after execution of TWRP

When booting TWRP using fastboot, without flashing it to the recovery partition, eg. "fastboot boot twrp-sanders-r20.img", only for the purpose of taking a partition backup, once done the device wont longer take OTA's!
That is IMHO a very unexpected behavior, as booting this way and keeping system read only should mean that nothing on the phone gets changed (well except the data partition if a backup is saved on these one).
One would expect this not to mess with the OTA process.
Now, this twrp at least: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910 does, after some investigation i found out that it is mounting the oem partition writable and modifying it adding a .twrp file to the root. Since the OTAs are checking and patching this partition of cause they will fail.
Luckily there is a way out, you can reflash the OEM partition for example from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
that is assuming that you are running the first Oreo 8.1 update, if you had an other version when the issue hit, you will need to find the right OEM partition image for you actual build.
IMHO this behavior of TWRP is unacceptable and should be fixed in a new release ASAP.

DavidXanatos said:
When booting TWRP using fastboot, without flashing it to the recovery partition, eg. "fastboot boot twrp-sanders-r20.img", only for the purpose of taking a partition backup, once done the device wont longer take OTA's!
That is IMHO a very unexpected behavior, as booting this way and keeping system read only should mean that nothing on the phone gets changed (well except the data partition if a backup is saved on these one).
One would expect this not to mess with the OTA process.
Now, this twrp at least: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910 does, after some investigation i found out that it is mounting the oem partition writable and modifying it adding a .twrp file to the root. Since the OTAs are checking and patching this partition of cause they will fail.
Luckily there is a way out, you can reflash the OEM partition for example from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
that is assuming that you are running the first Oreo 8.1 update, if you had an other version when the issue hit, you will need to find the right OEM partition image for you actual build.
IMHO this behavior of TWRP is unacceptable and should be fixed in a new release ASAP.
Click to expand...
Click to collapse
Agreed; received today a security update for my moto G5S plus (didn't root till i got the official 8.1 Oreo update) and every time i try to install takes me to TWRP and i keep it as READ ONLY (since TWRP itself says if u modify u won't b able to receive OTA updates) and... even without the modification i still can't get the update. this has to be fixed ASAP by TWRP

I did discover that if you keep the OTA files for older updates, you can re-run them to update the OEM partition. Unfortunately it only works one update generation.
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions

pizzaboy192 said:
I did discover that if you keep the OTA files for older updates, you can re-run them to update the OEM partition. Unfortunately it only works one update generation.
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
Click to expand...
Click to collapse
keep us posted man

pizzaboy192 said:
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
Click to expand...
Click to collapse
imho 99% sure, it still will fail, the partition does not just have to be semantically unchanged it must be 1:1 bit wise identical with what is expected.

I'll see what happens. I'm not a developer but I have pointed this out a few times to the developers of both TWRP threads, along with sharing these issues on the telegram group, but everyone else is focused on the latest custom ROM and doesn't care about stock, so the issues have fallen on deaf ears

in a nutshell how can i receive the last OTA security? do i revert to stock , install then root again? holy moly that's a lot of work

TheKicKer69 said:
in a nutshell how can i receive the last OTA security? do i revert to stock , install then root again? holy moly that's a lot of work
Click to expand...
Click to collapse
Unfortunately until they fix TWRP so it doesn't damage the OEM partition, you need a clean copy of the OEM partition to take the OTA.
However, there is a way you can prevent this, but it is a little hairy (you can't use any magisk modules). You can use the magisk app to patch the boot.img file that is from a slightly older Oreo firmware and flash that with fastboot, without using TWRP.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
DavidXanatos said:
imho 99% sure, it still will fail, the partition does not just have to be semantically unchanged it must be 1:1 bit wise identical with what is expected.
Click to expand...
Click to collapse
Yup. Just confirmed that deleting the .twrp file does not fix it.
I've reached out to Motorola to update their Lenovo Motorola Smart Assistant tool to support the official Oreo OTA which will allow us to download the latest full firmware file, which would give us the OEM partition to reflash before the next OTA.
I'll bother the TWRP devs again this week to get this unexpected behavior removed so we don't need to bother anyone in the future.

Update: none of the TWRP maintainers currently have replied to me about this issue.
@CheckYourScreen hasn't been active for a while but hasn't responded to a few different attempts to point this issue out (Been over a month since first notification with no acknowledgement)
@MasterAwesome has a custom TWRP that is latest, but they're still working on it. They're our best bet to possibly get it fixed since they're actively working on it. They've also been made aware, but no response yet (4 days since notifying and it was a weekend, so hopeful)
@GeneticEnginer was notified today. They developed the first unofficial TWRP (3.1.1) and might be able to help, but not holding my breath
I've also contacted a few people who do unofficial TWRP ports for some tips on unpacking one of our existing TWRP files and fixing it myself. It may be the way to go.

Hi guys. Final update. I've fixed TWRP temporarily. If we're not going to run custom ROMs, use this TWRP to backup. It does a bitwise backup of OEM and doesn't mount it as RW so it WILL work for restoring fully OTA capable stock ROM. It is NOT treble compatible as the treble compatible ones do weird things that I haven't documented.
https://forum.xda-developers.com/mo...-r20-stock-t3869192/post78205758#post78205758

[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