New TWRP available for download. Still appears not to have MTP. From 3.2.1-0 you must flash the new installer.zip. Reboot TWRP and flash Magisk again
Installation instructions here:
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
@joemossjr has an unofficial TWRP that has MTP working available here: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
I can't find the changelog on twrp.me, do you know what they changed?
axmirza2 said:
I can't find the changelog on twrp.me, do you know what they changed?
Click to expand...
Click to collapse
Nope your guess is as good as mine other than the general 3.2.2-0:
Quoted from TWRP.me site: "TWRP 3.2.2-0 is out now for most currently supported devices.
What's new in 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
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links."
lollyjay said:
New TWRP available for download. Still appears not to have MTP. I think you need to first boot the new image, and then from it you must flash the new installer.zip.
Click to expand...
Click to collapse
Thanks dude. Have you tested the MTP because the previous version I am not able to transfer anything from PC to the device.
Thanks.
Mulham82 said:
Thanks dude. Have you tested the MTP because the previous version I am not able to transfer anything from PC to the device.
Thanks.
Click to expand...
Click to collapse
As I stated in the OP, MTP appears not to be included.
lollyjay said:
As I stated in the OP, MTP appears not to be included.
Click to expand...
Click to collapse
I see. By the way, I have saw some guys are taking about GSI MIUI 10, so do you think that will be possible?!
Thanks.
lollyjay said:
Nope your guess is as good as mine other than the general 3.2.2-0:
Quoted from TWRP.me site: "TWRP 3.2.0-0 is out now for most currently supported devices.
What's new in 3.2.0-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"
Click to expand...
Click to collapse
can you elaborate on the fstab support?
virtyx said:
can you elaborate on the fstab support?
Click to expand...
Click to collapse
Hi I am only quoting from the twrp.me site.
virtyx said:
can you elaborate on the fstab support?
Click to expand...
Click to collapse
That's the changelog from 3.2.0.0 as far a single can tell he only made a visiual change everything else is the same functionally ty wise
Mulham82 said:
Thanks dude. Have you tested the MTP because the previous version I am not able to transfer anything from PC to the device.
Thanks.
Click to expand...
Click to collapse
lollyjay said:
As I stated in the OP, MTP appears not to be included.
Click to expand...
Click to collapse
MTP still does not work.
iElvis said:
MTP still does not work.
Click to expand...
Click to collapse
That is what I wrote
lollyjay said:
That is what I wrote
Click to expand...
Click to collapse
Sorry, was replying to the other guy.
joemossjr said:
That's the changelog from 3.2.0.0 as far a single can tell he only made a visiual change everything else is the same functionally ty wise
Click to expand...
Click to collapse
I got excited for a second
not being able to edit the fstab because /vendor cant be edited is why we can't remove encrypt
virtyx said:
I got excited for a second
not being able to edit the fstab because /vendor cant be edited is why we can't remove encrypt
Click to expand...
Click to collapse
Not really. It's more of a verity issue once you make the change in will be reverted due to verity
They removed MTP because sometimes you would get a kernel panic when entering twrp (putting in your password would freeze twrp) but even without MTP TWRP gives me a kernel panic every now and then. I think MTP support should be added back in especially since we don't have a MicroSD slot.
ajsmsg78 said:
They removed MTP because sometimes you would get a kernel panic when entering twrp (putting in your password would freeze twrp) but even without MTP TWRP gives me a kernel panic every now and then. I think MTP support should be added back in especially since we don't have a MicroSD slot.
Click to expand...
Click to collapse
im not gonna deny that mtp is important but you also have the ability to to do adb push rom.zip /sdcard and it will transfer that way.
joemossjr said:
im not gonna deny that mtp is important but you also have the ability to to do adb push rom.zip /sdcard and it will transfer that way.
Click to expand...
Click to collapse
Sometimes when the phone doesn't boot and have to factory reset, MTP comes in handy to backup the internal storage.
so sad mtp still not there. (((
also, by installing "TWRP 3.2.2-0" in twrp I got constant reboot into twrp and was have to flash "[OFFICIAL]OxygenOS.OTA" and root, xposed, custom recovery
oneplus6 is still highly unstable,
thanks to Oneplus and Google for poor work.
because of it nexus6 is still my primary phone and oneplus6 just as a second toy ((
joemossjr said:
im not gonna deny that mtp is important but you also have the ability to to do adb push rom.zip /sdcard and it will transfer that way.
Click to expand...
Click to collapse
I hear you but it's good for those times where you flash something then reboot then you end up in a bootloop and forgot to back up a few files before you rebooted. Having MTP in TWRP saves you in that case and it's a nice feature to have.
Does aroma work now?
Related
Hello !
Currently i'm working in Le 2 kernel and device tree. My purpose is to make meaningful changes and additions so other ROMs can implement them.
Confirmed working with LOS, Carbon, LegendROM (latest releases)
This thread is all about the kernel. Currently the kernel features
sdcardfs support
cpu-input boost
power efficient work-queues
improvements to touchscreen driver, preparing support for dt2w
adj tree
low memory killer improvements
powersuspend driver
nvidia patches for energy efficiency
memory bus improvements
Adreno memory pools
and other small improvements in battery management and scheduler
Download: https://drive.google.com/open?id=0B4AOvCehd4v3OXBEX3dMSkdxQ3c
Source: https://github.com/mthomos/android_kernel_leeco_msm8976
To enable sdcardfs support just add this line in build.prop
Code:
ro.sys.sdcardfs=true
To be clear from the beginning: I will not answer to any feature requests and i respond to bug reports without logs. I hope to understand this
Cheers !
XDA:DevDB Information
Diades Kernel, Kernel for the LeEco Le 2
Contributors
marios199546
Kernel Special Features:
Version Information
Status: Testing
Created 2017-09-05
Last Updated 2017-09-07
What's the decryption key?
Good luck :good::good:
For which ROM?
Nice one.
Gonna try and report!
Its asking for decryption key!
OP updated with new link
Work on rom based in eui or only aosp rom ?
Sent from my Le X522 using XDA-Developers Legacy app
fmehdi said:
Work on rom based in eui or only aosp rom ?
Click to expand...
Click to collapse
Doesnt work on eui base
Only custom roms
What does sdcardfs mean?
bonsai.14 said:
What does sdcardfs mean?
Click to expand...
Click to collapse
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
billybobjoe512 said:
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
Click to expand...
Click to collapse
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Njishi said:
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Click to expand...
Click to collapse
So where would I flash these .img files? Or do I have to do something else before flashing
billybobjoe512 said:
So where would I flash these .img files? Or do I have to do something else before flashing
Click to expand...
Click to collapse
What else you can do? Like going for a walk is recommended!?
You just have to boot into recovery. And then flash them like the way i said.
Or else you can use this app.
https://youtu.be/6IMvOCUy2Wc
You can also flash .img via fastboot with this command : fastboot flash boot <file_name.img>
Also if you have magisk installed you have to flash again the magisk install every time you install a new kernel.
I am a bit of a noob so I'm probably doing a ton of things wrong here
So how long does it take to start up the device after flashing the kernel? I flashed to boot partition and I waited for about 10 minutes and I got impatient so I restarted and tried to take a logcat but it just said waiting for device so I just restored a backup that I had made
Did I mess up somewhere or do I need to have a logcat for this
Phone don't boot bro I waite d 20 min
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
marios199546 said:
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
Click to expand...
Click to collapse
Phone not booting. Stuck at Spash screen. Cant take logs (waiting for device).
It should work when you flash it, but using it is still a try at your own risk procedure.
To temporarily boot this recovery:
Code:
fastboot boot TWRP-3.2.3-0-unnoficial-oreo-land.img
To permanently flash it:
Code:
fastboot flash recovery TWRP-3.2.3.0_Land-Treble.img
Download: TWRP-3.2.3.0_Land-Treble.img
older
TWRP-3.1.1-0-unnoficial-oreo-v2-land.img
TWRP-3.2.0-0-unnoficial-oreo-land.img
TWRP-3.2.1-UNOFFICIAL-land.img
3.2.0.1-TWRP-Land-Treble.img
twrp-3.2.1-0-land-UNOFFICIAL.img
TWRP-3.2.2.0_Land-Treble.img
You need this TWRP to flash oreo.
XDA:DevDB Information
TeamWinRecovery, ROM for the Xiaomi Redmi 3S
Contributors
TeamMex
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2017-11-07
Last Updated 2018-08-03
Reserved
TWRP 3.2.0-0 is out now for most currently supported devices.
What's new in 3.2.3-0-Treble:
Updated DRM blobs
TWRP 3.2.3
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
Drop ueventd
fs: symlink platform/soc/${ro.boot.bootdevice} to bootdevice based on Addison implementation (https://github.com/TeamWin/android_...mmit/ea6c6302d06fc210f81932d39b81ef4d7a4b77c3)
What's new in 3.2.1-0-Treble:
Posibility to mount CUST as vendor
You can do a wipe to CUST partition (Called now vendor)
no this not move the partitions names so u can't get brick
What's new in 3.2.1-0:
minui fixes (cryptomilk)
Better android-8.0 compatibility in ROM trees (Dees_Troy)
Fix missing library in android-8.0 (nkk71)
Fix inconsistent SDCard naming (DevUt)
Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
What's new in 3.2.0-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
Reserved
Can i flash over old twrp?
Thanks for not giving up on land
Hey @TeamMex bro can u help me here. I want to know what is the use of this twrp? I flashed your oreo rom with red wolf twrp and that worked. So what is the use of this twrp? Thanks!
Rukijo said:
Can i flash over old twrp?
Click to expand...
Click to collapse
yes.
baba9 said:
Hey @TeamMex bro can u help me here. I want to know what is the use of this twrp? I flashed your oreo rom with red wolf twrp and that worked. So what is the use of this twrp? Thanks!
Click to expand...
Click to collapse
you not need to edit the updater-script anymore with this recovery
bekcicandrej said:
Thanks for not giving up on land
Click to expand...
Click to collapse
Yeah, i think it's better you focus on developing O for our land. ?
nice recovery.
1 feature request i have.
its related but unralated at the same time.
can you add a feature in the updater of your o rom to check for updates for your twrp recovery also?
austinpinto said:
nice recovery.
1 feature request i have.
its related but unralated at the same time.
can you add a feature in the updater of your o rom to check for updates for your twrp recovery also?
Click to expand...
Click to collapse
I will update this until TWRP release a new version xd so no problem not need to update in some time.
Can i restore the rom backups created by the old version of trwp on the new one? Will there be any problem?
yes. you can restore.
no problem.
NaYaB786 said:
Can i restore the rom backups created by the old version of trwp on the new one? Will there be any problem?
Click to expand...
Click to collapse
austinpinto said:
yes. you can restore.
no problem.
Click to expand...
Click to collapse
Thanks for the confirmation
TeamMex said:
try at your own risk
Click to expand...
Click to collapse
Just to confirm that there is NO risk.
Could successfully flash the latest Oreo ROM with this TWRP in temporary mode.
Falcon_fan said:
Just to confirm that there is NO risk.
Could successfully flash the latest Oreo ROM with this TWRP in temporary mode.[/QUOTE
Yes successfully flash the Oreo ROM with this TWRP
Click to expand...
Click to collapse
I tried this recovery, nice but display blinking some times..
You are rocking ?? Good days for land users @TeamMex
+1
So...i flashed it, any way i can confirm that it was successful?
Ayush Neek said:
So...i flashed it, any way i can confirm that it was successful?
Click to expand...
Click to collapse
A minor change I noticed is the external sdcard is now named 'micro sdcard'. In official twrp it was 'microsd'
Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet
Thanks ?
Thank you for the ROM!
There's a Typo in the ROM os version description.
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?
Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first
Download link not working
Edit: UC browser was the culprit
dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer
rom keeps rebooting into twrp , i did every step
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too
Device not charging above 86%. Anyone else facing this bug ?
PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!
lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build
PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.
lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint
Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Quote:
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.
Click to expand...
Click to collapse
NOTE: This version of TWRP is intended to be used with the original unlock for karnak by xyz`.
If you unlocked or updated using amonet-3 it already contains an updated TWRP.
This version will still work, but it lacks support for features such as reboot to hacked BL.
Features:
amonet-aware
SDCard support
USB-OTG support
Backup/Restore support
Downgrade/Overwrite-protection for LK/PL/TZ
Autorestore of broken boot-patch
Also patches amonet-microloader when flashing images
Supports flashing stock-update bins (rename to .zip, no modification necessary )
NOTE: Your device needs to be unlocked.
NOTE: When backing up or restoring stock ROM (or any other ROM that has dm-verity enabled) make sure to select "System Image" instead of "System".
Many thanks to @Kaijones23 for testing!
Download: twrp-karnak-3.3.1-0.zip
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the Amazon Fire HD 8 and HD 10
Contributors
k4y0z, xyz`
Source Code: https://github.com/chaosmaster/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-07-17
Created 2019-07-16
Last Updated 2019-07-17
Changelog
17.07.2019:
Update TWRP to 3.3.1-0
Add support for vendor partition
16.07.2019:
Fix USB-OTG
Reserved #2
Reserved #3
Sent from my Pixel 3a XL using Tapatalk
@k4y0z @Kaijones23 good work guys!!
Great work!
Just flash from existing TWRP to update?
Michajin said:
Great work!
Just flash from existing TWRP to update?
Click to expand...
Click to collapse
Yup
Just uploaded a new build, that also fixes USB-OTG
Works great on my HD8 2018 that I just got today.
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
k4y0z said:
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
Click to expand...
Click to collapse
Wow very nice!
Does karnak has vendor partition??
Rortiz2 said:
Wow very nice!
Does karnak has vendor partition??
Click to expand...
Click to collapse
It has, but not used by stock as far as i can tell.
I added support in TWRP, so it could potentially be used by custom ROMS.
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
jibgilmon said:
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
Click to expand...
Click to collapse
Reflashing Magsik should not have been necessary if it was already installed
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
agr8lemon said:
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
Click to expand...
Click to collapse
You can do it either way, but just flashing the zip in recovery is probably the easiest way. You can reboot recovery while in TWRP to check that it flashed successfully, if you want to.
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
5442 said:
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
Click to expand...
Click to collapse
I just installed YouTube Vanced from Magisk.
nujak said:
I just installed YouTube Vanced from Magisk.
Click to expand...
Click to collapse
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
5442 said:
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
Click to expand...
Click to collapse
Flashing YT VANCED in TWRP will also work.
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
Hello, this is a test build for coral users (will work on crosshatch/blueline later).
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
- allow repacking of TWRP from boot.img
- magisk not working currently on repacked image
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
- fix repacking magisk with TWRP
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_twrp_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
Glad to see this!
Finally TWRPified! Thanks for bringing this to us!
bigbiff said:
[RECOVERY] TWRP 3.4.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me
Click to expand...
Click to collapse
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Daisymae said:
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Click to expand...
Click to collapse
Same here ?
I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:
I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001
Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw
If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Surge1223 said:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Click to expand...
Click to collapse
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
bigbiff said:
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
Click to expand...
Click to collapse
Sure, no problem. logs attached
Surge1223 said:
Sure, no problem. logs attached
Click to expand...
Click to collapse
Thanks, did you try test2?
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
Boggling my mind that it works on my coral with out linking issues.
Can you post the results of getprop please?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
bigbiff said:
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
Click to expand...
Click to collapse
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
Click to expand...
Click to collapse
Wait did you want getprop while in recovery or booted?
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Wait did you want getprop while in recovery or booted?
Click to expand...
Click to collapse
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
bigbiff said:
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
Click to expand...
Click to collapse
heres getprop
https://hastebin.com/eluqagolub.md
heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl
Got some $$ coming your way Monday OP.
Thank you for this. It could not have been easy
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
dhacke said:
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
Click to expand...
Click to collapse
No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.