Moto E4 Plus (Qualcomm) OWENS Stock ROMs - Moto E4 Plus ROMs, Kernels, Recoveries, & Other De

Introduction
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Important!​You MUST be updated to the lastest firmware or this ROM will not work properly!​
How to install​1- Boot to TWRP and wipe system, data, cache and dalvik-cache.
2- Flash the ROM.
3- Flash your choice of zips from here to disable dm-verity (no-verity-opt-encrypt will disable force-encryption, no-verity-force-encrypt will keep force encryption, but disable dm-verity).
4- Flash the latest Magisk if you want root.
5- If you want Magisk modules to work properly, flash the kernel here: https://forum.xda-developers.com/mo...release-f2fs-bug-fix-kernel-qualcomm-t3724103 then a zip to disable dm-verity and Magisk.
5- Reboot TWRP. (This is important to keep the stock recovery from replacing TWRP!)
6- Allow TWRP to modify system. (This important to be able to flash zips and have them actually make changes.)
7- Reboot.
​
Downloads​Sprint XT1776 Stock NCR26.58-44 for Sprint All Variants Untouched-Sprint/Boost/Virgin Mobile
Retail XT1775 Stock NPR26.58-25 Untouched-Retail
Important!​You MUST flash the deodexed oem.img zip with the deodexed ROMs!​
No need to flash a zip for disabling dm-verity and forced encryption with the deodexed versions. The kernel is already patched for this along with init.d enabled.​
Latest Deodexed Stock for Sprint All Variants Deodexed-Sprint/Boost/Virgin Mobile
Deodexed-debloated (deGoogled) Stock for Sprint All Variants Deodexed-debloated- Sprint/Boost/Virgin Mobile
Deodexed-fully-debloated (deGoogled/deMotoed) Stock for Sprint All Variariants Deodexed-debloated-deGoogled-DeMotoed-Sprint/Boost/Virgin Mobile
Deodexed-debloated oem.img for Sprint All Variants Deodexed-oem- Sprint/Boost/Virgin Mobile
Debloated, deodexed, and other variants coming soon.​
DO NOT flash Gapps, because this is stock based they are already included and this will likely cause problems!​
Contributors
Goose03
Credits
Big thanks to
SuperR. for
SuperR's Kitchen
ROM OS Version: 7.1 Nougat
ROM Kernel: Linux 3.18
Based on: Stock
Version Information
Status: Fully stable
Created 2018-3-02
Last Updated 2018-3-02

Reserved

Reserved.

If someone with the retail variant updates with the latest ota I'm hearing about, I'll make a flashable if you can provide me with a system backup before rooting.

Thank you for this. Now we have a stock option to flash with TWRP instead of fastboot. And no forced encryption.. That is going to speed this little device up some... Great job. As soon as you have a retail version out for use in the XT1775, I will test.
Sent from my Nexus 6 using XDA Premium HD app

glockman4519 said:
Thank you for this. Now we have a stock option to flash with TWRP instead of fastboot. And no forced encryption.. That is going to speed this little device up some... Great job. As soon as you have a retail version out for use in the XT1775, I will test.
Click to expand...
Click to collapse
I made a twrp flashable ota update zip (partition updater) for the sprint variants and the E4 sprint variants. They've been tested and work fine (this guy was happy https://forum.xda-developers.com/showpost.php?p=75854847&postcount=25) for use with the ROMs made from the same firmware version. If someone, after updating would pull me the required imgs along with the system backup, I'll make a retail version also. Otherwise you won't be able to use the updated ROM without taking the ota update or flashing the firmware with fastboot first when it is released.
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
If someone with the retail variant updates with the latest ota I'm hearing about, I'll make a flashable if you can provide me with a system backup before rooting.
Click to expand...
Click to collapse
When you say a system backup, what are all of the partitions that you need?
---------- Post added at 04:43 PM ---------- Previous post was at 04:40 PM ----------
Also how do I get the updated version full zip like it is here:
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/

soaringowl2145 said:
When you say a system backup, what are all of the partitions that you need?
---------- Post added at 04:43 PM ---------- Previous post was at 04:40 PM ----------
Also how do I get the updated version full zip like it is here:
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Click to expand...
Click to collapse
I only need a twrp system backup and the pulled boot.img, oem.img and modem.img, the only parts with patches in the ota. The rest installs fine being replaced rather than just patched. That newer firmware isn't released yet. You'll have to wait.
Edit: actually I need a twrp boot.img backup also, I like to have both just in case.
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
I only need a twrp system backup and the pulled boot.img, oem.img and modem.img, the only parts with patches in the ota. The rest installs fine being replaced rather than just patched. That newer firmware isn't released yet. You'll have to wait.
Click to expand...
Click to collapse
How exactly do I pull the OEM, and modem? Can it be done through fastboot or adb? Also will this zip need to be installed on top of the current retail zip or can we install it the first time?

soaringowl2145 said:
How exactly do I pull the OEM, and modem? Can it be done through fastboot or adb? Also will this zip need to be installed on top of the current retail zip or can we install it the first time?
Click to expand...
Click to collapse
With adb:
dd if=/dev/block/bootdevice/by-name/oem of=/oem.img
or you can also use the terminal in twrp:
dd if=/dev/block/bootdevice/by-name/oem of=sdcard/oem.img
or a terminal emulator from the Play Store and do it right on the phone while the OS is running with the same commands as for the twrp terminal. For the modem just replace oem with modem.
Edit: with a system backup, I will make a ROM that will be able to be clean installed, but anyone who hasn't updated with the ota or official firmware will have to flash the partition updater I make before flashing the ROM.
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
With adb:
dd if=/dev/block/bootdevice/by-name/oem of=/oem.img
or you can also use the terminal in twrp:
dd if=/dev/block/bootdevice/by-name/oem of=sdcard/oem.img
or a terminal emulator from the Play Store and do it right on the phone while the OS is running with the same commands as for the twrp terminal. For the modem just replace oem with modem.
Edit: with a system backup, I will make a ROM that will be able to be clean installed, but anyone who hasn't updated with the ota or official firmware will have to flash the partition updater I make before flashing the ROM.
Click to expand...
Click to collapse
I will use twrp to backup system, system image, and boot. Then I will use adb to pull the system, boot, oem, modem, and modemst1 and 2 and upload those. That is all you need right?
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
soaringowl2145 said:
I will use twrp to backup system, system image, and boot. Then I will use adb to pull the system, boot, oem, modem, and modemst1 and 2 and upload those. That is all you need right?
Click to expand...
Click to collapse
Also after flashing twrp and doing a backup to take the next ota do I just need to flash stock recovery back and then do the ota?

soaringowl2145 said:
I will use twrp to backup system, system image, and boot. Then I will use adb to pull the system, boot, oem, modem, and modemst1 and 2 and upload those. That is all you need right?
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
Also after flashing twrp and doing a backup to take the next ota do I just need to flash stock recovery back and then do the ota?
Click to expand...
Click to collapse
I only need what I asked for, no more. I don't need a twrp system image. Only the normal backup. Also, the modem.img nothing more.
I'm not sure your understanding this. What I need is for you to flash the existing stock firmware package with fastboot, the whole package. Boot up your device and install the ota update, then flash twrp and make the system and boot backup and then pull the oem and modem.
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
I only need what I asked for, no more. I don't need a twrp system image. Only the normal backup. Also, the modem.img nothing more.
I'm not sure your understanding this. What I need is for you to flash the existing stock firmware package with fastboot, the whole package. Boot up your device and install the ota update, then flash twrp and make the system and boot backup and then pull the oem and modem.
Click to expand...
Click to collapse
I think I understand this. Use twrp to backup system and boot. Then use adb to pull oem and modem.
Right?
Edit:. I have already done the fastboot full flash and done the ota.

soaringowl2145 said:
I think I understand this. Use twrp to backup system and boot. Then use adb to pull oem and modem.
Right?
Edit:. I have already done the fastboot full flash and done the ota.
Click to expand...
Click to collapse
Yes
Edit: please pull the boot.img with adb also.
If you can zip up the system backup by itself and the rest together in another zip so it's not all one big zip that would be great.
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
Yes
Edit: please pull the boot.img with adb also.
Click to expand...
Click to collapse
Should I do a factory reset as well? I did disable some of the system apps through the normal settings. Or is a reset unnecessary?
Also will any of my personal info be pulled as well or just the Moto stuff?

soaringowl2145 said:
Should I do a factory reset as well? I did disable some of the system apps through the normal settings. Or is a reset unnecessary?
Also will any of my personal info be pulled as well or just the Moto stuff?
Click to expand...
Click to collapse
A factory reset isn't necessary, as long as you only disabled apps through settings and didn't actually modify the system any other way. None of your data will be included in anything I'm asking for unless you were to give me a backup of your data partition.
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
A factory reset isn't necessary, as long as you only disabled apps through settings and didn't actually modify the system any other way. None of your data will be included in anything I'm asking for unless you were to give me a backup of your data partition.
Click to expand...
Click to collapse
In that case I will probably upload this tonight after 11:30 but before 12:00 am EST time.

@Goose03 To take the next ota do I just flash stock recovery back then update?

soaringowl2145 said:
@Goose03 To take the next ota do I just flash stock recovery back then update?
Click to expand...
Click to collapse
You might be able to do that, as long as you didn't do anything but make a backup with twrp.
Sent from my Moto E (4) Plus using XDA Labs

Thank you both for taking on this endeavor!

Related

[ROM][ATT][4.4]Kitkat 140.44.3.ghost_att + root for locked bootloader [UPDATED]

Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away

How to get back to a Stock ROM

Hi,
sorry if i'm the 100th person to ask this question but how can i go back to the stock ROM with OTA?
I currently have a flavor of LinageOS with the Turbo Z kernel installed on my phone but it's just to buggy for me. I want to have root access on my phone for various reasons though.
I tried to just download different (6.0/7.0) stock ROM files but i can't install them with TWRP. I know that 7.1.x was released but i can not find the ROM for it.
What is the easiest way to just go back to a stock ROM? I know my way around the console but i don't want to brick my phone. I made backups of my files and also with TWRP so data loss is not an issue.
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
First things first.
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Use the fastboot flash / erase commands, as in this thread:
https://forum.xda-developers.com/showpost.php?p=73119650&postcount=1
If at any stage your phone get bricked, ie, black screen after reboot, no charging, etc. Use these instructions. They saved me in the last week from returning my device for a replacement(and paying $350.00):
https://forum.xda-developers.com/showpost.php?p=71874880&postcount=1
lollyjay said:
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Does this work for the EU version too? I'm not sure if the baseband thingy is compatible. I'll need a EU ROM otherwise but i can't find any for Android 7 :/
bert269 said:
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Click to expand...
Click to collapse
I've already updated to Android 7 so i guess i've to use a stock Nougat ROM.
Read my last post on page 15 of this thread
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113/page15
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
If you didn't take a backup of your stock boot and recovery before, then i think you'll have to go the long way by flashing the whole rom.
If you manage to install the 7.1.1 OTA after that, boot once into TWRP, backup stock recovery & boot and save it on your sdcard/pc. Then you can start flashing TWRP permantly, root, etc
Someone correct me, if I'm wrong.
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
What is your build number?
lollyjay said:
What is your build number?
Click to expand...
Click to collapse
The current build number is NPLS25.86-30-12
Byte_76 said:
The current build number is NPLS25.86-30-12
Click to expand...
Click to collapse
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Byte_76 said:
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Click to expand...
Click to collapse
You must have fully stock. I would suggest that you uninstall Magisk
lollyjay said:
You must have fully stock. I would suggest that you uninstall Magisk
Click to expand...
Click to collapse
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Byte_76 said:
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Click to expand...
Click to collapse
I still would suggest that you uninstall Magisk because the OTA would not work.
lollyjay said:
I still would suggest that you uninstall Magisk because the OTA would not work.
Click to expand...
Click to collapse
Okay I uninstalled Magisk which initiated an immediate reboot and resulted in a bootloop just after the bootloader message.
I think the issue occurs because the Data partition gets encrypted when root is uninstalled and decrpyption fails because of a bad key due to the unlocked bootloader.
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption. I then ran "fastboot continue" after which my phone booted back into Android:
https://forum.xda-developers.com/moto-z/help/bricked-moto-z-unlocking-bootlader-t3634701
My phone status was then: Stock Android 7.0.0, no_verity patch (no encryption), stock recovery, unlocked bootloader.
So my phone is about as close to stock as I can get it with unlocked bootloader.
I finally attempted to install the 7.1.1 OTA again. It reboots and indicates that it is installing and then pops up with a message that says "Error".
Pressing the power and up button brings up the recovery screen with the error log (with info that I don't understand) and from there I can reboot into system again where I get another message indicating that the update failed and no changes were made.
I'm hesitant to install RETBR or other non-RETEU roms (Because although they might work, there probably are some differences such as LTE bands etc. and they are not actually correct for my phone) so I'm not sure how else to get to 7.1.1 unless the wifi issue is resolved with the image that Erfanoabdi uploaded in another thread or Lenovo releases an official 7.1.1 firmware package for the RETEU model.
Byte_76 said:
.....
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption.........
Click to expand...
Click to collapse
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
bert269 said:
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
Click to expand...
Click to collapse
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Byte_76 said:
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Click to expand...
Click to collapse
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
Are these the commands that I should run?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
It's out of my knowledge if your verity patch influences either bootloader or gpt partition. So i would recommend to flash those two commands in order to "repair" them. If you'll get an error message, skip them and proceed with the rest.
I always prefer RSD method instead of manually flashing by fastboot commands.
Have you installed the latest version of RSD-lite 6.2.4? Have you installed the latest moto drivers?
If you have extracted the RETBR. zip, search for "flashall.xml" file. Open it with a texteditor and you'll find the correct flashing commands.

[Stock Recovery] Getting back to Stock Recovery after you've flashed TWRP.

As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Steps are pretty straight forward, if you already have a backup of your stock recovery just do the below steps, if else you could download one from the below link.
Put the device into fastboot mode. There are two ways to do that.
1)By long pressing the power button and volume down button whilst the USB is connected.
2)Just do a adb reboot bootloader command if you could boot into the system.
Then just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Then disconnect the USB and long press the power and volume up button until you see the "The device is booting now" message.
Downloads
- Stock recovery for BKL-L09
Thanks, you saved me.
Thanks
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Copperhead100 said:
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Click to expand...
Click to collapse
MD5 hash wouldn't possibly match, because the backup was taken using dd and there might be some config files modified or added when I used the stock recovery once. But, hey the thing would work if you have BKL-L09 device
Thanks. This works!
shihabsoft said:
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Click to expand...
Click to collapse
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
atf2m4 said:
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
Click to expand...
Click to collapse
Ofc it does
shihabsoft said:
Ofc it does
Click to expand...
Click to collapse
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
Not sure, as it might check integrity before giving updates. Just download Firmware Finder app and check for updates constantly.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
You will receive the updates but you won't be able to install them with TWRP. Simply flash the stock recovery and the updates will self install when they come. You'll have to root again with Magisk after the updates, but that's a simple process.
Sent from my Honor View 10 using XDA Labs
Hie,
How can I get back from lineage OS to stock using this? I guess I'm on the same boat as a lot of people out there and could really use some help here. I'm on Cosmos OS and can't go back to stock. I tried flashing this recovery.img but can't figure out a way back.
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Can you help me with the commands please?
---------- Post added at 09:20 PM ---------- Previous post was at 09:12 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Wildfire, can you please help me with the commands? I believe there's an inclusion of ramdisk in the commands now.
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoys.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Apparently, there isn't any system.img file in the Indian firmware I downloaded. The rest are there but not the system.img.
Someone please help me out
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
ankan1993 said:
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
Click to expand...
Click to collapse
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Einwod said:
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Click to expand...
Click to collapse
Indeed! Can you please help me this one time?
ankan1993 said:
Indeed! Can you please help me this one time?
Click to expand...
Click to collapse
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Einwod said:
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Click to expand...
Click to collapse
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
ankan1993 said:
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
Click to expand...
Click to collapse
What device do you have exactly?

[Unofficial] Fixed TWRP 3.2.1-r20 for stock ROM & OTA compatibility

Did some learning, some digging, and found what is so broken on the current TWRP builds that are out there.
We're missing one line in the fstab.qcom
Code:
/dev/block/bootdevice/by-name/oem /oem ext4 ro wait
So I did the simple fix. Took TWRP 3.2.1-R20 (which supports backing up OEM) and added that line to fstab.qcom.
You can now backup & restore the OEM partition using TWRP and it isn't broken for OTAs.
EDIT: backup & Restore might still be broken, but it does not damage the OEM just booting TWRP. Looking into how to backup via image instead of backup via TWRP GUI.
Edit2: I've fixed the OEM backup so it now backs up as an image like /system does. This takes up 768MB of space compared to the previous 141MB, but for working OTAs it's worth it. Enable compression and the extra space isn't wasted. I've uploaded the fix as well and updated the link at the bottom of the post.
To add this fix to TWRP for devs, change the line in \etc\recovery.fstab from
Code:
/oem ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
to
Code:
/oem emmc /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
Adding that as an additional line will allow us to pick between a bitwise perfect OEM backup or just a basic "copied files" backup.
In the meantime, you can back up OEM using DD.
You can install Magisk in TWRP without breaking OEM.
I've tested and confirmed this on my XT1806 but it should work with all of them.
I've linked to the file at the bottom of this post. It's able to be directly flashed over your existing TWRP.
To fix your OEM partition for future updates:
Identify what software you're running. If you are running the first Oreo OTA build, just download the full firmware file and fastboot flash the OEM partition again. Then OTA should take
If you are running October patch, you will need to fastboot flash the first Oreo OTA OEM file and then ADB Sideload the October OTA on top of it. Then you're up to date. The October OTA can update just the OEM partition without needing to patch the rest.
If you are running Nougat, same applies, Just fastboot flash whatever OEM you are currently on and then OTAs should work.
To all TWRP devs, please add the OEM RO line to your fstab.qcom so we don't run into this in the future. it's a simple fix.
Edit3: I've added the ability to backup the Persist file as well since that's not included in standard R20. link updated as well.
DOWNLOAD:
https://drive.google.com/open?id=1FRWyndazNcfDugHExAOvSvDdOfy53PYq
That's pretty cool
squirting the #hit out of me!
thx
Thanx. Flashing via adb succeeded, installed Magisk 19.1 at once, System booted normally. Fine
But was is meant by "In the meantime, you can back up OEM using DD."? May i not take a TRWP backup? Using stock oreo 8.1.0, and plan to flash a custom rom, maybe pie...
Thanx in advance!
Klaus R said:
Thanx. Flashing via adb succeeded, installed Magisk 19.1 at once, System booted normally. Fine
But was is meant by "In the meantime, you can back up OEM using DD."? May i not take a TRWP backup? Using stock oreo 8.1.0, and plan to flash a custom rom, maybe pie...
Thanx in advance!
Click to expand...
Click to collapse
Hi,
My bad. Just use the current link and do a regular backup. That line is out of date when I was still experimenting
pizzaboy192 said:
Hi,
My bad. Just use the current link and do a regular backup. That line is out of date when I was still experimenting
Click to expand...
Click to collapse
Sorry for asking, being quite an newbie. "use the current link and do a regular backup" means, use Backup feature in TWRP normally?
Klaus R said:
Sorry for asking, being quite an newbie. "use the current link and do a regular backup" means, use Backup feature in TWRP normally?
Click to expand...
Click to collapse
Yup! I believe the file is called twrp-sanders-r20-oemsafe (might also mention persist)
I just did a rebbot in fastboot mode, from there to recovery, TWRP starts. Excellent. But internal storage (Data) is 0MB? Did i forget something?
Tanx a lot for your assistance
Klaus R said:
storage (Data) is 0MB
Click to expand...
Click to collapse
Seems to be encryption problem. https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595
Can't fix the problem. First everything's fine, twrp's backup shows some Mb in /data (caused by magisk or su). So decryption is working at that point. Then, after booting into system and doing some settings, root is still there (rootchecker), but back to twrp there will be /data again with 0MB.
Anyone a hint? Main purpose of twrp for me is taking backups (before trying custom roms)
Running stock oreo 8.1.0 Europe with 01.02.19 sec patches
Need the TWRP installer please
Need the TWRP installer please
does this, or any similar twrp increase the chances of getting volte (which works on my xt1806 in stock oreo when i use the lenovo recovery app) up and running on say RR pie builds (which i was using unpatched twrp 3.2.1-r16 to install RR and gapps, then booting, updating OTA, then going back to install the TWRP 3.3 from this forum to flash Magisk)?
---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------
Souravskrba said:
Need the TWRP installer please
Click to expand...
Click to collapse
the "installer" is either fastboot from your PC or install from your current TWRP (if you already have another version installed) hit install then >> flash img button)
hi this fixes the error 1 when flashing magisk?
thanks
M4T145 said:
hi this fixes the error 1 when flashing magisk?
thanks
Click to expand...
Click to collapse
Probably no. Search for Treble TWRP Moto G5s Plus on google. You need a trebelized TWRP in order to flash magisk.
link doesn't exist.
Please update the link to the file. Gdrive page results in URL not found.
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
krist0ph3r said:
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
Click to expand...
Click to collapse
Download the one that's there in the Sanders Telegram group.
krist0ph3r said:
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
Click to expand...
Click to collapse
I've had troubles with recent versions of TWRP too, mostly with encryption . That's why I stuck with 3.2.1.r22; it's the only one I've had no trouble with so far. It doesn't support OTA update, but I've had no problem with manual updates. FYI I'm using Arrows 11.
It may not be as trustworthy as you'd hope for, but here's the link anyway: https://upload.disroot.org/r/NaH0_6dV#DZn8wBuuDERBm+db05p15OPzT5F/f2LFvs+IT5E54O4=
sBinnala said:
Download the one that's there in the Sanders Telegram group.
Click to expand...
Click to collapse
link?
okayk said:
I've had troubles with recent versions of TWRP too, mostly with encryption . That's why I stuck with 3.2.1.r22; it's the only one I've had no trouble with so far. It doesn't support OTA update, but I've had no problem with manual updates. FYI I'm using Arrows 11.
It may not be as trustworthy as you'd hope for, but here's the link anyway: https://upload.disroot.org/r/NaH0_6dV#DZn8wBuuDERBm+db05p15OPzT5F/f2LFvs+IT5E54O4=
Click to expand...
Click to collapse
no luck, same error that i get with 3.4.0.0:
Code:
> fastboot flash recovery "twrp-sanders-treble-new(ByGeneticEnginer).img"
target reported max download size of 534773760 bytes
sending 'recovery' (14636 KB)...
OKAY [ 0.320s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.179s]
finished. total time: 0.503s

Advice to update Pie MIUI 10.2.2.0 PDTMIXM

Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
orozcore said:
Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
Click to expand...
Click to collapse
There's a TWRP for pie
mr_reaper said:
There's a TWRP for pie
Click to expand...
Click to collapse
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Which TWRP version u running?
mr_reaper said:
Which TWRP version u running?
Click to expand...
Click to collapse
sorry for the late reply the version i'm using is recovery-TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150
orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Click to expand...
Click to collapse
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
EDIT: Also, the stock Pie release is good. I am currently on Pixel Experience but may switch back to stock rooted at some point. Until Xiaomi releases the Pie kernel sources, no custom ROM is going to be perfect.
lexridge said:
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
Click to expand...
Click to collapse
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go.
Click to expand...
Click to collapse
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
chan200606 said:
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
Click to expand...
Click to collapse
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
lexridge said:
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Not many people will shutdown their phones to test the restore guys. It's difficult, but we have to wait for someone to try this with the latest version of twrp. Nothing dusturbing here in my opinion. We will thank whoever tries this first that's for sure.
chan200606 said:
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Click to expand...
Click to collapse
Interesting. I did not know you can flash img files directly with TWRP. Haha. Color me stupid!! How does TWRP know which partition to write the .img to? Does it give you a choice?
Yes it does. Choose recovery.
lexridge said:
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
MetallicGR said:
Yes it does. Choose recovery.
Click to expand...
Click to collapse
good to know you can flash a img within twpr so i'll try when I update
mr_reaper said:
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
Click to expand...
Click to collapse
Yes is bad to wait so much time and there's nothing you can do I read about the version of the unlocker but with no luck. So I finally have unlocked bootloader.
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
If you didn´t read before a member linked to you In the post #6 both TWRP versions.
About your steps:
- No need to backup previous TWRP, just flash the new image and reboot to recovery again.
- If you already have Magisk no need to flash it again so you won´t lose root status nor any data/settings of the rom.
If you want to unroot the 0212 has this option in advanced menu.
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
You should probably update your TWRP first and foremost, otherwise no access to data after you flash the update.. You will also need the Magisk Manager as an apk somewhere on your microSD card. I edited your to-do list:
* Download Magisk Manager and store on your microSD card.
* Flash new TWRP (0212 or 0121).
* Make a full twrp backup and do a recovery only backup as well
* download the update
* let it update and hope no lost of data
* Reflash img or TWRP Recovery backup 0212 or 0121
* Reboot recovery, check that you can decrypt data
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
* After first boot, manually install your saved Magisk Manager app from microSD card. Run it. Check if all is good.
Do you use Titanium Backup? If so, make a full TB before doing any of this.
---------- Post added at 01:04 AM ---------- Previous post was at 12:42 AM ----------
SubwayChamp said:
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
Click to expand...
Click to collapse
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
lexridge said:
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
Click to expand...
Click to collapse
I never saw before this kind of weird behaviour btw is working generally speaking fine.
I´m not a fan of camera but the stock is so far better, I noticed that HavocOs rom has the feature to enable camera2 api and EIS, maybe you might try it. Regarding to use a custom launcher on stock miui rom there´s Poco launcher that keeps the same system icons than theme chosen and is very fast.

Categories

Resources