. The full changelog
5G
OnePlus 6T
Win a Mi 9
Honor View20
Honor Hub
Android Q
Galaxy Note 9
LG V40
Snapdragon 855
Pixel 3
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
For most users, installing any kind of after-market software modification, whether it be a custom ROM, custom kernel, or other tool, requires the use of a custom recovery like TWRP. TWRP has been around for years as the go-to recovery solution for the XDA community. It’s open source and supports hundreds of devices. It offers features like full backup and restore, ADB sideloading, and much more. Today, the project has been bumped to version 3.3.1-0, bringing many improvements in decryption, new features, and a major change to the way TWRP is installed.
The full changelog outlining the many improvements in TWRP’s decryption support can be found below, but for users, the most important change will be the new way to install the custom recovery. Currently, installing TWRP on a device with A/B partitions requires booting TWRP temporarily and then installing it permanently using an installer script. Going forward, users will be presented with a new “install recovery ramdisk” option in recovery. This means that users can boot TWRP and then install it without downloading a separate ZIP file. XDA Senior Recognized Developer Dees_Troy worked with XDA Recognized Developer topjohnwu to make this possible by adapting Magisk‘s boot image patching for TWRP. Dees_Troy says the team will offer installer ZIPs this time around to give people a chance to update from older versions, but future TWRP releases won’t have separate installer scripts.
The other change that’s most relevant to users is the inclusion of a “reboot to EDL mode” button. Emergency Download mode can help you fully unbrick a device if you have the right tool, but the button combination to enter it isn’t as well known to users as the reboot to recovery method.
Here’s the full changelog for the update:
TWRP 3.4.0-0 Changelog
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP
Developers behind (Dees_Troy with thanks to topjohnwu of course)
Directory Access
https://eu.dl.twrp.me/woods/
https://eu.dl.twrp.me/woods/twrp-3.4.0-0-woods.img
Fair warning don't restore previous backups from other versions of TWRP make a fresh one first[/SIZE]
:good:
Finally,a dev to keep woods alive
Well done good job sir. We support you. Contribute to moto e4 more.
Does it support the official OTA updates?
nabirosama said:
Does it support the official OTA updates?
Click to expand...
Click to collapse
Yes if your previous version is. From official channel
Abish4 said:
Yes it your previous version is. From official channel
Click to expand...
Click to collapse
On my device it is Software Channel "reteu", should be supported?
The original patch level is on my device october 2018, i think we can not expect updates from the manufacturer any longer.
I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
fastboot boot twrp-3.3.1-0-woods.img
downloading 'boot.img'...
OKAY [ 0.509s]
booting...
OKAY [ 0.068s]
finished. total time: 0.577s
Click to expand...
Click to collapse
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762
I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops
Spielmops said:
I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops
Click to expand...
Click to collapse
The recovery backup would be some kind of a fail save, if twrp will not boot. If the direct boot would work, I had more faith. :fingers-crossed:
How can I backup the recovery over adb?
I found this:
https://android.stackexchange.com/questions/132314/can-we-backup-the-stock-recovery-img-in-any-way
But I still need root and I can not flash magisk without twrp (and system backup).
Update:
However, because it is working by others, i tried flash recovery twrp-3.3.1-0-woods.img (official), it seems to work.
Creating full backup now ...
Have a look here: https://android.stackexchange.com/questions/205354/show-adb-backup-manual
hi, I have the same problem (XT1761), any idea? thank you
maven33 said:
I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762
Click to expand...
Click to collapse
hi, I have the same problem (XT1761), any idea? thank you
Click to expand...
Click to collapse
hi, I have the same advice ...
Spielmops
hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Spielmops said:
hi, I have the same advice ...
Spielmops
Click to expand...
Click to collapse
hitman72 said:
hi, solved (even if I don't know why)...
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
Did you even try to disable verified boot ?
cause thats the almost every time with boot images on newer or updated devices..
The bootloader was unlocked in by activating USB-debugging, EOM-Unlock in the developer settings. In fastboot mode , only "fastboot oem unlock".
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.
dm verity disable
maven33 said:
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.
Click to expand...
Click to collapse
If you are moving from stock rom and locked device u need to unlock with official key or you can just format your device data... DMVERITY must be disabled at all cost or you have to flash entire stock software update to be running.
See or check post relating to disabling verity in FASTBOOT mode (probably zip) also reboot recovery after flashing.
:fingers-crossed:
hitman72 said:
hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
The mega link isn't working. Can you please update the link to the file.
Related
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.1.1-0:
-waiting for official docs, looks like any thread has been updated.. Nor official website
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: doc (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
Download:
3.1.0: Google Drive
3.1.1: Android File Host
XDA:DevDB Information
Unofficial TWRP for the UMI SUPER, Tool/Utility for all devices (see above for details)
Contributors
joe2k01
Source Code: https://github.com/joe2k01/android_device_umi_SUPER/tree/TWRP
Version Information
Status: Testing
Created 2017-03-19
Last Updated 2017-05-14
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Problem with TWRP
gayfagxxx said:
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Click to expand...
Click to collapse
Same problem !
any solutions :crying:
Same problem as the friends above @SerialFlasher33 and @gayfagxxx .
I transfer the TWRP successfully via sp flash tool, pore at the time of loading anything on the screen nothing.
Already tried several versions of TWRP.
Here I have android 7 already with update.
rexbauru said:
Same problem as the friends above @SerialFlasher33 and @gayfagxxx .
I transfer the TWRP successfully via sp flash tool, pore at the time of loading anything on the screen nothing.
Already tried several versions of TWRP.
Here I have android 7 already with update.
Click to expand...
Click to collapse
SerialFlasher33 said:
Same problem !
any solutions :crying:
Click to expand...
Click to collapse
gayfagxxx said:
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Click to expand...
Click to collapse
You must boot in TWRP exactly after flashing it: Flash in SPFT then start pressing volup and then press power
could you also share this new build here?
https://forum.xda-developers.com/general/general/umi-install-custom-recovery-twrp-cwm-t3385733
any scatter file provided to flash it via Flashtool?
thnx
megthebest said:
could you also share this new build here?
https://forum.xda-developers.com/general/general/umi-install-custom-recovery-twrp-cwm-t3385733
any scatter file provided to flash it via Flashtool?
thnx
Click to expand...
Click to collapse
You can use the stock ROM's scatter file
joe2k01 said:
You can use the stock ROM's scatter file
Click to expand...
Click to collapse
I know my friend, it's not for me but for all users that can be in trouble without scatter provided (if they come from stock Umi Super).
So is only a suggestion..
thanks anyway
joe2k01 said:
You must boot in TWRP exactly after flashing it: Flash in SPFT then start pressing volup and then press power
Click to expand...
Click to collapse
Thanks, this worked.
I used the latest march rom on my phone and loaded the scatter from the same rom. I obtained the rom file and the flash tool on the UMi forums.
Then I un-ticked everything and changed the location to the recovery, pressed download, shutdown my phone, waited for it to be done, unplugged it, held volup+power and now it works.
Unfortunately for me it does not work ... I tried to start immediately the phone into recovery but after a short flash the display starts the system stock umi
@bastard81 can you try to connect your phone(powered on) and from adb type adb reboot recovery ?
joe2k01 said:
@bastard81 can you try to connect your phone(powered on) and from adb type adb reboot recovery ?
Click to expand...
Click to collapse
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
bastard81 said:
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
Click to expand...
Click to collapse
I guess you some how corrupted recovery partition, try to backup your IMEIs and then try the option format all+reflash on SPFT. You'll lose IMEI
worked well with me (Y)
Hi joe2k01 from the forum 4PDA. Thanks for the work. Put Your TWRP3.1.0 through TWRP3.0.2 and tested on firmware v7.01_20170123. While there are no errors.
Cant Get into Anything But TWRP
I Flashed Twrp, Twrp works fine, just nothing else. Even flashed a rom and have no boot just twrp.
TIA
joe2k01 said:
Team Win Recovery Project 3.x
Click to expand...
Click to collapse
you ****ing young hacker. you need to make reference to the authors , when you take other people's files...
jemmini said:
you ****ing young hacker. you need to make reference to the authors , when you take other people's files...
Click to expand...
Click to collapse
WTF is wrong with you man? You are in the credits list on GitHub. I took only your kernel since you are anti-opensource and don't want to explain how you built it.
bastard81 said:
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
Click to expand...
Click to collapse
The same for me
Im on stock v3.02_20161121 odex from silent27 had TWRP 3.02 and just flashed TWRP 3.1.1 super img. over and it worked just fine.
On top of that flashed a twrp theme(310x v.2 hdpi light play theme by z31s1g) wich on TWRP 3.02 themes didnt worked for me.
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!
Introduction
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
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse
Frequently Asked Questions (FAQ):
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP installed to the current slot
Magisk Manager
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install "TWRP A/B Retention Script" module by @osm0sis in Magisk Manager
Install Magisk "to Inactive Slot (After OTA)" in Magisk Manager
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites:
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip.
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse
Reserved
Big thanks to @Buffydamion for all his tireless testing and log-providing to get this TWRP in fully working order!!
Hopefully there aren't any bugs besides the upstream ones listed in the OP, but if there are, I'll do my best to figure them out.
Since I don't have the device, I'll have to rely on all of you for logs and feedback.
Enjoy!!
--Cap
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Volski_ said:
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Click to expand...
Click to collapse
@Dees_Troy isn't the only person on the TWRP team.
@bigbiff has been working tirelessly to add Android 10 support to TWRP, with help from @mauronofrio, @androiabledroid, myself and others. TWRP is open-source and a team effort. As you'll notice, there are still some upstream bugs that need to be fixed, which is why the official TWRP hasn't been updated yet. But it's working well enough to release it for devices that need it, and when the official TWRP is ready, these devices will have official support.
Works fine for me. Thanks!
The data partition was already partitioned to f2fs.
Flashed magisk and have a rooted phone now. Perfect!
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Captain_Throwback said:
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Click to expand...
Click to collapse
So I had to remove the above build as it didn't boot. Building a new one now and hopefully it'll work. I'll keep everyone posted.
New release 20200922-14
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Update prebuilt kernel to source built with @aleasto's patch for f2fs
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
luiscaproducer said:
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
Click to expand...
Click to collapse
That is normal for dynamic partitions. The full super partition can be written but not the individual block devices.
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
luiscaproducer said:
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
Click to expand...
Click to collapse
That is unrelated to TWRP being official or not, lol.
TWRP upstream will soon be updated to allow read/write of the system partition, but keep in mind that verity will need to be disabled for you to change any of the content, unless you don't want your device to boot .
--Cap
P.S. If you need to make modifications to system, you should use Magisk - it's made for this exact situation.
Captain_Throwback said:
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Click to expand...
Click to collapse
Works perfect for me. Thank you
Update 20201001-02
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Captain_Throwback said:
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
[email protected] said:
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
Click to expand...
Click to collapse
You don't need #3, as you're flashing TWRP to both slots in #2. That zip is for keeping TWRP after flashing a full firmware zip.
To update with an incremental OTA, you have to have the stock boot and recovery images from the current firmware available to be flashed in TWRP. You have to boot to TWRP and flash both stock boot and recovery, and then you can flash the incremental OTA. Then reboot to bootloader and flash TWRP, then reboot to recovery and flash Magisk for root.
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
[email protected] said:
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
Click to expand...
Click to collapse
Correct.
And then you need to flash the zip that flashes TWRP to the opposite slot so you keep TWRP once you reboot. You'll have to reboot back into TWRP and flash Magisk if you want to keep root.
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too.
As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] 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...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
Download the twrp-installer zip
Flash it with Magisk manager or some other kernel flash utility
Reflash your custom kernel and Magisk.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
Don't reboot
Rename downloaded Magisk.apk to Magisk.zip
Open Magisk app
Select Modules tab
Click "Install from storage"
Select Magisk.zip
2. Option for users with other custom recoveries but without root:
Download the twrp-installer zip
Reboot to recovery
Flash it with "adb sideload twrp-installer*.zip"
Reboot to recovery
Reflash your custom kernel and Magisk.apk if previously installed
3. Option is universal:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Go to Advanced > Flash Current TWRP
Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps.
Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
Reboot to bootloader
Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.
TWRP Updates:
Download and flash the twrp-installer zip
After that reflash your custom kernel and Magisk if previously installed
ROM Updates:
Please follow the official update instructions for your ROM!
If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.
In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!
Instructions that work for me (on LOS based ROMs):
Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
Reboot to system
If Gapps packages keep crashing:
Reboot to TWRP
Flash Gapps again
Reboot to system
For OOS updates should work out of the box, but if you have issues you can follow these steps (I haven't tested them):
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
About backups/restore:
Restore data only WITHOUT pin/pattern set.
If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.
Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to system.
In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
How to use MTP, adb and fastbootD:
Windows:
Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.
To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.
Steps for choosing a specific driver (no the exact wording):
Connect phone in specific mode
Open device manager
Right click on phone either under "Android device" or "USB device", depending on mode
Select "update driver"
Select 2. option "browse my computer"
Select "pick from available drivers"
Pick driver according to above description
Linux:
Intall the fastboot and adb packages for your distribution
Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/nilz3000/android_hardware_oplus
Bugs:
Permanent installation alongside TMO stock isn't possible
Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
In case you notice anything else please let me know.
If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.
Thanks to:
@Nebrassy for the original device tree
@osm0sis for the zip installer
TWRP team
LineageOS
Thank you for this! Will try tomorrow.
Ah man this is dope. Thank you bud!!!
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
vipinpvarghese said:
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
Click to expand...
Click to collapse
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
der_akinator said:
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
Click to expand...
Click to collapse
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
vipinpvarghese said:
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
Click to expand...
Click to collapse
Yes, but it was the same ROM I reinstalled after wipe.
der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
Sorry i forgot about recovery log
EugenStanis said:
Sorry i forgot about recovery log
Click to expand...
Click to collapse
recovery.log
Zippyshare.com - Free File Hosting
www1.zippyshare.com
Anyone tested it with stock OOS13?
der_akinator said:
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] 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...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
Run "fastboot boot boot.img" with the TWRP boot image.
Go to Advanced > Flash Current TWRP.
After that is done, if you were using a custom kernel, reflash it now.
If you were using magisk, reflash it now.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/LineageOS/android_hardware_oplus
Bugs:
Please let me know. I have not encountered anything major yet.
Thanks to:
Nebrassy
TWRP team
LineageOS
Click to expand...
Click to collapse
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Here is a link to the github issue, maybe it helps you solving the problem.
createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project
Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...
github.com
tnchng said:
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Click to expand...
Click to collapse
I use C.63 and have not tested with other firmware versions.
der_akinator said:
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Click to expand...
Click to collapse
Strange, i have never ever in my life used multiuser
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka ADB) and USB drivers should be set beforehand. Latest versions are reliable enough. PixelExperience, PixelOS and MIUI (official and Xiaomi.eu) ROMs have been tested. Before proceeding to flash, make sure about your ROM type (standard or vendor_boot) to avoid not desired consequences. Blew are the most recent versions.
_________________________________________________________________________
TWRP (standard)
Android 12:
twrp-3.7.0_12-v7.7_A12-alioth-skkk.img
Android 13:
twrp-3.7.0_12-v7.8_A13-alioth-skkk.img
[Instructions]
1. Reboot to fastboot mode.
2. Execute command below in ADB on PC:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your downloaded recovery file address.
3. Choose "Flash current TWRP" from TWRP's "Advanced" option.
4. Reboot.
_________________________________________________________________________
OrangeFox (standard)
Android 12+:
[email protected]_3_A12.zip
[Instructions]
1. Reboot to TWRP.
2. Choose "ADB Sideload" from TWRP's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
_________________________________________________________________________
OrangeFox (vendor_boot)
Read this thread for a detailed explanation and list of vendor_boot ROMs.
This is beta release. Treat it as such.
Android 13:
[email protected]_1_vendor_boot_vBaR.zip
[Instructions]
1. Reboot to your ROM's recovery.
2. Choose "ADB Sideload" from recovery's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
fastboot flash vendor_boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your extracted recovery image address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Run "flash-whole-image.bat" file.
4. Reboot
_________________________________________________________________________
Ps: though there are some glitches, both recoveries can install Magisk to root the device.
_________________________________________________________________________
Sourceforge archive page
OrangeFox homepage
Platform Tools download page
Google USB Driver download page
Last time I tried installing lineageos using latest twrp it failed miserably
heybaybee said:
Last time I tried installing lineageos using latest twrp it failed miserably
Click to expand...
Click to collapse
Me too, better use its recovery.
New versions available. Links have been updated.
rashazad said:
New versions available. Links have been updated.
Click to expand...
Click to collapse
Thanks for the thread. Does the latest version support flashing MIUI Global ROMs? Im having a hard time flashing them via TWRP SKK 3.7.0_A12_V6.7_A13.
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
panjgoori said:
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
Click to expand...
Click to collapse
Which ROM are you using?
DarthJabba9 said:
Which ROM are you using?
Click to expand...
Click to collapse
MIUI EU 13.0.9
panjgoori said:
MIUI EU 13.0.9
Click to expand...
Click to collapse
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
I accidently bricked my phone and its in EDL Mode now. Can you help me please
panjgoori said:
I accidently bricked my phone and its in EDL Mode now. Can you help me please
Click to expand...
Click to collapse
Sorry, I know nothing about EDL mode for this device. But I'm sure there are lots of tutorials on XDA or in a general Google search.
Vendor_Boot recovery links and instructions added.
Small changes made in instructions.
New version (7.8) for TWRP A13 (standard).
New version (11.1_1) for OFox (vendor_boot).
New version (11.1_3) for OFox (standard).
DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
néonaloj said:
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
Click to expand...
Click to collapse
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
rashazad said:
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
"recovery.img" being your extracted recovery image address.
4. Reboot.
Click to expand...
Click to collapse
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
nehalchoy said:
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
Click to expand...
Click to collapse
That error does not seem to be related to the process.
Something (probably free apace) is wrong about your pc or phone.
What ROM were you using?
rashazad said:
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
Click to expand...
Click to collapse
Well I didn't want to make a complete tutorial ...
To flash twrp trough twrp, 'install' > change with "image" > install the recovery.img.. It has always worked, for long years..
About flashing a A13 rom (++) coming from MIUI A12 (I each time restarted from scratch, re-installing global MIUI) : I've tried a lot of ways.
I began to install A12 twrp skkk in fastboot mode (1st 'boot' then flash), reboot to recovery, then upgrade to A13 twrp through twrp (reboot to recovery), then A13 FW > bootloop ;
I tried flash A12 twrp (fastboot)(reboot to recovery), then A13 twrp (fastboot too)(reboot to recovery), flash FW > bootloop ;
I also tried A12 twrp (reboot to recovery), then FW (reboot to recovery ok), A13 twrp (reboot to recovery) > bootloop...
I won't list all what i did ! but finally I flashed A13 twrp directly on A12 MIUI (reboot to recovery ok), flash FW (reboot to recovery ok) and that worked. I then flashed my A13 rom (without rebooting system first) > reboot to recovery +reboot system, and finally flashed Gapps, magisk and other stuff. I do know it's not a common way, but the one that worked.
EDIT : I do know it can work (maybe even easier) to flash the MIUI A13 fastboot rom, but had a other device hard bricked some time ago doing this. That's why i tried to only flash the FW
PS : if you can help, I've only one issue to solve yet : I've flashed magisk 26.1, i could have bank & pro apps to work correctly, the only app that I cannot is the FAI tv (error P531 'can't reach my account' (even if i'm well connected), probably root detected.. thanks ! (ofc it's on the deny list, with magisk modules such as Universal Safetynet Fix, zygisk ....)
And edit 2 : I forgot to thank you for this thread !
Common way to flash rom with upgrade (not update) is clean install.
Also, magisk handles safetynet with no problem. No need for that. And zygisk is not module.
For that specific application, check that it is fully selected in zygisk since sometimes all checkboxes for application is not selected.
You're welcome
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
jcp2 said:
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot
jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?
Use PixelFlasher and the latest full update.
AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.
jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk
I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.
@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.
I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .
Android flash tool is by far the easiest way to go for sure. Happy you got it fixed
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".