Develop Bugs

Understanding how DM-Verity is triggered - How to update easily 4.0.x -> 4.0.x+1

Hey there,
I have been really annoyed since i installed OOS 4.0.0. First because it took ages the first time to get it right, and then because i had to start from scratch with every little 30MB update AGAIN.
I didn't find any reliable source to what happens in the folowing cases, thus this thread :
1- Flashing official recovery + updating through android
=> Will it work/DM-Verity error appear ?
2- Flash official recovery and sideload OTA/Full ZIP
=> Is /data getting wiped ? Same question about DM-Verity
3-Flash full Zip in latest eng.stk TWRP followed with supersu
Has anyone explored these solutions ?
Thanks in advance
EDIT: Working way for updating:
1: Dirty flash full ROM in latest modified TWRP
2: Flash SuperSU WITHOUT booting into system
3: Wipe dalvik/cache
4: reboot to system.
For explanation about what triggers DM-Verity check out post 19

DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance

2x4 said:
DM verity is triggered by the firmware. You can't avoid it unless you want to run old firmware
It is not an error nor a bug - it is a notification. There is no impact to performance
Click to expand...
Click to collapse
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.

Nobody07 said:
I do know that. I simply try to find the best way to update without hassle and without getting the DM-Verity message.
Click to expand...
Click to collapse
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.

2x4 said:
update everything (ROM/TWRP), flash old (non-4.x) firmware
FYI you're fixing an aesthetic issues and there may be more bugs from using the old firmware.
Click to expand...
Click to collapse
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.

Nobody07 said:
I don't have the issue right now with a 4.x firmware ... You are not helping... My guess is using OnePlus recovery and updating through android there wont be a DM Verity message. Do you know if this is true ? If not you aren't telling me anything i do not know.
Click to expand...
Click to collapse
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.

2x4 said:
if you use stock recovery you won't get the dm-verity notice either.
not sure why you mentioned eng.stk TWRP if you're not trying to run TWRP.
Click to expand...
Click to collapse
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?

Nobody07 said:
Thank you for answering, but seriously, did you even read the first post ?
So i can flash OnePlus firmware, update android within the system and then flash twrp again. With no DM Verity appearing ?
Click to expand...
Click to collapse
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)

2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
That's were you are wrong...
I currently have twrp and no dm-verity.

Nobody07 said:
That's were you are wrong...
I currently have twrp and no dm-verity.
Click to expand...
Click to collapse
because you are on pre-nougat ROM and/or firmware

2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Im getting tired of you ignoring what i say.
I'm on OOS 4.0.1. I did a clean sideload through OnePlus recovery, and flashed twrp/root afterwards. No DM-Verity. I DID NOT flash an old firmware.

it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------
2x4 said:
no - it's not the flashing process.
DM verity notification will always be present while you have TWRP (unless you go back to old firmware)
Click to expand...
Click to collapse
not true, i have the latest 4.0.2 firmware and TWRP and no DM verity .

theduke7 said:
it's a compilation of things not just one thing, the firmware thing is just the easy way out, if you decrypt the phone data (just wipe it) and rooted then re encrypted it, you wont get the dm verity issue...
so simply, sideload or flash the full rom , if you sideloaded immediately fastboot TWRP (the latest official or modified) , then immediately flash SuperSU... reboot to system, no dm verity will appear.
Click to expand...
Click to collapse
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?

Nobody07 said:
What you are saying is i can flash full ROM through twrp, followed by supersu, reboot, and i wont get dm-verity nor loose any data?
Click to expand...
Click to collapse
yes , idid exactly that updating from 4.0.1 to 4.0.2, dirty flashed the full rom , then immediately SuperSU, and then TWRP again just to be sure...and Viola

2x4 said:
because you are on pre-nougat ROM and/or firmware
Click to expand...
Click to collapse
Did a clean flash (beta 10) with the stock recovery, flashed TWRP with SuperSU afterwards.
No dm-verity.
After dirty flashing beta11 full zip + SuperSU through TWRP the dm-verity screen is still NOT there.
Btw, this has been already discussed weeks ago.
Do your homework.

dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax

cpt.macp said:
dm verity is a fail safe present in system boot.img . Nothing related to firmware. Don't know from where people getting all this hoax
Click to expand...
Click to collapse
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag

Bradl79 said:
BC whether it's a band-aid or fixes the issue, if u flash an old fw outside of nougat with trwp, it gits rid of the nag
Click to expand...
Click to collapse
it's the worst way to "fix" the issue, you're using an old firmware that's more than likely have incompatibility issues with the OOS updated rom, so unless you're using a custom rom (not OOS or OOS based) where it doesn't matter what firmware you use it's not a recommended practice.

Neither flashing twrp, nor OOS would trigger dm-verity (unless you already have that message)
If you however boot into system, dm-verity will be triggered. The idea is to patch that before it gets triggered.
Flashing SuperSU patches DM verity. Which is great if you want root access. Again this patch won't work if you already have dm-verity warning. Once you flash the ROM, do not boot into system. Flash SuperSU 2.79 or above and verity will be patched. You will also see a line "patching dm-verity" in SuperSU installation process. Now verity message won't appear.
If you don't want root, there is a no-verity zip that you can flash which will have the same effect. I use SuperSU so I don't have any links to this but Google is your best friend.
- if you already have verity
- if you forgot patching verity, booted into system and now warning screen has appeared.
Now here is where things get tricky. Boot to fastboot, connect phone and type
fastboot format userdata
Remember the above step will wipe internal storage completely
Reboot to recovery
Format data (not wipe but format. This step is very important)
Flash OOS
Flash SuperSU
Reboot to system. Now there will be no dm-verity warning

@ungeeked great detailed explanation that should put an end to all chatter TBH your reply should be pinned in this section for some while and titled DM-Verity explained.

[EOL][RECOVERY][Android 8 / 9][Stock/SODP][XZ2/C/P/3] TWRP 3.3.1-0 [UNofficial]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
FAQ:
If your stock camera preview is black, please follow this issue ticket.
https://github.com/sonyxperiadev/bug_tracker/issues/261
https://github.com/MartinX3-AndroidDevelopment/bug_tracker/issues/7
Just wiping your phone in TWRP lead into an encrypted & not readable userdata in the stock system.
You need to open advanced wiping and check the entries data and internal storage.
Of course clear the dalvik, too.
If you backed up system and/or vendor partitions and you want to restore them, make sure that TWRP setting "Use rm -rf instead of formatting" is set!.
If after the usage of NewFlasher or the OTA Updater or something else, which installs stock firmware parts you get stuck into the TWRP or SONY Logo, you need again to disable the verification with the vbmeta.img file and its parameters in fastboot.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Weird problems not easily to reproduce by other users require that you make sure, that you
Use the newest platform tools (adb & fastboot)
Downloaded the newest firmware via Xperifirm from XDA and installed the newest firmware via Newflasher from XDA
Newflasher from XDA
Xperifirm from XDA
Removing the stock bloat apps via titanium backup may result in a boot loop. Use a file explorer to remove them, disable them or try to use my unfinished bloat removal script at github.
Your phone reboots into recovery, instead of system? Maybe it crashed too often due to a wrong installation or whatever?
In TWRP:
Code:
cat /dev/block/bootdevice/by-name/misc
shows you the reason.
Please replace it with an empty string.
Known Bugs:
The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
Bugtracker:
TWRP Bugtracker -> If you think the problem is in TWRP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
The TWRP should be still usable if you just "fastboot boot twrp.img" it.
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@dees_troy and his team of volunteers for the TWRP code
@M-ROM for his hint activating the touch in TWRP
@osm0sis
@nreuge
@FartyParty
@pandemic
@nasko_spasko
@VeixES
@Klaus N.
@old.splatterhand
@yanke928
@michele2
@niaboc79
@j4nn for hacking the kernel to make "fastboot boot twrp.img" possible
@shoey63 for testing @j4nn 's hack
@oshmoun for a better "fastboot boot twrp.img" solution
@dhacke thank your for providing a download server
Shame on me if I forgot someone after searching through the thread and my PM's!
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv
XDA:DevDB Information
TWRP, ROM for the Xperia XZ2
Contributors
MartinX3, oshmoun, Marijn, Sony
Source Code: https://github.com/MartinX3-AndroidDevelopment
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Matching to firmware in twrp name
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-08-10
Created 2018-07-26
Last Updated 2020-10-23

Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with https://7-zip.org/ or Linux.
Installation Android 9.0:
Update to newest stock firmware before unlocking!!!
Enter fastboot via software, not hardware buttons. See "Known Bugs".
(Optional; If you modify the system or need the camerafix.zip)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
Reboot into installed TWRP
Want Root? -> Magisk
(Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
In case of touch issues on the XZ2 compact:
Download (try the v10 zip first, if it doesn't work try v9 or v8)
Do the same steps, but with the TWRP test release.
Installation Android 8.0:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta-xz2(?).img
fastboot flash boot twrp.img
Install stockkernel-xz2(?)-installer.zip
Install twrp-3.2.3-0-xz2-xz2c-xz2p-installer-xz?-installer.zip
Install Magisk-v17.1.zip
(Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)

News
30.01.2020
i put this twrp officially into the endoflife status.
Due to twrp 10.0 being work in progress, i am unable to compile it in a 10.0 build environment.
So the 10.0 release will take its time.
(and sony didn't release the source code for the stock kernel until now).
I will try to experiment with a 9.0 twrp and a 4.14 kernel, so look if it is usable in the new 10.0 4.14 custom roms as a temporally workaround, when i have free time.
If that works, i will experiement with the stock kernel source, after it got released.
But for now i have no clue for any eta. (the curse of doing it as a volunteer :d)
Click to expand...
Click to collapse
17.11.2019
stock twrp 52.0.a.11.32 doesn't decrypt userdata.
Waiting that the needed patches get submit in twrp/omnirom.
Then i rebuild a new twrp for 52.0.a.11.32.
Please only "fastboot boot" it, don't flash it to the phone or the twrp will be just stuck at twrp logo.
Click to expand...
Click to collapse
16.11.2019
stock twrp 52.0.a.11.32
Click to expand...
Click to collapse
16.10.2019
stock twrp 52.0.a.11.3
Click to expand...
Click to collapse
13.10.2019
september security patch level:
Stock twrp 52.0.a.10.6
smaller download size:
Removed bundled magisk, since the newest one doesn't make bootloops anymore.
Removed touch drivers from twrp, now a script greps them dynamically from the vendor partition.
Click to expand...
Click to collapse
08.09.2019
a testbuild for the apollo/xz2c users with the not working tcm touch hardware.
Together with the testbuild for omnirom and sonyaosp every apollo user should be able now to use the touchscreen.
apollo_twrp_v8.zip
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
10.08.2019
august security patch level:
Stock twrp 52.0.a.8.131
sodp twrp
Click to expand...
Click to collapse
09.08.2019
removed the august stock twrp.
The new aosp pie august security patch level introduced new updates to the de/encryption, which needs to get adapted by twrp first.
Click to expand...
Click to collapse
08.08.2019
august security patch level:
Stock twrp 52.0.a.8.131
Click to expand...
Click to collapse
30.07.2019
stock twrp:
Upgraded the touch drivers to the 52.0.a.8.107 version.
Should fix all possible happening touch issues in twrp.
Click to expand...
Click to collapse
13.07.2019
fixed stock twrp touch
(culprit was the activation of the logcat support; working fine in the sodp twrp, but kills the touch workaround of the stock twrp)
Click to expand...
Click to collapse
12.07.2019
fixed stock twrp touch
(accidentially delivered with sodp kernel leading into not working touch)
Click to expand...
Click to collapse
12.07.2019
july security patch level:
Stock twrp 52.0.a.8.107
sodp twrp
Click to expand...
Click to collapse
11.06.2019
stock twrp 3.3.1 firmware 52.0.a.8.83 (june security patch level)
Click to expand...
Click to collapse
10.06.2019
custom rom twrp with june 2019 security patch level.
For the upcoming sonyaosp / omnirom june 2019 security patch level release.
Click to expand...
Click to collapse
01.06.2019
reuploaded custom rom twrp with hotfix to decrypt devices fullwiped on may 2019 or newer.
Click to expand...
Click to collapse
31.05.2019
custom rom twrp 3.3.1 with may 2019 security patch level.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
That'll save bandwith and server storage.
Click to expand...
Click to collapse
18.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
13.05.2019
stock twrp firmware 52.0.a.8.50 (may security patch level)
Click to expand...
Click to collapse
24.04.2019
reuploaded aosp/stock twrp.
Accidentially uploaded (build environment bug) the akari xz2 twrp for every device. It boots & installs magisk, but it can't mount the other partitions.
Sorry!
Click to expand...
Click to collapse
22.04.2019
aosp twrp
hello "fastboot boot twrp.img"!
Bye bye twrp installer zip file! (see installation instructions.)
reduced the download size!
Click to expand...
Click to collapse
17.04.2019
stock twrp
hello "fastboot boot twrp.img"!
Bye bye twrp installer zip file! (see installation instructions.)
reduced the download size!
Click to expand...
Click to collapse
09.04.2019
stock twrp firmware 52.0.a.8.25 (april security patch level)
fixed touch problems some people have.
Twrp is now at version 3.3.0-0.
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
06.04.2019
reuploaded april security patch level aosp twrp with a newer kernel and more upstream merged changes from sony aosp.
I hope now the wifi problem is gone.
Twrp is now at version 3.3.0-0.
Click to expand...
Click to collapse
02.04.2019
reuploaded april security patch level aosp twrp.
Reverted https://gerrit.omnirom.org/#/c/andro...overy/+/33783/
now zips are installable again without the "digest" error.
Omnirom still has the bug. Just install it on top of omnirom or replace its boot.img by the twrp.img.
Click to expand...
Click to collapse
02.04.2019
aosp twrp released for aosp / custom roms with april 2019 security patchlevel.
Click to expand...
Click to collapse
01.04.2019
aosp twrp released for aosp / custom roms with march 2019 security patchlevel.
May contain the stock twrp mtp bug.
A zip installer is not needed anymore.
Just flash the boot.img, the dtbo.img and the vbmeta.img with the parameters.
Click to expand...
Click to collapse
31.03.2019
reuploading twrp.
Removed the old build, which stopped at twrp logo.
Now the mtp and touchscreen problems should mostly be fixed.
Click to expand...
Click to collapse
30.03.2019
reuploading twrp.
Removed the old build.
Now the mtp and touchscreen problems should be fixed.
I tried to automate the upload with my new android file host access.
It is unstable.
Sadly android file host is the only hoster with unlimited quota.
Click to expand...
Click to collapse
25.03.2019
stock twrp released for stock firmware 52.0.a.8.14.
Many new fixes and features and sadly a new bug:
Wait until the password entry appears, before you connect the phone with your computer or the touch won't work.
But i hope that the touch bug on the xz3 is now fixed.
Click to expand...
Click to collapse
14.03.2019
dear people, sadly no new twrp for the new stock march firmware with shiny new twrp bugfixes and so on until i finished my next exam (of many) at the 20.03.2019.
But after that i'll release a new release.
Maybe with working "fastboot boot twrp.img"
i hope
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/33287/
will got merged then, too, so i can hopefully remove the twrp installer zip file.
Ps:
The good thing is, if you rely on the twrp and won't update the firmware before i release it, you can see others complaining about march firmware bugs without having them on your phone. [emoji14]
Click to expand...
Click to collapse
19.02.2019
bundling now .202 touch drivers.
The difference to the first version is, that i don't try to get them from the vendor partition.
Instead i bundled them into my ramdisk file.
I hope the touch problems are now fixed for everyone, which i sadly can't reproduce.
Click to expand...
Click to collapse
17.02.2019
since some users still get no working touch, i switched back from .202 touch drivers to .163 touch drivers.
Click to expand...
Click to collapse
16.02.2019
hotfix for stock xz2 twrp. I introduced a bug with the last update.
Click to expand...
Click to collapse
16.02.2019
hopefully fixed touch bugs some where having (even with the exact same hardware/firmware combination like me)
Click to expand...
Click to collapse
13.02.2019
twrp firmware 2019 february 52.0.a.3.202
including a camera fix, which is compatible with the latest twrp release. (fixes only the black preview)
reduced the twrp download size by around 6mb. If the touch doesn't work, pelase report it asap.
Click to expand...
Click to collapse
10.02.2019
in combination with my sonyaosp _r31 release i uploaded the twrp for custom rom's / aosp (february patch level)
it is importand to use the same twrp security patch level as the rom or avb 2.0 will lead into bootloops in twrp and the system.
Click to expand...
Click to collapse
08.02.2019
i found the broken twrp solution together with the sony developers.
It's the cause of the omni 9.0.0_r31 ramdisk (february security level)
i need to wait for the february security patch stock update.
The rollback security is preventing me to use an january kernel with the february firmware, resulting in a blinking bootlooping black/logo/black/logo twrp animation.
Will release the next working twrp with twrp camerafix & magisk camerafix included and maybe my touch driver approch will work then, ( now i know it should work, it was only the cause of this security behaviour)
Click to expand...
Click to collapse
07.02.2019
i̶n̶c̶l̶u̶d̶i̶n̶g̶ ̶a̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶c̶a̶m̶e̶r̶a̶ ̶f̶i̶x̶ ̶c̶o̶m̶p̶a̶t̶i̶b̶l̶e̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶l̶a̶t̶e̶s̶t̶ ̶t̶w̶r̶p̶ ̶u̶p̶d̶a̶t̶e̶.̶ ̶(̶o̶n̶l̶y̶ ̶f̶i̶x̶e̶s̶ ̶b̶l̶a̶c̶k̶ ̶c̶a̶m̶e̶r̶a̶ ̶p̶r̶e̶v̶i̶e̶w̶.̶)̶
Click to expand...
Click to collapse
06.02.2019
r̶e̶d̶u̶c̶e̶d̶ ̶t̶h̶e̶ ̶t̶w̶r̶p̶ ̶d̶o̶w̶n̶l̶o̶a̶d̶ ̶s̶i̶z̶e̶ ̶b̶y̶ ̶a̶r̶o̶u̶n̶d̶ ̶6̶m̶b̶.̶ ̶i̶f̶ ̶t̶h̶e̶ ̶t̶o̶u̶c̶h̶ ̶d̶o̶e̶s̶n̶'̶t̶ ̶w̶o̶r̶k̶,̶ ̶p̶l̶e̶a̶s̶e̶ ̶p̶r̶o̶v̶i̶d̶e̶ ̶m̶e̶ ̶t̶h̶e̶ ̶i̶n̶f̶o̶r̶m̶a̶t̶i̶o̶n̶s̶ ̶l̶i̶n̶k̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶f̶a̶q̶.̶
Click to expand...
Click to collapse
03.02.2019
a mysterious bugfix for the stock twrp appeared. It is super effective for stock decryption.
Click to expand...
Click to collapse
01.02.2019
added the aosp/customrom support. I tested it on my xz2 with omnirom, aosp and resurrection remix.
Click to expand...
Click to collapse
19.01.2019
updated to stock firmware 52.0.a.3.163 (jan 2019)
Click to expand...
Click to collapse
19.01.2019
created buildenvironment for twrp.
Twrp is now based on tama omnirom builds.
That means we now get the latest twrp code commits.
This are the twrp code changes:
https://github.com/omnirom/android_...8=✓&q=committer-date:>2018-12-10&type=commits
Click to expand...
Click to collapse
15.01.2019
hopefully activated the xz3 twrp touch.
Click to expand...
Click to collapse
10.12.2018
twrp android 9.0 pie december update.
Synced my stuff with the 52.0.a.3.126 stock firmware (drivers, kernel, etc.).
Added the xz3.
uploaded the last pie firmware with a working camera on unlocked devices.
Click to expand...
Click to collapse
16.11.2018
the xz2p has a different kernel.
I fixed the xz2p twrp by splitting it in its own twrp boot.img file.
Click to expand...
Click to collapse
16.11.2018
twrp android 9.0 pie november update.
Synced my stuff with the 52.0.a.3.84 stock firmware (drivers, kernel, etc.)
Click to expand...
Click to collapse
13.10.2018
android 9.0 pie update.
Cleaned unused stuff.
Fixed mtp.
Only for xz2 and xz2c as universal installer.
Encryption still not supported, but my device config files are now usable to compile your own twrp.
Of course, the configsettings still are not fully optimal for this device.
Click to expand...
Click to collapse
13.10.2018
android 9.0 pie twrp for xz2 and xz2c got released!
Xz2p will follow, after it gets the same update.
Mtp is still deactivated.
Encrpytion of the userdata doesn't work (password always wrong), because of the new android 9.0 pie encryption.
I think the next release will fix this.
Btw. In the first post is now a know bugs section.
And thanks to @m-rom, @michele2 and @niaboc79, who tried to helped me in this emergency situtation that pie got released and needed a new twrp while i was at work. :silly:
Click to expand...
Click to collapse
11.10.2018
i seperated the twrp builds again, because of touch bugs in the xz2c.
The xz2, xz2c and the xz2p got seperated twrp.img files and stock kernel installer for twrp.
Click to expand...
Click to collapse
10.10.2018
i seperated the xz2_xz2c build from the xz2_premium build.
It seems that i made a mistake.
The xz2 and xz2c are sharing the same kernel, but the xz2premium kernel has little differents.
I also optimized the folder structure behind the downloadlink.
Click to expand...
Click to collapse
10.10.2018
working together with @storm// to achieve a working xperifix drmfix.
After we got success, i will highly recommend removing the old drmfix and installing his one.
The old one may brick the device forever during a longer time period. (2 weeks or longer)
old drmfix uninstall routine:
Flash with newflasher (v13+) only the file:
Vendor_x-flash-all-b6b5.sin
but remember to flash both slots.
Not only a or b.
twrp is your friend.
Or
fastboot set_active other
Click to expand...
Click to collapse
10.10.2018
i am happy to announce the twrp for the xz2, xz2c and xz2p!
I need test results for the xz2c and the xz2p which i don't own.
Installation instructions got updated.
The last file got uploaded a few minutes ago.
Click to expand...
Click to collapse
08.10.2018
fixed sdcard
in the 2018-10-08_01:36+2:00 folder.
Code:
1 fastboot format userdata
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Reboot into recovery
4. Twrp flash stock kernel xz2_51boot.zip
5. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
6. Install drmfix by storm// [b]or[/b] m-rom
7. Twrp flash magisk-v17.1.zip
8. Twrp flash permissive.zip
9. Reboot into system
Click to expand...
Click to collapse
06.10.2018
new try, thanks to everyone who helps me, tests for me and are a part of this nice little project.
in the 2018-10-06_14:53+2:00 folder.
Code:
1. Clean flash
[b]or[/b]
1.1 fastboot format cache
1.2 fastboot format userdata
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4. Reboot into recovery
5. Twrp flash stock kernel xz2_51boot.zip
6. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
7. Install drmfix by storm// [b]or[/b] m-rom
8. Twrp flash magisk-v17.1.zip
9. Twrp flash permissive.zip
10. Reboot into system
Click to expand...
Click to collapse
05.10.2018
new try, thanks to everyone who helps me, tests for me and are a part of this nice little project.
in the 2018-10-05_16:10+2:00 folder.
Code:
1. Clean flash
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4. Reboot into recovery
5. Install drmfix by storm
6. Twrp flash stock kernel xz2_51boot.zip
7. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
8. Twrp flash magisk-v17.1.zip
9. Twrp flash permissive.zip
10. Reboot into system
Click to expand...
Click to collapse
05.10.2018
modified the twrp recovery hack by @m-rom again.
Now i fixed the security settings for adb.
Twrp-xz2-2c-fixed-fstab-fixed-security.img
in the 2018-10-05_10:22+2:00 folder.
Click to expand...
Click to collapse
04.10.2018
modified the twrp recovery hack by @m-rom again.
Now unpacked and repacked by android image kitchen.
Twrp-xz2-2c-fixed-fstab.img
in the 2018-10-04_21:00+2:00 folder.
I exchanged the twrp.fstab and the recovery.fstab. I hope this fixed the shell problem.
Click to expand...
Click to collapse
04.10.2018
modified the twrp recovery hack by @m-rom.
Twrp-xz2-2c.img
in the 2018-10-04_11:30+2:00 folder.
I exchanged the twrp.fstab and the recovery.fstab. I hope this fixed the shell problem.
Click to expand...
Click to collapse
02.10.2018
a new build.
Twrp__more_oem_drivers__oem_firmware__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
in the 2018-09-27_22:20+2:00 folder.
I added the entire firmware, bin, and radio folder and some more lib64 drivers from the aosp oem 8.1.6.3_r1_v15 binaries, so we can test, if the touch works now.
Click to expand...
Click to collapse
28.09.2018
a new build.
Twrp__more_oem_drivers__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
in the 2018-09-27_22:20+2:00 folder.
I added every lib64 driver, so we can test, if the touch works now.
Click to expand...
Click to collapse
27.09.2018
a new build.
Twrp__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
i tweaked some configs.
Switched back to oem 8.1 v15 drivers.
I did not upgrade the kernel, because the current code could damage the display.
Kernel bugs are listed in my aosp rom thread.
Click to expand...
Click to collapse
20.09.2018
new builds.
Feel free to test.
boot__omni_8.0__stock_8.0_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.1__stock_8.0_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.0__stock_8.0_kernel__oem_8.1_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__oem_8.1_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__oem_8.1_libs.img.gz
boot__omni_8.1__stock_8.0_kernel__oem_8.1_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img.gz
boot__omni_8.0__stock_8.0_kernel__oem_9.0_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__oem_9.0_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__oem_9.0_libs.img.gz
boot__omni_8.1__stock_8.0_kernel__oem_9.0_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__oem_9.0_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__oem_9.0_libs.img.gz
Click to expand...
Click to collapse
18.09.2018
a new build.
Twrp_8.0_oldconfig.img.gz
twrp_8.0_newconfig.img.gz
now i used the source code of the stock kernel to create a prebuild kernel image.
And i updated the device config.
And it looks like, that i can't put the stock source into the kernel folder of omni build environment.
It stops with the error, that it can't find a rule to make the zimage.
It is much more easier to build the aosp kernel, than the stock kernel.
Click to expand...
Click to collapse
17.09.2018
i downloaded the 51.1.a.11.51 firmware and extracted all the needed stuff, including the new kernel to update the twrp device sources. Hehe.
One is got built with omni 8.0 and the other one with omni 8.1.
Feel free to test them.
Click to expand...
Click to collapse
16.09.2018
split the aosp rom part into its own project.
https://forum.xda-developers.com/xperia-xz2/development/aosp-aosp-8-1-h8266-t3843269
Click to expand...
Click to collapse
15.09.2018
i uploaded the aosp rom.
Feel free to test it.
Its kernel will be the one with my twrp build.
So i need to know if the kernel work or has bugs and broken functions.
If the kernel and the aosp image is fine, i will update the twrp build.
Click to expand...
Click to collapse
14.09.2018
the bootloader v60 got released with the september patch.
i will now build aosp with the latest sources and if it will boot and work, i will use its kernel and the updated device sources to build twrp.
Click to expand...
Click to collapse
27.08.2018
don't use this twrp builds.
We need to wait for the bootloader update from sony.
The device will be announced as part of the sony open devices project at the same time and the following issue will be closed:
https://github.com/sonyxperiadev/bug_tracker/issues/149.
The leading developer jerpelea told us, that it would be released with the september stock update.
Click to expand...
Click to collapse
18.08.2018
i compiled the xperia aosp 8.1 image for the xz2 (h8266).
Feel free to test it.
I don't know, if we need the bootloader patch to run it.
Please follow the installing instructions in the third post.
https://drive.google.com/open?id=1-p7sknnber8pc9ya7ojpkvcltuwlgnri
Click to expand...
Click to collapse
04.08.2018 #3
i compiled the sony 51.1.a.4.265 stock kernel.
I compiled the normal bootimage with the sony stock kernel and the sony aosp build sources, to test if it is bootable.
I did the same with the omni 8.0 sources and the sony stock kernel.
I uploaded them with the file ending "-with-stockkernel.img"
i don't know, if the stock kernel is compatible with the sony aosp or the omni sources.
Click to expand...
Click to collapse
04.08.2018 #2
i compiled the normal bootimage with the sony aosp kernel and the sony aosp build sources, to test if it is bootable.
sony-aosp-8.1-04-08-2018-bootimage.img
Click to expand...
Click to collapse
04.08.2018
i recompiled the sony aosp 4.9 after its change to 'beta'.
I recompiled omni 8.0 twrp bootimage and recoveryimage with it.
Please test it and provide a feedback.
Ps: Omni 8.0 because since the last 'repo sync' i am not able to compile 8.1 anymore because of missing framework lib dependencies.
Click to expand...
Click to collapse
01.08.2018
i was able to compile the standard recovery with the sony 4.9 aosp kernel for the xz2.
I also compiled a bootimage and a recoveryimage with twrp with the sony 4.9 kernel and the omni sources.
Please test it and provide a feedback.
Click to expand...
Click to collapse
30.07.2018
the build is not working.
It seems, that we need to wait for sony to stable their asop kernel on github (e.g. To announce, that the xz2 is now a part of the open source project.)
Click to expand...
Click to collapse

Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it

mitpio said:
Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it
Click to expand...
Click to collapse
Could you tell me, which error message you get?
Or does nothing happen?
Did you unlock your bootloader?
Do the command
"fastboot devices"
(Without "")
Will it ahow your device with a number?
_______________________________________
Or if you need to get into the Fastboot Mode
Connect your device to your PC and write
"adb devices"
This should show you your device and a number.
Then you can do
adb reboot bootloader
And choose the fastboot mode.

entering fastboot mode xperia xz2
mitpio said:
Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it
Click to expand...
Click to collapse
Switch off the phone. Press and hold the Volume Up button
Connect to your PC using a USB Cable while holding down the Volume Up button on your Xperia XZ2
Before plugging in the USB cable on your Xperia XZ2 make sure that the other end of USB cable is already connected to the PC.
Wait till the LED turns into blue (the volume up button has to be pressed all the time till you see the blue led). Blue LED -> no more need to press the volume up button. Now you are in fastboot mode.
Using Linux do the following: open a terminal, type 'sudo fastboot devices' (without the quotes) (make sure before that you have fastboot installed on your linux box).
The output should be something like: QV7016A31E fastboot
The procedure should be very similar using windows (without using the sudo command), but I never tried it.

Ok, thanks, I'll try
Wysłane z mojego H8266 przy użyciu Tapatalka

mitpio said:
Ok, thanks, I'll try
Wysłane z mojego H8266 przy użyciu Tapatalka
Click to expand...
Click to collapse
Are you using linux or windows?

windows

mitpio said:
windows
Click to expand...
Click to collapse
https://lifehacker.com/google-finally-lets-you-download-adb-and-fastboot-as-st-1790840830
https://www.desinerd.co.in/how-to-adb-and-fastboot-windows-mac-linux/
https://thedroidarena.com/best-adb-fastboot-commands-list-android/
https://wiki.lineageos.org/adb_fastboot_guide.html

Unfortunately this build seems not working, it did something out of an ordinary boot though.
Here's what exactly what I did:
1. The phone is unlocked, model H8266.
2. Shut down and get into fastboot mode, with blue LED on.
3."fastboot boot xz2_twrp.img" and get it booting.
and this is what I observed:
1. Screen turns on with Blue LED on, diaplaying "Your device software cannot... Blablablah".
2. After 5 seconds the screen turns off, but the blue LED is still on.
3. After around 20 seconds the screen turns on again with "SONY" logo, blue LED is still on.
4.About 5 seconds later, Blue LED turns off.
5.Again about 10 seconds later, screen turns off.
6.The red LED blinked a few times, with two times of vibration.
7.Screen turns on with "SONY" logo, then it's totally an ordinary boot into Android.
Hope the feedback will help.

yanke928 said:
Unfortunately this build seems not working, it did something out of an ordinary boot though.
Here's what exactly what I did:
1. The phone is unlocked, model H8266.
2. Shut down and get into fastboot mode, with blue LED on.
3."fastboot boot xz2_twrp.img" and get it booting.
and this is what I observed:
1. Screen turns on with Blue LED on, diaplaying "Your device software cannot... Blablablah".
2. After 5 seconds the screen turns off, but the blue LED is still on.
3. After around 20 seconds the screen turns on again with "SONY" logo, blue LED is still on.
4.About 5 seconds later, Blue LED turns off.
5.Again about 10 seconds later, screen turns off.
6.The red LED blinked a few times, with two times of vibration.
7.Screen turns on with "SONY" logo, then it's totally an ordinary boot into Android.
Hope the feedback will help.
Click to expand...
Click to collapse
Can you give use the entire Message of "Your device software cannot.."?

MartinX3 said:
Can you give use the entire Message of "Your device software cannot.."?
Click to expand...
Click to collapse
Well, it's just the same warning as the bootloader is unlocked, "Your device software cant' be checked for corruption, please lock the bootloader", quite common after a bootloader unlock.

I should compile the Android 8.0 kernel with the Omni 8.0 sources, instead of 8.1 I think.
I also can't use the Sony Kernel 4.9.116 on Github, because it is not finish and stick with the delivered Kernel 4.9.65 from the July update.
(It is hard to test without an unlocked phone, hehe)
@yanke928
Can you use a second terminal to use
adb -d logcat &> log.txt
OR
ddms (in the android sdk)
while entering the fastboot boot cmd
to look, if it will give us any logs?
There is also a xda guide
https://www.xda-developers.com/guide-on-using-adb-logcat-and-ddms/

MartinX3 said:
I should compile the Android 8.0 kernel with the Omni 8.0 sources, instead of 8.1 I think.
I also can't use the Sony Kernel 4.9.116 on Github, because it is not finish and stick with the delivered Kernel 4.9.65 from the July update.
(It is hard to test without an unlocked phone, hehe)
@yanke928
Can you use a second terminal to use
adb -d logcat &> log.txt
OR
ddms (in the android sdk)
while entering the fastboot boot cmd
to look, if it will give us any logs?
There is also a xda guide
https://www.xda-developers.com/guide-on-using-adb-logcat-and-ddms/
Click to expand...
Click to collapse
Tried to get log during the recovery booting but failed.
By issuing "adb logcat > logcat.txt" at the second terminal while booting the device from fastboot to the TWRP, it doesn't output anything when it's trying to boot the TWRP, but after the failure boot of TWRP, it does catch logs of an ordinary boot. Which means the adb works fine, while the TWRP doesn't give out any logs.
---------- Post added at 03:01 PM ---------- Previous post was at 02:27 PM ----------
MartinX3 said:
I should compile the Android 8.0 kernel with the Omni 8.0 sources, instead of 8.1 I think.
I also can't use the Sony Kernel 4.9.116 on Github, because it is not finish and stick with the delivered Kernel 4.9.65 from the July update.
(It is hard to test without an unlocked phone, hehe)
@yanke928
Can you use a second terminal to use
adb -d logcat &> log.txt
OR
ddms (in the android sdk)
while entering the fastboot boot cmd
to look, if it will give us any logs?
There is also a xda guide
https://www.xda-developers.com/guide-on-using-adb-logcat-and-ddms/
Click to expand...
Click to collapse
I've found that I did a stupid thing, model confused.
Seemed you've compile it for H8266 for Chinese Mainland market, while I have H8296, HK version, but I don't think this will matter somehow since the phone of HK version and Chinese version can be flashed with each other's firmware. Also, if you're Chinese, you can communicate with me directly without English

yanke928 said:
Tried to get log during the recovery booting but failed.
By issuing "adb logcat > logcat.txt" at the second terminal while booting the device from fastboot to the TWRP, it doesn't output anything when it's trying to boot the TWRP, but after the failure boot of TWRP, it does catch logs of an ordinary boot. Which means the adb works fine, while the TWRP doesn't give out any logs.
---------- Post added at 03:01 PM ---------- Previous post was at 02:27 PM ----------
I've found that I did a stupid thing, model confused.
Seemed you've compile it for H8266 for Chinese Mainland market, while I have H8296, HK version, but I don't think this will matter somehow since the phone of HK version and Chinese version can be flashed with each other's firmware. Also, if you're Chinese, you can communicate with me directly without English
Click to expand...
Click to collapse
I am also using the H8296 HongKong device, because of the 6GB ram, but I installed the H8266 German firmware on it.
@spirit-eh got the same error, but I don't know his device.
PS:
I am still downloading the minimal platform_manifest_twrp_omni on 8.0 branch, before I can compile it again.
Many stuff to download and I got only 5Mbit internet on my vacation. :silly:
Edit:
A notable difference between the XZ2 image and the XA2 image is the kernel size
XZ2 kernel 15.3 MB
XA2 kernel 46 MB
Maybe he compiled the AOSP one from github.
Edit2:
I assume hardly, that I need to wait for the XZ2 to be added to the Sony open source programm.
So I can use the AOSP 8.1 kernel, instead of this hacked thing delivered in the Sony open source downloads in their site.
The XA2 twrp maintainer did the same.

An older version of twrp does not work on xz2 (H8216) ? @MartinX3

Pandemic said:
An older version of twrp does not work on xz2 (H8216) ? @MartinX3
Click to expand...
Click to collapse
TWRP 3.1 introduced support for A/B-Devices.
TWRP 3.2.0 introduced the Android 8.x compatibility and 3.2.1 and 3.2.2 included important fixes.
I wouldn't try an older version.
I also need to compile TWRP from source with my collected config files to work with the XZ2.
(TWRP need to compiled for every device on its own).
Now I try to compile it with OMNI 8.0 instead of 8.1, because it is a hacky 8.0 kernel, which I need to use.
(Sony's Android 8.1 AOSP 4.9 kernel is not finished.)

01.08.2018
I was able to compile the standard recovery with the Sony 4.9 AOSP kernel for the XZ2.
Click to expand...
Click to collapse

MartinX3 said:
01.08.2018
Click to expand...
Click to collapse
Also for H8216 bro ?
Btw see pm

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Root and Magisk on Oreo (oct security patch)

After using this phone for a while I decided to root it.
I unlocked bootloader, installed TWRP and flashed Magisk, but all I get is bootloop or stuck on bootlogo (your device has been unlocked.....)
SOLUTION
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Applicable also for moto Z2 Play, just with appropriate recovery, of course
Please note the updates to the first post. It may be necessary to do the procedure twice.
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks

Klen2 said:
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Click to expand...
Click to collapse
I did 3.2.3-0 TWRP method (by Junior Passos) on my XT1710-06 device with 8.0 on August 1 security patch (purposefully neglected updating any further cause method was tested exactly up to August patch according to Passos) and everything seems working pretty fine for a month now. Think I've installed no Magisk modules other than Xposed systemless yet and I've no interest in SafetyNet as well, so not deeply tested either. Don't know for sure, but I guess there's a good chance for such method to work on October patch too. Just be sure to perform every step as it is now in the 3.2.3-0 OP. One word of advice: after performing TWRP backup, look for it in /system/media and move it to both external and internal SDcards just in case something goes wrong (usually because of a missed step, I can say)... Also: I recommend to install Magisk v17.1 first time; then, if you want, update to v18 but right from the installer...
Sent from my Moto Z2 Play using XDA Labs

Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).

Have these steps worked for me...
1.)Flash TWRP using Fastboot
2.)Go to TWRP/Settings and open Terminal.
3.)Run both of following commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
Click to expand...
Click to collapse
4.)Flash Magisk-v17.1.zip
5.)Repeat step 2 and 3 dont wipe.
6.)Start
NOTE: before Reinstall stock or uninstall Magisk.

I did the Junior Passos method of doing the backup, and everything is working like a charm.

Cupcake 1.5 said:
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Click to expand...
Click to collapse
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop

OldUncle said:
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
Click to expand...
Click to collapse
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.

Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Perfect!
Thank you very much!
The only solution which worked!
Finally I got full control on my Z2 Play.

Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Regarding backup, this is done through the stock ROM correct (Settings --> System --> Backup to Google Drive).
Thanks,
smithmal

Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
This worked perfectly on my Moto Z2 XT1710-06 with Oreo 8.0 when no other options worked.
Flash or Boot into TWRP
Backup System and Boot partitions in TWRP
Restore System and Boot Partitions in TWRP (note I had to enable R/W access in TWRP to restore the system partition)
Flash Magisk-v19.3.zip
Reboot
That is it. Now Rooted and passes all SafteyNet test. No more restricted apps. Even Google Pay now works.
Thank You.

sick
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
your method worked like charm, thanks alot man

[ROM/FW][STOCK]LG V30 (Joan) T-Mobile H932 20r TWRP flashable firmware (incl. ROM)

LG V30 T-Mobile H932 20r ROM​
For U.S. T-mobile H932 ONLY. Do NOT install this on any other V30/V30+/V30S except U.S. T-mobile H932. You will brick your phone.
DISCLAIMER : I do not hold responsiblity for any of the following but not limited to : Bricks due to not reading, nuclear war, cat dying. I will not be held responsible for any damage of any kind due to the result of this zip. It is held under your own risk. This does not mean that i wont help in any way shape or form to recover from anything that may happen at the result of flashing this zip. PLEASE FLASH RESPONSIBLY! PS. This zip has NOT been tested by me!​
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20r firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS build prop
Added all lockscreen weather animations build prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
H93220r.zip [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20r firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20r zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)​
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-1-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...

#RESERVED
Please to anyone who had issues with the zip.....
We have a fix!
Flash this zip
https://www.androidfilehost.com/?fid=1395089523397908552
Then flash a rom from your SD CARD
ONLY FLASH THIS OF YOU HAD A BRICK FROM 20R!!

Zip is live! Enjoy!

your zip name is wrong.. should be h93220r* ( it doesnt matter but i was confused at first)
also, i flashed it and nothing happened. my system is still the same as i was before (20p)
and in the script, i think it says 'model=VS996' or something. since it just words, it may not matter.
but maybe you used the wrong script for h932
In any case, the zip did nothing for me. flashing only took about 10 secs in total, and flashing system barely took a second.

So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work

JohnFawkes said:
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
Click to expand...
Click to collapse
Did you remove the file?
Sent from my LG-H932 using XDA Labs

BROKEN1981 said:
Did you remove the file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour

JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
Ahh ok, thought I was missing something.
Sent from my LG-H932 using XDA Labs

JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
looking forward to the fix.

I figured people might want these files.
Root-System-Media

Uploading new zip now! figured out all issues

JohnFawkes said:
Uploading new zip now! figured out all issues
Click to expand...
Click to collapse
Awesome thank you!
Sent from my LG-H932 using XDA Labs

BROKEN1981 said:
Awesome thank you!
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
no problem. should be live in about 15 minutes

zip is live!

Awesome. Woke up this morning to the system update notification. Glad there are still T-Mobile users around here that works to get this stuff out. Downloading now. Will report back after I flash it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:19 AM ----------
BROKEN1981 said:
I figured people might want these files.
Root-System-Media
Click to expand...
Click to collapse
Are these new in this update?

JohnFawkes said:
zip is live!
Click to expand...
Click to collapse
At the end of the flash it looks like it flashed fine but then it tells me it failed to mount everything. When I go to reboot into the system it tells me there is no OS. I was just going to flash the 20p zip I had but then it restarted and now I can't get into TWRP again. Now it just restarts into fastboot mode
UPDATE: I was able to get back into TWRP by going through the factory reset option (Volume down + Power, etc.) I'm now flashing the 20p zip I have.
UPDATE 2: Didn't work. Got into a bootloop. Restoring an old Lineage backup I have. Should have made a backup of my current state before flashing but I wasn't thinking
UPDATE 3: That didn't work either. Everything I flash it tells me failed to mount '/persist-lg' and just boot loops. I guess the next thing to do is try and use LGUP to restore

Same here as above. Doesnt mount system persist cache.

sunmybun said:
Same here as above. Doesnt mount system persist cache.
Click to expand...
Click to collapse
Flashing anything else doesn't fix it either. My phone is chillin' in recovery mode until I can figure it out

im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on

JohnFawkes said:
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
Click to expand...
Click to collapse
Thanks. Searching around, I see there have been people having issues like this before with other devices. Something to do with the persist.img. Did the last zip include one? Also, I hope whatever it is can be fixed with a new zip. I don't know why restoring a backup or flashing an old full stock zip wouldn't fix anything.
This is basically what I'm getting
http://en.miui.com/thread-467490-1-1.html