Related
Hello!
This is development thread of TWRP Recovery v2.8.0.0 by NovaFusion.
Credits:
marcin1147
Macław
Huge thanks to TWRP team.
You can get it from http://novafusion.pl/.
Download is directly provided from our servers - it's fast, stable and fully resumable!
If you appreciate our work, please, use thanks button!
XDA:DevDB Information
TWRP v2.8.0.0, Kernel for the Samsung Galaxy S III Mini
Contributors
New Macław, marcin1147
Kernel Special Features: Only one recovery with full KitKat support!
Version Information
Status: Stable
Current Stable Version: 20140911
Stable Release Date: 2014-09-11
Created 2014-03-11
Last Updated 2014-09-11
Changelog
20140911 (v2.8.0.0)
Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
Add command line capabilities – you can now execute various TWRP features via adb instead of the touchscreen
Add support for color in the console and give error, warning, and highlight lines different colors
Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
Improve handling of /misc thanks to mdmower
Improve setting of time on Qualcomm devices thanks to [NUT]
Allow using images on slidervalue GUI objects thanks to Tassadar
Allow using variables and addition and subtraction in variables for easier theming
Add support for 1440×2560, 280×280, and 320×320 resolutions and update 240×240
Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
Other minor fixes and improvements
What's new in 2.7.1.1 from 20140720?
upstream changes in TWRP
updated kernel
device updates
What new in 2.7.1.0 from 20140612?
full f2fs support for S3 Mini!
What's new in 2.7.1.0?
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don’t have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
What's new in 2.7.0.0?
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Downloads
All releases are available for download from:
http://novafusion.pl
Download is directly provided from our servers - it's fast, stable and fully resumable!
Sources: http://github.com/NovaFusion
Thanks
Sent from my GT-I8190 using Tapatalk
:thumbup::thumbup::thumbup:
Great, Thanks!
Awesome work. Thanks a lot Mac & Marcin, you guys rock:good:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
calvooo said:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
Click to expand...
Click to collapse
Will check right now Of course if it's true, we will fix it as soon as possible.
calvooo said:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
Click to expand...
Click to collapse
New Macław said:
Will check right now Of course if it's true, we will fix it as soon as possible.
Click to expand...
Click to collapse
Just make a backup (stored on the sd card) & works flawless, so...:good:
calvooo said:
Does it work properly? Because some people cant acess to SDcard.. or its just another user fail?
Click to expand...
Click to collapse
TWRP Backup and restore from and to sdcard works. Also apps like helium works with my 32gb sdcard.
Also ok for me. Thanks for fast reply guys!
Ok, i flash recovery and works fine. What about SElinux, is still disabled?
Backup to and restore from extSd is working without any issue for me. Good work!
Btw : I like the Panda in recovery :thumbup:
Silly question maybe...
Why use this one when the official TWRP (now at 2.7.0.1) is available? Is there a subtle difference that means this works when theirs doesn't?
(Edt: having asked the dumb question - I discover that the "official" download appears to be a 10 KB empty tar file! *laughs*)
giociampa said:
Silly question maybe...
Why use this one when the official TWRP (now at 2.7.0.1) is available? Is there a subtle difference that means this works when theirs doesn't?
Click to expand...
Click to collapse
TWRP team doesn't support s3 mini anymore, so, Marcin made his magic, just for us
mauam said:
TWRP team doesn't sipport s3mini anymore, so, Marcin made his magic, just for us
Click to expand...
Click to collapse
So I've just discovered (see edit above)
giociampa said:
Why use this one when the official TWRP (now at 2.7.0.1) is available?
Click to expand...
Click to collapse
Are you sure?
http://teamw.in/project/twrp2
Not even for the N7² it has a newer version.
Hi. i flashed previous version from cwm so i have twrp . for update flash new version with twrp or odin ?
Thanks.
mahdik.m said:
Hi. i flashed previous version from cwm so i have twrp . for update flash new version with twrp or odin ?
Click to expand...
Click to collapse
With TWRP
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11
Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* 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
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.
Yup... just the system partition.
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.
YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !
DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks
sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers
Ok, will test it now without wipes
redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully
This Thread is deprecated!
Please use https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-lineageos-15-1-xperia-z1-compact-t3884247/
We'll provide Lineage 15.1 builds there as well. They come in two different flavours:
pure LineageOS
Security hardened microG LineageOS
Functionality is completely the same as provived by the builds from this thread - they are build from the same sources. Only difference: The new builds are signed to guarantee a maximum of security.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in 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. Hard & a lot.
*
*/
Status
List template by AdrianDC
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: didn't test
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok, but installing updates only works with adb sideload!
- SEPolicies : Enforcing
Download
https://androidfilehost.com/?w=files&flid=269301
latest version: https://www.androidfilehost.com/?fid=11410963190603873784
Click to expand...
Click to collapse
FAQ
What about device encryption?
Device encryption is working. You only have to keep in mind that you need a PC with adb to install systemupdates.
Flashing via recovery isn't working until now, because there isn't a recovery capable of decrypting Oreo /data partitions at the moment. But an easy "adb sideload" should do the job. Or installing from the external SD card.
Click to expand...
Click to collapse
What about reboot to recovery?
Reboot to recovery is only working with magisk installed. Investigating this...
Reboot to recovery is working as it should now (and of course also without magisk).
Click to expand...
Click to collapse
What about GPS?
GPS apps like GPS Status&Toolbox or SatStat don't get location fixes. Nevertheless navigating with Osmand or googleMaps should work. Positionfinding is also slow. Got better
Click to expand...
Click to collapse
I found a bug. What should I do?
We need your feedback for optimization. But your feedback is only useful in connection with logs --> see section Bugreports
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 15.1 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/AICP/kernel_sony_msm8974
Manifest: https://github.com/115ek/manifest
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 15.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/115ek/manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-09-10
Created 2018-09-10
Last Updated 2019-03-18
Changelog
13.12.2018
fixed wrong bluetooth MAC address (00:00:00:00:5a:ad on all devices), now displaying correct device specific one
12.12.2018
synced LineageOS sources (security patch level December 05, 2018)
11.11.2018
fix problem with Lineage SU addon by using 64-bit binder API (thanks @NyQuilXT)
synced LineageOS sources (security patch level November 05, 2018)
14.10.2018
fixed GPS 3D fix
08.10.2018
fixed MHL (thanks @koron393)
added callrecording
synced LineageOS sources (security patch level October 05, 2018)
23.09.2018
fixed reboot to recovery without magisk
minor improvements from AICP devices trees (thanks @SpiritCroc)
synced LineageOS sources
10.09.2018
initial release
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
Encryption : Ok but needs recovery capable of Oreo decryption for installing updates (AFAIK such a recovery doesn't exist until now for our device...)
Click to expand...
Click to collapse
I'm actually having some trouble finding a up-to-date recovery.
Jeroen1000 said:
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
I'm actually having some trouble finding a up-to-date recovery.
Click to expand...
Click to collapse
You can use this https://androidfilehost.com/?fid=5862345805528046823 or that https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450.
For Lineage 15.x flashing you need TWRP>=3.2.x If the version is older you'll end up in a error 7.
Concerning decryption: Google introduced some new encryption stuff and so the decryption of /data from inside TWRP is broken. Some guys are working on it (@nailyk).
Encrypting the device should work fine, but I don't know what happens if you want to update the encrypted device. (I'm going to test that ).
Basically you need to store the update package outside of encrypted partitions... Maybe adb sideload works - but it's circumstantial.
Edit:
That's only interesting if you plan to encrypt your device. Otherways you can relax.
Edit2:
adb sideload should do the job. But you need a PC for updating. Installing an image directly via recovery isn't possible until now.
With sources for both kernel and system unlike the other port! Thanks, I'll definitely be using this!
Xperia J1 Compact
could this work on an Xperia J1 Compact?
it's basically the same phone with the same specs right?
The rom looks very stable and balance, but I've some problems with root procedure. I tried the lineage addon, the root seems active, but opening apps (es. Ad away) results unrooted, any ideas?
Update: Now Works. Flashed lastest Magisk
Amazing to see this old device on Oreo, just installed and it feels smooth and nice. Just a pity that I have broken the sim card connectors inside so I cant use it as a phone but I will fins use of it at home just for fun. Thank you for your work 115ek :good:
Great to see this rom realy! This rom have stock camera?
munjeni said:
Great to see this rom realy! This rom have stock camera?
Click to expand...
Click to collapse
What do you mean with stock camera?
There was a thing with kernel versions 3.4 and 3.10, wasn't it? We're using 3.4.
Concerning the camera: I'm not that expert, but it looks okay I would say.
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
115ek said:
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
Click to expand...
Click to collapse
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
raschad said:
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
Click to expand...
Click to collapse
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
115ek said:
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
Click to expand...
Click to collapse
I meant does this rom have stock camera blobs? Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
munjeni said:
Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
Click to expand...
Click to collapse
Good news: an easy import of your init_board_device.h did the trick. Maybe a timing problem?
Anyway: reboot to recovery is now working correctly, even without magisk
Is that okay for you: http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/73688 ?
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
munjeni said:
I meant does this rom have stock camera blobs?
Click to expand...
Click to collapse
We're using them https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/rhine-common/proprietary/vendor, so I guess yes.
You're more into topic, aren't you? How to distinguish between AOSP and stock blobs? There were some mysteries around DRM, camera quality and so on. I remember a separate thread you also participated in...
But I'm not really into this topic.
munjeni said:
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
Click to expand...
Click to collapse
No, it's actually in here: https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/include/init_sony/init_board_device.h
But It's different from yours. Yours performs another keycheck.
Seems rom have stock blobs. To distinguish between AOSP and stock blobs... depends on kernel you have using, aosp kernel can't be used with stock blobs since aosp camera kernel module is diferent, but I'm out of development for long, have no free time and to be honest I still didn't forgot treatment & injustice for my status on xda, that made me more inactive here. Recognised members have bad treatment here, seems senior members have much more priority than recognised members, and thats reason why everybody here need to care how many hours per day to waste here. I decided to stop wasting my time on xda since xda leaders do not respect anybody's hard work here. I recommend the same to everyone here.
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem ?
ULT][MO said:
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem
Click to expand...
Click to collapse
What recovery are you using? I recommend this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
With mine from here https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450 it still won't work. Maybe a timing thing.
But it's okay if we have at least one working TWRP.
And oreo /data decryption is still an issue we have to address.
This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. 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.
Disclaimer
Code:
/*
* Your warranty is... still valid?
*
* 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 RECOVERY
* 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.
*/
Requirements
ASUS ZenFone Max Pro (M1) ZB601/2KL (of course)
Unlocked bootloader, in either ways (official, unofficial)
Some knowledge on how to deal with your device... and patience.
Flashing InstructionsI assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Up button until ASUS logo with "FASTBOOT MODE" message appears.
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x_9-<kernel>-y-KudProject-X00T.img
Where:
x and y are version of TWRP you're going to flash.
kernel: k4.4 - stock firmware or custom ROMs with FDE encryption; and k4.14 - FBE for custom ROMs with FBE encryption.
IMPORTANT: After flashing, immediately press and hold Power + Volume Down for about 10 seconds button to reboot to recovery.
Swipe the option to allow modifications. This way, you'll trip Android Verified Boot (AVB) and it's required to flash no verity zip in order to be able to boot stock ROM.
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues
k4.4: Due to QTI keymaster's behavior, only specific stock firmware as well as custom ROMs with same platform security patch level that can only be decrypted by TWRP. Applicable versions will be indicated explicitly in the changelog.
k4.14: Recovery may start with very low vibration level. You can adjust vibration intensity in settings later.
k4.14: Recovery can only decrypt userdata partition encrypted using AES-256-XTS algorithm. Only ROMs using Qualcomm's Inline Crypto Engine (ICE) with 4.14 kernel may also be decrypted by the recovery as well. This can be assumed an intended behavior since implementation of fscrypt_ice on msm-4.14 and msm-4.19 kernels are completely different. Tell ROM maintainers wanting to switch to FBE to use AES-256-XTS instead.
Special Thanks
Dees_Troy and everyone behind TWRP
shakalaca - base device tree used for older releases
Ankit Gourav - his work on whyred
Shivam Kumar Jha - person who kickstarted ZenFone Max Pro (M1) development
Everyone involved in testing numbers of test builds.
Sources
TWRP repository fork
Device tree
Kernel source: k4.4 - k4.14
Some stuffs...Another TWRP thread? Why?
I like to keep discussions about my builds separate. Moreover, the existing TWRP that already available on XDA before doesn't seem to be maintained anymore.
I flashed via fastboot but it always fails.
Check or change your cable, use other USB slot (especially 2.0 one if 3.0+ doesn't work), or if needed try to flash recovery with USB connected to a hub.
Changelogstwrp-3.5.2_9-1-KudProject-X00T
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Builds are now splitted for devices running FDE (targetting stock, running 4.4 kernel) and FBE encryption (targetting custom ROMs, running 4.14 kernel, only works with ROMs using AES-256-XTS encryption)
FDE: Can decrypt 16.2017.2009.087 stock firmware and any custom ROM with 5 September 2020 security patch
Restored ability to backup system and vendor partition (images backup for these partitions are recommended)
Switched to build system libraries from source
Added persist partition backup support
Added support for NFC availability check in recovery
Added support for formatting asusfw partition in GUI
Updated set_version script to match up Android 10's system-as-root behavior
FBE: Updated crypto blobs from 17.2017.2012.438 stock firmware
twrp-3.4.0-0-KudProject-X00T
Merged TWRP source changes up to 11 June 2020 (UTC+8)
Can decrypt 16.2017.2005.082 stock firmware and any custom ROM with 5 May 2020 security patch
Switched f2fs-tools to latest AOSP master
Only allow user to backup system and vendor images
set_version script doesn't longer touch persist partition; script now has hardcoded SKU and version instead in case ASUS props can't be found
Updated prebuilt kernel based on S082 source drop
F2FS kernel driver updated to 5.3-rc1 with backports up to 5.7-rc1 from 4.9
Switched to arter97's fork of exFAT
Switched from NTFS kernel driver to FUSE ntfs-3g due to incomplete write support
twrp-3.3.1-0-X00T-20190526
Fixed stock ROM flashing due to missing prop
Fixed FDE decryption
twrp-3.3.1-0-X00T-20190525
Updated F2FS on kernel to 5.2-rc1
TWRP 3.3.1 + upstream changes
twrp-3.3.0-0-X00T-20190513
Updated base to android-9.0
Updated blobs from 16.2017.1903.050
Support for flashing unmodified stock firmware (please read notes!)
Rebased kernel to S050 source drop
Updated F2FS on kernel to 5.1-rc1
TWRP 3.3.0 + upstream changes
twrp-3.2.3-0-X00T-20190217
Now based on whyred official TWRP tree
Reverted kernel to stock-based as-released (S339) with F2FS upstream and sdFAT included
(this should fix USB-OTG support while retaining support with latest f2fs-tools)
TWRP upstream changes
twrp-3.2.3-0-X00T-20190118
Pick more patches from LineageTWRP project
Updated f2fs-tools to latest development branch
Slight cleanup
TWRP upstream changes
twrp-3.2.3-0-X00T-20190115
ADB sideload fixed for everyone
f2fs-tools v1.12.0
Disabled Synaptics' firmware update driver entirely
Removed qcacld-3.0 from kernel
TWRP upstream changes
twrp-3.2.3-0-X00T-20190108
Removed ntfs-3g from recovery
Included several extra recovery keys
Updated kernel to S338-based
Disabled Synaptics' startup firmware update
TWRP upstream changes
twrp-3.2.3-0-X00T-20181231
Updated platform security patch override to 2018-11-01 (matches 338 firmware)
twrp-3.2.3-0-X00T-20181226
Imported more proprietary blobs from stock 337 firmware
TWRP upstream changes
twrp-3.2.3-0-X00T-20181224
Allow wiping vendor partition
2nd CPU target set to Cortex-A73
Initial import of proprietary blobs from stock 337 firmware
Updated kernel to S337-based
TWRP upstream changes
twrp-3.2.3-0-X00T-20181215
Removed texfat and tntfs stock modules
Enabled DT2W
twrp-3.2.3-0-X00T-20181214
Rebased to shakalaca's tree
CPU target set to kryo
Updated platform security patch override to 2018-10-01 (matches 337 firmware)
Switched to my rebased kernel
TWRP upstream changes (android-9.0 branch)
twrp-3.2.3-0-X00TD-20181024
Initial build, based on ASUS-X00TD tree
Notes
"fastboot boot" command isn't supported by our bootloader. Don't ever try that. (blame ASUS/Huaqin)
I'll try to always keep this recovery updated especially when ASUS releases firmware update that also updates AOSP security patch. Security patch set in TWRP needs to match stock firmware used so TWRP can decrypt data partition. This isn't possible with current state as the bump is useless.
Unmodified Stock Firmware SupportWith introduction of unmodified stock firmware support, I need to clear up some confusions you've if any. Notes below are copy-pasta from my post elsewhere:
Code:
Starting this build, recovery supports flashing stock firmware without modifying the updater-script. In order for it to be possible, ro.product.device has to be set to ASUS_X00TD.
This, however, breaks flashing of custom ROMs that check for either X00TD or X00T.
Simply supporting it doesn't mean that you can flash stock firmware directly; you need to be at least on stock when you flash the recovery, so required properties can be exported to /persist which then will be set on every recovery boot up.
Still not sure though, as some ROMs check for ro.product.device and then fallback to ro.build.product for matching devices.
Flashing incremental OTAs are supported but not recommended, since you'll most likely flash verity disabler at the minimum and get the flashing failed upon patching boot.
In plain text:
The recovery has ro.product.device set to ASUS_X00TD that may break custom ROM flashing.
You need to be on stock before booting the recovery for the first time, then afterwards you can flash any stock firmware. 21 June 2020 UPDATE: Now not required, as it's now hardcoded in the script itself and since touching persist is never a good idea to begin with.
If you modify your system in any ways and don't have any system backup to restore, don't flash incremental OTAs. This also includes TWRP tampering system to prevent stock recovery from overwriting TWRP.
Verifying released buildsThis was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:
gpg --import krascgq.gpg
To verify builds on Linux:
Code:
gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.
size is almost half from official recovery ?
I have been using official TWRP 3.2.3.0 since last 2-3 FW updates and haven't faced any problem. However, it's good to have a specific updated TWRP for 601KL.
theraaj said:
size is almost half from official recovery ?
Click to expand...
Click to collapse
And that almost half size comes from unwanted and unused SDM630, SDM636, and SDM660 DTBs concatenated inside kernel image used.
Sent from my ASUS_X00TD using XDA Labs
First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?
Ak-64 said:
First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?
Click to expand...
Click to collapse
1. It's not a Synaptics' exclusive version, and well you can override any installed TWRP versions.
2. Not tested on my side since my data isn't encrypted, but I try to keep the platform patch inline with latest firmware so feel free to test.
Sent from my ASUS_X00TD using XDA Labs
Thank you very much for your amazing work.... hope this TWRP will get the official tag soon??
Can this decrypt encrypted data partition yet?
Thank you for your excellent work, @krasCGQ
@krasCGQ Have you been able to fix the adb sideload function that doesn't work in the older twrp builds? Thanks. Otherwise, this is good as official. Thanks for your hardwork!
I couldn't able to touch anything after booting in to recovery
I need to press power button twice to use it
Any solution
krasCGQ said:
2. Not tested on my side since my data isn't encrypted, but I try to keep the platform patch inline with latest firmware so feel free to test.
Click to expand...
Click to collapse
Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is [email protected] with "-qti" at the end. Than encrypted data will work. I already test it.
vladlp said:
Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is [email protected] with "-qti" at the end. Than encrypted data will work. I already test it.
Click to expand...
Click to collapse
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Sent from my ASUS_X00TD using XDA Labs
krasCGQ said:
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Click to expand...
Click to collapse
Any planning to official sir ?
Sorry if asking.
gusbalaa said:
Any planning to official sir ?
Sorry if asking.
Click to expand...
Click to collapse
Nope.
Sent from my ASUS_X00TD using XDA Labs
sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm
SlamDec said:
sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm
Click to expand...
Click to collapse
The latter if you flash it on the right partition; if not... :silly:
Sent from my ASUS_X00TD using XDA Labs
krasCGQ said:
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Click to expand...
Click to collapse
And... ~24 hours late from expectations, lol.
It's up for public now.
Sent from my ASUS_X00TD using XDA Labs
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.5.1 :
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
DOWNLOADS: twrp-3.6.2_9-0-ginkgo.img
HOW TO FLASH:
Fastboot Method :
fastboot flash recovery twrp-3.5.2_9-1-ginkgo.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.5.2_9-1-ginkgo.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod/Lineage Android
XDAevDB Information
[RECOVERY][OFFICIAL]TWRP-3.5.2 for Xiaomi Redmi Note 8/8T, Kernel for the Android General
Contributors
Erwinabs
mauronofrio
Source Code: https://github.com/TeamWin/android_device_xiaomi_ginkgo
Version Information
Status: Stable
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- F2FS support
- Fastboot boot command support
- Compatibility.zip error fixed
- Willow fully supported
- Android 11 Decryption
- Android 12.1 Decryption
- Android 13 DecryptionDOWNLOAD BUILD :Base A9
twrp-3.6.2_9-0-ginkgo.img64M2022-06-05 20:01:45 UTCtwrp-3.6.1_9-0-ginkgo.img64M2022-03-13 23:24:43 UTCtwrp-3.5.2_9-1-ginkgo.img64M2021-07-04 14:16:19 UTCtwrp-3.5.2_9-0-ginkgo.img64M2021-04-05 05:10:04 UTCtwrp-3.5.1_9-0-ginkgo.img64M2021-03-13 23:04:47 UTCtwrp-3.5.0_9-1-ginkgo.img64M2021-03-06 17:20:59 UTCtwrp-3.5.0_9-0-ginkgo.img64M2020-12-28 17:19:58 UTCtwrp-3.4.0-1-ginkgo.img64M2020-07-22 22:06:01 UTCtwrp-3.4.0-0-ginkgo.img64M2020-06-22 11:27:29 UTCtwrp-3.3.1-1-ginkgo.img64M2020-02-15 00:04:51 UTCtwrp-3.3.1-0-ginkgo.img64M2019-12-05 00:59:27 UTC
Base A10
twrp-3.5.2_10-2-ginkgo.img64M2021-09-26 17:01:39 UTC
Base A11
twrp-3.6.2_11-0-ginkgo.img64M2021-09-26 17:01:39 UTC
Base A12.1
twrp-3.6.2_12-0-ginkgo.img64M2022-07-11 17:01:39 UTC
twrp-3.6.2_12-1-ginkgo.img64M2022-07-2217:01:39 UTC
twrp-3.6.2_12-2-ginkgo.img64M2022-09-21 17:01:39 UTC
Guide Install TWRP - HERE
Does this work with the android 11 decryption? Because my current 3.4x keeps saying "Unable to Decrypt FBE".
22naresn said:
Does this work with the android 11 decryption? Because my current 3.4x keeps saying "Unable to Decrypt FBE".
Click to expand...
Click to collapse
Yes work
Great, I'll try it out!
22naresn said:
Great, I'll try it out!
Click to expand...
Click to collapse
yes, everything is working fine
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
wsdyleon said:
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
Click to expand...
Click to collapse
Thanks
wsdyleon said:
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
Click to expand...
Click to collapse
And hiding it for backup and restore too? I don't think it's a good idea.
x3r0.13urn said:
And hiding it for backup and restore too? I don't think it's a good idea.
Click to expand...
Click to collapse
persist is needed when you lose imei
x3r0.13urn said:
And hiding it for backup and restore too? I don't think it's a good idea.
Click to expand...
Click to collapse
u r →，it's not a good idea for someone。That was the fault that who first “display” the persist partion。
the best solution i thought was that giving one special option to whether display the persist partion
can you guys work on metadata based encryption
to decrypt it.
iamsaalim said:
can you guys work on metadata based encryption
Click to expand...
Click to collapse
Yes bhai
Cool cool
Anyway to force flash this via QFIL?
Every time i connect to internet the phone blocks via mi account.
Do not have the number ou access to the registered mi account anymore.
Anyone knows how to solve this withwout contacting a shaby russian that have the misteryous authorized account?
Erwin Abs said:
DOWNLOAD BUILD :
Official Build :- twrp-3.5.2_9-1-ginkgo.img
Unofficial Build :- recovery_3.5.2_9-Unofficial.img
Click to expand...
Click to collapse
Any clear summary of differences between official and unofficial builds?
pnin said:
Any clear summary of differences between official and unofficial builds?
Click to expand...
Click to collapse
no special difference, just add it
Nixye said:
Anyway to force flash this via QFIL?
Every time i connect to internet the phone blocks via mi account.
Do not have the number ou access to the registered mi account anymore.
Anyone knows how to solve this withwout contacting a shaby russian that have the misteryous authorized account?
Click to expand...
Click to collapse
Dont know , search in youtube
Changelog:
- initial Build A10
twrp-3.5.2_10-0-ginkgo.img