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
Related
This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Dude, quit being so amazing. It's getting ridiculous.
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Yes!!! Glad to see you!
@WugFresh
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.
I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.
bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.
Can confirm a working flash. Everything looks great! Thanks for all the hard work
no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Edit
Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.
dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks
Yes it seems Google decided to remove the backup confirmation dialog from TcSettings
So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2
*FILES REMOVED UNTIL FURTHER NOTICE, AS USERS ARE HAVING CONNECTION ISSUES AFTER FLASHING*
Here are the latest stock retail builds packaged into TWRP flashable format.
You can use these files to upgrade and downgrade stock builds safely, as they do not include gpt (partition table) or bootloader.
Usage is simple:
Copy file to device storage
Reboot into TWRP
Flash zip
Profit!
Please remember to hit the "THANKS" button if these files help you!
NOTES:
Dm-verity and force encryption have been disabled in the boot images, and unlocked device/dm-verity warnings have been disabled in the logo images.
Do NOT attempt to apply standard OTAs over these builds; they will fail.
If you get an OTA for a build that's not yet available, please share it!
How To Pull An OTA update:
Download the update
Power off and boot into TWRP
Go to Advanced > File Manager
Navigate to /cache
There will be a Blur_Version_blah.zip file
Copy to internal storage or sdcard
Copy from internal storage or sdcard to PC (optional, recommended)
Upload to Drive, Mega, or whichever file sharing service you choose
Share the link!
If you're rooted/modded and want to prevent potential auto updating, you can wipe /cache to remove the file.
DOWNLOADS:
CREDITS:
Android
Lenovorola
@tal.aloni for SparseConverter posted here:
https://forum.xda-developers.com/showthread.php?t=2749797
@erfanoabdi for imgpatchtools posted here:
https://forum.xda-developers.com/an...ev-img-patch-tools-sdat2img-ota-zips-t3640308
@A.S._id for img repack tools posted here:
https://forum.xda-developers.com/showthread.php?t=2600364
@xpirt for sdat tools posted here:
https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
Please tell me these actually work. I am desperate for any ROM for the XT1710-01 variant. I will go as far as paying.
Thank you so much,it works on xt1710-08 well,just backup EFS in trwp just in case of no signal,after flash this rom in twrp,restore EFS and enjoy it.Also,you can root it with flashing magisk
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Are these 7.1.2 yet?
THANKS
KeepingItCuttingEdge said:
Are these 7.1.2 yet?
Click to expand...
Click to collapse
It's still 7.1.1. See the attached screenshot.
KeepingItCuttingEdge said:
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Click to expand...
Click to collapse
Any response to these questions, OP?
I am in the same boat.
New builds are up
KeepingItCuttingEdge said:
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Are these 7.1.2 yet?
THANKS
Click to expand...
Click to collapse
There is no 118-9 version.
pizza_pablo said:
Any response to these questions, OP?
I am in the same boat.
Click to expand...
Click to collapse
There is no 118-9 version.
If I knew, I would answer.
These files are are made from official fastboot files shared by @Junior Passos.
Check out his afh page for albus here: https://androidfilehost.com/?a=show&w=files&flid=195559
Q9Nap said:
New builds are up
There is no 118-9 version.
There is no 118-9 version.
If I knew, I would answer.
These files are are made from official fastboot files shared by @Junior Passos.
Check out his afh page for albus here: https://androidfilehost.com/?a=show&w=files&flid=195559
Click to expand...
Click to collapse
This is from a US unlocked Z2 Play.
The model number is XT1710-01.
Are the listed firmware versions proper for my model?
pizza_pablo said:
This is from a US unlocked Z2 Play.
The model number is XT1710-01.
Are the listed firmware versions proper for my model?
Click to expand...
Click to collapse
Dude, what did I just say? I DON'T KNOW.
I'm sure it will work, but it may take you off your official upgrade path.
And with no fastboot file available for your current software version, I would take a full TWRP backup and copy to pc for safekeeping before trying anything.
Welcome to Flashing 101
Q9Nap said:
*removed*
Due to lack of interest.
Click to expand...
Click to collapse
Noooo, please restore! I've been using the steps and files provided to get rid of the annoying "an update is available" notifications on my rooted XT1710-09!
And yesterday a new one has appeared...
Indeed please restore it can't hurt having it up here
We don't even have custom roms, this is the closest we can get for now. Please post more builds!
Q9Nap said:
*removed*
Due to lack of interest.
Click to expand...
Click to collapse
I'm going to buy my z2 play bike at the end of the year and it's a shame not to have an updated lite rom. Probably you should be doing a good job.
It would be nice to have a rom lite for ALL MODEL with deodex, delete more apps OTA / CCC / CCE, OTA process is deleted, remove a lot of the background services collect and send data on the type of phone (DropBox, MotoCare , MotoConntect, Drive and etc).
ilgrosso said:
Noooo, please restore! I've been using the steps and files provided to get rid of the annoying "an update is available" notifications on my rooted XT1710-09!
And yesterday a new one has appeared...
Click to expand...
Click to collapse
Lars1703 said:
Indeed please restore it can't hurt having it up here
Click to expand...
Click to collapse
f.baio said:
We don't even have custom roms, this is the closest we can get for now. Please post more builds!
Click to expand...
Click to collapse
Guth13 said:
I'm going to buy my z2 play bike at the end of the year and it's a shame not to have an updated lite rom. Probably you should be doing a good job.
It would be nice to have a rom lite for ALL MODEL with deodex, delete more apps OTA / CCC / CCE, OTA process is deleted, remove a lot of the background services collect and send data on the type of phone (DropBox, MotoCare , MotoConntect, Drive and etc).
Click to expand...
Click to collapse
Updated the OP with the latest retail build NPSS26.118-19-11.
Unlike most carrier unlocked moto devices, which tend to have multiple upgrade paths for different regions, the albus seems to have only one upgrade path for the retail variant so far.
Someone correct me if I'm wrong, and please post the OTA files for alternate upgrade paths if you have them; directions are in the OP.
I have linked the tools I use to create these at the bottom of the OP.
You can use these tools and info in their threads to reverse engineer the stock build and modify it to your liking.
Thank you so much now i can have the latest update for my rooted moto thanks a lot
I have an unlocked Moto Z2 Play XT1710-01 and this is the latest update I am seeing:
NPSS26.118-24-6
https://drive.google.com/file/d/1IUG-o0HWCgFGyNwX3aWzd4oqhHAzK25T/view?usp=sharing
EDIT:
I think i now understand the file name structure and that it includes the date. My updated was from 6/26 and your updated was from 11/19. I just updated to the newest. Thank you for doing this!
sirkuttin said:
I have an unlocked Moto Z2 Play XT1710-01 and this is the latest update I am seeing:
NPSS26.118-24-6
https://drive.google.com/file/d/1IUG-o0HWCgFGyNwX3aWzd4oqhHAzK25T/view?usp=sharing
EDIT:
I think i now understand the file name structure and that it includes the date. My updated was from 6/26 and your updated was from 11/19. I just updated to the newest. Thank you for doing this!
Click to expand...
Click to collapse
The file name structure doesn't have anything to do with the date it was made afaik.
That update is for "albus_c" and not "albus". I'm not sure what the difference is.
Apparently, there are multiple upgrade paths after all.
Flashing this will likely take you off your current upgrade path, but it is safe, so you can always go back to your previous stock build if you want.
Q9Nap said:
Updated the OP with the latest retail build NPSS26.118-19-11.
Unlike most carrier unlocked moto devices, which tend to have multiple upgrade paths for different regions, the albus seems to have only one upgrade path for the retail variant so far.
Someone correct me if I'm wrong, and please post the OTA files for alternate upgrade paths if you have them; directions are in the OP.
I have linked the tools I use to create these at the bottom of the OP.
You can use these tools and info in their threads to reverse engineer the stock build and modify it to your liking.
Click to expand...
Click to collapse
Thanks @Q9Nap!
I've attempted to follow your instructions about applying OTA via TWRP, but that fails because of mismatching thumbprint - which sounds odd since I've downloaded and attempted to flash on exactly the same device...
Anyway, I'll try soon to flash the full stock ROM, after download from the link you've re-posted.
New update NOT PATCHED YET NPSS26.118-19-14
https://drive.google.com/file/d/1df6c3cWDU0mxt__mFhL-GiqzQzLWdKrD/view?usp=drivesdk
Contains November security updates
This has not yet been patched please wait for OP to do So
@Q9Nap can you put a tutorial on here telling us how to make a update flashable
I am not responsible if you break your phone in any way, these are here for your aid. I will help as much as i can, but it is on YOU, the user to read the OP and understand exactly what it is you are doing at ALL times.
READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS
These can be used to return to 100% stock as long as you can get into fastboot mode on the device, and have unlocked the bootloader and critical partitions. All images contained in the zips are directly from the essential Fastboot zips and OTA's, and dumps for the rest
Prerequisites:
1. Working fastboot environment in bootloader: (test using the command fastboot devices should return your s/n) Windows drivers are at the bottom of the OP.
Essentials windows drivers contain working ADB/Fastboot and places an environment variable to link to these binaries, i would HIGHLY recommend ditching any and all adb/fastboots you may have (minimal, HTC, etc) and use what is supplied by essential, they just work (Not gonna help you either if your hellbent on using your adb/fastboot).
The zips contain all the firmware (19 Images), TWRP11.img (the latest version), and a stockboot.img (so you can conveniently place on your phone and flash in twrp) when rooting with magisk, and boot.fix.red.img (In case you kill verity).
2. Bootloader unlocked: run the command fastboot flashing unlock in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock will relock the bootloader. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
3. Critical partition unlocked: run the command fastboot flashing unlock_critical in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock_critical will relock the critical partition flashability. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
4. Common Sense: Use IT!!!!!
Downloads
Android 10 BTS Folder: https://sourceforge.net/projects/mata-bts/files/10
Q Beta BTS Folder: https://sourceforge.net/projects/mata-bts/files/Q-Beta/
Pie BTS & Novendor Folder: https://sourceforge.net/projects/mata-bts/files/Pie
P Beta BTS: https://sourceforge.net/projects/mata-bts/files/P-Beta/
Oreo BTS & NOVENDOR: https://sourceforge.net/projects/mata-bts/files/Oreo/
The Files below are OLD as dirt BTS
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
OPM1.170911.130 mega.nz (oreo 8.0 beta)
NMK32F AFH (latest nougat 7.1)
NMJ88C mega.nz (nougat 7.1)
NMJ51B AFH (nougat 7.1)
NMJ32F AFH (nougat 7.1)
NMJ20D mega.nz (nougat 7.1)
NMI81C AFH (nougat 7.1)
Drive Folder of Patched Essential Boot images Credit Goes to @dazeone
Some OLD AS DIRT Novendor zips aswell... if anyone still cares
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
Windows Drivers
drivers
Unzip this and check out the flash-all.[bat,sh] scripts for win/lin (they're identical but provided for easier flashability).
They're set up to flash to both slots. Most people will want to do this on a back to stock mission, but they can be adjusted if your goal is something else.
If coming from some other rom, you're also going to want to wipe your data, or you're not going to boot. This can be accomplished by the command in the bootloader: fastboot -w keep in mind there are multiple scripts to wipe for you in the zips.
These can also be used to make custom roms/rooted boot images/etc too, so have fun with it!
Thanks:
@invisiblek - aer0zer0 stole his thread, he put most of it together
@aer0zer0 - i stole the thread from aer0, his 2yr old son makes more use of the PH-1 than he does.
@bmg1001 - Root thread, found here root
@dazeone - Provides independent patched boot images and has an awesome YouTube Channel of Guides! DazeOne Youtube Channel
Enjoy
Heck ya
Yesssss
Ill be giving this a shot in a few days hoping to return my phone back to complete stock.
Hot diggity... been fun reading/watching you all work on this through Discord, think I'll go ahead and unlock it while I still have my S8 in case I trash things
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
vekenti said:
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
Click to expand...
Click to collapse
Lineage okay for you lol?
You've got one of the top devs on Lineage working on this so I think you're good.
Thank you! I'll be rooting now that we have a safety net!
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
invisiblek said:
So as we're still waiting for Essential to release official factory images, I thought it'd be helpful to link the dumps that we've produced. These can be used to return to 100% stock as long as you can get into fastboot mode on the device.
Click to expand...
Click to collapse
Thanks for this. My fingerprint sensor was not working for some reason after rooting and I thought i would go completely stock. This thread helped me to go completely stock and get the fingerprint back to working.
Thought I haven't locked the bootloader yet. Will try it later.
---------- Post added at 05:55 AM ---------- Previous post was at 05:48 AM ----------
sarcoptic said:
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
Click to expand...
Click to collapse
For flashing to critical partition you need to unlock them. The command is similar to unlock boot-loader.
Code:
fastboot flashing unlock_critical
And to lock it again
Code:
fastboot flashing lock_critical
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
sarcoptic said:
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
Click to expand...
Click to collapse
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Freaking rockstar thanks!
invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Thanks mate.
Thanks for the dump! Just yesterday I was trying to figure out how to do the adb backup command but I gave up cause I couldn't get a good reliable connection to my phone (driver issues, then to failed to connect to device, then to using the adb shell and a mouse on recovery, fun times.)
Great
please can someone guide on how to root it
chambar said:
please can someone guide on how to root it
Click to expand...
Click to collapse
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
charlie.s said:
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
Click to expand...
Click to collapse
Much appreciated, indeed dunno how i missed it.
free XDA points for @invisiblek .......Thanks for putting it all together, hopefully you can get a teiko sports watch when you turn all the points in, LOL
Seriously, thanks for putting it all together
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
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Why you so eager that you can't wait a few days?
It's available now.
it has been up for about 5 hours
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
Layoffs, poor employee morale, and Google moving away from innovation and a move to deplete resources from projects/divisions that are not returning enough profit.
If you've ever had to deal with Google customer "service" for any technical issues before, you already know why. Sometimes you get lucky and find a unicorn of a tech to help, but it's usually an infuriating mess dealing with them.
But, to be honest, I'd rather have a delayed update than a rushed and buggy update. Quality control is important.
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
After all we are all just humans ... they sure have their reasons
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
No problems here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
Rooted, Kirisakura Kernel, Apr. update. All good here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it???
The mobile phone system is running normally.
Click to expand...
Click to collapse
Assuming you're rooted, that message is normal and can be ignored.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored.
Click to expand...
Click to collapse
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored I am root and magisk on my device..
Click to expand...
Click to collapse
Lughnasadh said:
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
Click to expand...
Click to collapse
I refresh init_boot.img or prompt this message.
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
ozyk100 said:
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
Click to expand...
Click to collapse
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
simplepinoi177 said:
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for that explanation, I'll read up on it from the provided link.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
I had the same issue, but everything works normally without any issues. I regularly flash custom roms and factory images, so if you still want to fix this issue, restore a factory image using the Android flash tool.
Any info on whether the fingerprint scanner is being fixed or at east bettered with this?