[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx | - Nokia 7 Plus ROMs, Kernels, Recoveries, & Other De

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx | - Nokia 7 Plus ROMs, Kernels, Recoveries, & Other De

XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7 Plus
Contributors
Raghu varma
Source Code:
https://github.com/TeamWin/android_device_nokia_B2N_sprout
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Beta Version: 3.4.0-0
Created 2019-06-16
Last Updated 2020-06-25

* Reserved

[DELETED]

Tenshou170 said:
Silly question, but will it work with locked bootloader?
Click to expand...
Click to collapse
No mate

Is that means my phone will be rooted and i can install another system ?

GrandLuLu said:
Is that means my phone will be rooted and i can install another system ?
Click to expand...
Click to collapse
No,without unlocked bootloader nothing.

Thank you for compiling and shearing this. I'm really excited to test it out, especially the crypto part if it works properly !
I've been looking through your repositories and I've noticed you've build B2N tree from DRG tree. How much are they alike, with emphasis on audio part, eg mixer paths ?
Also I'm the owner of an bl-unlocked B2N , if you ever need someone to beta test PM me.

>> Remove lock screen password , pin , pattern
but this remove crypt from internal_storage or not?? anyway this step is i hope need only if i want acces to internal_storage from TWRP, if i not need and use (same as with https://forum.xda-developers.com/nokia-7-plus/development/recovery-twrp-3-2-3-0-t3892644) USB-C where store Magisk.zip for install, then is this step not need?
>> this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
sure? for boot only is not need same TWRP version as installed SecurityPatch, and twrp-installer is not "only" patching/adding TWRP to actual/stock/any_sec_patch_version??

ban.codrut said:
Thank you for compiling and shearing this. I'm really excited to test it out, especially the crypto part if it works properly !
I've been looking through your repositories and I've noticed you've build B2N tree from DRG tree. How much are they alike, with emphasis on audio part, eg mixer paths ?
Also I'm the owner of an bl-unlocked B2N (by you), if you ever need someone to beta test PM me.
Click to expand...
Click to collapse
Sure thanks

Share some screenshots. Do you mean we install without even unlocking bootloader?

Stuck at Spash Screen after installing TWRP
Title says it all.
Using fastboot boot works properly and I'm presented with the decrypt page after a couple of seconds.
Using the installer.zip and trying to boot into recovery ends up being stuck at the spash screen, with no decrypt page showing up. I've uploaded recovery.log
View attachment stuckspash.log with permanent installer stops at line 81
View attachment fastbootrecovery.log with fastboot boot continues after line 82 with key management : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
on a side note: other issues / small annoyances
a) While fastboot boot into it, on the decrypt page there is some graphical glitches: flashing yellow on top bar, and other color errors. Touching the screen first time fixes it. Also (maybe a TWRP thing) the aspec ratio is 16:9 with gap on top.
b) Display locking doesn't work properly. It's unable to actually turn off the screen, instead it only dims the screen and stays on with the last frame on it (no picture update), instead of actually turning off the screen.
Both can be seen in fastbootrecovery.log:
a) line 15 - 25 :
Code:
Starting the UI...
setting DRM_FORMAT_BGRA8888 and GGL_PIXEL_FORMAT_BGRA_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
RECOVERY_BGRA
b) line 26 - 33:
Code:
framebuffer: 0 (1080 x 2160)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 1.083333x, offsets x: 0 y: 80 w: 0 h: -80

ban.codrut said:
Title says it all.
Using fastboot boot works properly and I'm presented with the decrypt page after a couple of seconds.
Using the installer.zip and trying to boot into recovery ends up being stuck at the spash screen, with no decrypt page showing up. I've uploaded recovery.log
View attachment 4780973 with permanent installer stops at line 81
View attachment 4780979 with fastboot boot continues after line 82 with key management : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
on a side note: other issues / small annoyances
a) While fastboot boot into it, on the decrypt page there is some graphical glitches: flashing yellow on top bar, and other color errors. Touching the screen first time fixes it. Also (maybe a TWRP thing) the aspec ratio is 16:9 with gap on top.
b) Display locking doesn't work properly. It's unable to actually turn off the screen, instead it only dims the screen and stays on with the last frame on it (no picture update), instead of actually turning off the screen.
Both can be seen in fastbootrecovery.log:
a) line 15 - 25 :
Code:
Starting the UI...
setting DRM_FORMAT_BGRA8888 and GGL_PIXEL_FORMAT_BGRA_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
RECOVERY_BGRA
b) line 26 - 33:
Code:
framebuffer: 0 (1080 x 2160)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 1.083333x, offsets x: 0 y: 80 w: 0 h: -80
Click to expand...
Click to collapse
as i said this will work only on June 2019 security patch due to decryption works according to security patch
may be you may forgot to read that line
{ Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month & if you get password error in twrp just get back to system and Remove lock screen password , pin , pattern and keep in swipe mode and follow the procedure }
and thanks for posting logs

Raghu varma said:
as i said this will work only on June 2019 security patch due to decryption works according to security patch
may be you may forgot to read that line
{ Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month & if you get password error in twrp just get back to system and Remove lock screen password , pin , pattern and keep in swipe mode and follow the procedure }
and thanks for posting logs
Click to expand...
Click to collapse
Admittedly I haven't payed much attention to that line.
I read it but didn't understood it, mainly because there is no June SP out there yet.
So you are saying that we must wait for the SP to come out before trying the permanent zip installer ?
For my own reading, could you please share a link to the decryption changes ? I've tried to look for something related in Android Security Bulletin but couldn't find. Maybe I missed it

I have the last security patch (May 2019), will this TWRP work in it? The June security patch is not still avaibable.

TWRP 3.3.1-0 for May Security Patch
With Varma's guide here is a repacked version of his TWRP for May SP. This is temporarily until June SP arrives to stock gsi.
View attachment twrp-installer-3.3.1-0-B2N-May.zip use this installer

@k3dar7 you might be interested in my post above. Apparently TWRP and the installer has security patch version hardcoded, meaning it is not taken from what you have.

ban.codrut said:
With Varma's guide here is a repacked version of his TWRP for May SP. This is temporarily until June SP arrives to stock gsi.
View attachment 4781656 use this installer
Click to expand...
Click to collapse
Thanks for posting links

As of this the May repack is not needed anymore.
I know it hasn't rolled out fully yet, but you can still use stock recovery and sd card update method.
So after some days after this post I will remove the link to May repack as it will not be needed.

ban.codrut said:
@k3dar7 you might be interested in my post above. Apparently TWRP and the installer has security patch version hardcoded, meaning it is not taken from what you have.
Click to expand...
Click to collapse
thanks, understand and confirm that twrp from #1 work with june security update installed with data decryption
only question for clarify, if i (or other who this read) not want in twrp decrypt data partition (with using usb-c flash or push zip from pc to /tmp), is possible use actual version with older/newer than june ota update?

that means the device will be easy to root by using our trp steps ,.,..,write
it will grant root permission

Related

[OFFICIAL][TWRP][d5110] TWRP for Infinix Hot 2

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOADS
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
TWRP for Infinix Hot 2
Credits
@MSF Jarvis
@Nonta72
@Dees_troy
@jcadduono
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[OFFICIAL][TWRP][d5110] TeamWin Touch Recovery, Tool/Utility for the Infinix HOT 2
Contributors
HostZero, MSF Jarvis, Dees_troy
Source Code: https://github.com/TeamWin/android_device_infinix_d5110
Version Information
Status: Stable
Created 2016-06-08
Last Updated 2016-06-08

Reserved

How to back to stock recovery ?

0utc0ntr0l said:
How to back to stock recovery ?
Click to expand...
Click to collapse
Download STOCK recovery and flash it using TWRP.

Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition

youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
Thankyou I will work on patch soon.

youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images

RendyAK said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images
Click to expand...
Click to collapse
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card

youssef0789 said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card
Click to expand...
Click to collapse
Yeah, that is the bug of this twrp :3 @HostZero

RendyAK said:
Yeah, that is the bug of this twrp :3 @HostZero
Click to expand...
Click to collapse
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero

HostZero said:
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero
Click to expand...
Click to collapse
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.

RendyAK said:
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.
Click to expand...
Click to collapse
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero

HostZero said:
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero
Click to expand...
Click to collapse
This can be do with Terminal tho :3

RendyAK said:
This can be do with Terminal tho :3
Click to expand...
Click to collapse
Thankyou I will enter new table and most probably 3.0.2-1 or wait for 3.0.3-0.
- HostZero

I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.

awaaas said:
I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.
Click to expand...
Click to collapse
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero

HostZero said:
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero
Click to expand...
Click to collapse
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?

awaaas said:
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?
Click to expand...
Click to collapse
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.

HostZero said:
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.
Click to expand...
Click to collapse
You +1'd my changes on gerrit. And it IS pushed to github, you can check the commits of mine in TWRP device tree, it is pushed on June 19th.
https://github.com/TeamWin/android_device_infinix_d5110/commits/android-5.1
While it is good you added more partition to backup (note: IIRC, oem partition is not used by infinix) and cpu temp, I only complained about my changes duplicated by you, and that you claimed it.
Anyways, please don't make a duplicate fix in the future

CPU TEMPRATURE, Theres a Fix That i discovered.
and OEM partition is there for d5110 as per me.
I have duplicated on NVRAM etc all are new.

[UNOFFICIAL][RECOVERY][ham] TWRP 3.2.3-0 touch recovery [02-02-2019]

CHANGELOG for 3.2.1-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
CHANGELOG for 3.2.2-0:
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Fixed TWRP Decryption on Android version 7.1.2+ (i.e. 8.1 and 9.0)
TWRP release (twrp-3.2.3-20190202-ham) is based on Lineage-15.1 sources
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Download the latest version from here | Regular : twrp-3.2.3-20190202-ham
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
Click to expand...
Click to collapse
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot -i 0x2b4c flash recovery <recovery.img name>.img
Click to expand...
Click to collapse
fastboot -i 0x2b4c oem reboot-recovery
Click to expand...
Click to collapse
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Good work bro! But I'm unable to use both versions due to missconfigured onscreen touch sensor. Upper left button is reachable via touching of lower right part of the screen and so all other onscreen stuff is inaccessible completely...

adanoss said:
Good work bro! But I'm unable to use both versions due to missconfigured onscreen touch sensor. Upper left button is reachable via touching of lower right part of the screen and so all other onscreen stuff is inaccessible completely...
Click to expand...
Click to collapse
I guess, its kernel issue. The same was happening on lineage-15.0 with others. Thanks for reporting. Will check that issue and update new build.

[UNOFFICIAL][RECOVERY][ham] TWRP 3.2.1-0 touch recovery [11-12-2017]
Update:
1. Fix touch issue that was faced by some users.
2. Added option where you can now backup /persist , /firmware & /splash too.
3. Fix OTA assertions issue while flashing android version 7.1.2 & below.
4. And other bug fixes
Link updated in OP. Enjoy!

Now everything seems to work fine, even backing up to external USB stick via OTG. Haven't tried to restore via OTG though.

shubhambhise said:
Update:
1. Fix touch issue that was faced by some users.
2. Added option where you can now backup /persist , /firmware & /splash too.
3. Fix OTA assertions issue while flashing android version 7.1.2 & below.
4. And other bug fixes
Link updated in OP. Enjoy!
Click to expand...
Click to collapse
The new version is unable to decrypt data anymore. It always shows: Pattern failed, please try again!:crying:

Data is not mounting for me. I flashed this twrp with flashify. But later I flashed it through 3.1.0. Still it doesn't show data partition

Aroma gapps not working

Rafiq007 said:
Data is not mounting for me. I flashed this twrp with flashify. But later I flashed it through 3.1.0. Still it doesn't show data partition
Click to expand...
Click to collapse
Looks like ftfs partitions are not detecting

Confirmed. I have data as F2FS and it doesn't mount.

Ok. So those who are facing f2fs data mount issues in TWRP-3.2.1 contact me on telegram to test the the new version that hopefully fixes this issue.
Telegram ID - https://t.me/sb6596

how to backup previous rom in this new twrp?

[UNOFFICIAL][RECOVERY][ham] TWRP 3.2.1-0 touch recovery [17-12-2017]
Update:
1. Fix the data mounting issue on F2FS filesystem.
2. Hopefully encryption is fixed. Don't know cause I haven't checked.
Link Updated in OP. Enjoy!

shubhambhise said:
Update:
1. Fix the data mounting issue on F2FS filesystem.
2. Hopefully encryption is fixed. Don't know cause I haven't checked.
Link Updated in OP. Enjoy!
Click to expand...
Click to collapse
Awesome! Thank you!

shubhambhise said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.2.1-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks[/SIZE]
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Download the latest version from here | Regular : twrp-3.2.1-0-ham | Green : twrp-3.2.1-0-ham-green | ( To see how green themed twrp looks like? Head towards screenshot section )
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Hello, I am a Chinese user, Androidfile can not be used in China, can provide other solutions, I am very grateful.

shubhambhise said:
Update:
1. Fix the data mounting issue on F2FS filesystem.
2. Hopefully encryption is fixed. Don't know cause I haven't checked.
Link Updated in OP. Enjoy!
Click to expand...
Click to collapse
Still failed to decrypt data. The only one version of TWRP can decrypts data on my ZUK Z1 is this: https://forum.xda-developers.com/zu...-3-1-0-0-touch-recovery-t3572069/post71801936

Linzeal said:
Still failed to decrypt data. The only one version of TWRP can decrypts data on my ZUK Z1 is this: https://forum.xda-developers.com/zu...-3-1-0-0-touch-recovery-t3572069/post71801936
Click to expand...
Click to collapse
Thanks. I will go through it and will push an update.

Dzwa said:
Hello, I am a Chinese user, Androidfile can not be used in China, can provide other solutions, I am very grateful.
Click to expand...
Click to collapse
Here you go..??
https://drive.google.com/file/d/19RVLX9am9Qd-4xx0j9-XcUtjI0kswKCP/view?usp=drivesdk
Sent from my Lenovo Zuk Z1 using XDA Labs

Since 17.01.2018 there is an official Version of TWRP 3.2.1.
I have tried to flash it with the official TWRP app and got the message "failed".
Now i do not dare to flash the image file over the recovery. Has anyone of you sucessfully flashed the official TWRP 3.2.1 Recovery with the app or recovery?
Thank you for your answers

Matze1909 said:
Since 17.01.2018 there is an official Version of TWRP 3.2.1.
I have tried to flash it with the official TWRP app and got the message "failed".
Now i do not dare to flash the image file over the recovery. Has anyone of you sucessfully flashed the official TWRP 3.2.1 Recovery with the app or recovery?
Thank you for your answers
Click to expand...
Click to collapse
when you're going to flash img, select flash img option in twrp before flashing...
And then flash the recovery img...

[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [T710][T715][T715Y][T810][T815][T815Y]

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Tab S2 8.0 2015 (LTE)
TWRP for Samsung Galaxy Tab S2 8.0 2015 (Wi-Fi)
TWRP for Samsung Galaxy Tab S2 9.7 2015 (LTE)
TWRP for Samsung Galaxy Tab S2 9.7 2015 (Wi-Fi)
How to flash a bootloader and/or modem1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import either the bootloader.tar or bootloader_modem.tar file, depending on your variant, with the "AP" button.
How to flash TWRP with Odin1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy Tab S2").
How to flash TWRP within a previous version of TWRP1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy Tab S2").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
E:recv error on uevent
- This warning appears during the process of making a nandroid backup. I assure you that it's perfectly innocence: your backup should complete successfully and it should restore successfully without any reference to this warning. This is a known bug that affects other Exynos devices as well, such as the Samsung Galaxy S7 Edge (hero2lte).
- Technical explanation from bigbiff himself: "I think it must be a bug, probably shouldn't print the log out if we aren't using ueventd to pull in partition information on a target device. I am not sure what devices we are supporting using ueventd however. Looks like it only runs from the process_fstab function. It's harmless, but I wonder if it should be put in an ifdef guard."
Credits
- Inspiration in motivating me to learn how to build TWRP: ashyx
- Updated partition sizes: jcadduono
- Testing of my gts28wifi builds to figure out the X-Y orientation bug: tripLr
- Providing source to fix MTP and ADB: bonuzzz
- Every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the gts28ltexx, gts28wifi, gts210ltexx, and gts210wifi.
Sources
- gts2 kernel repository
- gts28ltexx repository
- gts28wifi repository
- gts210ltexx repository
- gts210wifi repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy Tab S2
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-05
Created 2017-12-15
Last Updated 2022-12-09

Reserved
CHANGELOG
3.2.3-0
* Device now appears properly in adb shell, as per @t-o-f-u's patch in post #69.

Reserved

T710 only
Tested original version bad
Tested version ending in 1 working.
Backup all partitions pic below

T710 only Root access confirmed in file manager

You Might change title to [TWRP][Unofficial] xxxxxxxx

TotalNoobTrucker said:
You Might change title to [TWRP][Unofficial] xxxxxxxx
Click to expand...
Click to collapse
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.

ripee said:
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
Click to expand...
Click to collapse
Ok,
Flashed back to ashyxx
Flashed file ending in 2. It works ...!
Flashed back to ashyx
Flashed file ending in 3. It works too!!!
Don't know what u did, but 1 2 and 3 worked.
I checked your md5 and they were all different.
So something was different in each one but the last 3 of 4 work.
Flashing your un numbered file now.. rechecking

There are 2 TWRP flash that rotate the screen orientation from portrait to landscape that must be added if the TW_THEME is set to landscape:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
My first link from a few hours ago was build with both of these included, and we established that it didn't work.
Build 1 from a while ago had both of these removed, build 2 only included the top one, and build 3 only had the bottom one. Do all 3 numbered builds work equally well?

Great! Just tried lastest version of TWRP for T710 (dec-15) and touch is working great! Thank you for your work!

ripee said:
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
Click to expand...
Click to collapse
Ok. Reloaded the file from basket build with no number. It works same as 2 and 3
Send it off. By the way if there is a way to append the 3.2.1-0 with ripee I would do it ashyxx did. Haha
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
ripee said:
There are 2 TWRP flash that rotate the screen orientation from portrait to landscape that must be added if the TW_THEME is set to landscape:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
My first link from a few hours ago was build with both of these included, and we established that it didn't work.
Build 1 from a while ago had both of these removed, build 2 only included the top one, and build 3 only had the bottom one. Do all 3 numbered builds work equally well?
Click to expand...
Click to collapse
Your build one is now not named 1 it works but does not rotate.
Lemme check 2 and 3

TotalNoobTrucker said:
Ok. Reloaded the file from basket build with no number. It works same as 2 and 3
Send it off. By the way if there is a way to append the 3.2.1-0 with ripee I would do it ashyxx did. Haha
Click to expand...
Click to collapse
I'd have to add the optional flag TW_DEVICE_VERSION := _ripee to the BoardConfig.mk file, but with all due respect to ashyx, I'm not particularly interested in labelling my builds. But TWRP's Jenkins builder just appends the next available version number after the dash anyway.
Ok, the code is sent off for official support!

1 2 and 3 do not rotate. Portrait only, no landscape, flip, or flip landscape . Who cares. The root works in all 3 with touch screen on each file and directory. So the screen works great
I tested a full backup in 1, 10 gig to the SD card. So mounts are working.
Wohoo
---------- Post added at 04:16 AM ---------- Previous post was at 04:15 AM ----------
By the way rebooting into download mode directly from TWRP saved a ton of boot time
---------- Post added at 04:26 AM ---------- Previous post was at 04:16 AM ----------
Running twrp-3.2.1-0-gts28wifi.tar from Odin now full time. Thanks.
Let me know if you want to play with lineage 8.0. the t710 has 64 bit processors, and the developer from posiedon 1.0 got the source from Samsung to build it.

I just tested the version for the T810:
- flashing is successful
- touchscreen is working well
- besides the normal partitions there are "modem" and "efs" listed
- a test backup throws a lot of "E:recv error on uevent" errors.
So for now I went back to TWRP 3.1.1

hurray said:
I just tested the version for the T810:
- flashing is successful
- touchscreen is working well
- besides the normal partitions there are "modem" and "efs" listed
- a test backup throws a lot of "E:recv error on uevent" errors.
So for now I went back to TWRP 3.1.1
Click to expand...
Click to collapse
I can imagine that they used the same partitions as the mobile data variants. Do modem and efs cause problems with backing up? I'll run my own backup today to confirm.
If you're using my 3.1.1, well I built it from the same sources as 3.2.1 so let's see.

I did not run the backup till the last partitions as the error came directly with the first partition. Then I interrupt the backup. I can upload the recovery.log if it is useful for you.

hurray said:
I did not run the backup till the last partitions as the error came directly with the first partition. Then I interrupt the backup. I can upload the recovery.log if it is useful for you.
Click to expand...
Click to collapse
Sorry but I'm unable to reproduce your error so please post the log. Here's what I did:
I made 2 separate backups on my T810, one with a password and one without, of the 3 partitions that are checked off by default when you go into the Backup screen. Yes, modem and EFS are present and listed as having some data, but I didn't check either of them off.
At no point in either of the backup or restore procedures did I get the "E:recv error on uevent" error, or any error for that matter.

ripee said:
Sorry but I'm unable to reproduce your error so please post the log. Here's what I did:
I made 2 separate backups on my T810, one with a password and one without, of the 3 partitions that are checked off by default when you go into the Backup screen. Yes, modem and EFS are present and listed as having some data, but I didn't check either of them off.
At no point in either of the backup or restore procedures did I get the "E:recv error on uevent" error, or any error for that matter.
Click to expand...
Click to collapse
Here is the log of my backup. As I wrote I did not finished the backup. I interrupted it as soon as I saw the error.
I don't think that the error cames from selecting the modem and EFS partitions.
Here is a litte snipped from the relevant part of the log (on line #2641 in the log):
Code:
I:addFile '/system/fonts/RobotoCondensed-BoldItalic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent
I:addFile '/system/fonts/RobotoCondensed-Italic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
I don't know why this behaviour accours. The TWRP "twrp-3.1.1-0-gts210wifi.img" from you works without error (backup AND restore ). I don't use a password or encryption on the Tab S2. The only option I use is "compress" to save some space as my backups are space consuming on the external sdcard without it.

@ripee
Hello my friend. Thank you for your effort, I want to mention about the issue in TWRP , when you run any aroma it ru in wrong orientation. I want to ask If you fix that issue in your build.
My device is T815
Sent from my SM-T815 using Tapatalk

hurray said:
Here is the log of my backup. As I wrote I did not finished the backup. I interrupted it as soon as I saw the error.
I don't think that the error cames from selecting the modem and EFS partitions.
Here is a litte snipped from the relevant part of the log (on line #2641 in the log):
Code:
I:addFile '/system/fonts/RobotoCondensed-BoldItalic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent
I:addFile '/system/fonts/RobotoCondensed-Italic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
I don't know why this behaviour accours. The TWRP "twrp-3.1.1-0-gts210wifi.img" from you works without error (backup AND restore ). I don't use a password or encryption on the Tab S2. The only option I use is "compress" to save some space as my backups are space consuming on the external sdcard without it.
Click to expand...
Click to collapse
Please allow the backup to finish without stopping it. Let me know of any other errors that pop up and, if it stops by itself, which partition it was backing up when it stopped. In the meantime, I'll take a look at your log.
NeWONEx said:
@ripee
Hello my friend. Thank you for your effort, I want to mention about the issue in TWRP , when you run any aroma it ru in wrong orientation. I want to ask If you fix that issue in your build.
My device is T815
Sent from my SM-T815 using Tapatalk
Click to expand...
Click to collapse
Is Aroma displaying in portrait orientation while TWRP is in landscape? Which exact Aroma build are you trying to flash? Did this also occur on older versions of TWRP? Are you able to tap on Aroma's menus properly, or does the tap location not correspond to the place that Aroma thinks you tapped? I need more details to be able to help.
There is a chance that Aroma needs to be updated to TWRP 3.2.

[RECOVERY][UNOFFICIAL] TWRP-3.2.3-0 Permanent Installer [20190122]

nageen9211 said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Decryption
Installation :
Procedure:
1.Boot into TWRP(using old twrp that u guys use)
2.Go to wipe option (optional reason on 3 rd step)
3.Select format data ((if you want to make internal storage readable)(This will erase all data on internal storage)
4.Then go back and flash twrp installer from the install option.
5.After installation,go to reboot option (select recovery) and reboot.
6.Done!
Download Link : Download
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP-3.2.3-0 Permanent Installer [20190122], Tool/Utility for the Nokia 7 Plus
Contributors
nageen9211, sriram prakhya
Source Code:https://github.com/Ram9199/TWRP_Basil_Device_tree
Version Information
Status: Stable
Created 2019-01-22
Last Updated 2019-01-22
Click to expand...
Click to collapse
Make it normal flash able and also provide order twrp link

Great work bro.:good:

Purak6 said:
Make it normal flash able and also provide order twrp link
Click to expand...
Click to collapse
Normal flashable won't work with every rom , as every one is using different variant and different security patches .. that's why I have made it ...

nageen9211 said:
Normal flashable won't work with every rom , as every one is using different variant and different security patches .. that's why I have made it ...
Click to expand...
Click to collapse
And older twrp link ?

It's possible to use with TA-1055 or isn't tested on that variant?

death_jax said:
It's possible to use with TA-1055 or isn't tested on that variant?
Click to expand...
Click to collapse
test it and report. Bdw, android pie is preffered. It is reported that it stuck at boot logo on oreo roms

Purak6 said:
And older twrp link ?
Click to expand...
Click to collapse
i dont know about them, this is the fresh twrp . and we will maintain this only..

nageen9211 said:
[...] TWRP-3.2.3-0 Permanent Installer [20190122] [...]
Click to expand...
Click to collapse
can you please clarify what is mean "Permanent Installer"?
1) is this TWRP universal for any Android9 version? does not require exactly version?
2) is persistend after OTA update?
i ask because N7p don't have separate recovery partition and use hybrid boot for boot+recovery, this TWRP is not in boot partition?

k3dar7 said:
can you please clarify what is mean "Permanent Installer"?
1) is this TWRP universal for any Android9 version? does not require exactly version?
2) is persistend after OTA update?
i ask because N7p don't have separate recovery partition and use hybrid boot for boot+recovery, this TWRP is not in boot partition?
Click to expand...
Click to collapse
yes, This installer will unpack your boot.img from your current rom , and patch the twrp in it and repack it.
it works on almost all pie roms . have problem on oreo gsi .
and i think.. as long as boot partition is not affected by ota (which most of the times is affected ) twrp will persist. other wise u have to repatch your boot.img with this installer.

How to install twrp recovery on Nokia tell me set by step

bharath moram said:
How to install twrp recovery on Nokia tell me set by step
Click to expand...
Click to collapse
You can use this me howto for Magisk install:
https://forum.xda-developers.com/nokia-7-plus/help/pie-october-update-failed-t3862758/post78285662
Where is say Magisk.zip you use TRWP installer zip from first post in this thread..,

Good work, sir.
By the way, does it have format data to f2fs support? TWRP images for this device out there doesn't have.

Lot of warnings in recovery.log
Thanks for making this!
I'm getting lots of warnings like this one:
Code:
WARNING: linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
Should I be worried about TWRP correct functioning?
Busybox seems to be all well and good though!

k3dar7 said:
You can use this me howto for Magisk install:
https://forum.xda-developers.com/nokia-7-plus/help/pie-october-update-failed-t3862758/post78285662
Where is say Magisk.zip you use TRWP installer zip from first post in this thread..,
Click to expand...
Click to collapse
Hi, thanks for this.
But after I fastboot boot the twrp boot img, all the folder names in TWRP are strange, like they're encrypted. How do I get around this?

Read step 3 in the OP. You have to format data.
I've found that using another twrp image to boot (not flash) it decrypts the data by asking the pattern I've set up in the os.
Now I want to ask the dev @nageen9211 if he can use that image to make this script.

ban.codrut said:
Read step 3 in the OP. You have to format data.
I've found that using another twrp image to boot (not flash) it decrypts the data by asking the pattern I've set up in the os.
Now I want to ask the dev @nageen9211 if he can use that image to make this script.
Click to expand...
Click to collapse
Thanks for the reply - actually I tried the OP originally, but formatting data got rid of my google play services as well, and I couldn't use my phone at all as a result, because a popup saying "google play services stopped working"/"google battery saver had stopped working" kept popping up repeatedly.
I had to reflash using OST and start over again. Which is why I was interested in another method without formatting data
Unless there is a way around fixing the Google Play services issue after formatting data?

Iam using Nokia 7 pLus rom having Android pie how to install twrp recovery tell step buy step

bharath moram said:
Iam using Nokia 7 pLus rom having Android pie how to install twrp recovery tell step buy step
Click to expand...
Click to collapse
If you have unlocked bootloader, howto i write before some mess on this page of this thread.. then first step is read this thread

I saw that on 15 of april was out the 3.3.0-0 of TWRP...how can we get it?
There is a very good changelog, especially for our A/B device(s):
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)

[Treble]vndk30(11) and vndk32(12L) treble vendor for galaxy s7 hero2lte

https://gitlab.com/hackintosh5/TrebleInfo
Credits
https://github.com/8890q/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/osm0sis/ for anykernel, used for the twrp patching zip
Special thankshttps://github.com/ExpressLuke for hero2lte testing
https://github.com/00p513-dev for suggesting using squashfs for vendor partition, making it possible to skip partition table modding
https://github.com/phhusson for looking into the double tap to wake issues with phh GSI
https://github.com/ivanmeler for prompting me to look into lpm again, now it is migrated into /vendor
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
2022-06-12 the CACHE partition is now used as vendor, the HIDDEN patition is now used as cache, no more partition table mods required
Updates:
2023-02-23
added store_mode.zip flashable that uses "/sys/class/power_supply/battery/store_mode" and "/sys/module/sec_battery/parameters/store_mode_max" interfaces for limiting battery charging
flash to limit battery charging to 70%, flash again to disable charging limitafter flashing, charging limit can be adjusted at "/system/etc/init/8890_store_mode.rc" by changing "70" on the line "service enable_store_mode /system/bin/8890_store_mode 1 70" to other percentage values
2023-02-15
include libaptX_encoder.so in patchers
adding patches to support phh android 13 GSIs:
includes lineage lmkd, LineageOS/[email protected] seems required for lmkd to work on this kernelfix bluetooth audio by disabling sysbta (generic in-system bluetooth audio implementation), see phhusson/treble_experimentations#2519disable full disk encryption and quota when booting android 13, 8890q/[email protected] 8890q/[email protected] ; FDE still works when using android 12 GSIsdisable healthd offline charging service, conflicts with lpm
2022-10-04
update gps blobs from https://github.com/8890q/proprietary_vendor_samsung/commit/698ddd9acd7bdca78ecea93e06fd78a0d9dbc407
2022-09-05
adding keystore fixes to a12_patcher.zip:
https://github.com/LineageOS/android_system_security/commit/356c125115c0a9b9f9670b5b86b6e291c5ec5404
https://github.com/8890q/patches/commit/9a322b4e71ca784d4a2f71494d1ef0e52f835efe
which fixes keystore apps and device encryption on Google 12L GSI, might also fix some keystore apps issues on phh GSI
2022-07-10
moved lpm to vendor partition
2022-06-26
rebased vndk32 on 2022-06-24 build from ivan
new smaller vendor flasher, flashes only boot and vendor
2022-06-24
lpm_installer.zip should work with Phh and Andy Yan GSIs better now
2022-06-18
vndk30 prop changes, might help booting exotic GSIs
2022-06-13
android 12 data usage meter now works with a12_patcher.zip
2022-06-12
fixed neural network api hal
fixed fingerprint sensor
switched vendor image to squashfs, no CreateVendor required anymore with it's small size
new twrp patcher zip, should no longer cause "twrp is stuck after flashing CreateVendor"
bigger GSIs should fit better now with the original ~4.5GB SYSTEM partition; device native roms can be used without RevertVendor
2022-05-31
fixed wifi tethering
vndk32: rebased on 2022-05-26 12L build from ivan
phh_wifitethering_patcher.zip for wifi hotspot on phh GSIs
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:
some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
data usage stays at 0 MB used on android 12 GSIs, because ebpf is used for metering
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from https://github.com/8890q/patches
a11_patcher.zip creates /system_root/efs if required
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
as a workaround, disable usb adb and use wifi adb
Wifi tethering does not work on phh GSIs <= 414
https://github.com/phhusson/vendor_hardware_overlay/tree/pie/Tethering conflicts with our Tethering overlay
flash phh_wifitethering_patcher.zip after installing phh GSIs
Alarm clock not working on aosp GSI
it should be fixed on phh 414 and up, it is not a vendor issue. If you are using an older aosp GSI, flash deskclock_powersaving.zip to fix that. See https://github.com/LineageOS/androi...mmit/8dd096c4cfb647960be1695a57246727878b8c8d
Google android 13 GSIs do not work
post-build patching got more involved in android 13 since on-java patches are now required, stick with phh/treble droid GSIs which already include build time patches for bpf-less kernel support
Disk encryption does not work on android 13 GSIs
full disk encryption is removed in android 13, file based encryption not available currently https://github.com/8890q/android_de...mmit/3cbcf972465419c18bf4850d26320896df465b18
Installation
If you are using the old partition table mod zip heroxlte_CreateVendor_2.0.zip from older versions, first flash heroxlte_RevertVendor_2.0.zip, or revert your partition table other ways such as odin. Skip this step if you have never touched your partition table
Install twrp-3.6.2_9-0 from https://eu.dl.twrp.me/herolte/ (s7) or https://eu.dl.twrp.me/hero2lte/ (s7 edge), as of rignt now newest(twrp-3.7.0_9-0) is too big for flashing
Flash twrp_patcher.zip to enable system.img flashing, it'll reboot to recovery once it's done, tested on 3.6.2_9-0 but newer versions should work unless recovery.fstab changes
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Flash the system.img of your choice
If you are using phh GSI version <= 414, flash phh_wifitethering_patcher.zip
If you are using phh GSI version <= 414, flash phh_dt2w_patcher.zip to fix double tap to wake
If you are using phh GSI version <= 413 or pure aosp, flash deskclock_powersaving.zip to fix alarm clock
If you are using an android 12/12L GSI, flash a12_patcher.zip
If you are using an android 11 GSI, flash a11_patcher.zip
If you are using a phh/treble droid android 13 GSI, flash phh_aosp13_patcher.zip
Updating vendor
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Undo twrp_patcher.zip and revert to device native romsThis is not required for using device native roms, however OTA updates might require this
Flash the newest twrp again
Format cache using wipe -> select cache -> repair or change file system -> change file system -> ext4
Flash a device native rom
Buildinglineage_build_herolte_vendor_part, lineage_build_hero2lte_vendor_part, lineage_build_herolte_vendor_part_18.1 and lineage_build_hero2lte_vendor_part_18.1 builds lineageos along with treble vendor using https://github.com/lineageos4microg/docker-lineage-cicd
you'll need ~15GB of free ram, ~300GB free disk space and podman
# create directories
mkdir src
mkdir zips
mkdir logs
mkdir ccache
# builds lineage 19.1 along with vndk32 for herolte (s7 flat exynos)
bash lineage_build_herolte_vendor_part
Reporting issues besides the known ones:
You can report them over https://github.com/Kethen/herolte_treble/issues
Downloadshttps://github.com/Kethen/herolte_treble/releases

Never thought I would see this coming to our device, this is absolutely amazing. Thank you for your hard work

Twrp (latest version) got stuck after flashing twrp patcher, i reflashed it with Odin but now my phone is stuck on the Samsung logo, i cant boot to twrp, only to download mode, what do i do?

"some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs"
indeed GSI google Android 13 does not start what do you mean by mounting efs manually can you explain please thank you

Full House said:
"some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs"
indeed GSI google Android 13 does not start what do you mean by mounting efs manually can you explain please thank you
Click to expand...
Click to collapse
it lacks the mount point, so I meant adding the mount point by modifying system and adding a directory called 'efs'
a11_patcher.zip and a12_patcher.zip does that for you
meanwhile, android 13 beta GSI from google does not boot and I probably won't look into it until android 13 source is released

Omarkoopa said:
Twrp (latest version) got stuck after flashing twrp patcher, i reflashed it with Odin but now my phone is stuck on the Samsung logo, i cant boot to twrp, only to download mode, what do i do?
Click to expand...
Click to collapse
assuming you did the odin flash correctly, try booting samsung recovery and factory reset there

katharinechui said:
important: system as root builds, you'd want ab build GSIs
Click to expand...
Click to collapse
We can use A/B builds too? Didn't really understand, sorry

1lopes said:
We can use A/B builds too? Didn't really understand, sorry
Click to expand...
Click to collapse
you can only use A/B builds, which is also known as system as root builds

Support s7?

katharinechui said:
you can only use A/B builds, which is also known as system as root builds
Click to expand...
Click to collapse
Thank you so much for your response.
Ill try and boot a Nippon GSI and update it here, or start testing some GSIs.
Great project, looks like you put some hard effort

1lopes said:
Thank you so much for your response.
Ill try and boot a Nippon GSI and update it here, or start testing some GSIs.
Great project, looks like you put some hard effort
Click to expand...
Click to collapse
nippon GSIs usually have broken selinux policies and other weird oem rom stuffs that prevent booting.

katharinechui said:
nippon GSIs usually have broken selinux policies and other weird oem rom stuffs that prevent booting.
Click to expand...
Click to collapse
I followed your guide, flashed TWRP 3.6.2_9-0, then twrp_patcher.zip, rebooted to recovery and I dont see any .img ROM, only .zip, and I am sure I do have atleast 1 .img system on my SD card.
Then proceeded to reflash stock ROM, reflashed TWRP once again, did the same steps and the same. I don't know what I am doing wrong, please help me.
Edit: Could it be because I didn't revert partitions? Where can I find the files? I don't see them on github.

1lopes said:
I followed your guide, flashed TWRP 3.6.2_9-0, then twrp_patcher.zip, rebooted to recovery and I dont see any .img ROM, only .zip, and I am sure I do have atleast 1 .img system on my SD card.
Click to expand...
Click to collapse
{
"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"
}
1lopes said:
Edit: Could it be because I didn't revert partitions? Where can I find the files? I don't see them on github.
Click to expand...
Click to collapse
You'd only need revert partition if you've changed your partition table in the past. While the zip is available in all previous releases, I forgot to upload it to the latest release. As of this post it has been re-uploaded to the latest release as well.
1lopes said:
Click to expand...
Click to collapse
Ask nippon to fix their GSIs

katharinechui said:
View attachment 5673497View attachment 5673499View attachment 5673501View attachment 5673503
You'd only need revert partition if you've changed your partition table in the past. While the zip is available in all previous releases, I forgot to upload it to the latest release. As of this post it has been re-uploaded to the latest release as well.
Ask nippon to fix their GSIs
Click to expand...
Click to collapse
Ohhh, i am so sorry. I thought there was something wrong I was doing, as I am actually familiar to only .zip flashing on twrp and fastboot too.
thank you so much for the help!

please add offline charger, thanks

Cuonghmm said:
please add offline charger, thanks
Click to expand...
Click to collapse
it works, what do you mean

katharinechui said:
it works, what do you mean
Click to expand...
Click to collapse
yes it works ,s7, mine, charge and use, it's very hot, is there any way to fix it? thanks

Cuonghmm said:
yes it works ,s7, mine, charge and use, it's very hot, is there any way to fix it? thanks
Click to expand...
Click to collapse
Put it in a freezer... Now being serious, no. Thank Exynos and Samsung battery. Disable fast charge or stop charging when it reaches the limit

1lopes said:
Put it in a freezer... Now being serious, no. Thank Exynos and Samsung battery. Disable fast charge or stop charging when it reaches the limit
Click to expand...
Click to collapse
luckily, offline charging works

Cuonghmm said:
yes it works ,s7, mine, charge and use, it's very hot, is there any way to fix it? thanks
Click to expand...
Click to collapse
using a 1 amp or less charger should help with the temps

Database Develop

welcome