Database Users

[Q] Hardware Key mapping

Hi
How can I get the key in this format
| Play | Back | Start |Power | Serach
and I do not want to Use End Key in My Hd2
tnx

[ROM][5.1.x][Unfficial][Pisces] MI3 TD CM-12.1/13.0/14.0 [2016-10-03]

Status in latest release:
Available
Dialing
Incoming Call
Hand free conversation
Phone conversation
Call recording
Single/Dual mic noise reduction
Vibration
NFC
Sensors
Auto brightness
Compass (seems buggy in some apps)
Charge only mode (Power down charging)
Power off alarm
Broken/Unavailable
App - FM
VPN/Shadowsocks? - need apps update for Android 5
Broken/Missing/WIP
Vibrate along with Music
Setting - Single/Dual mic mode
Since there'e isn't many ppl want this rom and updating this thread is hard, infomation in this thread is no longer being actively maintained, but rom files will keep being published in download links
XDA:DevDB Information
MI3TD, ROM for the Xiaomi Mi 3
Contributors
xuefer, xuefer
Source Code: https://github.com/MI3TD
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Current Beta Version: 2016-10-03
Beta Release Date: 2016-10-03
Created 2015-03-06
Last Updated 2016-10-05

Download links
Tools:
(Required) Recovery
English TWRP2 for MI3 TD: TWRP2.8-12.1-20150523-UNOFFICIAL-pisces.zip, flashable zip with img inside
Dual System fully supported, can flash/boot system-2
Dual Data co-existing (when enabled), allow system-1 / system-2 use different data, recovery must be used to switch system along with data
Flash using "fastboot flash recovery recovery.img"
Data Media supported, auto patch system (mount_ext4.sh) to support /data/media, which can be standalone or merged into data partition
Re-partition Internal Storage (use Advanced -> Partition SD Card), merge or split data/media
Download: @baidu, @androidfilehost (MD5: 5bd1176ccf0d2f2eb777a3df50612ab3)
new updates:
MI 3 TD CM 12.1/13.0 ROMs
MI3TD CM12.1/13.0/14.0-2016XXXX (CM: XXXX, Device: XXXX), latest random updates
Download: @baidu | @360 9f89 | @androidfilehost
MI3TD CM12.1-20150528 (CM: 0528, Device: 0528)
Download: @baidu | @androidfilehost | MD5: 136d1cada4b30223de2298d5d82ecd8b
MI3TD CM12.1-20150526 (CM: 0526, Device: 0526)
Download: @baidu | @androidfilehost | MD5: 3ebaefcf6975529033f097ae03d05b62
MI3TD CM12.1-20150519 (CM: 0519, Device: 0426)
Download: @baidu | @androidfilehost | MD5: 1ca1f2792a8960bb102c5fce4c56c131
MI3TD CM12.1-20150507 (CM: 0507, Device: 0426)
Download: @baidu | @androidfilehost | MD5: a370104c8d2e2b3f6b24f625baa669c1
MI3TD CM12.1-20150426 (CM: 0426, Device: 0426)
Download: @baidu | @androidfilehost | MD5: c65dabbdc0b0482860948bad533b92c9
MI3TD CM12.1-20150424 (CM: 0424, Device: 0424)
Download: @baidu | @androidfilehost | MD5: 89dca605e0922f4ae920123175d1de29
MI 3 TD CM 12.0 ROMs
MI3TD CM12.0-20150420 (CM: 0420, Device: 0420)
Download: @baidu| @androidfilehost | MD5: 64ccae192a8616307d7723e92b3bc5cf
MI3TD CM12.0-20150412 (CM: 0412, Device: 0412)
Download: @baidu | @androidfilehost | MD5: 64ccae192a8616307d7723e92b3bc5cf
MI3TD CM12.0-20150316 (CM: 0316, Device: 0316)
Download: @baidu | @androidfilehost | MD5: 155268021356ba018a63ff0cc67421bd
MI3TD CM12.0-20150304 (CM: 0304, Device: 0304)
Download: @baidu | @androidfilehost | MD5: 68a7618a4706887fb948933ba46364c8
Optional downloads:
(Optional) Minimal Gapps for 5.0.x: pa_gapps-modular-pico-5.0.1-2015xxxx-signed.zip
or Minimal Gapps for 5.1.x: pa_gapps-modular-pico-5.1-20150418-signed.zip
Downloads: @xda
(Optional) Xposed 3.0 module: xposed-sdk22-arm-*.zip
Downloads: @xda
or Xposed 3.0, Android 5.1: xposed-sdk21-arm-*.zip
Downloads: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
ChangeLog
[color=#ff0ff]2015-05-28[/color]
Fixed connectivity check by using g.cn as default check server
Updated CM to 05-28
[color=#ff0ff]2015-05-26[/color]
Optimized boot time (maybe hard to be noticed)
Updated kernel to 0522
Updated CM to 05-26 date
[color=#ff0ff]2015-04-26 ~ 2015-05-19[/color]
Updated CM to corresponding date
[color=#ff0ff]2015-04-24[/color]
Switch to CM-12.1
Updated CM to 20150424
Kernel updated to MI3TD_5.4.22 (3.4.35-g5971b39, Sat Apr 18 20:20:31 CST 2015)
[color=#ff0ff]2015-04-20[/color]
Added: Power off alarm (Both "Power Off" and "Power Off Charging" is supported)
Updated CM to 20150420
[color=#ff0ff]2015-04-12[/color]
Added: Support for System-2. Allow being installed to System-2 and boot from it.
Fixed: rework fix for recording issue
Added: U un-mount
Updated: libnfc*.so libtbb.so file to MIUI 5.3.20
Added: Power off alarm (Both "Power Off" and "Power Off Charging" is supported)
Fixed: Allow adb access to power off charging (only if authorized already)
Improved: Bigger charging icon
Added: Allow disabling APN
Added: Bluetooth A2DP sink (as client/speaker) (setprop persist.service.bt.a2dp.sink 1, restart bluetooth)
Fixed: Can't change USB Computer mode after selecting USB Charge Only
Changed: disabled Sms to Mms convertion
Added: Show 2G/3G after carrier name
Added: Vibration intensity setting
Improved: may reduce radio not initialized after boot
Updated CM to 20150412
2015-03-16
Warning: Only boot from 1st system as of now
Fixed: audio recording (which cashed video recording), this is a temp fix. may cause battery drain
Fixed: Bluetooth sharing
Fixed: volume key wake up
Fixed: variable button key light
Fixed: color settings battery/notification led
Added: hardware testing app
Fixed: charge only mode (power "off" charging), fix graph, fix led, fix percentage
Fixed: AudioFX FC
Improved: glove mode (in Settings -> Language & Input)
Improved: AMAPNetworkLocation (provided in MIUI rom), remove it if you wan't Gapps Network Location
Improved: charge only mode when connecting with computer (implemented by CM, MTP=off, adb=off, seems buggy, gray when clicked)
Improved: add dirac effect (not tested) from MIUI
Improved: compatible with datamedia mode (yet re-partition recovery script is not provided)
Improved: compatible with FAT32, NTFS, exFAT, ext4 USB disk
Improved: improved MIUI audio blob support for stability
Improved: disable wlbwservice which restart loop (may reduce battery drain)
Improved: vibrator was too weak, update to same as MIUI
2015-03-04
Warning: Only boot from 1st system as of now
Re-enable support non-PIC/non-PIE executable (Roll back some changes of AOSP/CM-12)
Fixes: Vibrator (was unsupported by CM-12)
Added: App to SD
Fixes: Phone (fixed fild)
Fixes: Audio (Updated MIUI API patch for CM-12)
Simplified steps to flash
fastboot flash recovery recovery.img (TWRP2 English)
fastboot reboot (while holding volume UP, to boot into TWRP2 recovery)
Switch system to "Current System: 1"
Select MI3 TD CM12 zip file from sdcard, flash
(Optionall) Flash Gapps
Simplified steps to return to stock rom
fastboot flash recovery images\recovery.img (the one from MIUI MI3TD flastboot package http://www.miui.com/shuaji-393.html)
fastboot flash boot+boot1 images\boot.img
fastboot flash system+system1 images\system.img
or follow the guide in http://www.miui.com/shuaji-393.html

The ROM is uploaded to baidu cloud storage @ china, if you have mirror the it to other country which is faster out of China, please send me the link for the thread
True Dual boot should be disabled because since MIUIv6 adds encryption to data is is not supported by this recovery hack
Please install to system 1, only
The recovery provided by my link is in Chinese menu, you may want to use English one. I don't have time to find English one for you

:good:
I have flashed it,the lollipop is sweet!

@xuefer Here is the link:
File is online: https://www.androidfilehost.com/?w=files&flid=27244

Bitti09 said:
@xuefer Here is the link:
File is online: https://www.androidfilehost.com/?w=files&flid=27244
Click to expand...
Click to collapse
Can you built some of these WIP feature into your CM 12.These are some great feature that makes a phone stand out.Also can you do anything about camera quality.Sony Z or z1 uses same sensor,they have great image quality.
Please include feature which will make our phone stand out.Thanks

can we use this rom for MI 3W...?

I'm working on some feature/bug fixes
No it won't work on anything else other than MI3 TD. Check MI3 W roms for MI3 W

ok thanks...

hi dear
i flashed on Mi 3 TD 64 GB
but its not working not coming up what can i do?
thanks

you need to disable the dual boot and install it on system 1

The bugs i found till now
maps google search not working fc
, camera video force close on saving
, sometimes in calls just turning call on background on call reply
, graphics glitch on performance when trying antutu i have some screen glitches
storage not shown as normal don't see sd internal storage in settings only system storage
- antutu score 37055 performance 26540 on balanced
root works perfectly

some screenshots with bugs and antutu
I've atached the antutu score and camera and google maps problem

ROM updated. some bug fixed

please update links
on baidu fails to download pleas put androidhost links or other sources that work well outside of china failed download every time
---------- Post added at 09:05 AM ---------- Previous post was at 08:52 AM ----------
when i reach the half of the download crashes for the first 5 min works great then jumps on low transfer then chrashes , that's strange on a gigabit connection use anything else for this but can't dowload it

Finaly managed to install it
every bugs that i reported are fixed i'll try to see if i'll find any more bugs , sorry for tte delay but i had to write the kk recovery again via adb because it was overwriten by the cyanogen one , for now everything works only one request do you know someone to translate the kk recovery it took a week for me to find the options i don't know chinese and the tdb was not a option in the clasic one so arangement differs a litle from the english version .
i'll test it for any more bugs i will atatch screenshots

draven32 said:
every bugs that i reported are fixed i'll try to see if i'll find any more bugs , sorry for tte delay but i had to write the kk recovery again via adb because it was overwriten by the cyanogen one , for now everything works only one request do you know someone to translate the kk recovery it took a week for me to find the options i don't know chinese and the tdb was not a option in the clasic one so arangement differs a litle from the english version .
i'll test it for any more bugs i will atatch screenshots
Click to expand...
Click to collapse
sorry, i don't have access to the source of this version of kk recovery

good job
after all the fixes and an antutu test i found a 400 points boost , maps and voice work now still i will have to test on a long term bases to see the battery stats, no bugs except you reported i mean fm radio ,
there is a bit of lag in call animations but is easaly fix with reducing animation to 0.5
by the way can you put the internal sd in storage i only see system memory and i need to go to file explorer to see how much storage i have

an ironical opinion about cm12 vs miui
for me at list it's more stable then miui v6 rom on miui v6 had some sim problems and found myself with no sim error mobile networks grayed out on cm12 never had that problem some small glitches but there were fixed ,
i mean this is ironical that a custom firmware works better then the original rom , if xuefer works the fm radio we will have a better rom than miui v6( i don't use that but i mean that is the only thing that is missing for me )
P.S : thanks xuefer for the fast support ,

FM app is not working for the lack of MIUI framework
SIM card may not work after a hot reboot, so make sure you can dial after boot (it's easier by checking carrier name, it seems different between working or now)
good to know most bug is fixed correctly. the animation is by CM or AOSP which i don't know, they should have tweaked it better i guess
the way MI3 TD partition the disk, emulating SD-card using a separated partition, is in-formal way and isn't supported by AOSP/CM
MIUI show it by hacking the framework code.
I could try to build a recovery with support for
true dual boot
English
datamedia (merged emulated-SD-card to data)
But It take some, and maybe donation. It seems not much non-China user is using MI3 TD. And a little (if not zero) of the China user like to donate

[IIIII] CROSS - Custom ROM Scripted Setup

Nexus 7'13 CROSS - Custom ROM Scripted Setup (c)2020-2021 k23m
CROSS works on PC with Windows, or WinPE if you do not have Windows installed, or VirtualBox with a Windows guest.
Currently supported ROMs:
- Android 10 LineageOS 17.1
- Android 11 LineageOS 18.1
- Android 11 LineageOS 18.1-flox
Previously supported ROMs:
- Android 7 LineageOS 14.1
- Android 7 LineageOS 14.1-microG
- Android 10 LineageOS 17.1-flox
FEATURES
- automatic scan of developer's website for the latest ROM version
- automatic download of all required components
- automatic single-click installation
- optional components like root or special kernel
- all you have to do is select yes/no during the installation
- both flo and deb are supported
PREREQUISITES
- unlocked device
- installed N7 USB drivers
- original eMMC partition layout may be required
All of the above are ensured with RESTOCK - also a scripted tool, available here:
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
---------------------
lineage-install-2.bat
---------------------
This script installs and/or offers the following optional components:
- Android 10 LineageOS 17.1 UNOFFICIAL maintained by ripee https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-17-1-t4038425
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-max.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
---------------------
lineage-install-3.bat
---------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1 UNOFFICIAL maintained by followmsi https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-04-07.3569067/
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
NOTE: automatic scan of the developer's website is not possible.
Please download the ROM from: https://drive.google.com/drive/fold...HZThGTnM?resourcekey=0-0BunAmDBWluYPghT0Fs6CA
Save it in CROSS' folder and drag-and-drop it on lineage-install-3.bat to start the installation.
--------------------------
lineage-install-3-flox.bat
--------------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1-flox OFFICIAL maintained by npjohnson https://forum.xda-developers.com/t/...s-7-2013-wi-fi-repartition-only-flox.4255325/
- TWRP-flox (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip (flox compatible) by k23m (optional, no need if already flox-repartitioned)
- root: Magisk (optional)
- GApps: pico unofficial by ipdev (optional)
------------------------
getlog.bat and relog.bat
------------------------
If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.
----------
fstrim.bat
----------
Improve performance of your eMMC.
---------------
repartition.bat
---------------
If sysrepart repartition is impossible due to TWRP or GPT issues, run the repartition.bat script.
SUPPORT
[FIX][EMMC] Nexus 7 2013 ⊕ bricked, dead, frozen or stuck ⊕
Quick Links if fastboot mode is not available, try Unbricking Guide if fastboot mode is available, do RESTOCK In this thread I would like to consolidate information about eMMC flash memory failures and remedies. When flash memory fails it...
forum.xda-developers.com
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
If you select the local file option, CROSS will scan the data folder and offer the newest found file for installation. If nothing is found, you can type/paste a specific file name to install. You can drop anything you like to the data folder - CROSS is now a basic universal ROM installer.
SAMPLE OUTPUT
Code:
Nexus 7'13 LineageOS 17.1 Install v1.3 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]:
--2020-05-15 06:17:53-- https://lineageos.wickenberg.nu/flo/
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'tmp1'
tmp1 [ <=> ] 6.32K --.-KB/s in 0.001s
2020-05-15 06:17:57 (5.33 MB/s) - 'tmp1' saved [6473]
Found for download: lineage-17.1-20200515-UNOFFICIAL-flo.zip
Use local TWRP file? (no if unsure) [y/n]:
Press any key to continue . . .
Downloading installation files.
--2020-05-15 06:19:02-- https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img
Resolving dl.twrp.me... 45.249.91.154
Connecting to dl.twrp.me|45.249.91.154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9271296 (8.8M) [application/octet-stream]
Saving to: 'twrp-3.3.1-0-flo.img'
twrp-3.3.1-0-flo.img 100%[=================================================>] 8.84M 945KB/s in 11s
2020-05-15 06:19:15 (788 KB/s) - 'twrp-3.3.1-0-flo.img' saved [9271296/9271296]
--2020-05-15 06:19:15-- https://lineageos.wickenberg.nu/flo/lineage-17.1-20200515-UNOFFICIAL-flo.zip
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 413523888 (394M) [application/zip]
Saving to: 'lineage-17.1-20200515-UNOFFICIAL-flo.zip'
lineage-17.1-20200515-UNOFFIC 100%[=================================================>] 394.37M 2.71MB/s in 3m 17s
2020-05-15 06:22:34 (2.01 MB/s) - 'lineage-17.1-20200515-UNOFFICIAL-flo.zip' saved [413523888/413523888]
--2020-05-15 06:22:34-- https://jaist.dl.sourceforge.net/project/opengapps/arm/20200515/open_gapps-arm-10.0-pico-202005
15.zip
Resolving jaist.dl.sourceforge.net... 150.65.7.130
Connecting to jaist.dl.sourceforge.net|150.65.7.130|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 101519489 (97M) [application/octet-stream]
Saving to: 'open_gapps-arm-10.0-pico-20200515.zip'
open_gapps-arm-10.0-pico-2020 100%[=================================================>] 96.82M 3.25MB/s in 36s
2020-05-15 06:23:11 (2.73 MB/s) - 'open_gapps-arm-10.0-pico-20200515.zip' saved [101519489/101519489]
--2020-05-15 06:23:11-- https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Resolving github.com... 52.64.108.95
Connecting to github.com|52.64.108.95|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f19-3a5b8341b6e2?
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-
Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a13162209f0fff91
&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filename%3DMagisk-v20
.4.zip&response-content-type=application%2Foctet-stream [following]
--2020-05-15 06:23:11-- https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f1
9-3a5b8341b6e2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4
_request&X-Amz-Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a
13162209f0fff91&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filena
me%3DMagisk-v20.4.zip&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... 52.216.134.219
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|52.216.134.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5942417 (5.7M) [application/octet-stream]
Saving to: 'Magisk-v20.4.zip'
Magisk-v20.4.zip 100%[=================================================>] 5.67M 2.30MB/s in 2.5s
2020-05-15 06:23:15 (2.30 MB/s) - 'Magisk-v20.4.zip' saved [5942417/5942417]
--2020-05-15 06:23:15-- https://forum.xda-developers.com/attachment.php?attachmentid=4480528
Resolving forum.xda-developers.com... 104.18.19.88, 104.18.18.88
Connecting to forum.xda-developers.com|104.18.19.88|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594 [following]
--2020-05-15 06:23:16-- https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594
Resolving dl.xda-cdn.com... 104.27.191.76, 104.27.190.76
Connecting to dl.xda-cdn.com|104.27.191.76|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 782958 (765K) [application/zip]
Saving to: 'sysrepart.zip'
sysrepart.zip 100%[=================================================>] 764.61K 591KB/s in 1.3s
2020-05-15 06:23:20 (591 KB/s) - 'sysrepart.zip' saved [782958/782958]
Press any key to continue . . .
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
Verify...
Lock status...
Flash TWRP? [y/n]: y
sending 'recovery' (9054 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.516s]
finished. total time: 0.812s
1. on N7 select "Recovery mode" with volume button
2. on N7 press power button to boot Recovery
3. when you see TWRP main menu press any key to continue
Wait...
*
Installing...
*****
Repartition? (no if already repartitioned) [y/n]: y
Transferring: 782958/782958 (100%)
2575 KB/s (782958 bytes in 0.296s)
***
Wait...
Installing zip file '/sdcard/sysrepart.zip'
Checking for Digest file...
###############################
# k23m Nexus 7'13 Repartition #
###############################
Creating log and gpt backup
Removing partitions
Creating new partitions
Formatting new partitions
###############################
Operation completed. Copy backup gpt and log files from internal storage to PC before rebooting.
###############################
Done processing script file
***
...REBOOTING
When you see TWRP main menu press any key to continue...
*****
Proceed only if you really see TWRP main menu
Press any key to continue . . .
Do dirty flash? (no if unsure) [y/n]: n
Wiping data without wiping /data/media ...
Done.
Formatting Cache using make_ext4fs...
Done processing script file
Formatting System using make_ext4fs...
Done processing script file
Wiping Cache & Dalvik...
-- Dalvik Cache Directories Wipe Complete!
Done processing script file
Formatting cache using make_ext4fs...
Done processing script file
***
Transferring: 413523888/413523888 (100%)
3649 KB/s (413523888 bytes in 110.640s)
***
Wait...
Installing zip file '/sdcard/lineage-17.1-20200515-UNOFFICIAL-flo.zip'
Checking for Digest file...
Warning: No file_contextsTarget: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keysPatching system image unconditio
nally...script succeeded: result was [1.000000]Done processing script file
Install root? [y/n]: y
Transferring: 5942417/5942417 (100%)
3868 KB/s (5942417 bytes in 1.500s)
***
Wait...
Installing zip file '/sdcard/Magisk-v20.4.zip'
Checking for Digest file...
***********************
Magisk 20.4 Installer
***********************
- Mounting /system
- Device is system-as-root
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.tzdata
- System-as-root, keep dm/avb-verity
- Target image: /dev/block/mmcblk0p14
- Device platform: arm
- Constructing environment
- Adding addon.d survival script
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Done processing script file
Install GApps? [y/n]: y
Transferring: 101519489/101519489 (100%)
3623 KB/s (101519489 bytes in 27.359s)
***
Wait...
Installing zip file '/sdcard/open_gapps-arm-10.0-pico-20200515.zip'
Checking for Digest file...
##############################
_____ _____ ___ ____
/ _ \ | __ \ / _ \ | _ \
| / \ || |__) | |_| || | \ \
| | | || ___/| __/ | | | |
| \ / || | \ |__ | | | |
\_/ \_/ |_| \___| |_| |_|
___ _ ___ ___ ___
/ __| /_\ | _ \ _ \/ __|
| (_ |/ _ \| _/ _/\__ \
\___/_/ \_\_| |_| |___/
##############################
Open GApps pico 10.0 - 20200515
- Mounting partitions
- Gathering device & ROM information
- Performing system space calculations
- Removing existing/obsolete Apps
- Installing core GApps
- Installing swypelibs
- Installing calsync
- Installing googletts
- Installing packageinstallergoogle
- Miscellaneous tasks
- Copying Log to /sdcard
- Installation complete!
- Unmounting partitions
Done processing script file
***
Done.
Press any key to continue . . .
SUPPORT - http://bit.ly/2C35sLZ
Press any key to exit...
_____________________________________________________
REPARTITION
sysrepart.zip - 1.1GB system, data is not wiped
sysrepart-max.zip - 1.3GB system, data is not wiped, automatically downloaded by LOS 17.1 script
sysrepart-flox.zip - 1.5GB system, data is wiped, 'vendor' partition is added, automatically downloaded by LOS 17.1-flox script
sysrepart-ultimate.zip - 4GB system, data is wiped, 'vendor' partition is added, 'recovery' is enlarged to 64MB in-place and your current TWRP continues to function, flox compatible, automatically downloaded by LOS 18.1-flox script. For N7-16GB try sysrepart-ultimate-2.zip
sysrepart-stock.zip - data is wiped, original partitions are restored
reboot immediately after repartition!
sysrepart-ultimate/stock work on any previous repartitions
sysrepart/max/flox work reliably only on original partitions
to install GApps larger than pico/nano you need sysrepart-ultimate
sysrepart-ultimate supports custom, oversized TWRP builds
To recover from other repartition attempts, simply install sysrepart-ultimate if you intend to use LOS17+ or sysrepart-stock if you have other plans. If direct sysrepart installation is impossible due to TWRP or GPT issues, run the repartition.bat script. On rare occasions you may have to run RESTOCK and "Restore original partitions" with it.
_____________________________________________________
UPDATE version 2.5 changes:
- update components' URLs
- update relog.bat
- remove installation scripts of no longer available ROMs
- add update.bat cleanup script (run it once)
- add repartition.bat script for repartition-only
- add lineage-install-3.bat script
Download CROSS2.zip and unzip it then download cross-update-XXX.zip and unzip it to the CROSS folder, overwrite existing files.
Also check the very latest interim updates in this post https://forum.xda-developers.com/t/iiiii-cross-custom-rom-scripted-setup.4092215/post-87622749
____________________________________________________
NOTE - most of the attached files are meant for direct script download. Except for CROSS and its updates do not download them manually unless you know what you are doing.

Hi, thank you very much for this useful tool.
I wonder whether your script could be updated to support dirty flash also. Now it seems to always make a clean flash. But it is not very convenient to set up the device after each security update.
I am not very experienced in making batch files but I was thinking about adjusting your script like follows. From:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="Red"]echo.
echo Installing...
call:wait 5
adb shell twrp wipe /data[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
To:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="red"]echo.
set /p FLASHTYPE=Do you want to make clean flash or dirty flash? Clean flash will erase all data (except the files in the internal storage) [clean/dirty]: || set FLASHTYPE=null
echo Installing...
call:wait 5
if /i %FLASHTYPE%==dirty (
echo Skipping wiping data...
echo Performing dirty flash...
goto dirty)
if /i %FLASHTYPE%==clean (
adb shell twrp wipe /data
)
:dirty[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
Any comment on this? Would this worked correctly?

prorokrak said:
....Any comment on this? Would this worked correctly?
Click to expand...
Click to collapse
Thanks for the suggestion. This code can be abbreviated, same as the other optional items:
Code:
set /p ANS=Do dirty flash? (no if unsure) [y/n]: || set ANS=n
if /i !ANS!==n (
adb shell twrp wipe /data
)
I added it to the v1.2 update.

I just gave this script a try. This is quite slick and saves a bunch of time! Thanks for this. :good:

CROSS 2 release
CROSS version 2.0
- new log script
- new fstrim script
- updated components' URLs
- removed LOS microG as it is no longer available
Both LineageOS 14.1 and LineageOS 17.1 install flawlessly. There may be temporary download issues. If so, retry later. LOS17 server errors...
Code:
Resolving lineageos.wickenberg.nu... 83.209.185.118
Connecting to lineageos.wickenberg.nu|83.209.185.118|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-10-11 10:13:40 ERROR 500: Internal Server Error.
:highfive:

Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?

jelles01 said:
Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?
Click to expand...
Click to collapse
Hi again, first copy eg "lineage-17.1-20201009-UNOFFICIAL-flo.zip" to "CROSS\data" folder, then answer [y] to the question...
Code:
Nexus 7'13 LineageOS 17.1 Install v2.0 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]: y
Found local file: lineage-17.1-20201009-UNOFFICIAL-flo.zip
As you can see it is found automatically without entering a file name. If nothing is found, you could type any file name but the file must be located in the data folder.

It has worked! The install and setup was buttery smooth, thank you so much for this tool. Amazing!

A little help.
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1?
Thanks in advance!:highfive:

GeekyTanuj said:
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1? Thanks in advance!:highfive:
Click to expand...
Click to collapse
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:

You are a lifesaver!
k23m said:
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:
Click to expand...
Click to collapse
Thank you so much for developing this, RESTOCK as well as stock MM debloat script. it literally saved hours and hours of hassle that one has to face while getting to different versions of android! Running 10 with latest updates. feels so good!

kernel Configuration.
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:

GeekyTanuj said:
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:
Click to expand...
Click to collapse
For video and games LOS17 seems optimal, check these benchmarks.
Personally I use LOS14 without Gapps and with EX kernel including a modification to the battery life extender. I lowered max battery charge to 4.00V which is equivalent to 75% (under)charge resulting in 8x increase of battery life. Furthermore, the mod allows for constant external power connection and no battery overcharging nor overheating/swelling. I edited "buildconfig.sh" in EX zip:
Code:
replace
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4200" >> $CONFIGFILE
with
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4000" >> $CONFIGFILE
:good:

You gave my Nexus 7 (2013) a new lease on life! Woo-hoo!
I was running a years-old version of the vanilla stock FW and it was soooo slow. Somebody in some comment section somewhere mentioned RESTOCK & CROSS, so I tried out RESTOCK2 and it worked flawlessly.
Then I tried installing 17.1 via CROSS2 without repartitioning (as I believed RESTOCK did that). I got an error that I did not save, hoping it wasn't a big deal. I got stuck on the Google loading screen, so I ran CROSS again. I was going to try 14.1, but wasn't given the option again (bonus? 17.1 looks beautiful and it didn't make me redownload anything, which was smart coding on your part).
I think I should have run the logging programs when I first saw errors, because I'm afraid they were cleared by the reinstallation. I did send what I could after running the loggers post-successful installation, just in case.
Now, 17.1 is working so smoothly with a quick Netflix sideload (no GApps here, used APKMirror + the APKMirror Installer) - which certainly is only working thanks to Magisk. How long did it take me to figure out how to put app icons on the homescreen (swipe up, of course!) I don't think I want to reveal
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!

iforget said:
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!
Click to expand...
Click to collapse
If the Lineage build is using followmsi's sources, then you do not need to change kernels.
You just need to activate DT2W.
See this post on how to activate using a kernel manager.
The thread with the ever changing name. xda thread - Link
If you want something simple, I use a magisk module that enables it on boot.
DT2W GitHub - Link
Cheers.
PS.
Sorry for a bit of OT.
PPS.
The Lineage 17.1 build is using followmsi's sources.

hi
I have issue with otg on my N7, i used cross2 without problems : i installed twrp, lineageos 14, root the nexus and installed elementalx and googleapp
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ?
it's a kernel issue?
any app works
thx

gibnexus said:
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ? it's a kernel issue?
Click to expand...
Click to collapse
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.

k23m said:
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.
Click to expand...
Click to collapse
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx

gibnexus said:
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx
Click to expand...
Click to collapse
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all

gibnexus said:
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all
Click to expand...
Click to collapse
I can assure you that straight LOS14+EX OTG works fine.
You must have enabled the "USB OTG + charge mode" option which is meant for car use or externally powered OTG devices. It is NOT NEEDED for normal, N7-powered OTG storage.

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S6 SM-G920F stock to Android 11

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S6 SM-G920F Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S6 SM-G920F/zerofltexx Any version to Android 11 R / LineageOS 18.1
This detailed step-by-step guide helps you transform your Samsung Galaxy S6 SM-G920F/zerofltexx to a powerful one with Android 11.
Make sure your phone is SM-G920F before going further: in Android, go to Settings > About > Check model is SM-G920F.
If not, quit this tutorial.
### You won't be able to use Banking apps with a custom ROM
CHANGELOG
v7. Upgrade to Android 11
v6. Move to MindTheGapps
v5. Improved tutorial thanks to @g3rrydanc3
v4. Alternative ROM LineageOS 17.1, updated Magisk, reworked tutorial
v3. Change ROM for PixelExperience, latest Magisk zip, added GPU optimizations.
v2. Link to latest build
v1. Initial release for Android 10
1) DOWNLOAD
- djibe Galaxy S6 zerofltexx pack (57 Mo): https://bit.ly/djibe-galaxys6-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.3.1-0 official recovery + Magisk Root). Unzip files.
+ ROM LineageOS 18.1 Unofficial: https://forum.xda-developers.com/t/rom-g920-5-f-i-s-k-l-11-0-unofficial-lineageos-18-1.4266447/
Download latest @enesuzun2002 build: https://github.com/enesuzun2002/lineageos-ota/releases
+ MindTheGapps 11 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud backup and apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators,
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
3) FLASH TWRP 3.3 RECOVERY
Shut down phone.
Boot in Download Mode : hold Home + Power + Volume- until you see Samsung's logo and release all buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays: Download mode, do not turn off target.
Connect phone in USB, wait for bootloader drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select twrp-3.3.1-0-zeroflte.img.tar
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black.
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
Boot in Recovery Mode : Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot.
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Backup > you can select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup EFS, Boot, Data and System partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe, tap on Format data.
Type yes and confirm with bottom right button (check icon)
Now go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe.
### Don't try to format to F2FS, it won't work.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, GAPPS
Back to TWRP main menu, go to Mount menu.
Check Data partition
Bottom right button shows Disable MTP. If not, tap on button.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy files of ROM + GApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
then Add more Zips > mindthegapps*.zip
then Swipe to confirm Flash.
Wait for operation to end.
### Don't flash Magisk now
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Let Android start and configure it at first launch.
Don't try to set fingerprints at first setup. It will crash.
Optional for root: Then restart to Recovery once again.
Back to TWRP, go to Install, select Magisk and swipe to flash.
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
7) ROOT ACCESS
No need for extra work to be root as Magisk launches with Android.
Superuser permissions can be managed from the Magisk Manager app.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide it.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
8) TWEAKS
- Physical buttons illuminated too often ?
Go to System > Buttons > Backlight > Illuminate only when pressed
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%: Settings > Display > Dark theme
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Advanced > Developer options.
- Change screen definition for low GPU/CPU usage.
Developer options must be activated.
In developer options: Set Windows animation scale, Transition animation scale and Animator duration scale to 0.5x.
Also switch On Terminal.
Now in apps list, open Terminal.
type
Code:
su
Grant superuser privileges.
then type
Code:
wm density 480
(original is 640),
then
Code:
wm size 1080x1920
(original is 1440x2560),
then
Code:
stop && start
.
- To tweak overclocking and more, use SmartPack-Kernel Manager
SmartPack-Kernel Manager - Apps on Google Play
The ultimate tool to manage your kernel
play.google.com
Enjoy,
djibe
Thanks : @Exhigh, Pixel Experience team, JoshuaDoes, ananjaser1211, Lunarixus, ripee, xSil3nt, @BenLue, @enesuzun2002, lukasb06, u99dev, TeamNexus, LOS Team, TWRP Team
---------------------------------------
Force Samsung Galaxy S restart
Hold Power + Volume down for 10-20 seconds

Flash twrp 3.3 recovery
thx fine

chinobi23 said:
ths fine
Click to expand...
Click to collapse
Hi, did you have a problem while flashing ?
Samsung's phones are tough thanks to Download mode.

djibe89 said:
Hi, did you have a problem while flashing ?
Samsung's phones are tough thanks to Download mode.
Click to expand...
Click to collapse
yes when i format I lost the rom, I install from my USB key ... everything works very well .. just the fast charge does not work ?? everything works fine thanks

chinobi23 said:
yes when i format I lost the rom, I install from my USB key ... everything works very well .. just the fast charge does not work ?? everything works fine thanks
Click to expand...
Click to collapse
Fast charge works for me.
Maybe try a new clean install

i try again
after reboot screen android 10 its reboot again in TWRP recovery :crying:

help !!
no body help ...!! plz
g920f
lineage-17.1-20200606-UNOFFICIAL-zerofltexx after instal end screen andiod10 reboot in twp ..!!
i don't have backup to restore ...
i try this rom : LineageOS-10-zero-multitarget-2020-04-13_2047 same probleme ...

chinobi23 said:
no body help ...!! plz
g920f
lineage-17.1-20200606-UNOFFICIAL-zerofltexx after instal end screen andiod10 reboot in twp ..!!
i don't have backup to restore ...
i try this rom : LineageOS-10-zero-multitarget-2020-04-13_2047 same probleme ...
Click to expand...
Click to collapse
Hi again,
- When you flashed TWRP recovery, you had the SUCCESS message in Odin ?
- Go back to TWRP recovery and start again from Step 5 of my tutorial ( 5) FORMAT PARTITIONS )
- All your partitions are in EXT4 ?
- Try to install only ROM zip, wipe cache and reboot system.

flashed TWRP recovery, SUCCESS
ok i will try again thx to answer me ..:fingers-crossed:
---------- Post added at 07:10 PM ---------- Previous post was at 07:06 PM ----------
now my phone is freez in samsung logo at start can't reboot or shotdown :crying:
---------- Post added at 07:26 PM ---------- Previous post was at 07:10 PM ----------
this before i try again nox im freezing in samsun log can't reboot
open_gapps_log
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 10
ROM Build ID | zerofltexx-userdebug 10 QQ3A.200605.001 238 test-keys
ROM Version increment | 238
ROM SDK version | 29
ROM/Recovery modversion | 17.1-20200606-UNOFFICIAL-zerofltexx
Device Recovery | TWRP 3.3.1-0-f5955b1c
Device Name | zeroflte
Device Model | SM-G920F
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 640
Install Type | Dirty[Data NOT Wiped]
Smart ART Pre-ODEX | false
Google Camera already installed | false
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | 20200606
Current Open GApps Package | micro
Google Camera version | Legacy
Installing GApps Zipfile | /usbstorage/open_gapps-arm64-10.0-micro-20200606.zip
Installing GApps Version | 20200606
Installing GApps Type | micro
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[default]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[default]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false[PackageInstallerGoogle]
Ignore Google NFC Tag | false
Ignore Google WebView | false
Total System Size (KB) | 3002848
Used System Space (KB) | 2077676
Current Free Space (KB) | 908788
Post Install Free Space (KB) | 889832 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 908788 | 908788
Remove | Existing GApps | + 578252 | 1487040
Remove | Obsolete Files | + 1088 | 1488128
Remove | calendarstock | + 0 | 1488128
Remove | exchangestock | + 0 | 1488128
Remove | extservicesstock | + 0 | 1488128
Remove | extsharedstock | + 0 | 1488128
Remove | packageinstallerstock | + 0 | 1488128
Remove | provision | + 0 | 1488128
Remove | wallpapersstock | + 0 | 1488128
Install | Core | - 161896 | 1326232
Install | actionsservices | - 66276 | 1259956
Install | batteryusage | - 10216 | 1249740
Install | calendargoogle | - 21652 | 1228088
Install | dialerframework | - 12 | 1228076
Install | exchangegoogle | - 480 | 1227596
Install | gmail | - 71072 | 1156524
Install | googletts | - 40180 | 1116344
Install | markup | - 14428 | 1101916
Install | packageinstallergoogle | - 1868 | 1100048
Install | pixellauncher | - 6588 | 1093460
Install | search | - 134272 | 959188
Install | soundpicker | - 4784 | 954404
Install | speech | - 39128 | 915276
Install | wallpapers | - 7944 | 907332
Install | wellbeing | - 8284 | 899048
| Buffer Space | - 9216 | 889832
------------------------------------------------------------------
Post Install Free Space | 889832
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
---------- Post added at 08:02 PM ---------- Previous post was at 07:26 PM ----------
i try again step by step all is succes put same probleme ...
this my first install roms whith fast charging problem ....LineageOS-10-zero-multitarget-2020-04-13_2047 open_gapps-arm64-10.0-micro-20200606
but now don't work same probleme with LineageOS-10-zero-multitarget-2020-04-13_2047 end lineage-17.1-20200606-UNOFFICIAL-zerofltexx
i try to downlaod anther one lineage-17.1-20200606-UNOFFICIAL-zerofltexx.zip

I used lineage-17.1-20200504-UNOFFICIAL-zerofltexx.zip
I investigated Fast charging : with Samsung's charger : i get 1200 mA
With Aukey Quick Charge 3.0 compatible : 1700 mA, so nearly full charge in 1h.
It relies mainly on charger (and USB cable)

@chinobi23 Your phone is SM-G920f ?

djibe89 said:
@chinobi23 Your phone is SM-G920f ?
Click to expand...
Click to collapse
yes
i try to install SFR-G920FXXU5EQL4-20180202154213 with odin succes but after reboot it steel in samsung logo :crying:

@chinobi23
Do you reboot immediatly ?
Let phone shut for 1 minute after flashing ROM.

djibe89 said:
@chinobi23
Do you reboot immediatly ?
Let phone shut for 1 minute after flashing ROM.
Click to expand...
Click to collapse
ok
no , nothing

nos i have
failed to mount '/data' (invalid argument)
!!!!!!!
o its ok now ...
advenced-ADB Sideload .... fix my probleme data

i found more detail for my phone if it can help...
PDA/AP Version
G920FXXU5EQL4
CSC Version
G920FSFR5EQI1
MODEM/CP Version
G920FXXU5EQEL
Region
SFR
— France

chinobi23 said:
i found more detail for my phone if it can help...
PDA/AP Version
G920FXXU5EQL4
CSC Version
G920FSFR5EQI1
MODEM/CP Version
G920FXXU5EQEL
Region
SFR
— France
Click to expand...
Click to collapse
Tried same build as me ?

If my version of SM-G920f does not have a microSD slot, does this become impossible?

mirrorsshutter said:
If my version of SM-G920f does not have a microSD slot, does this become impossible?
Click to expand...
Click to collapse
Hi, thx for reporting glitches in my tutorial.
There is no microSD slot in Galaxy S6

@mirrorsshutter . I updated tutorial to answer your question.

LineageOS 19.1 (A12L) [microG][OTA] for Moto Z (griffin)

{
"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"
}
LineageOS-19.1 microG For Moto Z (griffin)​
With the rise of Big Tech and the encroachment of government into our lives , I felt more of a desire to move away from Google and the like.
Moto Z (griffin) was built with microG and LineageOS source and is fully functional.
What it is. It's LineageOS with all of Google's closed-source binaries removed and replaced with microG. I.e. no Play services or GAPPS. UnifiedNLP is used as the networking location provider instead of Google's NLP. Aurora Store and F-Droid is installed by default and provides an alternative app store. However, with the Aurora Store, you cannot install all Google Play Store apps such as buy apps.
Other information
Google Play Store Alternative If you want to have full access to normal Android Play Store apps, After opening Aurora Store, select the appropriate option. usually option number 1 is the most commonly used with this ROM, unless changed by the user. After setup, you will have access to all apps as usual. Some apps require Play Services and cannot be used.
After installation - Open the microG app --> self-check sections should be successful. Location Services - By default, LocalGsmNlpBackend, which uses the NominatimGeocoderBackend, and NominatimNlpBackend, which uses Mapquest's Noninatim service, are disabled. Open the microG app --> location modules and enable the modules you want. Then restart the device.
It is strongly recommended not to install NikGapps as this ROM contains a replacement for NikGapps these are microG​
What's working:
Boot
RIL
Camera
Fingerprint Sensor
WiFi
Bluetooth
Audio
Video Playback
NFC
Sensors
Touch
Flash
Moto gestures
Network monitor
Secure boot
What's not working:
Encryption
SELinux
You tell me.
Installation instructions
Upgrade to Stock Oreo Firmware if not done already!
- Download the ROM from the website. (see download link below)
- Install a compatible Recovery
- Perform a backup of your current ROM (Optional)
- Wipe data & cache partitions and FORMAT DATA from TWRP of your device (required when coming from stock!).
- Flash ROM.
- Flash magisk (if needed)
- Reboot
instructions (if coming from another ROM or Android version )
Secure your data (recommended)
Removes custom encryption pins/passwords (recommended)
CLEAN FLASH
- Download the ROM from the website. (see download link below)
- Reboot to TWRP
- Create backup (optional)
- Wipe system, data, cache
- Flash the ROM
- Flash magisk (if needed)
- Reboot
DIRTYFLASH
1) via OTA
2) Manual method
- Download the ROM from the website.
- Reboot to TWRP
- Flash the ROM
- Flash magisk (if needed)
- Reboot
Official update
monthly
except for important bug fixes from Device maintainer .
Changelog
Spoiler: Klick
Date -25/06/2023
=================
Changelog 25.06.2023
- Synced with LineageOS sources
- June 2023 Merged Security Update
Changelog microG
- Update FakeStore 0.2.0
Date -15/05/2023
=================
Changelog 15.05.2023
- Synced with LineageOS sources
- Merged May 2023 Security update
Changelog microG
-----
Date -26/04/2023
=================
Changelog 26.04.2023
- Synced with LineageOS sources
- Merged April 2023 Security update
Changelog microG
- Update AuroraStore 4.2.1
- Update FDroid to 1.16.3
Date -24/03/2023
=================
- Synced with LineageOS sources
- Merged March 2023 Security update
Date -09/03/2023
=================
- Initial release
- with February 2023 Security update
Download Rom
Moto Z (griffin)
https://los-legacy.de/19.1/griffin
Source code Kernel
android_kernel_motorola_msm8996
Source code partner_gms / microG
android_vendor_partner_gms
Source code Rom construction :
docker-lineage-cicd
Source code system
https://github.com/LineageOS
for german support
LineageOS 19.1 (A12) [microG][OTA] für Moto Z (griffin) - Los-Legacy
LineageOS 19.1 (A12) microG für Moto Z (griffin) Mit dem Aufstieg von Big Tech und das Eindringen der Regierung in unser Leben, fühlte ich mehr von einem Wunsch, weg von Google und dergleichen zu bewegen. Motorola Z (griffin) wurde mit microG und…
forum.los-legacy.de
ROM Manufacturer:
Exodusnick
Device Maintainer:
SirRGB
thank you for testing the rom
SirRGB
Other information
All my roms are created with a signed private key.
If you want to use the Lineageos recovery,
However, I don't know how the Lineageos recovery works as I have never used it on my other devices as I only use twrp.
Everyone is responsible for their own actions. Neither Team Xda, nor I, the creator of the theme, will take responsibility for any damage to your device caused by any Flash attempts.

This Rom consists purely of MicroG and has no Gapps or nikgapps.
I have here a few screenshots original from Moto Z (griffin).

@Exodusnick Does VOLTE work in this ROM ?
Edit: I mean I can't make calls with either of these following ROMs if I set Preferred network type = LTE
Odd Solutions Downloads
updater.oddsolutions.us
[ROM][12.1] LineageOS 19.1 for griffin [UNOFFICIAL][18 Feb]
* Your warranty is now void. * /* * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
When I set the Preferred network type = LTE/WCDMA calls start working.

You can test it to see if Volte is working
Go to dialer and enter this code
*#*#4636#*#*
Go to phone information
Default is set to
GSM/WCDMA/LTE/(PRL)
top right on ...
Ims service jams

@Exodusnick If I set the preferred network type to GSM/WCDMA/LTE (PRL), the phone call is done in WCDMA/H+ mode.
Data over LTE is working fine on the Moto Z. I found some information about enabling VoLTE on Android:
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
[Guide] Easy method to Enable Volte (with root) on Tmobile and maybe other networks on Android 11 and maybe 10
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around. Then once you do that, follow these directions, What I did was manually entered all of these setprop commands below, on the...
forum.xda-developers.com
> setprop persist.vendor.dbg.ims_volte_enable 1
> setprop persist.vendor.dbg.volte_avail_ovr 1
> setprop persist.vendor.dbg.vt_avail_ovr 1
> setprop persist.vendor.dbg.wfc_avail_ovr 1
The Moto Z has these following properties, but is missing the persist.vendor.dbg.ims_volte_enable one:
> $ getprop | grep -i -e volte -e _avail
> [persist.dbg.volte_avail_ovr]: [1]
> [persist.dbg.vt_avail_ovr]: [1]
> [persist.dbg.wfc_avail_ovr]: [1]
> [sys.user.0.ce_available]: [true]
Could that be the problem that persist.vendor.dbg.ims_volte_enable is not shown in getprop? I haven't rooted the phone.
Best regards,
Aki

ok is not shown ?!
android_device_motorola_griffin/properties.mk at lineage-19.1 · griffin-experimental/android_device_motorola_griffin
Device trees for Moto Z to build misc roms. Contribute to griffin-experimental/android_device_motorola_griffin development by creating an account on GitHub.
github.com
will be added in the next update
persist.vendor.dbg.ims_volte_enable 1

Thank you for this built Exodusnick! I haven't installed it yet as my main use for this beloved Moto Z is with the Moto Mods. Can you please confirm if it has been tested and is working with the camera mod and the beamer mod?
Thanks

Vuche said:
Can you please confirm if it has been tested and is working with the camera mod and the beamer mod?
Thanks
Click to expand...
Click to collapse
I can not confirm if moto mods work,
Test my rom and let me know if it works or not . You can also ask @SirRGB he is Device Maintainer
and he has tested the rom.

I dont have any moto mods, but I expect the battery pack and only that to work.

Ok, thank you Guys!
I'll will try later this month and will let you know.

..

@Exodusnick I just tested this ROM on my Moto Z and unfortunately it looks like VoLTE is still not working. The phone ends the call immediately when I press the green call button.

Thanks for the info
I will undo it and delete this current build.
I have no idea how to get Volte to work.

@akikoo you can go back to the first build without problems

possible that it is wrong and that it must be so
persist.dbg.ims_volte_enable=1 \
and not persist.vendor.dbg.ims_volte_enable=1 \
persist.dbg.volte_avail_ovr=1 \
persist.dbg.vt_avail_ovr=1 \
persist.dbg.wfc_avail_ovr=1 \
plus this
persist.radio.calls.on.ims=1
@akikoo I will create a test build

Exodusnick said:
possible that it is wrong and that it must be so
persist.dbg.ims_volte_enable=1 \
and not persist.vendor.dbg.ims_volte_enable=1 \
persist.dbg.volte_avail_ovr=1 \
persist.dbg.vt_avail_ovr=1 \
persist.dbg.wfc_avail_ovr=1 \
plus this
persist.radio.calls.on.ims=1
@akikoo I will create a test build
Click to expand...
Click to collapse
And under the thread concerning VoLTE for the LG Velvet (that I use as my main phone at the moment), you have to create a directory in the phone in order to have it working. And even so I discovered that it doesn't work with my "old" sim card, although it does work with another more recent sim on the same network.

I don't think it works, because under LineageOS 18.1 officially you can't find the entry
persist.vendor.dbg.ims_volte_enable=1 \ or persist.dbg.ims_volte_enable=1 \
android_device_motorola_griffin/properties.mk at lineage-18.1 · LineageOS/android_device_motorola_griffin
Contribute to LineageOS/android_device_motorola_griffin development by creating an account on GitHub.
github.com
it is simply not supported by lineageos.

@Exodusnick I was hopeful VoLTE would work with your ROM as *#*#4636#*#* / Phone information showed these settings:
voice service = in service
voice network type = LTE
volte provisioned switch was in enabled position
Best regards,
Aki

Yes, but your call would be interrupted
So something is missing maybe this
persist.radio.calls.on.ims=1

@akikoo I will create a test build
is your sim card activated for volte?