Develop Bugs

Flashable TWRP v2.8.7.0 for Sony Z3+ E6553 Ivy_Kitakami

Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse

People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.

Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me

This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+

AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.

Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.

On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.

serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version

http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..

deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.

dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!

deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks

dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533

hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?

didnt get a thing... how do i install?

please, release TWRP for 6533 too
we need custom recovery so bad

Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????

Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk

Another TWRP 2.8.7 for Fota Partition with working brightness

TWRP updated to 2.8.7.2 including latest commits. Download at the bottom (see Dec25 file). Selinux permissive is set, so, should work on all roms. Remember, unzip and flash in fastboot.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
I know there is a bunch of different TWRP recoveries for our Z1, including the official one. Well. This one is for Fota. It was compiled in Z1 build environment with all the appropriate flags. And brightness is working fine. Why brightness is important? Because at maximum brightness your phone will overheat to over 65 degrees during flashing. And thanks to previously wrong value, the brightness level in other TWRPs is 15 times the maximum one.
You can flash this one in fastboot like this: fastboot flash recovery recovery.img. Just make sure that your kernel does not have inbuilt TWRP, because 2 identical recoveries will conflict with each other. Unzip first...
For those who would like to know what's new, look here: https://gerrit.omnirom.org/#/q/project:android_bootable_recovery
In this build, I have also reduced default vibration to 28/28/28, but you can set in Settings to whatever you want.

can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !

hawkeyexp said:
can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !
Click to expand...
Click to collapse
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe

ok will try it out if it works with my tree

Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk

Gawis said:
Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
That's right, but I am planning to update Jaguar's kernel. So, when it is done, I will
post it without recovery, so this one can work.
But it really makes no difference...

optimumpro said:
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe
Click to expand...
Click to collapse
Is working fine - thx !

Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk

swa100 said:
Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try, but there is a separate branch for TWRP for M. And anyway, M is not usable yet and won't be for a long time...

Thanks for this one!
I do however seem to experience an issue when trying another ROM like CM.
With your ROM I can reboot into this recovery but with CM I get a black screen. When using another older TWRP recovery I used when rooting both ROMS boot fine into recovery.
Sent from my Z1 using Tapatalk

@optimumpro is there any chance to make a flashable zip with it? Thanks

matcho13579 said:
@optimumpro is there any chance to make a flashable zip with it? Thanks
Click to expand...
Click to collapse
Use Rashr app to install this...

Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<

Snowblond said:
Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<
Click to expand...
Click to collapse
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.

optimumpro said:
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.
Click to expand...
Click to collapse
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
I don't know why it is not working for you. If you post your boot.img, I can put recovery in it..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.

drakonizer said:
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.
Click to expand...
Click to collapse
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-

Snowblond said:
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-
Click to expand...
Click to collapse
Did you try with another kernel? If it worked then, you can trace the problem to the kernel itself, and not the device or your flashing methodology.

Recovery updated to 2.8.7.2. See OP for download...

[Unofficial] [Updated 021217] TWRP 3.2.0-0 Mi Note 2 Themes & Aroma Guide

Unofficial TWRP 3.2.0-0 Mi Note 2 (scorpio)
Unofficial TWRP build for the Mi Note 2.
TWRP 3.1.1-0 Changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Compatible with TWRP Backup and Recuse Tool for PC
Download Link
twrp-3.2.0-0-scorpio.img
Update 14/07/17
Update TWRP to 3.2.0.0
Update 14/07/17
Update TWRP to 3.1.1-0
New streamlined kernel
Add F2FS support
Improved Android 7.0 Miui compatibility - If issues persist please let me know
Update 30/05/17
All features working as expected
Screenbrightness adjustment is now responding accurately with a suitable default brightness
Updated kernel.
Much quicker booting.
Installation Guide
Once you've got you're bootloader unlocked with MiFlash and run through all the Xiaomi hoops to unlock your bootloader and have a fastboot installed on your PC:
Simply place the download where you like and then open a command prompt and type
fastboot flash recovery /path/to/twrp-3.1.1-0-scorpio.img
BONUS THEMES & File Manager
Plus as a special treat I'm including a full guide below to use Materialised Theme and Aroma File Manager both working within TWRP 3.1.1-0
Themes available from here
1. Install the latest TWRP linked above.
2. Download one of the themes above (see screenshots below for recommendations)
3. Download Aroma File Manager for TWRP from here
4. Once booted into TWRP select Install and choose the theme.zip you've downloaded.
5. You will instantly see the theme applied
6. Click Install again and this time select "materialised_aromafm_200-b7.zip"
7. Once that zip has completed installing open the Materialised Options (the art palette icon on the top right)
8. Tick the box that says "Use Aroma File Manager"
9. Press back and select "File Manager" from the list.
10. Swipe to start Aroma File Manager
11. Enjoy!!
See attached thumbnails for themes in action.
Source:
https://github.com/stonetrapping/twrp_android_device_scorpio
Special thanks to:
z31s1g for the wonderful themes and the Aroma File Manager

Thanks, dude !

Working OK for both MIUI and AOSP based ROMs?

Working with ASAP and MIUI and encryption all round.

That's great! Thanks for sharing

After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?

stephendt0 said:
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
Click to expand...
Click to collapse
You can keep dm-verity. After flashing I'd suggest leaving fastboot and booting straight into recovery via fingerpress.
Flashing SuperSU or Magisk or similar should ensure survival of TWRP if it's being overwritten.

Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?

Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
1. I've noticed the slow speed too, I'm 100% sure why it's happening but I have some ideas.
2. The same ideas will hopefully address this issue.
It was a quick and dirty port since there was no native TWRP, I haven't had the time yet to improve it but I'll build an updated release based on 8.2.5.0 sometime soon and look to making it official.

Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.

Thanks, StoneTrapper !!
I will check later after flashing new version !
StoneTrapper said:
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Click to expand...
Click to collapse

Really fast at boot, maybe because is a release from the future (30052017 )
great job, thanks man!

Can not use usb otg function ...
Can not use usb otg function ...
Otg function, no work

[email protected] said:
Can not use usb otg function ...
Otg function, no work
Click to expand...
Click to collapse
I've had no issues with USB-OTB, with any standard formatted flash drive (FAT32, NTFS, EXT4).
This is also the first I've heard of anyone having such an issue.
Does the OTG drive mount successfully in whatever ROM you're using? Is it attached prior to booting to TWRP? Can you provide additional information.
TWRP doesn't like remounting the same USB multiple times - i.e if you unplug the USB while in TWRP, and then reattach the same drive it won't remount it.

Sorry to feedback lately because I was too busy in past 2-week.
Well, new TWRP is working well.
The only one problem: If I want to upgrade firmware, TWRP will be replaced by MIUI stock recovery after flashing new version of MIUI ROM.
It's pretty annoying because I need to get into fastboot mode then flash TWRP. After that, entering TWRP and flash lineage OS ...
Is it possible to be fixed in next coming version ?
Kris

May I know how to flash the TWRP rom?

I'm on MIUI.eu ROM, can I flash full global MIUI original ROM with TWRP without bricking the phone ??
Before on Redmi note 3 u can't flash original ROM without bricking the phone, u needed special TWRP (zxc version) or modify the ROM
Can you explain me ?
Envoyé de mon Mi Note 2 en utilisant Tapatalk

Link down.

chemha said:
Link down.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.

StoneTrapper said:
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
Click to expand...
Click to collapse
It does not work. No download link found

[Recovery] TWRP for maple

I want to share you a great twrp who support aroma installer.
Link:https://mega.nz/#!6MQxWIKa!ZuSMnC7DtXxh4R9Vb5hHMjRFFVk6kaCaHiodn5CSN3M

Blackghosthm said:
I want to share you a great twrp who support aroma installer.
Created by @Myself5.
Link:https://mega.nz/#!6MQxWIKa
Click to expand...
Click to collapse
You need a decryption key.
---------- Post added at 05:10 PM ---------- Previous post was at 04:27 PM ----------
Blackghosthm said:
I want to share you a great twrp who support aroma installer.
Created by @Myself5.
Link:https://mega.nz/#!6MQxWIKa!ZuSMnC7DtXxh4R9Vb5hHMjRFFVk6kaCaHiodn5CSN3M
Click to expand...
Click to collapse
What version of twrp is this?

Beetle84 said:
You need a decryption key.
---------- Post added at 05:10 PM ---------- Previous post was at 04:27 PM ----------
What version of twrp is this?
Click to expand...
Click to collapse
3.2.1 but not that version you can find in twrp.me

Blackghosthm said:
3.2.1 but not that version you can find in twrp.me
Click to expand...
Click to collapse
So how about you push your AROMA fix to the official TWRP trees that everyone can profit from it?
Also that image is certainly not created by me. It might be based on the official TWRP, but the way you put it is missleading IMO.

Myself5 said:
So how about you push your AROMA fix to the official TWRP trees that everyone can profit from it?
Also that image is certainly not created by me. It might be based on the official TWRP, but the way you put it is missleading IMO.
Click to expand...
Click to collapse
Ok, I removed your name.

Myself5 said:
So how about you push your AROMA fix to the official TWRP trees that everyone can profit from it?
Also that image is certainly not created by me. It might be based on the official TWRP, but the way you put it is missleading IMO.
Click to expand...
Click to collapse
More than likely from a Chinese site, possibly modified by @machao44

Beetle84 said:
More than likely from a Chinese site, possibly modified by @machao44
Click to expand...
Click to collapse
Yes,now I have the same idea but doesn't matter I didn't write it created by me,I don't think it have matter for developer because he didn't share the recovery in xda.

I still wouldn't mind if _whoever did it_ would push the fix to the TWRP repository.

Myself5 said:
I still wouldn't mind if _whoever did it_ would push the fix to the TWRP repository.
Click to expand...
Click to collapse
Will this affect all Xperias with 4.4 Kernel? Really happy that @Blackghosthm shared that with Me... Can't wait to push out some awesome AROMA Stuff again!
Thanks a lot to everyone who was involved! :angel:

Myself5 said:
I still wouldn't mind if _whoever did it_ would push the fix to the TWRP repository.
Click to expand...
Click to collapse
I believe it created by storm in xperi fix there are 2 twrp versions one of them is this twrp.
Also i heard in some post it created by storm.

heil Aroma!

@sToRm//
Can you shed any light on who made this?

Anyone tried the new official One? https://dl.twrp.me/maple/twrp-3.2.3-0-maple.img.html

Hi I am quite having a hard time figuring out how to install TWRP on my XZP dual global version.
I already flashed the latest firmware last August... I also tried to follow installing it through ADB using command prompt yet nothing did work... Is there someone out here who can help me with flashing TWRP... Thanks

I use in this moment the original 3.2.3-0 version.
Where's is the problem to install TWRP? enable adb, call adb during running phone and accept the PC all time.
If the bootloader unlocked,, boot in Fastmode (hold Volume up during connecting the USB cable with the PC) . Check the driver via fastboot devices, If you see the phone call fastboot flash revovery TWRP. img (if your TWRP version has the name "TWRP. img"). After that you can boot into TWRP

Excappare said:
Hi I am quite having a hard time figuring out how to install TWRP on my XZP dual global version.
I already flashed the latest firmware last August... I also tried to follow installing it through ADB using command prompt yet nothing did work... Is there someone out here who can help me with flashing TWRP... Thanks
Click to expand...
Click to collapse
You need to flash a kernel from a custom ROM first (like CarbonROM) in order to be able to boot from the recovery (FOTAKERNEL) partition. The stock kernels have recovery built-in and would use that instead of TWRP. You can get a CarbonROM kernel image (boot.img) from its flashable zip.
After flashing a custom kernel you can then flash the TWRP image via "fastboot flash recovery <recovery image>". You'll have to reboot the phone and follow the usual button combination (though I don't really know it's holding volume up or down) to access the recovery. Using "fastboot boot" will not work and it'll stuck on the Sony logo with the blue fastboot LED stay on.

I think twrp found from this thread,,you can check TWRP Folder,
,https://forum.xda-developers.com/showpost.php?p=78121448&postcount=4

I've also the Stock Kernel (Pie) on the phone and can reach TWRP without any problems : you must hold Power and Volume (up or down? Not sure in this moment) till you see TWRP on the Screen (around 6 Sec.) Maybe the screen switched off... Switch it on via short press via Power... That's all

[FIRMWARE] Flashable firmware / modem / baseband / RIL [OnePlus Nord] [avicii]

Flashable firmware / modem / baseband / RIL only (no full ROM).
Basically, it's a set of firmware/modem/baseband/RIL extracted from the OxygenOS Full ROM update payload and packed into a custom recovery flashable ZIP. Useful for users of a custom ROM, since the firmware/modem/baseband/RIL is never updated on most custom ROMs and thus becomes outdated. Those who use OxygenOS don't need this, since the firmware/modem/baseband/RIL is also updated with OTAs.
Important
If you have a OnePlus Nord (avicii) AC01AA, AC01BA or AC01DA and a custom ROM installed, feel free to proceed. However, I recommend making a backup before and get the unbrick tool from here, just in case.
Flash it with any (custom) recovery. It's not necessary to delete, wipe or format anything before or after installation.
Note: Packages are not signed.
Check the baseband version with: Settings → About phone → Android version → Baseband version
For OnePlus Nord - avicii - Android 12 based ROMs:
VersionModelDownload link11 F.20 AC01AAGlobalOnePlus_Nord_11-F-20-AC01AA_global_firmware.zip11 F.20 AC01BAEuropeOnePlus_Nord_11-F-20-AC01BA_europe_firmware.zip11 F.20 AC01DAIndiaOnePlus_Nord_11-F-20-AC01DA_india_firmware.zip
Baseband version after update: Q_V1_P14 or: MPSS.HI.2.5-01081-SAIPAN_GEN_PACK-1.7761.62_VENDOR
For OnePlus Nord - avicii - Android 10 and 11 based ROMs:
VersionModelDownload link11.1.10.10 AC01AAGlobalOnePlus_Nord_11-1-10-10-AC01AA_global_firmware.zip11.1.11.11 AC01BAEuropeOnePlus_Nord_11-1-11-11-AC01BA_europe_firmware.zip11.1.10.10 AC01DAIndiaOnePlus_Nord_11-1-10-10-AC01DA_india_firmware.zip
Baseband version after update: MPSS.HI.2.0.c9-00023-SAIPAN_GEN_PACK-1.422164.2.446371.2
Last Updated: 2023-06-04

Reserved 1

Reserved 2

Reserved 3

Great work! Thanks for the contribution.

can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance

Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".

hermesjconrad said:
Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".
Click to expand...
Click to collapse
I have included a safeguard so that these files cannot be accidentally installed on a device other than the Nord. But for some reason the LOS developers decided to name the device differently in LOS 17 recovery. In LOS 18 (or alternatively Orange Fox) recovery everything should work fine.
So I have removed this protection for now until an official LOS 18 or 19 is released. Download the appropriate package again and try to flash it again, it should now be able to be flashed with adb sideload.

Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?

vikd007 said:
can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance
Click to expand...
Click to collapse
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.

hermesjconrad said:
Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?
Click to expand...
Click to collapse
LOS recovery is totally OK if you only want to perform updates. But if you want to make backups and restore or want to get to the data partition, then it is no longer sufficient. Unfortunately there is still no official TWRP, so I use Orange Fox and it works great with the unofficial LOS 18, but you have to look in the Orange Fox thread there is a link to a newer version than the one in the opening post (see post 81 on page 5).

sniperle said:
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.
Click to expand...
Click to collapse
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work

vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".

Doc Sniper said:
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".
Click to expand...
Click to collapse
problem was there is no recovery for oos beta 12 as of now and no latest boot image

Managed to bork my phone by trying to upgrade magisk, managed to unbork by changing boot slots with fastboot, really neat.
Wanted to say thank you for providing the latest update file. Didn't need it in particular, but cool to have it and know it is available!

vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
I faced the same issue.. want to move on to a custom ROM but have 2 questions:
1. Does the phone loose Widevine L1 upon bootloader unlock on OOS12? I know i have to stop the phone from booting up after bootloader unlock and directly install the custom ROM, but i got stuck due to the recovery problem.
2. Does the custom ROM work good after this?

Hi,
Thank you for your work.
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
I have Magisk installed if it means anything in this case.

blorkraider said:
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
Click to expand...
Click to collapse
The ZIP files are not signed hence the message. But as far as I know, LOS-Recovery can also flash unsigned ZIPs. When the message appears, you can switch to yes with the volume buttons and then confirm with the power button. Then the ZIP should be installed.

Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.

mythos_ said:
Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.
Click to expand...
Click to collapse
According to the official Oneplus site, version 11 is still the current release version. Can you send me a download link to the release version of OOS 12? Thanks.