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

TWRP RECOVERY in to FOTA PARTITION GUIDE (XPERIA S)

Flash TWRP to FOTA Partition(SONY XPERIA S).(Terminal Command Method)I will not responsible if you do something wrong to yor device
You can flash TWRP into fota partition if your kernel supports to flash it.(Ask the developer if support is available or not,To know more about Fota Partition Read here.).if yes then follow procedure.
1. You must have to root your ROM first.
2. Download TWRP.img (is the recovery file) from TWRP website.Place the downloaded twrp.img in sdcard. (Don’t place it under any folder.just copy to sdcard.if the downloaded file name is something else then rename it to twrp.img).
3. Now goto playstore and install terminal emulator app to your phone.
4. Now open terminal emulator app and type
su (and press enter key.it will ask for root permission.GRANT it) then type
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
(and press enter keyr.be careful while you writing the above commands.)
Finished.Now you have successfully flashed twrp recovery into fotapartition.Reboot your phone and when you see pink led just tap Volume UP key to enter to recovery.
Rom Flash Procedure
METHOD 2:
First extract boot.img and recovery.img from rom.zip and copy both to SD card root folder
1. Flash twrp recovery image like you flash kernel/boot.img(by flash tool or by fastboot method).
2. Enter to recovery.
Then follow the image by the numbers written in the image.Swipe to flash.
Then do the same for boot.img but choose boot. Img from SD card and boot(partition) in image 4. Swipe to flash and done.

Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !

C0D3FR34K said:
Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !
Click to expand...
Click to collapse
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.

nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t

C0D3FR34K said:
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t
Click to expand...
Click to collapse
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.

Mirhawk said:
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.
Click to expand...
Click to collapse
Thanks ! I have installed TWRP latest build using fastboot !

nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
/sdcard #
Click to expand...
Click to collapse
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058

C0D3FR34K said:
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
Click to expand...
Click to collapse
I saw now that you have solved your problem. And this time also @mirhl is present there to help..good guy mirhl.

Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?

Torroan said:
Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?
Click to expand...
Click to collapse
Here is a link which will give you mickybart's recovery and kernel of nAOSO b26.but before flashing this first copy the rom to your phone because u can't boot the device after flashing it.so flash this and reboot to recovery and flash the rom you want.
Link.
https://mega.nz/#!SZ9DXZgZ!tzugmlsOMum3cZYXyTh69lDDlhGfGjV-Fw2VKvaYdK8

Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?

Torroan said:
Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?
Click to expand...
Click to collapse
Take backup of the current rom before flashing the other file.then do as I said

TWRP... thanks!

Thanks
Thanks for the guide really appreciate !!

BTW - only mine recovery dont show temperature? my soft is oneofakind and newest twrp recovery in FOTA via dd command.

I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.

guruAhtasham said:
I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.
Click to expand...
Click to collapse
Flash ucyan b04 kernel only on fastboot and try to reboot...

nageswarswain said:
Flash ucyan b04 kernel only on fastboot and try to reboot...
Click to expand...
Click to collapse
Thanks for the reply but it didn't work
have to do a clean flash again to make it boot.

[Unofficial] enhanced TWRP

Important: official TWRP does NOT backup the EFS partition correctly while this one does. Do NOT restore an EFS backup that you did not take on the same build of TWRP as the one you're currently using. You will lose IMEI
Get support here: https://discord.gg/UF9qnts
Same as official twrp but
Built with latest lineageOS trees
Built with latest kernel with ext4, f2fs, exfat and sdfat driver
Thanks a lot to @jcadduono for the exfat upstream
Undervolting
Supports signature verification for lineageOS official zips
Supports signature verification for haruhirom official zips
Built with GCC 8 for maximum speed
Support for backing up, restoring and flashing system image zips
Manifest: https://github.com/GlassROM-devices/platform_manifest_twrp_lineageos
Toolchain: https://bitbucket.org/anupritaisno1/aarch64-linux-gnu/overview
FPSUsername said:
You can flash a recovery using fastboot (
Code:
fastboot flash recovery recovery.img
).
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
anupritaisno1 said:
Also guys twrp can be flashed on locked bootloaders
If you are on a locked bootloader you must make sure that you ALWAYS flash twrp while booted into Android, using the dd command
Code:
dd if=recovery.img of=/dev/block/bootdevice/by-name/recovery
If you use the twrp flasher while on a locked bootloader you're just dumb
Click to expand...
Click to collapse

https://glassrom.pw/recovery.img

All sources (kernel source, device tree, etc) are bundled in the manifest. Please don't ask for separate sources just read the manifests

Just an FYI: official twrp builds are built by a bot, oneplus 2 doesn't have a twrp maintainer and nobody is reviewing the code that goes into twrp for our device
You really shouldn't use the official twrp builds

no comments, that means no issues. good job

Twrp 3.2.0 was released today so a new build for that is out
Please test and report bugs

Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Sent from my OnePlus2 using XDA Labs

sanjeetkumar495 said:
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Click to expand...
Click to collapse
I did, it works.

sanjeetkumar495 said:
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot:
Code:
fastboot flash recovery recovery.img
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.

FPSUsername said:
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot (
Code:
fastboot flash recovery recovery.img
).
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
Adding these to the main post

Also guys twrp can be flashed on locked bootloaders
If you are on a locked bootloader you must make sure that you ALWAYS flash twrp while booted into Android, using the dd command
Code:
dd if=recovery.img of=/dev/block/bootdevice/by-name/recovery
If you use the twrp flasher while on a locked bootloader you're just dumb

FPSUsername said:
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot:
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs

sanjeetkumar495 said:
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Then use the locked bootloader method

sanjeetkumar495 said:
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Use Flashify.

Deleted

Sad to say but this twrp doesnt come close to the latest official. I experienced lag and slow rates.

Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.

sujju said:
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
Click to expand...
Click to collapse
If your phone is rooted, you might want to give flashfire or flashify a try.

erzherzog said:
If your phone is rooted, you might want to give flashfire or flashify a try.
Click to expand...
Click to collapse
It's not rooted..

sujju said:
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
Click to expand...
Click to collapse
You must patch the rom to provide SuperSU's binaries at boot with oxygenos recovery and a signed boot.img
After booting you have to flash twrp using dd
Instructions for doing so are in the haruhirom thread
This definitely isn't for beginners

Reboot to recovery: "the system has been destroyed"

Hi
I followed this guide to root my son's phone
(the bootloader was already unlocked or so I tought - see below)
Now when I tried to reboot to twrp to root the phone, following these instructions in the guide:
“How To Root Mi A2 / A2 Lite Using Magisk
…
Now, boot your Xiaomi device into the TWRP Recovery Mode by pressing and holding the Volume Up and Power buttons simultaneously for a couple of seconds until the device starts booting.
…”
Click to expand...
Click to collapse
it does not boot to TWRP but instead displays a red error triangle with the message“The system has been destroyed”; I get exactly the same message after using the adb command
Code:
adb reboot recovery
as an alternative reboot-to-recovery method.
Reboot to system is perfectly fine!
Help anyone? Could it be the bootloader was not properly unlocked... I dit it when I received the phone and wa spretty sure it was unlocked then
Thanks

BenG7 said:
Hi
I followed this guide to root my son's phone
(the bootloader was already unlocked or so I tought - see below)
Now when I tried to reboot to twrp to root the phone, following these instructions in the guide:
it does not boot to TWRP but instead displays a red error triangle with the message“The system has been destroyed”; I get exactly the same message after using the adb command
as an alternative reboot-to-recovery method.
Reboot to system is perfectly fine!
Help anyone? Could it be the bootloader was not properly unlocked... I dit it when I received the phone and wa spretty sure it was unlocked then
Thanks
Click to expand...
Click to collapse
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.

nikoman1987 said:
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.
Click to expand...
Click to collapse
@nikoman1987: Thanks, so I suppose i should go thru the guide again, from the start, right? what is the difference between the offain and dees_troy twrps please?

BenG7 said:
@nikoman1987: Thanks, so I suppose i should go thru the guide again, from the start, right? what is the difference between the offain and dees_troy twrps please?
Click to expand...
Click to collapse
different developers ,i don't have any problems with the offain version.Some of the roms have priblems with dess-troy

nikoman1987 said:
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.
Click to expand...
Click to collapse
exactly the same deal with:
twrp-daisy-3.3.0-0-offain
twrp-3.3.0-dees_troy-daisy
--> red error triangle with the message“The system has been destroyed”...

You need 3.3.1, not 3.3.0
dl.twrp.me/daisy
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
You don't need to redo everything unless you failed to backup your boot image...

a1291762 said:
You need 3.3.1, not 3.3.0
dl.twrp.me/daisy
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
You don't need to redo everything unless you failed to backup your boot image...
Click to expand...
Click to collapse
Hi again @a1291762
I already downloaded and flashed the official daisy twrp but that didn't do it, 3.3.0 it was.
On the official twrp.me website there is only Dees_troy version (true I didn't try 3.3.1 - will do so tonight) - no offain version.
Just wondering, I think I saw some command in some posts to allow flashing on the Mi A2 lite - would that be required here (although not stated in the guide I referenced)?
[EDIT] found this:
I am seeing the ‘System has been destroyed’ message after installing TWRP on Mi A2 Lite (daisy)?
Then download the ‘aboot.img’ from V9.6.4.0 (Download Link), boot your Mi A2 to Fastboot Mode and flash it using the following command:
Code:
fastboot flash aboot_a aboot_9.6.4.img
fastboot flash aboot_b aboot_9.6.4.img
According to the explanation given by XDA Senior Member mac12m99, the newer bootloader (aboot.img) version checks for stock recovery, even when the bootloader is unlocked. To overcome this, you can flash an older bootloader version (Especifically from V9.6.4.0) to fix this issue.
Click to expand...
Click to collapse

BenG7 said:
Hi again @a1291762
I already downloaded and flashed the official daisy twrp but that didn't do it, 3.3.0 it was.
On the official twrp.me website there is only Dees_troy version (true I didn't try 3.3.1 - will do so tonight) - no offain version.
Just wondering, I think I saw some command in some posts to allow flashing on the Mi A2 lite - would that be required here (although not stated in the guide I referenced)?
Click to expand...
Click to collapse
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.

a1291762 said:
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.
Click to expand...
Click to collapse
My build is 10.0.13.0

BenG7 said:
My build is 10.0.13.0
Click to expand...
Click to collapse
Then use 3.3.3-1 dees_troy or :
https://drive.google.com/file/d/1-Enw0Kn2CAYyfN1Krv8t3CVNLyn0p0JX/view?usp=drivesdk
Here is the link for twrp 3.3.3-1 offain version ,but it is in .img format.Dont install it via fastboot or TWRP .You can boot it via this command:
fasboot boot twrp-daisy-3.3.1-0-offain.img ,install everything you want,and you'll be ok ,if you don't need permanent twrp recovery!
If you want permanent installation - I am using Android All in One tool from another XDA thread and that's what i do:
Reboot in Fastboot mode,then connect the device to PC open the all-in-one tool on your windows computer ,then click on the "Recovery Flasher and Device Rooter" button(after you see that the device is recognised in the program) ,you need to choose which version- set it to MANUAL. From there navigate to the recovery files(dees_troy and offain) in the first row navigate to the recovery image (offain) ,on the second row navigate to the recovery zip (dees_troy).Then hit the Flash button. The phone will boot in 3.3.3-1 offain twrp ,and automatically will install the dees_troy version and when everything is installed,the phone will reboot after the flash again in recovery.All the time i have 100% success with this all in one tool. When you are ready with the installation of twrp ,flash magisk and reboot to system.
Here is the thread for the tool:
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/
I guarantee it works every time with 100% chance for success

nikoman1987 said:
Then use 3.3.3-1 dees_troy or :
https://drive.google.com/file/d/1-Enw0Kn2CAYyfN1Krv8t3CVNLyn0p0JX/view?usp=drivesdk
Here is the link for twrp 3.3.3-1 offain version ,but it is in .img format.Dont install it via fastboot or TWRP .You can boot it via this command:
fasboot boot twrp-daisy-3.3.1-0-offain.img ,install everything you want,and you'll be ok ,if you don't need permanent twrp recovery!
...
Here is the thread for the tool:
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/
I guarantee it works every time with 100% chance for success
Click to expand...
Click to collapse
Thanks @a1291762 & @nikoman1987 but the tool won't do it for me at home
I do not think I need permanent TWRP (although I know how nice it is to know you can always fall back to twrp - I will have to use a PC instead); my intention is to flash https://forum.xda-developers.com/mi-a2-lite/development/lineageos-16-0-xiaomi-mi-a2-lite-t3919060LineageOS with temporary twrp 3.3.3-1 offain version

BenG7 said:
Thanks @a1291762 & @nikoman1987 but the tool won't do it for me at home
I do not think I need permanent TWRP (although I know how nice it is to know you can always fall back to twrp - I will have to use a PC instead); my intention is to flash LineageOS with temporary twrp 3.3.3-1 offain version
Click to expand...
Click to collapse
Your choice , but I always prefer to have permanent twrp with custom ROMs . You know what's best for you.

a1291762 said:
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.
Click to expand...
Click to collapse
@a1291762
I got this message after formatting the data and wiping system, trying to install LO:
Code:
"Device unable to boot. Error - mdtp image is corrupted"
I am now stuck on fastboot!
From the post https://forum.xda-developers.com/nov...7#post80993947
I understand I have to flash BOOT/RECOVERY/SYSTEM imgs to restore your device;
the commands are
Boot:
Code:
fastboot flash boot boot.img
Recovery:
Code:
fastboot flash recovery recovery.img
System:
Code:
fastboot flash system system.img
but the question is where can I get the
boot.img
recovery.img
system.img
for the xiaomi Mi A2 Lite (daisy); bearing in mind the phone is on a 2 partition system?
Thanks a lot in advance

BenG7 said:
@a1291762
I got this message after formatting the data and wiping system, trying to install LO:
Code:
"Device unable to boot. Error - mdtp image is corrupted"
I am now stuck on fastboot!
From the post https://forum.xda-developers.com/nov...7#post80993947
I understand I have to flash BOOT/RECOVERY/SYSTEM imgs to restore your device;
Click to expand...
Click to collapse
There is no recovery image because this is an A/B partitioned phone.
The mdtp issue seems to be a real issue for some people.
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
The advice I gave there is all I can give here. Try to fastboot/MiFlash a stock ROM.
If you don't have a stock image, they're listed here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Note that the newest image is 10.0.13.0 (14, 15, 16 did not get full releases, just OTAs).
These threads suggest it's possible to flash a stock ROM to fix a corrupt mdtp partition...
https://forum.xda-developers.com/mi-a2-lite/help/fastboot-loop-t3996081
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-stuck-fastboot-recovery-help-t3938175

a1291762 said:
There is no recovery image because this is an A/B partitioned phone.
The mdtp issue seems to be a real issue for some people.
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
The advice I gave there is all I can give here. Try to fastboot/MiFlash a stock ROM.
If you don't have a stock image, they're listed here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Note that the newest image is 10.0.13.0 (14, 15, 16 did not get full releases, just OTAs).
These threads suggest it's possible to flash a stock ROM to fix a corrupt mdtp partition...
https://forum.xda-developers.com/mi-a2-lite/help/fastboot-loop-t3996081
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-stuck-fastboot-recovery-help-t3938175
Click to expand...
Click to collapse
Thanks @a1291762.
I
Code:
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
as instructed by @SubwayChamp in the link you posted
but the phone boots straight back to fastboot after
Code:
fastboot reboot
so I believe I need to flash a stock rom
I'm on Debian; I am wondering wether I can use
Can XiaoMiTool V2 unbrick my device?
to unbrick my phone or just
fastboot flash the daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Code:
fastboot -w
fastboot update </path/to/your/Rom.zip>
and it will work with a .tgz format or do I need to extract it and then zip it?
Thanks for your help

BenG7 said:
Thanks @a1291762.
I
Code:
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
as instructed by @SubwayChamp in the link you posted
but the phone boots straight back to fastboot after
Code:
fastboot reboot
so I believe I need to flash a stock rom
I'm on Debian; I am wondering wether I can use
Can XiaoMiTool V2 unbrick my device?
to unbrick my phone or just
fastboot flash the daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Code:
fastboot -w
fastboot update </path/to/your/Rom.zip>
and it will work with a .tgz format or do I need to extract it and then zip it?
Thanks for your help
Click to expand...
Click to collapse
Mdtp flashes returned your device to an state where partitions are readable again otherwise you won´t enter not even to recovery.
You don´t have to try to flash recovery (nor stock or custom), only reboot to a custom recovery like TWRP, the process to do it is well explained there, I also faced an mdtp issue and I didn´t need to flash the whole rom, just booted to TWRP and from there I did what I wanted, but if you yet want to do it.......
First of all I´m not familiar with Debian coming to modding smartphones, just I use it within other distros for other purposes.
The tool that you linked is not useful for us, this tool works mainly to fool recovery to accept modded scripts as original/signed and our device although it has a recovery image doesn´t have a dedicated partition and it simply is not available for the normal user, it´s mean that this tool uses MiRecovery present on all the devices running Miui out of the box but not for the others running Android One.
If you can access to a Windows machine this is the tool that I frequently use: https://xiaomifirmware.com/downloads/miflashpro/ but if you only can access to a PC with Debian probably this tool works for you https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847

BenG7 said:
daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Click to expand...
Click to collapse
You can't throw a .tgz or .zip at fastboot?!
If you're going to flash a stock ROM, extract it and run a flash_XXX script. It will use your fastboot to flash every partition. Variants preserve data or relock bootloader.

if fastboot fails (data transfer failure (too many links))
-> use a different USB port which is not a charging port.
-> try a different USB cable

Delete me

TWRP Recovery, Android 9 Pie

Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!

Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions

Yes, you are right. I just patched boot.img

thanks, it worked perfectly for me.

Thanks a lot, not a lot of development and love on this device, I just wanted to say some of us really appreciate this.

SaiLas said:
Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Click to expand...
Click to collapse
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?

What's the benefit without ROM's for rooting your phone? Magisk modules?

notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145

SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
Hey thanks!

X-Nemesis said:
What's the benefit without ROM's for rooting your phone? Magisk modules?
Click to expand...
Click to collapse
Yes. On my V30 I've never installed a custom ROM. Rooted stock firmware when the TWRP custom recovery (gift by itself for backups), Magisk mods, Xposed mods. You can tweak yourself without having to install a ROM.

During flashing, you may see error messages about 'unable to unmount vendor'. This is fine as long as the zip flashing doesn't fail halfway.
Click to expand...
Click to collapse
realllllllllllly important. I kept getting unable to mount xx (one of vendor system systemroot randomly) and didn't notice it meant the magisk sticked until I gave up and was ready to settle with no twrp.

YUP
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse

SaiLas said:
Yes, you are right. I just patched boot.img
Click to expand...
Click to collapse
links dont work
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware

SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build

zfk110 said:
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
Click to expand...
Click to collapse

Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.

Excelstar said:
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Click to expand...
Click to collapse
I just went back to TWRP and used his boot.img to flash within TWRP to boot's partition and then I was able to boot without any issues, I was thinking the same, but it looked more work to do.

kaneorotar said:
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Click to expand...
Click to collapse
Just wanted to say thanks for the updated instructions. Worked like a charm.

Hello, can you help me with the TWRP file for the LG V350AWM?