Database Develop

[GUIDE][XT1789-06+][EU/intl.] How to safely BLunlock/TWRP/Root/BusyBox/Xposed

WARNING #1: operations indicated on this post might potentially brick your device, make it unusable, to cause explosions, eruptions of nearest volcano and a lot of similar disasters.
For sure they will void your warranty in most countries and need all of your data permanently deleted, so make a copy of anything valuable before starting and don't do any operations if you are not a trained guy and sure about what you are going to do.
These are *not* operations for rookies. I will not be responsible in any case about eventual damages. XDA is your friend: if unsure, please ask! :fingers-crossed:
WARNING #2: operations elencated on this post are indicated and first hand tested as working only on Moto Z2 Force (Nash) XT1789-06 GSM/3G/LTE dual sim 6GB RAM 64GB storage unbranded international version on sale on German market with Nougat v.7.1.1 onboard.
They will probably work on most of unlockable bootloader & SIM unlocked versions, included US -04 versions too, but you'll test them yourself.
They are not intended for (US mainly...) CDMA versions (-01 & -03 if I don't go wrong...) since of a bit different hw/fw so avoid to apply them "as is" on those devices.
WARNING #3: there will probably be better methods to obtain same results and, for sure, there would be more in future. This is only a "recap" of what I've found working and applied first hand on my unbranded XT1789-06 Nash - with, IMHO, great results... - on November 2017.
I think this could be useful for many.
WARNING #4: I'm Italian, English is not my first Language, so... be patient!
1. INTRODUCTION
On this guide you will not find anything particularly new and/or not already present on this section of XDA.
So, why this guide? For some reasons...
First of all, to date every guide posted here is for a single operation (e.g. root, TWRP, etc...) and do not take in needed consideration interactions between single operations that, often, can be present, potentially dangerous and/or lead to unexpected behaviours.
More, for a single operation here there are often different posts with different guides/solutions and this could leads to errors and or doubts about what's better for our device...
Last but not the least, to date Nash developers here are mainly from US and so working on devices for the most part provided with branded fw and/or a bit different hw/fw respect to international unbranded versions sold on Europe, Asia, South America & Australia.
From my previous experience with my "old" Griffin (Moto Z) Motorola's fws are often interchangeable between devices with no (or only minimal...) issues at all, but, anyway, having a guide with operations first hand tested on same device is surely safer...
So, in this guide I'll link all best single guides posted here and I'll comment & link them to obtain a single complete "to do list" of works...
2. WHAT WE'LL GET
Following this guide we'll get a Moto Z2 Force with unlocked bootloader, latest available firmware (at present...) on board, a working TWRP recovery, complete root access, BusyBox support (needed for A LOT of interesting sw/tasks...) and Xposed support (I don't think I need to explain Xposed features & benefits here... ).
Taking in consideration how Moto's devices come with a "quite stock/vanilla" Android version on board, they are between the best devices to be rooted & Xposed provided to obtain a great customized system.
If you want to remain stock with your device eventually go with Samsungs (or similar...), but if you want a device that is a "blank canvas" for your customizations, Motorolas and this configuration would quite be the best you could want.
You are surely thinking about lack of Magisk and "SU hiding" solutions... obviously there are reasons for this.
Magisk: I have first hand seen how Magisk is a "very intrusive" software with its installation, it goes to modify *A LOT* of things on system partitions and this could leads to eventual issues/incompatibility.
More, it has its own rooting system (that in my humble opinion isn't better than SuperSU) that I preferred not to use (beneath I think it could be disabled... ) and that could conflict with SuperSU, if not now, maybe on successive Magisk updates (as it happened on my old Griffin... ).
Last but not the least, it seems to still have issues with particular partitioning present on our device (we'll see them later) and with TWRP flashing for same reasons...
Not to mention how, to date, it has really so few functions/modules we can't have using Xposed....
SUhide: there is a detailed guide on how to install succesfully SuperSU with its SUhide function on our device. On the same guide it's reported how that method is uncompatible with Xposed and leads to unsolvable bootloops if we setup both of them.
It is still not clear (to me...) if this is related to SUhide itself or to the different SU installation needed for SUhide to work but, anyway, I preferred Xposed obviously.
Not to mention that for Xposed have been developed some modules to succesfully hidden root (even if I don't know if they already works with Nougat... )
3. LET'S TAKE A LOOK TO OUR DEVICE
Knowledge is power. So, taking a look to our device particular features will help us to avoid errors and eventual issues...
Motorola developed our device with a new configuration/partitioning scheme seen before only on Google Pixels / Pixels XL, making our device probably the first "not Google" one to adopt it.
It is mainly marked by two news:
- there is no more a recovery partition :crying:
- there are two copies of boot and system partitions, called boot_a, boot_b, system_a & system_b and device is capable eventually to boot from every of them :cyclops:
Let's look them in details..
Recovery is obviously still present victory BUT it has no more its own partition, it is instead included in boot partition (where before there was only kernel and little more...) creating a potentially unwanted (by us tweakers, probably wanted by Google for the opposite reason! ) link between boot and recovery where safe rules would want them as unlinked as possible!
This leads to the need to flash a boot.img containing both kernel and recovery when we want to update only one of them (e.g. installing TWRP...) and this will have to be taken in account every time we would go to update kernel, TWRP but even when rooting (in fact, at first, developers were not able to gain root together with TWRP... issue then solved succesfully :highfive.
On Pixels their developers have found some methods to overcome this problem, but on our device, to date, we still don't have a complete solution to this issue. Anyway we are going in the right direction and it will be only matter of time in my opinion (especially since I'm "stressing" our developers to realize a similar solution...! ).
Double partitions for boot & system, often referred as "A/B partitioning" is a system introduced by Google to distribute OTAs in safer & seamless way, without interrupting user work during updates... (bah... ).
They are so totally unuseful as originally designed for US, since of going with TWRP/root, OTAs are no more a solution to upgrade and this partitioning scheme introduced some complications which have led to issues as with Magisk (as already seen...).
BUT as soon as we'll learn how to well manage them, new horizons will open (like updating fw on a partition still having the older one on the other for safety reasons and/or having two different fw versions and be able to choose what to boot from.. ). It's only matter of time...
Anyway in this guide we'll face them ever with safe in mind at the moment...
4. READY? LET'S GO WITH UNLOCKING BOOTLOADER!
If your device has unlockable bootloader (and if it is an international unbranded XT1789-06 it should have...!), you can easily unlock it with this good guide:
https://forum.xda-developers.com/z2-force/how-to/how-to-unlock-bootloader-t-mobile-t3654657
There is no more to say about this guide since it is well done, only some notes:
- guide title speaks of T-Mobile but obviously is suitable for international/unbranded too...
- please note that unlocking bootloader will wipe from your device all data & media storage (and they will be wiped again in successive steps, so *be sure* not having nothing valuable - e.g. your girl pics.. - before starting with procedures);
- install Motorola's latest drivers & fastboot provided on their site as hinted on guide. Don't skip this step to avoid potential issues in successive steps...
- if I don't wrong remember, step 8 of guide has to be repeated two times to confirm unlocking. Anyway look at your console messages and follow directions...
Reboot to system and make a fast configuration (we'll wipe them in minutes... ) to check all is ok and re-enabling usb debugging is preferred.
5. DOWNLOAD & UPDATE YOUR FW
I don't know with what firmware your device will come, BUT if it has anything *before* Nougat v.7.1.1 rel. NXPS26-122-68-1 we well go to update to this for following reasons:
- we need a (good) complete stock fw image to be flashed in case of problems;
- it is updated to September 2017 security patch;
- we have a TWRP with *this exact kernel* (they are linked in same image, remember?) for those (like me... ) which like a "so close to stock as possible" system...
This firmware can be downloaded from the following link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (about 2,35 GB..)
PLEASE NOTE: If you have newer firmware don't use this BUT try to download a matching version with your actual one.
Zipped file has to be fully unzipped into the folder containing fastboot executable (downloaded from Motorola!) on your PC.
If you get any error unzipping, *DON'T FLASH* anything and download again (eventually from another browser/PC).
Fastboot sequence I used is the following:
Code:
fastboot devices
pause
fastboot flash modem NON-HLOS.bin
pause
fastboot flash fsg fsg.mbn
pause
fastboot erase modemst1
pause
fastboot erase modemst2
pause
fastboot flash bluetooth BTFM.bin
pause
fastboot flash dsp adspso.bin
pause
fastboot flash logo logo.bin
pause
fastboot flash boot boot.img
pause
fastboot flash system system.img_sparsechunk.0
pause
fastboot flash system system.img_sparsechunk.1
pause
fastboot flash system system.img_sparsechunk.2
pause
fastboot flash system system.img_sparsechunk.3
pause
fastboot flash system system.img_sparsechunk.4
pause
fastboot flash system system.img_sparsechunk.5
pause
fastboot flash system_b system_b.img_sparsechunk.0
pause
fastboot flash system_b system_b.img_sparsechunk.1
pause
fastboot flash system_b system_b.img_sparsechunk.2
pause
fastboot flash system_b system_b.img_sparsechunk.3
pause
fastboot flash oem oem.img
pause
fastboot erase carrier
pause
fastboot erase cache
pause
fastboot erase userdata
pause
fastboot erase ddr
pause
fastboot reboot
That is ready to be put into a batch file to avoid errors and having the possibility to check results of every single flashing since of pause commands presence (press a key to continue to next file). Batch file has to be placed and started from same folder of fastboot & unzipped files to avoid errors.
Please note:
- I've added a fastboot devices command as first to check if your device is properly connected;
- I've used stock sequence of flashing BUT removed gpt (partitions) and bootloader for safety reasons (no need to flash them usually... and let Motorola upgrading your bootloader rarely is a good choice... )
If all flashes will go fine your device /data would be wiped (yes, again!) and phone will reboot after last command.
If something go wrong stop the sequence by CTRL+C and do not reboot your phone until you have understood/cleared/fixed what has gone wrong.
If fine, again... reboot to system and make a fast configuration (we'll wipe them in minutes... ) to check all is ok and re-enabling usb debugging is preferred.
6. INSTALL TWRP
This is a quite simple step, but you have to take a decision before you start...
I'll provide two different boot+TWRP image files as attachment to chose from (both of them realized by @joemossjr )
First one is composed by stock NPXS26 kernel and TWRP v.2 (it's a 3.1.1-0 in TWRP versions), while the second is composed by a kernel recompiled (with little modifications) from sources by joemossjr and TWRP v.3 (still a 3.1.1-0 in TWRP versions) with some little improvements (you can go to his thread for details on TWRP https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421 and to this one for details on Pantheon kernel https://forum.xda-developers.com/z2-force/development/kernel-pantheon-kernel-t3702208 ).
If you are on NXPS software version (flashed before) and want to remain "full stock" go with TWRPNPXS.zip, otherwise (you preferring newest firmware or want all newest features) go with TWRPREV3.zip.
Both files *have to be* decompressed, *can't be directly flashed* and your choice of them has to be flashed in fastboot mode with the command:
Code:
fastboot flash boot TWRPxxxx.img
where xxxx is matching your choice.
If all have gone fine, you can now reboot to recovery and make some backups if you prefer (please note you will need to place them to an sd card or to a plugged USB key, since internal memory will be fully deleted again soon...
PLEASE NOTE: during this phase still *don't enable* TWRP to Mount system as R/W ("Swipe to allow modifications for /system" message...) since it could lead to a not booting system if DM verity check is still enabled (it shouldn't since what @ChainfireXDA reported on Twitter, but it is better to be safe...).
A reboot to system to check all is still ok is preferred. If TWRP asks to install his app files on exit, *be sure* to decline/skip (ever! There is an option in TWRP to disable this request too!).
PLEASE NOTE: this way we are flashing ONLY ONE of the boot partitions with TWRP (usually boot_a) while the other (boot_b) is unaffected. This is a wanted behaviour to stay on "safe side".
PLEASE NOTE: On the linked thread @joemossjr put a flashable zip file to update it from inside TWRP itself which flash both boot_a & boot_b. So if you'll want to update to newer versions (and remain on safe side...) unzip that file too (instead to flash it in TWRP), extract boot.img contained inside and flash it with the same command indicated before.
Please note all newer versions will use Pantheon Kernel.
WARNING: If you will in future reflash kernel/TWRP to update them, you would lose both root & disabled forced encryption!!!
So, after every boot.img flashing *you will need*, before booting system, to boot TWRP and flash again SuperSU before reboot to system.
If you fail to do this you'll face bootloops and/or your /data partition will be corrupted. So a /data backup (on external storage!) before a kernel/TWRP update would be mandatory.
7. ROOT & DECRYPT DEVICE
In this step we will go to finally root the device and decrypt its /data partition. This operation *will delete all data again* on you device (downloaded files & pics too!).
Decryption of /data is needed for many reasons:
- to date TWRP is unable to work with compressed /data (and, anyway, it's ever dangerous to work with encrypted data backups/restore... )
- some advanced software you'll go to use could have issues with encrypted data
- a decrypted device is slightly faster
- you definitely will want it unencrypted... listen to me!
Since our phone will come "force encrypted" (it can't be disabled on stock fw!), we need SuperSU help on this and so we'll need to follow *at perfection* the following provided sequence!
Not all SuperSU are equals (more... they are all different! :silly so, tested working fine version to be used is this: http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
If newer will be out, don't mind, you could ever upgrade it from inside a working system...
Steps are:
- boot to fastboot mode (from off, VOL DOWN + POWER)
- from fastboot mode select RECOVERY mode
- go to wipe menu and select /data FORMAT (not wipe or factory reset, FORMAT!)
- if you have placed downloaded SuperSU zip file on SDcard or USB key browse to it in TWRP Install menu (otherwise connect your phone to PC and trasfer it to internal memory and then browse for it), then Flash it.
- *do not* and I repeat it, *do NOT* clear cache/dalvik cache
- reboot to system
First boot could take a while and probably it reboots one (or two...) times, but at the end it will boot... :fingers-crossed:
You'll have to reconfigure again your system BUT this time, if all has gone fine, it's the good one, so you can do a better configuration if you want.
You will need a working Play Store for next steps, so add a data SIM and/or a wireless network and setup a Google account to enable it.
To check if all has gone fine you should have:
- a SuperSu icon into apps drawer
- on Settings - Security there should be an option to encrypt your system (DON'T chose it! :silly instead of the previous "encrypted" status..
It could be a good moment to download an useful Root check app. A good one is Root Check by JRummy Apps which is able to check Busybox & Xposed presence too (and more...).
8. BUSYBOX & XPOSED
If you have reached this point and all is fine, now it's very simple to complete.
Both Busybox & Xposed can in fact be installed from inside a working rooted system, so...
- download from Play Store BusyBox (free version) by Stephen (Stericson), open it, grant root permissions and press Install button without wait all the (unuseful) checks
- reboot
- enable in Settings - Security the "unknown sources"
- download from here https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299 latest Xposed installer/manager apk
- install it, open it and grant root
- select Xposed v.88.2 (or newer if available) for arm64 (if many options are showed be sure to select this, arm64!!!) and select Install (*NOT* via recovery... simply normal Install)
- when prompted for a reboot, accept it.
Please note first reboot could take a while and, again, it could self reboot one (or two times...). When at last it will reboot... gotcha!!! It's cigar time!!! :victory:
Well... it has been a LONG WORK to write this as simple & complete as possible. I hope to not have inserted any error and to have been enough clear on provided instructions.
If you'll find any errors please report to me for corrections.
Newer & better methods are welcome too.
If you liked this, PLEASE USE THANKS BUTTON!
EneTec
MANY THANKS TO:
@seniorstew
@joemossjr
@jhofseth
@Uzephi
for their useful linked guides and/or great development! :good:

Reserved #1.

Reserved #2.

Awesome guide! One of the most intricate guides that goes over every last detail that I've read on XDA in a long time. Thank you. ?

...

Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)

3's&7's said:
Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)
Click to expand...
Click to collapse
Our device still needs some cautions & tips...

Issue with Modem/Radio
After following your guide to the letter, my phone would not connect to a mobile network and would say "Error while searching for networks" when I tried to force it to find one. I ended up following this guide to try and get back to a working setup:
https://forum.xda-developers.com/z2...m-stock-november-hybrid-rom-t-mobile-t3712795
Unfortunately, nothing is working. Any help would be greatly appreciated.
Thanks!
-Josh-

I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.

might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao

just Wow!! What a great post!!

Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!
Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!
Any one have full stock image, at least of the boot partition from Dual SIM, UK?
PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.

hashnon said:
Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!
Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!
Any one have full stock image, at least of the boot partition from Dual SIM, UK?
PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.
Click to expand...
Click to collapse
Bitdefender blocked it for me for the longest time, then after reinstalling minimal ADB and Fastboot, Motorola Manager, and allowing access to Windows File Explore through Bitdefender, it worked for me; check your antivirus, hope that helps.

Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!

hashnon said:
Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!
Click to expand...
Click to collapse
Oh my bad, lol

Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.

hashnon said:
Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave my general idea what to do and what to check.
Click to expand...
Click to collapse
Good to hear that, I got so mad when I went in and tried rooting my Z2F without reading this guide first on the very first day that I got it. ??

Deester4x4jr said:
I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

ilovemeow said:
might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

hashnon said:
Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?
How do you fix your wifi issue exactly?

[NOOB’s][DETAILED] [GUIDE] TO Backup/Restore Stock+ Unlock Bootloader + TWRP + ROOT

A/A & Welcome,
READ THE FULL GUIDE OR YOU CAN LAND IN TROUBLE
Ain't gonna work on pie official
AND DO PRESS THE THANKS BUTTON
Disclaimer
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or anything that happens to your device
INTRO
This is a full guide for unlock/relock, install TWRP, Root your device and backup/restore stock OS. Each and every step is explained thoroughly with pictures and videos.
I have ASUS Zenfone Max Pro M1 (6GB variant) (X00TD) (ZB601KL), so I can’t test for other variants. Please report back issues, corrections, omissions, etc., though the guide should work for all devices.
THINGS TO KNOW (IMPORTANT)
~Every text written in double quotes “” means the same written without the quotes.
e.g.:- “abcd” means abcd
“zxcv” means zxcv
They (“”) help to separate usual text from the other text (like a command, file name, etc.)
~If you have not enabled file name extensions then you will see files without their extension and vice versa
e.g.:- “filename”, “mypicture” in 1st case
“filename.extension”, “mypicture.png” in 2nd case, respectively.
~Boot Partition or Bootloader:-This is the partition that enables the phone to boot. Without this partition, the device will not be able to boot.
~Recovery Partition:-Recovery partition lets you boots the device into a recovery mode to perform recovery tasks.
~TWRP: - stands for TeamWin Recovery Project. It is a custom touch recovery that is GUI based.
~Flashing: - simplest: - installing
~Fastboot Partition: - lets us reflash partitions. (On device)
~Fastboot: - is an executable used to reflash partitions. It comes with the Android SDK. (On PC)
~Rooting: - an Android phone lets owner edit system files. Thus enabling various tweaks and use of apps that require root access.
~Device driver: - determines how PC will communicate with a device.
~Unlocking/Relocking:-With a locked Bootloader, booting into custom things is not allowed is not. Unlocking lets us do so.
~Reboot: - Switching ON AND OFF (in simple terms)
Requirements
MIND, PC, USB Cable, Internet, Fully charged PC (Windows OS), and obviously Asus Zenfone Max Pro M1
The Real Steps From Here
FOLLOWING THIS GUIDE YOU WILL PROBABLY LOSE ALL THE DATA ON YOUR PHONE SO MAKE A BACKUP FIRST (Don’t worry it’s in guide too)
STEP 1. Downloading all the necessary files
a. Here are 2 zip file with everything you will probably need following the guide :-
basic zip
extension zip
. I have tested the procedures using these files only so maybe other versions might not work. A “guide.doc” with the same text as in here (on XDA) is also present. It will be of great help if you don’t have internet connection in PC.
The basic zip file contains minium files needed.
The extension zip file contains the TWRP recovery(then one used in the guide),guide.docx ,and the videos used here too.
Copy the twrp file to unlock folder of extracted folder.
b. Extract the zip file above.
First download the zip file and Copy to PC
Then Right Click on it
Then click “Extract All”
Uncheck “Show extracted files…”
Click on “Extract”
The folder “zip” will be extracted
Done
This “zip” folder will be called extracted folder in the guide video link to extract zip
To download most up to date version of the files go to links present at last
STEP 2. BACKUP
a. Use an apk backup tool to backup app installers
VIDEO TO BACKUP APP INSTALLERS
b. Some APPS like Whatsapp, etc. have backup to drive function use that
VIDEO TO BACKUP WHATSAPP CHATS
c. Backup SMS AND Call Logs
VIDEO TO BACKUP CALL LOGS AND MESSAGES
d. Copy each and every file from you internal storage to PC.
Video to backup each file to pc
DONE
Step 3. UNLOCKING BOOTLOADER(Data will be wiped)
2 options:-
A. Official Method (NOT TESTED): -
In extracted folder go to “unlock” folder then “Official” folder. Install the “UnlockTool_9.1.0.3_180621_fulldpi_signed_ZB601KL.apk” in Asus and follow the steps from there.
B. Unofficial Method (Tested):-
a. Installing Drivers
Connect phone using USB cable to PC
Right click on This Pc
Go to “Manage” > “Device Manager” Or Just search for “Computer Management”/“Device Manager”
A list will appear.
Find your device (best way to do so is by disconnecting/connecting the device and notice the changes accordingly in the list)
Now right click on it>”Update Driver Software”>“Browse my computer for driver software”
Now either enter path of the driver folder or click on browse and navigate to the driver path from there.
Press Next OR
“Let me pick …”>and select the driver
video to install driver
The drivers have been installed
b. Booting into FASTBOOT
Switch Off the Phone
Hold the Volume UP and Power ON Button Simultaneously
Device buttons labbled image
You will see this on your phone
image of FASTBOOT screen
c. Unlocking Bootloader
Now connect phone using USB cable to PC
Look for the “unlock” folder in the extracted folder.
Open it
Find “unlock.cmd” or “unlock” file
(Or “unlock no erase.cmd” to keep data {not tested})
Open it
Done
d. You will see some messages in yellow/brown/white colour on your phone
You will most probably see “encrypting your device”, “warning Bootloader unlocked” messages, let phone do its work and don’t interrupt it, and keep cable connected. Phone might reboot too. The phone will at last boot into stock OS and you will see the device setup screen.
image of the warning message
e. Now if you wanted TO ONLY UNLOCK BOOTLOADER THEN THE JOB IS DONE, long press power button. If you want to root or flash TWRP then continue (Tested method to root requires TWRP flashing or you can try the untested method to root only)
Step4. Installing/Flashing TWRP
TESTED METHOD
a. Connect phone using USB cable to PC
b. Don’t setup your device just now because possibilities are you might lose the data again
c. Boot into fastboot mode
d. Open the “unlock” folder in the extracted folder.
Now Two Different ways to opt for from here:-
i. THE LAZY METHOD (Tested)
a. Open “flash_recovery.bat” or “flash_recovery” in the “unlock” folder of the extracted folder.
b. You can flash the tested or any other recovery using this script.
c. Follow the steps from the script
video of how to use the script
d.Then go to step of Flashing ZIPS of The Manual Method
e. Done
OR
ii. The Manual Method (Tested)
a. Keeping Shift Key pressed, right click {with mouse} in the blank white space of the “unlock” folder’s explorer window.
b. From the menu select “open command window here”
c. A CMD window will be opened
open cmd video
d. Now type “fastboot devices”
e. See if your device is connected. You will see something like this
f. Now type “fastboot flash recovery twrp-3.2.3-0-X00TD-20181024.img”
If you want to flash any other recovery instead of “twrp-3.2.3-0-X00TD-20181024.img” write the file name of your recovery file. Make sure it’s in “unlock folder”. Though this recovery is the only tested one (by me).
g. Now keeping the phone connected to PC, boot into TWRP/Recovery by pressing the Volume Down and Power ON Button Simultaneously.
h. The usual warnings, messages and recovery boot screen will flash:-
warning image
twrp flash screen image
i. It may take some time to load so wait for at least 2 minutes.
j. Now if touch is not working press power button 2 times (on and off the screen)
video showing how to enable touch in twrp
k. If it shows “Swipe to Unlock” do so. If it shows “Swipe to Allow Modifications” then wait and continue reading …
swipe to allow image
swipe to unlock
l. “Swipe to Allow Modifications” means you allow TWRP to modify system. This will make sure TWRP remains in the phone and not just vanish after a reboot but it also means you will have to flash some other files to be able to boot into stock rom back.
m.
2 ways from here:-
i. Now after swiping, Decrypt Screen will appear just press cancel.
decrypt screen image
OR
ii. If you have data on the device then enter pin/password or try default_password.
If you had kept pattern then either go back and change it or try this:-
1 2 3
4 5 6
7 8 9
these no’s correspond to pattern dots.
Say you kept pattern “third row left to right” then the password is 789 .
If all these fail then you will have to lose your data.
n. As we don’t have any precious data in our phone we will (or you are compromising)
Press “Wipe”
Press “Format Data”
TYPE “yes”
Press “tick” or “enter key”
Done
wipe data video
>Flashing ZIPS
o. Now Copy these 2 files
i. “decrypt.zip” or “decrypt”
ii. “Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip” or “Disable_Dm-Verity_ForceEncrypt_12.16.2018”
From extracted folder to your phones internal storage.
p. Go to Install>select the zip>swipe to flash (flash dm_verity… then decrypt…)
If you don’t see your device storage connected then try reconnecting using USB cable and also check if MTP is enabled.
enable mtp video
>Done
Want to root? Then continue…
or >
Now reboot to system Go to Reboot>System
video to show how to rebbot to system in twrp
Step 5. Rooting
We will be using Magisk to root you can use any other method but this is the only tested method.
a. Copy “Magisk-v18.0.zip” or “Magisk-v18.0” to your phones internal storage from extracted folder.
b. Go to Install>select Magisk…>swipe to flash
Done
c. Now reboot to system Go to Reboot>System
reboot video
e. To use Magisk properly you may need to download latest apk. (Link at last)
Step 6. Relock (NOT TESTED)
a. Connect phone using USB cable to PC
b. Boot into fastboot mode
c. Open “Relock” folder from extracted folder
d. Open “relock.cmd” or “relock” file
Done
Step 7. RESTORING
a. First setup the Device again
b. Copy each and every file back to the phone storage
c. Now to restore messages see the restoring part of this video here
d. WhatsApp messages will be automatically restored after you install the app with same number as before.
Tips
After rooting don’t just go on and flash a custom rom. Take a backup first (of all partitions) using TWRP and keep it safe somewhere so you won’t need to find unbrick tutorials later. Plus you will have your most stable and tailored rom with you.
Also don’t just go on and flash xyz mod. Research and then Flash.
Magisk is our best friend. It lets you do modifications without hurting the system. The Magisk modules are most safe mods as they can be reverted back easily.
And don’t just go on and debloat stock OS. In Magisk there is a module called Debloater use that. You can easily revert back if anything goes wrong.
Other good Magisk modules: - Energized, Systemizer, MidnightCore & Advanced Charging Controller (acc) but do read their XDA guides first.
Sources/Credits:-
Dm_Verity.zip Official XDA:-
link
Original unlocking XDA:-
link
Magisk XDA:-
link
Original Decrypt Data XDA:-
link
TWRP Used XDA:-
link
Credits to the authors of the above guides
Plus sorry for bad editing of videos. I am facing some problems. Will try to post better videos.
I thank all the members who have made the previous guides for their hard work. This guide by no means disrespects their hard work. This guide is just an Addition instead of an Alternative.
Read the full guide
Press the thanks button

Re edited the guide.
Added link of apps used in YouTube videos.

Not working for pie official

Deleted cruddy comments. Good job.

Good initiative but not so good noob guide. Please format it for better organization and better understanding.

malikmiran19 said:
2. BACKUP
>Use an apk backup tool to backup app installers
howto video
Click to expand...
Click to collapse
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/

camaroamarelo said:
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
Click to expand...
Click to collapse
Did so

GliderZ said:
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
Click to expand...
Click to collapse
Added apk links in YouTube videos

Anyone tried unlocking without erasing data?

TheDarkKnight said:
Anyone tried unlocking without erasing data?
Click to expand...
Click to collapse
nyimak

fuzuy said:
nyimak
Click to expand...
Click to collapse
What?

TheDarkKnight said:
What?
Click to expand...
Click to collapse
it means im interested in your question and im following it

I want to unlock bootloader, flash TWRP and flash a custom ROM (Cerberus OS).
I have rooted and flashed TWRP before in my previous device but I'm not familiar with unlocking and Custom ROM.
Do I have to follow all hese steps for what I want to do or I must skip decrypt/encrypt and Magisk?

dharsouparno1 said:
I want to unlock bootloader, flash TWRP and Custom ROM.
Click to expand...
Click to collapse
U can flash twrp then flash ROM and probably flash magisk for root tooo

malikmiran19 said:
U can flash twrp then flash ROM and probably flash magisk for root tooo
Click to expand...
Click to collapse
Thanks for the help.
I'm running into some problems while installing the driver software on my Windows 10 laptop. It shows Error 10 this device cannot start.
I tried to uninstall and reinstall the drivers, rebooted my pc on every step, tried to install while connected to my phone, but nothing seems to work.
I've installed the Pie Beta for Asus Zenfone Max Pro M1 (not sure if this is causing it)
Is there a solution to this problem?

I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root

thanks its working

I updated to pie beta and I think this guide is not working for that, because when flashing twrp. I'm getting 'request download size is more than allowed size' and I tried every way possible to solve it. But no luck Hope you can help me with it, or maybe it'll work after stable version?
---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------
utsavdey said:
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
Click to expand...
Click to collapse
It's not working for me. I also updated to pie beta few days back.

Is this method working on pie stable build

Anyone tried this method on the stable pie build 056?

[Guide]Installing Lineage

Installing Lineage​
Few quick things.
LOS 18.1 is now official so the guide will now just be covering that.
I also want to address a common question, you can use Windows for this process. I prefer Linux, and Fastboot just works in Linux without driver issues. If you have Fastboot and ADB working in Windows already feel free to use that if you want.
Frequently asked Questions:
This looks like a lot of work, is there an easier way to install? Try the LOS Wiki Method.
Using TWRP 3.5.2_9-0​1. Start off Fresh. Install OOS using the Fastboot ROM.
Start off with a fresh install of OOS. You need the latest version of OOS 10. I typically use a the fastboot ROMs for this as it will do both slots for me at once. (Alternatively you can use TWRP and install the ZIPs and do it twice to get it on both slots, or my least favorite, the MSM Tool if you want. Doesn't matter how OOS ends up on both slots, as long as it ends up on both slots.)
I use Linux, and honestly I feel like it's easier and more reliable for fastboot and ADB so that's what I'm including here in these steps. It's easy to boot from a USB.
To create a bootable Linux flash drive you can use Unetbootin, which you can download for free here (Your other option would be to burn the ISO straight to a DVD and skip the unetbootin step):
https://unetbootin.github.io/
For Linux, I'm using Linux Mint Cinnamon, You can download for free here:
https://www.linuxmint.com/download.php
Then run unetbootin (yours will look a little different, I'm running it in Linux):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Point it to the Linux ISO, and tell it where an empty flash drive is. It will erase everything on the flash drive. Afterwards you can load whatever you want on the flash drive. However be aware when booting Linux from this drive you can't access what is on the drive (at least not by normal methods).
After this has successfully completed, reboot the PC, and boot from the USB drive. Your PC will boot into Linux (turning off the PC and removing the USB drive will make it boot up like normal again).
Next we need to install fastboot and adb. You need to open up the "start menu" and open the "synaptic package manager". You can find this stuff in the menus, however the easiest way to get to these items is to just start typing the name of the item. See below:
Search fastboot, click the boxes, choose install. Then search for ADB, click the boxes, choose install and then click apply. It's that easy it will download everything that's needed and install.
Time to open up a terminal:
Just to make sure we don't run into any problems we need to update adb and fastboot. In the terminal run these commands to update fastboot and adb (this is downloading them directly from Google).
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
You will also need the appropriate fastboot ROM. Fastboot ROMs available in this thread. The catch being that thread is no longer updated. So we will need to make our own fastboot rom. To do this we need two things:
1. The stock rom zip (OP Site).
2. Payload dumper. I've yet to get the one from the GitHub link to work, so I've been using the one from this Article. Direct Download Link
You need to extract the payload.bin file from the stock rom zip. Extract the payload_dumper files as well, and place everything in the same folder. Payload_dumper requires python3. Open up Synaptic again, search for python3.6 and install it. Now open a terminal so we can extract the images from the payload.bin.
Navigate to the location of payload_dumper and your payload.bin file. In my case my commands are:
cd Desktop <-- switches to the Desktop folder
cd payload_dumper <-- switches to the payload_dumper folder on the Desktop
python3 payload_dumper.py payload.bin <-- runs the payload_dumper "program" and extract the images from the payload.bin
Now would be a good time to back everything up. The phone will get wiped. Extract the fastboot images to a folder that is easy to find. I would recommend the Desktop.
Now it's time to flash all those images we just extracted using payload dumper. Place the phone in fastboot mode. You can do this using the advanced reboot menu, ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
You can flash the images one by one or use a script. My script is available here. Flashing the fastboot ROM should look something like this:
That image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
cd flash <-- I put my fastboot images in a folder called flash. This stuff is case sensitive. My folder was all lowercase.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo sh FlashThese.sh <-- Tells the terminal to run my script, since the script contains fastboot commands it must be run as root.
At the end you should get something like this:
Then just choose start form Fastboot (If you were previously on a custom ROM go straight to recovery and wipe everything). Not booting and getting dumped off at the OnePlus recovery screen is nothing to worry about. Choose your language of choice, Wipe data and cache, Erase everything (Music, pics, etc), This can not be undone, continue. After that the phone will boot. Once booted enable developer options, advanced reboot, and reboot to fastboot.
2. Installing TWRP.
First step is to boot the correct TWRP image. Grab the current TWRP from the official site. You need both files, the img file, and the installer. Once again from the terminal:
The image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo fastboot boot twrp-3.5.2_9-0-fajita.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
Once in TWRP the phone should show up as a media device so you can copy files to it. Copy the TWRP installer over to it. Choose Install from the TWRP menu and navigate to where you placed the TWRP installer. Press on it, and swipe to confirm flash. When it is done hit the back button until you are back out to the main menu.
From the main menu choose reboot, and choose Recovery:
The first time you try and reboot the official version of TWRP it will ask you if you want to install the TWRP app. Do NOT install the app. In the settings you can disable this prompt. Your other option is just uncheck both boxes at the screen you see below when you get to it, and then click the button that says do not install. Do use the slider. At that point the phone will reboot as to recovery as you selected.
Now that you are back in TWRP that is now installed, time to wipe the phone. From the main menu choose Wipe. Swipe the factory reset slider at the bottom. Then hit back. Next hit Format Data. Type Yes to Continue. Hit back to continue. Keep hitting back till you get to the main menu.
Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. So go back into the reboot menu, choose reboot to recovery again (swipe to allow modifications if it asks). You must do this after formatting data.
3. Install Lineage
Links:
Lineage 18.1 XDA Thread
Official 6T Lineage Downloads
The phone should still be in TWRP at this point. You now need to copy Lineage to the phone. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. If it's not on the phone, just copy it over again real quick. On A/B devices ROMs get flashed to the opposite slot. Things like Gapps, Magisk, etc get flashed to the current slot. We need Lineage on both slots, so it must be flash again. Flashing it twice only needs to be done the first time as we need to get rid of OOS. For updates it just gets flashed once. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
Once back in TWRP flash Lineage again. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Now run the TWRP installer again. Back out to the main menu, and reboot to recovery.
4.Optional, Gapps
Links:
NikGapps <-- For Lineage 18.1 (Use the R Folders for Android 11. I recommend the "Core" version. I also tested Basic though if you want that level of Gapps. I strongly recommend you grab setup wizard out of the R Addons Folder, I used the regular setup wizard, not the pixel one.)
MindTheGapps <-- It's worth mentioning here Lineage recommends MindTheGapps for 18.1. Take your pick. I personally use NikGapps as I can use a "leaner" Gapps package.
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
5. Very Optional, Magisk
These steps are very optional. However this is how I, root, pass safety net, and get a various apps to appear in the Play store.
Flash Magisk in TWRP. For Magisk 23, you now have to rename the Magisk.apk to Magisk.zip. Then flash it in TWRP. If you wanted to uninstall it, you rename it to uninstall.zip. If you already had an older version of Magisk installed, make sure you do not have it hidden / nenamed when installing Magisk 23 for the first time. Restore the original package before installing 23.
Magisk <-- Flash this right after Gapps.
These items are add-ons are flashed in Magisk after the first boot (Don't flash these in TWRP anymore):
MagiskHide Props Config
Busybox
To flash modules in Magisk press the puzzle piece icon. Then choose install from storage. Now just choose your addons. After flashing the icons it will have a reboot icon at the bottom. You can reboot or you can press back and flash another. After you are done reboot.
You will also need a Terminal Emulator. I personally use:
Terminal Emulator for Android
Once all these are installed the first step is setup Magisk. Under Magisk go to settings:
In version 20.4+ Magisk Hide is no longer on by default. So make sure the Magisk Hide, Hide Magisk from various forms of detection switch is flipped. Then press Hide Magisk Manager. This will bring up a box for you to choose a random name for the Magisk Manager, type whatever you want here. You can leave it Manager if you wish, but I typically change this.
Now open Magisk again. It will ask you to download it again, click ok, then manually open the app again as it says. Now we need to open Magisk hide. This is now under the shield icon, then click the arrow at the top:
These are the apps you don't want to know that you have root. Less is better. You can cause instability problems by just choosing everything. My general rule of thumb is, Google, steaming video, music, and payment apps get selected. In my experience if I come across an app that needs it and I didn't select it, I just clear cache and/or data and re-open the app and it works. There are some big multiplayer apps that ban hardware / people, so do your research (don't ask me, I don't play those games).
Next time to change the device fingerprint using MagiskHide Props Config Module. We do this using the terminal emulator. In the terminal emulator, type "su" to gain root privileges. Then type props to run the module:
Now it's just following the menus. Choose option 1 - Edit device finger print. (type 1, hit enter)
After this you will see a menu of devices. It doesn't matter what device you pick really. If you want apps / Google to think you have a OPPO or Samsung pick one of those Fingerprints. However there's a bit more to passing Safety-net than that. Since Google has changed how things work not all those fingerprints that used to work will work now. Also now you may get an error when you turn on the phone because of the security dates. The OP6T Android 10 fingerprint has no issues at this point, so use that if you want:
After choosing the fingerprint you want, it will ask you if you want to reboot. Choose yes. After rebooting, you may need to clear the cache from the play store for some apps to appear in it. You should now pass safety net. Check this in Magisk:
6. Very Optional, Ad Blocking with a Host File.
You can block many things with a hosts file, most popular would be ads. I've been use StevenBlack's host file which is a compilation of several hosts files. This is located on Github:
https://github.com/StevenBlack/hosts (Scroll down you'll see the options of what you can block)
Direct link to the hosts file I use. This will block Adware / Malware.
Unfortunately for quite some time now on this device you can no longer just use a root browser to swap the hosts file. The easiest way is to use TWRP.
First we have to make the hosts file. The hosts file must use unix / linux line endings. If you are using linux, don't worry about this, just create the file. If you are using Windows, the easiest thing to do is use Notepad++ (Free).
Notepad++ Downloads
Next one other caveat. The hosts file is quite large. I've never had much luck copy and pasting it from any other browser than Firefox (Windows or Linux), but however you get it into Notepad++ is not a big deal.
Once in you have the hosts file into Notepad++ go to Edit, EOL Conversion, and Choose Unix (LF).
Now save the file as "hosts" no ending. This does mean under file type you will need to change it to All File types *.*. Move this hosts file to your phone. Then reboot to recovery. From the main TWRP menu, choose mount. Then mount system:
Hit the back button and go to the advanced menu. Choose File Manager:
You will find your hosts file under /sdcard, wherever you placed it. In my case I placed it in a folder called ROMs. Once you locate it, press and hold it for a moment, and relase. Then choose copy file:
At this point you need to tell TWRP where you want to paste the hosts file. It belongs in the /etc folder. The only hic-cup here is depending on what you were doing in TWRP this could be (on this device) /system/etc or /system/system/etc (you will see similar folders to the image below if you are in the right place). Once you are there, press "paste?" button in the lower right corner:
After this just swipe to confirm:
You can now reboot the device, and your hosts file should now be in place. Your ad block should now be active for all apps as it's global for all connections.
7. Reboot to system.
Updating Lineage​
1. Flash Lineage.
Reboot to recovery. You can use the advanced reboot menu, or Volume Down + Power while turning the phone on. Don't wipe anything. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
2. Optional, Gapps (if you installed them once you must continue to install them or do a clean install)
Links:
NikGapps
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
3. Reboot to system.
Last updated​Since I don't want people to have to wonder if these instructions are current, I am going to periodically test and update this post with my results. Please note I'm testing with a 6T, TMobile 6Ts are different. You can generally assume previous versions of LOS and OOS were also tested, but if you are unsure feel free to ask in this thread.
Last tested with:
OOS 10.3.7 and LOS 17.1 12-31 with TWRP 3.4.0-2
OOS 10.3.11 and LOS 18.1 05-27 with TWRP 3.5.2_9-0
This method has also been tested with:
OOS 10.3.3 and Omnirom 5-24 MicroG and Omnirom 5-24.

Cliff Notes
*TWRP 3.5.0_9-0+ Must be used with LOS 18 / 18.1
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery (This step wipes the device, make sure you backed everything up!)
- Factory Reset. (This is the slider at the bottom, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else)
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash Gapps (Optional)
- Flash Magisk (Optional) (Remember for ver 22 the Magisk.apk gets renamed to Magisk.zip, can also be renamed to uninstall.zip for uninstalling)
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
After this you should be able to update Lineage as normal.
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Optional, but if you flashed them once you have to keep flashing them.)
- Flash Magisk. (Optional)
- Reboot to system.
- No loss of data, or anything.

Thanks for the guide, able to flash los 17.1 successfully.

How to go back to OOS?
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?

fordjonathan said:
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
Click to expand...
Click to collapse
Back up your data, use Step 1 of these instructions. That will put OOS back on your phone.
MSM Tool, always my least favorite option, but always an option.
MSM Tools for Regular 6T (TMobile uses a different one)

installed 17.1!
OhioYJ said:
Installing Lineage...​
Click to expand...
Click to collapse
Massive thanks for your instructions!
- at first, I tried upgrading from LOS 16.0 to LOS 17.1. I followed the instructions on the wiki, but it landed me in the qualcomm crashdump mode.
- after that I ran into your instructions, and tried to follow your update guide, but it didn't help (not very surprising I guess, but I haven't had much to lose at this point ).
- after that, I just followed your fresh install guide (i.e. flashing the fastboot room and starting from scratch), followed every step and it worked!
I wonder if it's worth updating lineage OS wiki and pointing to your instructions? There is bunch of people in this thread, who also bricked the phone into crashdump, so perhaps it could help to prevent it for someone else.

Updating to LOS 17.1 ?
Dasseem said:
Thanks for the guide, able to flash los 17.1 successfully.
Click to expand...
Click to collapse
Initially I had problems with updating LOS, so I returned to Stock. As more people attempted to install LOS, and this fine Original Poster "Ohio" offered such excellent, and detailed instructions, I have been running LOS 16 since February.
However, I have not updated it, since I have had Zero Issues.
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:

barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Click to expand...
Click to collapse
Hi, I updated my previous reply to make it a bit more clear!
Yep, I was on LOS 16. Haven't had any issues, but figured why not update if I'll have to do it eventually
So I downloaded 17.1 and used the wiki instructions, which messed the phone up
Ended up flashing fastboot rom and starting from scratch, flashed gapps and magisk according to OhioYJ's instruction and it worked.

Flashing method
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
Click to expand...
Click to collapse
I was using carbon ROM previously, had to move to OOS latest for flashing the lineage 17.1, believe it needs to be done if you are coming from pie, people know better correct me if I am wrong here.
As Karlicoss mentioned, it's better to follow the method posted by Ohio.

OhioYJ said:
Cliff Notes Versions
Installing Lineage
- Install fastboot ROM boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk if you use Magisk. Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone may restart once, then Lineage will start up and all will be good.
Updating Lineage
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (Optional If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
Click to expand...
Click to collapse
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...

badpanda said:
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
Click to expand...
Click to collapse
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.

OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
No, no clean install. Just wanted to update to today's newest build os.

bump...

Thanks a lot for your guide. Very helpfull.
I'm using it with /e/ rom.

installing android 10 roms
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????

sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Just cycling airplane mode doesnt work? This isn't a TMobile 6T is it? You are in Sim slot 1? You maybe better asking in the LOS thread, and provide log it not working and then it working when you reinsert it. Im not quite sure whats going on there.

OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
So this means you do have to always format data for every single update??
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Change your sim card to the other slot...
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
@OhioYJ So for an update you boot to recovery flash LOS latest version then flash twrp again and then reboot to recovery second time then format data to possibly decript encrypted system and, transfer files both gapps and magisk to device and then install gapps and magisk, lastly just reboot to system?

reply
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.

badpanda said:
So this means you do have to always format data for every single update??
Click to expand...
Click to collapse
No that would be ridiculous. Not necessary at all. You have something else going on, but I dont know what. My update procedure is exactly as listed on the OP, on two 6Ts, two different carriers.

sickpoppy said:
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
Click to expand...
Click to collapse
A TMobile "converted" to global does not equal a global 6T. Logs posted in the LOS thread, may help out other TMobile users? The TMobile 6Ts introduce all sorts of quirks, and Im afraid I dont have any experience with them, so hopefully another TMobile user will be able to help.

Alternative method magisk root [stock android 9][NO TWRP][Samsung A70 FN/DS]

purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
 @raeumler for his guide.

Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.

kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10

Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka

Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?

DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods

i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....

raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.

[ROM][UNOFFICIAL][12][S]LineageOS 19.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.

Which GApps would you suggest?

I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.

Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.

I've set the state of the development to BETA due to quite good overall performance.

After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.

I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:

Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.

I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0

I'll take a look into it asap. Please be patient.

I can't find any reason for the crash; I'm sorry.

New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.

New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2

Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.

New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022

Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?

kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?

Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check

Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..

Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.