Update TWRP to 3.0.2.0 - XZDualRecovery - Xperia Z1 Q&A, Help & Troubleshooting

Hello, I installed TWRP via XZDualRecovery ( https://forum.xda-developers.com/showthread.php?t=2647487 ), because I have locked bootloader.
I want to update TWRP to 3.0.2.0. I tried TWRP app from Play Store - it said "Flash succesful", but I stil have 2.8.7.0. I wanted to flash 3.0.2.0 image via TWRP, but I can flash .img only to Kernel partition - no option to flash to recovery partition shows.
I'm new to this. Is there other some way to flash recovery or I have to wait for XZDualRecovery update? (Not sure if fastboot would work - i have locked bootloader)
Thanks!
(And sorry for my bad english ^^)

Install it to your FOTAKernel and than another rom because I think stock .236 doesnt work with recovery partition.

I've should also wrote, that I'm not using stock ROM, but DStrikerZ1's ROM.
But thanks, I'll take a look at that FOTAKernel thing ^^

Related

[Q] Change recovery to TWRP

Hello there... i'm new on this device (SGS i9000). i updated my firmware to CM 10.1. I understand that when i update to JB, the rom updates my recovery to CWM 6. i am trying to change it to TWRP without success. My methods are 2:
1) i download a flasheable zip with the TWRP recovery. I flash it through CWM but when i reboot into recovery again, there is CWM, no TWRP.
pd: CWM didn't indicate me any error during the flash of the zip. it says that it were successful.
2) i flash the recovery image through flash_image using the terminal. it says that it was successfully wrote in the recovery partition.
i guess there's an script that reflash CWM recovery in every boot but i am not sure. If i'm correct (or not) what do i have to do to to flash TWRP permanently?
sorry for my bad english
Both Mackay and Latrop kernel have TWRP, and Devil Kernel has TWRP as an option.
Sent from my GT-P7510 using Tapatalk HD
We have two options mackay or devil to twrp

Stuck at CyanogenMod

Hi everybody! I wanted a better battery life for my Z1 (1 screen hour at 75% :crying: ) so i flashed the CM11 latest snapshot, (as we all know, the LP builds has a very horrible battery management) and it worked, but when i switched from MX ROM to CM11 i lost my recovery (dual recovery) and it were replaced with CWM, i tried to install TWRP with some apps like Rashr, Flashify, ROM manager, Multirom manager and many others but it wasnt successful, and now im trying to flash a stock build of LP but flashtool gives to me this error:
- root this bundle is not valid -
I tried with a KK build but it was the same result. So I am stuck in CM, i dont know what more can i do... Can anyone help me?
The Bankshooter said:
Hi everybody! I wanted a better battery life for my Z1 (1 screen hour at 75% :crying: ) so i flashed the CM11 latest snapshot, (as we all know, the LP builds has a very horrible battery management) and it worked, but when i switched from MX ROM to CM11 i lost my recovery (dual recovery) and it were replaced with CWM, i tried to install TWRP with some apps like Rashr, Flashify, ROM manager, Multirom manager and many others but it wasnt successful, and now im trying to flash a stock build of LP but flashtool gives to me this error:
- root this bundle is not valid -
I tried with a KK build but it was the same result. So I am stuck in CM, i dont know what more can i do... Can anyone help me?
Click to expand...
Click to collapse
KK custom roms have recovery inside kernel. You have recovery in your FOTA or Recovery partition. The in-kernel recovery won't let you start Fota recovery, no matter what you try to install. Latest LP roms, as well as MM don't have recovery in kernel. So, you want to fastboot an LP kernel that has no recovery: fastboot flash boot boot.img. Then fastboot TWRP: fastboot flash recovery recovery.img. After that, you can boot into TWRP recovery and install whatever you want...
optimumpro said:
KK custom roms have recovery inside kernel. You have recovery in your FOTA or Recovery partition. The in-kernel recovery won't let you start Fota recovery, no matter what you try to install. Latest LP roms, as well as MM don't have recovery in kernel. So, you want to fastboot an LP kernel that has no recovery: fastboot flash boot boot.img. Then fastboot TWRP: fastboot flash recovery recovery.img. After that, you can boot into TWRP recovery and install whatever you want...
Click to expand...
Click to collapse
Thanks a lot! Ill try it

Unable to flash TWRP after with OOS 4.0.2

I flashed TWRP with succes according to cmd. But when booting to recovery it gives me the stock recovery. I had the same problem with my OPX. Someone on here said that MM had a new bootloader so i had a TWRP that was compatible with that bootloader. Is this the same for OP3T? If so can anyone link this
medick_ said:
I flashed TWRP with succes according to cmd. But when booting to recovery it gives me the stock recovery. I had the same problem with my OPX. Someone on here said that MM had a new bootloader so i had a TWRP that was compatible with that bootloader. Is this the same for OP3T? If so can anyone link this
Click to expand...
Click to collapse
flash twrp 3.0.4.0 (in OP3 forums, now unified), from fastboot boot immediately to recovery it should boot TWRP, flash SuperSU or similar (or kernel that will rename stock recovery) to keep TWRP, reboot recovery from TWRP to check it works, reboot to system and profit.
if you don't root, stock recovery will keep coming back.

Unable to update to MIUI 9

Hello guys.
I've just tried to update to MIUI 9.0.1.0 NDDMIEI from MIUI 8.5.9.0 NDDMIED on device Xiaomi Mi Max 2 but it failed.
I have an unlocked bootloader and SuperSu installed, but the recovery is Mi Stock Recovery. :cyclops:
I had directly booted TWRP Recovery without flashing using
Code:
fastboot boot twrp.img
to flash SuperSu on device. :good:
Need support with this issue. I don't want to flash whole ROM every time I recieve an update.
steve.24 said:
Hello guys.
I've just tried to update to MIUI 9.0.1.0 NDDMIEI from MIUI 8.5.9.0 NDDMIED on device Xiaomi Mi Max 2 but it failed.
I have an unlocked bootloader and SuperSu installed, but the recovery is Mi Stock Recovery. :cyclops:
I had directly booted TWRP Recovery without flashing using
Code:
fastboot boot twrp.img
to flash SuperSu on device. :good:
Need support with this issue. I don't want to flash whole ROM every time I recieve an update.
Click to expand...
Click to collapse
i successfully flashed to miui v9(V9.0.1.0.NDDMIEI) over miui v8(V8.5.8.0.NDDMIED) without data wipe. all my data were intact
Keep a backup just in case
make sure you downloaded recovery flashable full rom package ~1.38GB (not the 500mb OTA update )
donot wipe data/cache/dalvik
flash via TWRP recovery
just flashing rom wont boot due to dm-verity. (result will be bootloop)
u need to flash super user or magisk (or lazy flasher "ive not tried though" ) which patches boot.img which makes rom bootable
reversegear said:
i successfully flashed to miui v9(V9.0.1.0.NDDMIEI) over miui v8(V8.5.8.0.NDDMIED) without data wipe. all my data were intact
Keep a backup just in case
make sure you downloaded recovery flashable full rom package ~1.38GB (not the 500mb OTA update )
donot wipe data/cache/dalvik
flash via TWRP recovery
just flashing rom wont boot due to dm-verity. (result will be bootloop)
u need to flash super user or magisk (or lazy flasher "ive not tried though" ) which patches boot.img which makes rom bootable
Click to expand...
Click to collapse
I'll give it a try. Currently I have data wiped and installed full ROM through fastboot method. So next time, for sure I'll give it a shot.
But I have a doubt, where TWRP be able to flash an MIUI ROM. I mean the bootloader unlocked, encrypted system partition and all.
Since you have your device rooted, first install flashify, and backup your stock recovery. Then you can flash twrp recovery and install Miui 9, and root the device again. Last, install flashify again and restore your stock recovery.
scholastova said:
Since you have your device rooted, first install flashify, and backup your stock recovery. Then you can flash twrp recovery and install Miui 9, and root the device again. Last, install flashify again and restore your stock recovery.
Click to expand...
Click to collapse
Can you give stock recovery from mi max 2? I forgot to back up his original recovery stock and was hit with twrp.

Get opt encrypt and update rom [stock recovery and boot opt encrypt with magisk]

Here is my tutor after a hard work on my zenfone 4 max whole day.
first of all you must download the last asus update for zenfone 4 max, I used 233.
put it into sd card, boot into stock recovery and update. (if you have a new phone just do it, if you already unlocked bootloader and installed twrp, just boot bootloader and flash stock recovery above.)
https://drive.google.com/open?id=1YP7v9sBclQULxYPOndDPCMLikZsT8urN
after this step, just do unlock bootloader. (if not unlocked), and flash twrp.
*recommended reboot recovery twrp and make a backup now
reboot bootloader and flash the boot above, it has no decrypt and magisk 16
https://drive.google.com/open?id=1bHk0znQNsH-dWZ89P525gC-rrvN4e9bl
reboot recovery twrp. Do the following:
format data partition,
reboot recovery twrp
clear data, cache and dalvik cache.
Now boot system, all data encrypt is gone, and you can activate it if you want.
You cant boot system until this boot image is flashed, or encrypt will be activated.
How does one flash the kernel?
amspady20 said:
How does one flash the kernel?
Click to expand...
Click to collapse
kernel is the core, it is in boot image.
fastboot flash boot boot.img
(after extract boot image, cause it is zipped)
Stock Recovery
Do you have stock recovery img file for our Zenfone 4 Max (ZC554KL)? Kindly upload it again.
Hi, do you have latest stock recovery for this device? I want to update to oreo, but it requires latest firmware (at least ver .352) to execute it.
latest recovery version
Hi alegmx!
i'm really thankful that you provide this stock recovery image , it works!
but can you provide us with a newer version of the recovery image? it'll be big help if you can provide it with us!
your version is currently .215 , im upgrading my os to version 412 and it needs atleast the .352 version of the recovery.

Categories

Resources