Database Develop

[RECOVERY][T713] TWRP 3.3.0-0 Touch Recovery [OFFICIAL]

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.
DOWNLOAD: https://dl.twrp.me/gts28vewifi
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy 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
[RECOVERY][T713] TWRP 3.3.0-0 Touch Recovery [OFFICIAL], ROM for the Samsung Galaxy Tab S2
Contributors
LuK1337, luca020400, Olivier
Source Code: https://github.com/TeamWin
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2017-01-27
Last Updated 2019-04-15

-snip-

LuK1337 said:
-snip-
Click to expand...
Click to collapse
Thanks. It's great to have a proper version of TWRP.

No love for 2015 versions on TWRP site

it works with T719, so thank you

deleted

It also works with the T813. Great to have a real recovery on this device.

Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
I am on it.

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
Actually, I think the issue with decryption is with qcom_common. The following commit is needed (which exists on the android-7.1 branch): https://github.com/TeamWin/android_...mmit/c4dab0d6d73f05b70091761e536b751dc9328f49

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
Please try latest ( 3.1.1-1 ) build.

LuK1337 said:
Please try latest ( 3.1.1-1 ) build.
Click to expand...
Click to collapse
It works now, thank you very much.

Hi, would this be compatible with gts210veltexx

Alpha1BA said:
Hi, would this be compatible with gts210veltexx
Click to expand...
Click to collapse
No, T813 recovery probably is.

Hello, think I need some help with setting up this particular tab... None of the recovery images listed on the official site (plus the unofficial one here) work properly. Any 3.1.0+ one would say "Failed to mount /data (invalid arguments)" and not show me my internal storage and data (shows /system and SD card alright though), and lower version ones would just boot to TWRP splash screen then reboot, without getting to the main menu. I'm running the latest Nougat update (T713XXU2BQD3) if that matters.

AndyYan said:
Hello, think I need some help with setting up this particular tab... None of the recovery images listed on the official site (plus the unofficial one here) work properly. Any 3.1.0+ one would say "Failed to mount /data (invalid arguments)" and not show me my internal storage and data (shows /system and SD card alright though), and lower version ones would just boot to TWRP splash screen then reboot, without getting to the main menu. I'm running the latest Nougat update (T713XXU2BQD3) if that matters.
Click to expand...
Click to collapse
You can't mount data if you come from stock. It is encrypted and twrp doesn't support it so you got to format it to ext4 in order to mount it.

LuK1337 said:
You can't mount data if you come from stock. It is encrypted and twrp doesn't support it so you got to format it to ext4 in order to mount it.
Click to expand...
Click to collapse
Ugh. It had been a while since I touched any recent Samsung devices, didn't know I had to do extra work around encryption. Used a lot of other devices but TWRP handles all of them with a default key, that's why I'm quite baffled why it doesn't here. Thanks for the quick save though.

AndyYan said:
Ugh. It had been a while since I touched any recent Samsung devices, didn't know I had to do extra work around encryption. Used a lot of other devices but TWRP handles all of them with a default key, that's why I'm quite baffled why it doesn't here. Thanks for the quick save though.
Click to expand...
Click to collapse
Samsung uses different encryption and we only support AOSP one.

LuK1337 said:
Samsung uses different encryption and we only support AOSP one.
Click to expand...
Click to collapse
Alrighty, can understand. Can there be a notice somewhere up this thread or the TWRP device landing page about it?

Is LineageOS 14.1 the only rom for this t713wifi. I cant find any stock rooted.

[rom] lineageos 14.1

loaded this on my old phone, seems to work
https://drive.google.com/open?id=0B0...jNKZW1WQ3ExOWs

^ edited to include link

-- see below for update --

Bluetooth isn't working. The message bluetooth share stopped working appears as soon as I switch the toggle. Just letting you know. Great work with this build, I was able to make calls and send messages over lte on AT&T. Really great so far

fixed bluetooth: https://drive.google.com/open?id=0B08utbHfUyw6MjNKZW1WQ3ExOWs
source of fix:
https://github.com/LegacyHuawei/and...mmit/e1564746378cfe5e7b30bec65e626c3edebebacc

Thanks, that fixed Bluetooth, also mtp notified me that it stopped working the moment I make my sd marked as portable storage, I'll check if that occurs again when I try to transfer from my PC. No other problems so far
Update - otg and mtp working fine

source?
Thanks muchly for doing this. Is the source that you used to build the zipfile available someplace I could download it?

plasticchris said:
loaded this on my old phone, seems to work
https://drive.google.com/open?id=0B0...jNKZW1WQ3ExOWs
Click to expand...
Click to collapse
File no longer available?

Demasiados bugs el inestabilidad reinicios a cada rato

The VoIP doesn't seem to work. I tried the stock stack and Fongo. On connecting a call the I can hear the other side, but my voice is muffled/crackly and very very quiet. If I switch to the external speaker everything works but switching back causes the same problem. To me it seems like a sound routing problem.

protectivedad said:
The VoIP doesn't seem to work. I tried the stock stack and Fongo. On connecting a call the I can hear the other side, but my voice is muffled/crackly and very very quiet. If I switch to the external speaker everything works but switching back causes the same problem. To me it seems like a sound routing problem.
Click to expand...
Click to collapse
I had the same problem.
You need change those parametrs at build.prop:
use.dedicated.device.for.voip=true.
use.voice.path.for.pcm.voip=true.
change those parameters to "false"
At CianogenMod12.1(at this firmware Voip work fine), this parametrs are missing, maybe need simply deleting at Lineage 14.1. Today I use my smartphone whith those changes, problem resolved.

krv163 said:
I had the same problem.
You need change those parametrs at build.prop:
use.dedicated.device.for.voip=true.
use.voice.path.for.pcm.voip=true.
change those parameters to "false"
At CianogenMod12.1(at this firmware Voip work fine), this parametrs are missing, maybe need simply deleting at Lineage 14.1. Today I use my smartphone whith those changes, problem resolved.
Click to expand...
Click to collapse
Worked like a charm. Too bad the phone has started having a battery charge issues. I had it dismantled for the last three weeks. Reassembled to test. I will have to keep those settings in mind for other VoIP android phones.

Could you post the link of your device tree, kernel, vendor and any other repos that you used?

krv163 said:
I had the same problem.
You need change those parametrs at build.prop:
use.dedicated.device.for.voip=true.
use.voice.path.for.pcm.voip=true.
change those parameters to "false"
At CianogenMod12.1(at this firmware Voip work fine), this parametrs are missing, maybe need simply deleting at Lineage 14.1. Today I use my smartphone whith those changes, problem resolved.
Click to expand...
Click to collapse
What recovery you used?

Lineage-14.1-20200227-UNOFFICIAL-mb886
Lineage14.1 unoficial and TWRP 3.3.1-0 for the Atrix HD. It as only been tested on a Razr M. I will make an official thread in the development section if there's enough interest.
I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, thermonuclear war, or you getting fired because the alarm app
* failed. Please do some research if you have any concerns about features included
* in this ROM before flashing it! YOU are choosing to make these modifications, and
* if you point the finger at us for messing up your device, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
Procedure
NB: You must format your Data and Cache partitions as F2FS
Download the latest PICO or NANO GApps from OpenGapps
Backup your internal SD Card, off of the device eg USD or Hard Disk
Boot to TWRP
Make a nandroid backup, and ensure this backup is not on the device itself
Format your data partition and cache partition to F2FS (do NOT post for instructions
on how to do this on this thread!)
**Note: Touch still not working properly so you MUST use a mouse.
Wipe Cache , System & Dalvik-Cache
Flash the ROM Zip
Flash Gapps ARM -> 7.1
Wipe cache and dalvic
Done - Reboot to [System]
Wait...
Not Working:
You tell me
Rom: https://www.androidfilehost.com/?fid=4349826312261733183
MD5sum: https://www.androidfilehost.com/?fid=4349826312261733184
Recovery: Here
***Don't forget a mouse***
All work is done here: https://github.com/Wheels564
Screenshot https://www.androidfilehost.com/?fid=4349826312261715435
Edit: Added recovery download to OP

Wheels564 said:
Here is a test version of lineage14.1 unnoficial and TWRP 3.1.1-0 for the Atrix HD. It as only been tested on a Razr M. I do not have enough posts to make a new thread so I'm adding it here.
I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, thermonuclear war, or you getting fired because the alarm app
* failed. Please do some research if you have any concerns about features included
* in this ROM before flashing it! YOU are choosing to make these modifications, and
* if you point the finger at us for messing up your device, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
Procedure
NB: You must format your Data and Cache partitions as F2FS
Download the latest PICO or NANO GApps from OpenGapps
Backup your internal SD Card, off of the device eg USD or Hard Disk
Boot to TWRP
Make a nandroid backup, and ensure this backup is not on the device itself
Format your data partition and cache partition to F2FS (do NOT post for instructions on how
to do this on this thread!)
Wipe Cache , System & Dalvik-Cache
Flash the ROM Zip
Flash Gapps ARM -> 7.1
Wipe cache and dalvic
Done - Reboot to [System]
Wait...
Rom: https://www.androidfilehost.com/?fid=4349826312261715411
MD5 sum: https://www.androidfilehost.com/?fid=4349826312261715412
Recovery: https://www.androidfilehost.com/?fid=4349826312261715413
All work is done here: https://github.com/Wheels564
Screenshot https://www.androidfilehost.com/?fid=4349826312261715435
Click to expand...
Click to collapse
does not work on atrix hd. touch doesnt work.
---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------
jerryspring said:
does not work on atrix hd. touch doesnt work.
Click to expand...
Click to collapse
on other roms that i have flashed that required to format to f2fs i successfully flashed with 6059 philz f2fs recovery without changing that options.. wouldnt your rom flash on that recovery as well?

jerryspring said:
does not work on atrix hd. touch doesnt work.
---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------
on other roms that i have flashed that required to format to f2fs i successfully flashed with 6059 philz f2fs recovery without changing that options.. wouldnt your rom flash on that recovery as well?
Click to expand...
Click to collapse
I'll see if I can build one with the old touch driver. Touch worked fine on the Razr M both in recovery and rom. My Razr HD had the old touch driver but works fine with the new one.
The old Philz recovery probably won't support android 7.1. I'll see what I can do with it when I get time.

Wheels564 said:
I'll see if I can build one with the old touch driver. Touch worked fine on the Razr M both in recovery and rom. My Razr HD had the old touch driver but works fine with the new one.
The old Philz recovery probably won't support android 7.1. I'll see what I can do with it when I get time.
Click to expand...
Click to collapse
Yeah. Got status 7 using philz f2fs recovery

TWRP and Lineage
New builds up:
Read op for info on rom and twrp.

lineage-14.1-20200227-UNOFFICIAL
New build up
lineage-14.1-20200227-UNOFFICIAL-mb886
Changelog
Bluetooth fixed
Rom: https://www.androidfilehost.com/?fid=4349826312261733183
MD5sum: https://www.androidfilehost.com/?fid=4349826312261733184
Don't forget to read the op about TWRP https://forum.xda-developers.com/showpost.php?p=81672185&postcount=15

Unofficial TWRP for sagit [F2FS+EXT4][Unofficial]

Unofficial TWRP and OrangeFox builds.
TWRP : https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/
OrangeFox - deprecated : https://sourceforge.net/projects/ep...overy/OrangeFox-Unofficial-sagit.img/download
This is TWRP-3.3.1 unofficially updated with lots of new improvements!
What's here but not in the official one?
Compiled with Pie blobs and in pie environment
Updated kernel, based on CAF's latest pie tag and compiled with latest Clang 9.0.3 by Google
Additional debug support - This TWRP won't overwrite /sys/fs/pstore
F2FS support
Cleaned unused HALs from manifests
System as Root variant available
How to install this TWRP?
Boot into fastboot mode by pressing volume down + power when the device is turned off
Connect your device to your computer
Download the TWRP build
Open a shell at the download folder
Rename the downloaded file to twrp.img
Type
Code:
fastboot flash recovery twrp.img
To leave the fastboot mode type
Code:
fastboot reboot
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
How to use F2FS for /data and /cache?
Reboot into this TWRP
Select wipe > format data then type yes and reboot into recovery again
Then select wipe > advanced wipe select cache then select repair or change file system and select F2FS
Do the same step with Data
Install a supported ROM and GApps
Reboot into the ROM

Thank you for your great work . keep it up

Thanks,I'm following the topic

Sorry for my ignorance....but can somebody tell me the difference between these two?

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Between orange fox and twrp? Orange fox is a fork of twrp with some special features and a redesign.

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Have a look here - https://orangefox.tech/

DarthJabba9 said:
Have a look here - https://orangefox.tech/
Click to expand...
Click to collapse
happy to see you here, Will sagit devices have an official version? We are looking forward

fr0bs said:
happy to see you here, Will sagit devices have an official version? We are looking forward
Click to expand...
Click to collapse
In due course

New TWRP test build is available!
TWRP was updated to version 3.3.0 and is usable with f2fs.
Download : https://drive.google.com/file/d/1UwT5UBz_8PVugEhWLYlcwKM3VAi25jkI/view
This build is possible due to Ultraschorsch 's support by providing a Google Cloud trial ?

Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0

Decryption problem
NeoArian said:
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Click to expand...
Click to collapse
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?

perspicio said:
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
Click to expand...
Click to collapse
There is a problem with decrypting devices formatted with may ASB, I see about it. You could go f2fs or setup rom on April build and upgrade to new one for now.
Edit:// should be fixed here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1

I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...

Hi @NeoArian, it seems that at least your latest TWRP-sar version has issues with mounting external usb storages: at least my sandisk 64GB key that I always used to save nandroids to is not detected, thus I have to rely on internal memory to save nandroids, fw, and user data.
Using TWRP version 3.2.3-sagit-shev.img I have no issues (but unfortunately no support for your lineageos unofficial builds if I'm not mistaken).
Am I doing something wrong? Do you have any suggestions?

Cavaler said:
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Click to expand...
Click to collapse
I thought it was some codes in twrp that cause the problem.
If I use 3.3.1.0 everything works fine. but it won't decrypt my data even I had no pattern for lock screen with 3.3.1.2.
( all mentioned above are official builds )

This version TWRP have arch bug.
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444

New twrp update available: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1-20191204
AmaoBilibili said:
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
Click to expand...
Click to collapse
I assume that's a problem with OpenGapps installer.

Hi, I'm running twrp 3.3.1-20191204 with your Lineage 17 very happily thanks!
For the last couple of lineage installs though (2019-12-24 and 2020-01-08) I'm getting a failure in twrp when running a backup, on data partition specifically:
createTarFork() process ended with ERROR: 255
recovery.log is far more helpful:
Code:
# tail -n 50 /tmp/recovery.log
I:addFile '/data/anr/anr_2020-01-10-11-49-31-592' including root: 1
==> set selinux context: u:object_r:anr_data_file:s0
I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '0eb5afb598811574'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/161a6490/2020-01-10--16-29-03_lineage_sagit-userdebug_10_QQ1B200105004_en/data.ext4.win008'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
There's an (empty) folder '/data/per_boot' which seems to be breaking the backup process. I'm not sure if it's lineage itself or one of my apps creating this dir, but if I manually delete it the backup works... then it gets recreated next boot.
A somewhat minor issue, in case it's either easy enough to fix and/or other's run into the same problem!

I assume this twrp version use for flashing gsi. Am I correct?

[RECOVERY][3.4.0-14][phoenix/in]Unofficial TWRP for Xiaomi Poco X2/Redmi K30 (Beta)

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:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
TWRP 3.4.0-10 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_phoenix
https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @merothh for the hard testing and other support
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-16

Nice work the first build...
Thanks and waiting for 2nd build.....

mauronofrio said:
- Backup restore and image flash (system-vendor-product)
Click to expand...
Click to collapse
But does backup & restore for the data partition work?

Nice work!!!

Ya_SG said:
But does backup & restore for the data partition work?
Click to expand...
Click to collapse
it is in non working list

Nice. May I ask does Format data works reliably yet? (mean after Format data and flash rom, the phone won't automatically encrypt)

Never_Sm1le said:
Nice. May I ask does Format data works reliably yet? (mean after Format data and flash rom, the phone won't automatically encrypt)
Click to expand...
Click to collapse
Yes works

Finally!
Now I don't have to be afraid the phone will brick because of unknown sourced twrp from chinese.

Martensite said:
Finally!
Now I don't have to be afraid the phone will brick because of unknown sourced twrp from chinese.
Click to expand...
Click to collapse
I'm using the chinese one for months and it does not have any issues.
Until this has stable status or official status I'm more afraid of flashing this one

It's always asking for the password. Even though i did format data using that chinese twrp, when i flash this, it asks for password again.

TWRP 3.4.0-14 for Xiaomi Poco X2 (phoenix-phoenixin):
- Fixed decryption request also when the device is not encrypted.
TWRP 3.4.0-14 Unofficial by mauronofrio

mauronofrio said:
TWRP 3.4.0-14 for Xiaomi Poco X2 (phoenix-phoenixin):
- Fixed decryption request also when the device is not encrypted.
So the remaining issues still exist?
Thanks btw for new build
Click to expand...
Click to collapse

internal storage not showing in pc from this latest build. cannot copy rom zips to internal

This TWRP is worked on my Redmi k30 Phoenix. I have tried 'recovery-TWRP-3.4.0B-0209-REDMI_K30-CN-wzsx150', but failed boot twrp.
Thank u so much 'Dev', Please continue releasing newer version <3

arifn82 said:
internal storage not showing in pc from this latest build. cannot copy rom zips to internal
Click to expand...
Click to collapse
reboot again in TWRP, connect USB cable to pc. now u can see internal storage

How can i make the twrp permanent ?

Userbaban said:
How can i make the twrp permanent ?
Click to expand...
Click to collapse
Don't Flash stock ROM/ official ROM .

'boot ' fastboot command in lastest platform-tools won't work in that way.It assume the file is a KERNEL,not a whole boot image.This will only make device go blackscreen.Check the binaries' help before run this command!

I found a problem.
If I use WIPE to format internal storage in TWRP and still can't mount internal storage after rebooting recovery.
It will not be possible to copy ROM files properly.
If you restart the system, re-entering TWRP after a successful system boot will restore the system to normal.
I wonder if it can be fixed?

ask Decrypt password everytime I reboot to twrp.
Help!

Make any GSI work fully on the Xiaomi Redmi 8

Code:
/*
* Your warranty is now void lol.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* 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.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * I am 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...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial

Forgot to mention that magisk WONT WORK on roms that use android 11!!
Its a limitation of android 11 and i cannot fix this.

Seems promising. Would try on weekend and cast vote.
Thanks for you efforts for community.

Realized once again that you dont even need to boot, just flash the lineageOS rom, then the GSI on top.

thank you very much its working the problem i always encounter is my bluetooth but now its working fine sorry for my bad english BTW i use havoc <3

I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?

thanks, in the evening I will check and tell exactly what works and what does not work, probably all GSIs are giving me some problems (problem with brightness or bluetooth headphones)

Thank you for this guide. I installed havoc os 4.1 using this exact method wiped everything formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?

Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?

Dragonnuu said:
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Click to expand...
Click to collapse
We need LOLZ because the lineage kernel gets carried over and its broken (Try booting lineage clear, you wont get far)

mwaseem851 said:
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
Click to expand...
Click to collapse
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.

I have done lots of experimentation since last post and finally settled with Havoc OS 3.12 (all android 11 roms are still buggy).
Thanks.
boofiboi said:
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
Click to expand...
Click to collapse

boofiboi said:
Code:
/*
* Your warranty is now void lol.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* 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.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * I am 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...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Click to expand...
Click to collapse
Can you flash the AOSP beta GSIs from released on the Android website? For example the Android 12 Beta GSI?
I tried installing Android 12 on Redmi 8 but it did something perplexing.
TWRP said no OS was installed. Rebooting had the phone boot back into TWRP. I tried installing through both fastboot and TWRP. Installations were successful tho.