easy Way to root and install trwp on z ultra with marshmallow 6.0.1
tested on Aospa 6.0.1
first to install trwp twrp-3.0.2-0-togari
1-turn off your mobile and put in fastboot mod
2-copy twrp-3.0.2-0-togari on Minimal Adb installed folder
3-open Minimal ADB and type fastboot flash recovery twrp-3.0.2-0-togari.img
down we have trwp installed now
next setup restart on trwp recovery and flash BETA-SuperSU-v2.77-20160827190633
after restart install super su from goolge play and you are done
download from here
http://forum.xda-developers.com/showthread.php?t=2317790
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-recovery-2-8-7-0-2016-02-03-t3307043
https://download.chainfire.eu/999/SuperSU/BETA-SuperSU-v2.77-20160827190633.zip
XDA:DevDB Information
(guide) How to Root and install twrp marshmallow 6.0.1, Tool/Utility for the Sony Xperia Z Ultra
Contributors
andro971, 1, i
Source Code: i
Version Information
Status: Stable
Created 2016-09-01
Last Updated 2016-09-01
Reserved
Reserved
TeamWin Recovery Project 3.2.3
WARNING #1: Flashing a custom recovery voids your warranty. I'm not responsible for misuse of the recovery which make soft brick the phone.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
FEATURES
1. SUPPORT SD CARD IN RECOVERY !
2. DATA RESTORATION SUCCESSFULLY FROM ROM BACKUP .
3. DUALBOOT PATCHER SUPPORT. ( STOCK ROM: DO NOT UPDATE RAMDISK AS STOCK KERNEL CONTAIN ENCRYPTION !!! )
HOW-TO INSTALL
Flash it via old twrp and restart to recovery.. enjoy
SUPPORTED DEVICES
SM-G316HU
vivalto5mve3g
(Test your Device, if you want to take the risk )
CAUTION !!!
FLASH THIS RECOVERY WITH TWRP APP OR PREVIOUS TWRP
Latest TWRP Download
Updated Link Shared In Next Post.
Contributors
Omni 5.1.1 Minimal Twrp Source
Ubuntu 16.04
Google
HWDEV
****
More Information Given Later
XDA:DevDB Information
TWRP RECOVERY, Recovery for the Samsung Galaxy Ace 4
Contributors
HWDEV, Google
Kernel Special Features: Updated
Version Information
Status: Stable
Current Stable Version: 3.2.3
Stable Release Date: 2018-10-09
Created 2018-10-08
Last Updated 2018-10-28
TWRP 3.2.3 From Latest Sources By TWRP BUILDER
Fixed By HWDEV
TWRP_3.2.3
Twrp materialised using auto materialised tool
Twrp materialised
ABOUT VERSIONS OF kvt:
2.x is if you're coming from stock Oreo or Pie
3.x seems to be only for stock Pie (otherwise networks don't work) - Oreo modem still has to be flashed though
There is a guide for GSI, but it is outdated, no longer maintained and all links are dead. That's why I'm creating this up to date guide.
If you do not know, what is Project Treble and GSIs, google it first. Proceed only if you know what are you doing. This guide is only for those, who know what is bootloader, fastboot, recovery and TWRP. If you don't, learn that first. There are many guides (for example guides for rooting and Magisk) UNLOCKED BOTLOADER REQUIRED
Guide
1) Download needed files:
- treble recovery: https://mega.nz/#F!b8RgGQCa!48TRsDcJFpaAGNOcc9Fb-A?GxR2TCAA
(this is my mirror, as original links are dead, don't know who is the original developer)
- kvt (find lastest version here) https://androidfilehost.com/?w=files&flid=303096&sort_by=date&sort_dir=DESC (developer deivesj)
(this allows GSI to work on Moto Z2 Play with some of it's stock features like fingerprint gestures, device gestures, pass safety-net and more)
- if you want to use Android 9.0 Pie based ROMs and older, you might want to use V7 kvt instead:
https://mega.nz/#!7w5V1KpQ!uoCMqynn5D83trvZ6uXY30S8b9rLiBlXf1JTeMYQ0rc
- if you are coming from stock Android 9.0 Pie ROM, you will need modem from Android 8.0 Oreo
https://mega.nz/file/mxhxXCaI#nJpdQ3nPnc6urkYP8vLrVb_vc_7EsnXK7MXw3U1xohw
- you may need stock recovery https://mega.nz/#!XphFEIxK!yNdHJSakfO90K1ua92SODoqd85nvwRi7h65EA8RkOuI
-GSI of your choice (links below)
transfer kvt to your phone to external microSD, keep the rest in your PC
1) go to fastboot mode (power+volume up simulaneously)
2) flash treble recovery (using fastboot command: fastboot flash recovery 'filename.img')
3) boot to recovery and wipe system, data, cache
Note: after boot to recovery, touchscreen doesn't work. Turn screen off and on to make it work!
4) in recovery, flash kvt zip. It will guide you through
5) reboot back to bootloader
6) flash chosen GSI as system image (fastboot flash system 'filename.img')
7) if you are coming from stock Pie, flash Oreo modem (fastboot flash modem NON-HLOS.bin)
reboot
Note: If you are coming from stock ROM, decryption may fail. The easiest way is to temporarily flash stock recovery. After decryption fails, it will prompt you to reboot and format data. TWRP can't do it, but stock recovery can. After you are booted, you can flash TWRP again.
Where to get GSIs:
the biggest list is here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
For Z2 Play, always download arm64 version and Aonly
There is a folder with ported stock ROMS (MIUI, Samsung, Moto...) on mirrors.lollinet but they do not work on Z2 Play. I also tried various stock ROM ports from other sources and they did not work. Custom ROMs fork fine.
Magisk:
Standard Magisk versions may not work. If you get bootloop, after installing Magisk, flash uninstaller. Then you can try phusson's version:
leodexe said:
Updates:
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
Click to expand...
Click to collapse
Ask if something isn't clear.
updated treble
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Confirmation
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
lordfinix said:
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
Click to expand...
Click to collapse
I don't use fingerprint gestures so I can't tell you about that. Also I had experiencing some crashes and reboots with this GSI lately, so I will try with another one once I can access internet to download anothet GSI.
CONFIRMED
i confirm it by flashing the flickering issue is gone and the gestures works as well this is by far the most stable KVT released kudos to developers
There are new versions of kvt available. Check the updated first post for link to deivesj's last files.
I did not experience any flickering or other graphical glitches with the new (2.X) versions of kvt (unlike the old v8 one).
Fingerprint gestures work, but not in all gsis
leodexe said:
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Click to expand...
Click to collapse
Thanks, I will update the guide
Could someone please give me a mirror of kvt v2.6? androidfilehost is terribly slow...
Hello,
Seem to have lost my network after flashing the pixel experience gsi from stock. imei missing as well. Any help?
It may be problem with modem.
What was your stock ROM? 8.0 or 9.0?
What version of kvt did you use? 2.x or 3.x?
How install?
how is the modem installed?
It's explained in the guide, step 7.
Wrongly flashed modem may cause WiFi, Bluetooth and SIM not to work
Kvt link is down. But you can use LineageOS with treble support now
Lineage Recovery for S10 Lite (SM-G770F/FD)
Other type of S10 Lite models are not tested yet.
Flash Guide:
Unlock your bootloader and disable AVB
If you dont know how to:
https://forum.xda-developers.com/galaxy-s10-lite/development/how-to-root-galaxy-s10-lite-t4099777
Go to download mode
Put the .tar file to AP slot in Odin, and click start
Reboot to recovery via recovery key combo
Not working:
Internal storage access
Decryption
Download:
https://github.com/mainey/release-r5q/releases
Join the telegram group: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
I do this kind of stuff on my free time. If you like my work, please consider making a donation with the link below.
paypal.me/michbt
XDA:DevDB Information
[RECOVERY][G770F] Lineage Recovery, ROM for the Samsung Galaxy S10 Lite
Contributors
Vaughnn
Source Code: https://github.com/mainey/android_kernel_samsung_r5q
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: BTF1 and up
Based On: LineageOS
Version Information
Status: Beta
Created 2020-08-18
Last Updated 2020-08-18
Reserved
Im gonna test it tomorrow morning. God bless u and a Big thank u!!!!!
great.
As there isn't anything to flash yet, is it useful for anything right now?
Edit.. I just show the 1st rom, so i got my answer
sosimple said:
As there isn't anything to flash yet, is it useful for anything right now?
Edit.. I just show the 1st rom, so i got my answer
Click to expand...
Click to collapse
Even if there was no ROM, you can easily flash magisk to get root with this recovery. Because before this recovery it was little bit confusing and hard for some people to root.
Hi, bootloader unlocked recovery installed, please which steps I'll have to do for installing Magisk? Please 1) 2) etc. I received error signature from update from sd where was Magisk 20.4, so please help me i'm in trouble with this Los recovery, i usually use twrp or orange Fox thx
Italiandoitbetter said:
Hi, bootloader unlocked recovery installed, please which steps I'll have to do for installing Magisk? Please 1) 2) etc. I received error signature from update from sd where was Magisk 20.4, so please help me i'm in trouble with this Los recovery, i usually use twrp or orange Fox thx
Click to expand...
Click to collapse
I just got the s10 and I rooted a little different. I first unlocked bootloader. Than I flashed the G770FXXS3CTI1 BTU. Loaded it up developer options I load it all up and reformat about 3 times through this. Turn off check apps usb adb option.
Than I flashed the dbmeta dummy file with odin and than I flash TWRP recovery and format wipe yes, flash samsung disabler and than just flash magisk v21.1 you dont have to patch boot img magisk will patch your bootimg when you flash it. Now magisk will be loaded on your home screen when you reboot and than you finish installing. Gotta have 21.1 canary version. Thats a lot eaiser than all the other steps. Good luck.
Newer recovery version for Lineage 18.1 are up https://github.com/mainey/release-r5q/releases/tag/recovery-20210117
Hi all
We Have built Lineage OS 17.1 for Ulefone Power 6 (we have kernel and device tree sources and for vendor we use from stock rom) and flashed it on the device and now works perfectly fine and has not any problem.
Then we built Lineage OS 18.1 for this device successfully with the device tree and the kernel of the before (kernel without any change and device tree with a little change to resolve the build errors compared with lineage OS 17.1 one) and vendor from the stock rom (for either of them i.e. Lineage OS 17.1 and 18.1), but when we flashed it on the device, it could not boot and stuck in boot loop!
it seems that the only tool available for debugging is last kernel message logs in recovery mode.
from the "/proc/last_kmsg" it seems that the problem is originated from init process in mounting partitions (specially system partition) unsuccessfully (or from not finding the mount entries for some partitions from fstab file) and without considering the log, we should maybe apply some changes to vendor for the Lineage 18.1 to be able to boot up.
can anyone help me to find the origin of the problem or help me to know the general way for successful transition from Lineage OS 17.1 to Lineage OS 18.1 for a device
thanks in advance
i have a spare Ulefone power 6 on hand, appreciate if you can share the rom of lineage OS for me to flash and take a look