Related
I just purchased an Amazon Kindle Fire 5th Gen. Since I have the Jem and Tate version running cyangenmod I decided to install it on the 5th gen as well. Since the boot loader is locked I flashed with chain fire's flashfire.apk. Also the cyangenmod I flashed is not the official version but it is stable. So I ordered the command via flasfire to wipe followed by install rom finishing with install gaps pico version. So when the kindle rebooted it booted into cyangemod no problem but I quickly noticed I had no google play. So I went into flashfire again but when i did it gave me an error alerting me that either I was not rooted or was not using supers or cm su set to permissive. When I go into developer options I can see my SElinux is set to permissive and did enable root access for adb and apps. But when I checked root checker I was not rooted. So I installed Kingroot and gain root again but when I tried installing supersu it could not update binaries. I think its an conflict with cm su because it does sometime say it detected another su and tried uninstalling it but couldn't. Also I tried flashing su through fast boot but I can not get into TWRP temporally to do so. I keep getting...
$ sudo fastboot -i 0x1bbb boot TWRP_Fire_2.8.7.0_adb.img
Password:
downloading 'boot.img'...
OKAY [ 0.258s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.260s
I tried this on boot my pc and mac to no avail. I stuck at this point I tried disabling the CM root but I get nowhere. I have no recovery image since my boot loader is locked so I can't ref lash. Flashfire won't work because I need su and CM root is conflicting with the install? Adb is working and fast boot seem too because i rebooted the device and it shows under fast boot.
Designassist said:
I just purchased an Amazon Kindle Fire 5th Gen. Since I have the Jem and Tate version running cyangenmod I decided to install it on the 5th gen as well. Since the boot loader is locked I flashed with chain fire's flashfire.apk. Also the cyangenmod I flashed is not the official version but it is stable. So I ordered the command via flasfire to wipe followed by install rom finishing with install gaps pico version. So when the kindle rebooted it booted into cyangemod no problem but I quickly noticed I had no google play. So I went into flashfire again but when i did it gave me an error alerting me that either I was not rooted or was not using supers or cm su set to permissive. When I go into developer options I can see my SElinux is set to permissive and did enable root access for adb and apps. But when I checked root checker I was not rooted. So I installed Kingroot and gain root again but when I tried installing supersu it could not update binaries. I think its an conflict with cm su because it does sometime say it detected another su and tried uninstalling it but couldn't. Also I tried flashing su through fast boot but I can not get into TWRP temporally to do so. I keep getting...
$ sudo fastboot -i 0x1bbb boot TWRP_Fire_2.8.7.0_adb.img
Password:
downloading 'boot.img'...
OKAY [ 0.258s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.260s
I tried this on boot my pc and mac to no avail. I stuck at this point I tried disabling the CM root but I get nowhere. I have no recovery image since my boot loader is locked so I can't ref lash. Flashfire won't work because I need su and CM root is conflicting with the install? Adb is working and fast boot seem too because i rebooted the device and it shows under fast boot.
Click to expand...
Click to collapse
Well I fixed my own problem...well immediate problem. I tried several times to install supersu finally got it working. So flash fire works again. I realized the gapp zip was for 6.0 and I'm running lollipop 5.1. So i downloaded gapp from opengapps 5.1 mini and installed its working now. But I realized I have no recovery it got wiped while flashing with flash fire. Hope someone figures how to fix that issue.
Hi,
there is something wrong with my Xperia Tablet Z. After upgrading from CyanogenMod 11 to CyanogenMod 12 a few Mouth ago the Custom Recovery i've installed before was replaced with CyanogenMod-Recovery. Because CM doesn't work very well i downgraded to Stock-ROM using Flashtool. Because i couldn't find a Way to root Firmware 4.2.x and higher i downgraded to 4.1.2 and rooted with towelroot. The Bootloader is unlocked (checked with *#*#7378423#*#*).
But when i try to install TWRP it failed. This is the error with Fastboot
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
All drivers are installed. I've tried this on Ubuntu 16.04 and Windows 7 with installed Flashtool and also with installed ADB Installer (https://forum.xda-developers.com/showthread.php?p=48915118#post48915118). I tried it with three usb cables and different usb ports.
It also doesn't work with TWRP Manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=de) and the Official TWRP App (https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=de). TWRP Manager show me this error
Code:
Flashing recovery was unsuccessful. Either you already have thos recovery installed or another error has occuured. Would you like to attempt to recovery now?
When i try to reboot the App freeze.
The Official TWRP App seems to install the recovery ("was successfully installed"), but i can't reboot into recovery with VOL+ (also tried VOL-). The Table starts normally.
Maybe there is something wrong with my Tablet now? Is there any other Way to flash a Recovery or to flash a Custom-Rom or a pre-rooted Stock-Rom? As i said before i can't root it with a Firmware higher 4.1.x. Update with the internal Update fuction also failed. So at the moment i can use [email protected] or a higher Version without root.
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Hi,
after some years with my pollux_windy left untouched, I decided I'd install my first custom ROM. But I'm having serious trouble to do so, and it seems unsolvable to me after hours of despair (I've been trying for almost 10 hours now).
I was on Lollipop (firmware .222), first unlocked my bootloader, then rooted my tablet (using kingroot). Then I tried to install twrp, and the only way I managed to do this was through this "TabZ-lockeddualrecovery2.8.26" thing. Only, I couldn't manage to flash anything, ended up bricking my tablet.
I then flashed a stock 5.0.2 ROM (.454), retried installing twrp via the same method, and although I manage to access twrp, I get the same error each time I want to flash a new ROM (tried CM/LineageOS 14.1 and ResurrectionRemix v5.7.0), which is : "E: error executing updater binary in zip [insert name of the .zip]".
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
I'm completely lost in this... How can I get that damn recovery to work, and/or get a custom ROM ?
Edit : Alright, with a good 3 hours-long night and a lucky shot, I managed to install LineageOS ! I used twrp recovery (from the dualrecovery thingy-thing) to wipe clean the device, then tried to install the ROM. It gave me the same error message about updating binary. So I rebooted the device into fastboot (couldn't access the recovery anyway... not sure if it's normal), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device. On the bootlogo, I tried to enter recovery with Vol-, and it worked. i then flashed with ease the ROM. Maybe it will help somebody !
Hapaxx said:
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
Click to expand...
Click to collapse
yep, one just need to
fastboot flash boot boot.img
Click to expand...
Click to collapse
enter recovery and flash firmware zip, gapps, etc from it.
Root works now, but i can't install TWRP 3.0.2.0 (but XZDualRecovery works).
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Hapaxx said:
So I rebooted the device into fastboot (...), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device.
Click to expand...
Click to collapse
If i understand correct Hapaxx flashed the boot.img form the LineageOS 14.1 Image? I don't want to install a Custom-ROM. crDroid is for Nexus. Where can i download a Kernel with build-in Recovery for tabz? or can i use the same crDroid also for tabz?
how can i flash the recovery to fota? can i do this with the same *.img or do i need an other image?
i just unlocked my bootloader and i dont know what else to do, i would like to install lineage 14.1 but i dont know what path to follow, i also hit the whole command not allowed thing, and what Hapaxx said, i'm unable to understand, could someone give a clear set of commands to follow? please? what to do in order so i dont brick my tablet.
Hi PiereMallao,
i have the same Odyssey behind me! Sony Xperia Tablet Z SGP321 LTE (16GB)
1. First check Bootloader unlocked with Flashtools 0.9.18.6. Check!
2. Install SGP321_10.1.1.A.1.307_Unbranded.ftf with Flashtools 0.9.18.6. Check!
3. Developertools on. USB-Debugging on. unknown sources on. Check!
4. Root with Doomlord_Rootkit_v18.rar. Check!
5. Check with App "Root-Checker" in Google PlayStore. Check!
6. And now I try to install TWRP for 3 days !
First try with TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip its ok, but i come only once after the installation in the recovery mode. Afterwards I have it with Vol+ or Vol- tried. It always starts the normal system.
7. With Fastboot -
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
target didn't report max-download-size
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
How can i check Bootloader unlock ? In Android Tablet Z i didnt have a keyboard to put in the hex-code *#*#7378423#*#* ?
In Flashtools i checked Bootloader unlock so i have no idea at this Point.
What can I do ?
sorry, i have so solution for this problem. i have given up. theonly way i know to ceck the bl is unlocked or not is flashtool.
I'm having issues with this as well. Trying to install LineageOS 14.1, I can initially get twrp onto the tablet, flash LineageOS 14.1.. boot into it, set up (it is recommended to reboot the tablet once before flashing gapps) ...however, rebooting wipes twrp out. I'm not used to this FOTA thing (first i've ever heard of it) so not sure how to get twrp to 'stick' and not get wiped out
I got it installed this weekend. First secret was fastboot TWRP to boot, not recovery:
Fastboot flash boot twrp-------.img
Make sure you have the right TWRP image.
Then boot into recovery and TWRP comes up.
Flash lineage and gapps.
See:
https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
bowguy said:
I got it installed this weekend.
Click to expand...
Click to collapse
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
x000x said:
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
Click to expand...
Click to collapse
I never did step 14. Looks straight forward. You should ask this question on that thread
bowguy said:
I never did step 14. Looks straight forward. You should ask this question on that thread
Click to expand...
Click to collapse
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
x000x said:
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
Click to expand...
Click to collapse
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
bowguy said:
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
Click to expand...
Click to collapse
Are you using twrp-3.0.2-0-pollux_windy?
x000x said:
Are you using twrp-3.0.2-0-pollux_windy?
Click to expand...
Click to collapse
Yes.
I never bothered with step 14 in the guide. It works fine as is.
P.S.
As per my post on the guide referenced, I installed Rashr and flashed TWRP that way. Seemed to work perfectly. TWRP now shows 3.0.2 which is correct version. No change to system boot. Nice app
Rootk1t said:
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Bro please give me link to twrp latest for sgp321 m going to unlock bootloader using" flash tool" is it ok
Please tell me how to flash recovary too
Is it ok if i root my tab after unlocking bootloader using king root ajnd flash using flashify
Is ressuraction remex stableto use tell me bugs
?
i had equal problem
FAILED (remote: Command not allowed)
i also have the same problem with my huawei chc u23 gplay mini bricked no recovery please help
Hello guys,
I have the SGP321 running on android 5.1.1. It is rooted with SuperSU and I installed TWRP via [NUT]'s XZDualRecovery. When I try to flash Resurrection Remix (same error with LineageOS 14.1 btw) the installation fails with error: execute updater binary in zip. Two lines above (but not in red text) it says that this rom is meant to be installed on a SGP321 (which I have) but my device is a [empty space]. I don't know if this has something to do with the mentioned error. A Google search led me to posts with the same error, but mostly on the OP One and the Moto G4. They say that you have to update the bootloader. Has anyone experienced the same problems with their Xperia TabZ and has found a solution to this?
Edit: TWRP Log https://i.imgur.com/418FJx2.jpg
julius1504 said:
Hello guys,
I have the SGP321 running on android 5.1.1. It is rooted with SuperSU and I installed TWRP via [NUT]'s XZDualRecovery. When I try to flash Resurrection Remix (same error with LineageOS 14.1 btw) the installation fails with error: execute updater binary in zip. Two lines above (but not in red text) it says that this rom is meant to be installed on a SGP321 (which I have) but my device is a [empty space]. I don't know if this has something to do with the mentioned error. A Google search led me to posts with the same error, but mostly on the OP One and the Moto G4. They say that you have to update the bootloader. Has anyone experienced the same problems with their Xperia TabZ and has found a solution to this?
Edit: TWRP Log https://i.imgur.com/418FJx2.jpg
Click to expand...
Click to collapse
Recovery 2.8.7.0 is not compatible with with the lastest custom firmwares like android 7.1.2 or 8.1.
To flash them successfully you need to flash recovery version at least 3.2.1.x to your device.
Rootk1t said:
Recovery 2.8.7.0 is not compatible with with the lastest custom firmwares like android 7.1.2 or 8.1.
To flash them successfully you need to flash recovery version at least 3.2.1.x to your device.
Click to expand...
Click to collapse
Good to know, thank you! How can I flash the newer version of TWRP? I tried to flash via Fastboot but get the error "FAILED (remote: Command not allowed)". I think this is because Sony's devices don't have a recovery partition.
julius1504 said:
Good to know, thank you! How can I flash the newer version of TWRP? I tried to flash via Fastboot but get the error "FAILED (remote: Command not allowed)". I think this is because Sony's devices don't have a recovery partition.
Click to expand...
Click to collapse
Use Rashr tool.
Download twrp.img from the link above. Flash it to recovery via Rashr and reboot. After you can enter it via Vol+ on boot.
Rashr says I need a FOTA kernel partition, how do I get that? Thank you for your help, hope that this was my last question
EDIT:
OK I tried different things with Rashr. I uninstalled XZDualRecovery with the flashable zip and flashed full stock rom 5.1.1 with Flashtool and rooted it again. I was not able to install the latest twrp by any means using Rashr.
I found another solution:
1. I installed (again) XZDualRecovery and booted into TWRP 2.8
2. I flashed the Marshmallow Version of Resurrection Remix (https://forum.xda-developers.com/xp...pment/rom-resurrection-remix-m-5-7-3-t3440876) --> This installed the CM-Recovery (Vol-) AND TWRP 3.2.1 (Vol+)
3. Booted into TWRP 3.2.1
4. Successfully flashed an Android 8.1 Rom
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Hello Guys and Girls,
the title is obvious: Here is a twrp build for the HTC U12+. I spent quite a bit of time together with the dear @Captain_Throwback to get everything working.
At this place a huge thanks to @Captain_Throwback for helping me, even though not having the device at his hands!
Instructions:
With A/B devices the command
Code:
fastboot flash recovery recovery.img
is not possible, because these devices generally don´t have a recovery partition any longer. The recovery sits now in the ramdisk of the boot.img.
So how do we get TWRP on it?
The first option is to just boot TWRP temporarily with the command
Code:
fastboot boot twrp.img
. This will just boot up TWRP, not actually flash it onto your device. After rebooting the phone, TWRP will be gone. This is a great option for those, who just like to flash their phone one time, don´t want to modify the boot.img and don´t need a permanently installed TWRP.
The second option is to use the twrp flashable installer zip to install TWRP permanently to your ramdisk from the booted TWRP or magisk manager! Installing from Magisk Manager was made possible by @osm0sis!
So you see there are generally 2 steps needed on A/B devices now.
First booting TWRP. Second flashing the installer zip.
But and now comes HTC into play. When permanently flashing TWRP zip touchscreen gets disabled, because HTC added a nasty little check into the touchscreen driver. If it detects that the phone is in recovery mode it disables the touchscreen.
Luckily we found 2 ways around that!
First way is to have a custom kernel, that has this check patched out!
Second option is to use a zip we provide here, that also patches your kernel, to avoid tripping this check. The downside of flashing this zip is that all commands like
HTML:
adb reboot recovery
, hitting reboot to recovery in magisk manager and finally reboot to recovery in TWRP are not working and only boot to the OS!
How to temporary boot TWRP:
1. You need a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img provided in this thread and copy it to your fastboot folder (pay attention that firmware version matches)
3. Open a command prompt in your fastboot folder!
3.a While your phone is booted to the OS and USB debugging is enabled, type:
Code:
adb reboot bootloader
4. You need to fastboot boot twrp currently
Code:
fastboot boot <filename of the twrp.img>
example:
Code:
fastboot boot twrp-3.2.3-2-ime.img
5. Wait for twrp to be booted
6. You´re now in TWRP
7. Please note that you need to fastboot boot the TWRP every single time you need it. After a reboot it will be gone!
8. Important:
Please note that
Code:
fastboot boot twrp.img
(like done in step 4) will also break OTA functionality. More about this in the FAQ.
How to permanently flash TWRP via the .zip installer
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the flashable TWRP installer zip provided in this thread!
2a. If you´re on a stock kernel that has no touchscreen fix for recovery included please also download the touchscreen_hexpatcher.zip
3. Flash the TWRP-Installer.Zip from the booted TWRP or Magisk Manager on your phone (hit the + while in modules section)
3a. Important: Directly afterwards flash the magisk zip from TWRP or Magisk Manager
If you don´t flash it you will only be able to reboot to TWRP, regardless of the option you choose
4.Only needed when on stock kernel without touchscreen fix:
also flash the touchscreen_hexpatcher.zip from TWRP or Magisk Manager
Be aware that flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes
Code:
adb reboot recovery
, reboot to recovery from magisk manager and reboot to recovery from inside TWRP.
To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
5. Reboot
6. Congratulations: you can now reboot into your permanently flashed TWRP
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from the offical twrp site
2a. If you´re on a stock kernel that has no touchscreen fix for recovery included please also download the touchscreen_hexpatcher.zip
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either 3a or 3b.
3a. If you want to be rooted flash the magisk.zip
3b. If you don´t want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
4.Only needed when on stock kernel without touchscreen fix:
also flash the touchscreen_hexpatcher.zip from TWRP or Magisk Manager
Be aware that flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes
Code:
adb reboot recovery
, reboot to recovery from magisk manager and reboot to recovery from inside TWRP.
To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
5. Reboot
6. Congratulations: you can now reboot into your permanently flashed TWRP
Few tips and tricks:
1. You need to mount ext_sd card before you can access it in the file manager
2. Go to mount and click on mount usb storage to access the ext sdcard when connected via USB
3. Don´t forget you can connect an usb device via usb-otg to backup/flash stuff from/to an usb storage device
Official Changelog: twrp.me
22.06.2020 3.4.0-0
HTC Firmware on Android Pie can´t be decrypted.
Add support to be able to decrypt Viper GSI - Huge Thanks to @Captain_Throwback
20.05.2019 3.3.1-0
Decryption on devices running firmware 1.68.xxx.y with security patch state of 1st April 2019 when fastboot booting the twrp.img
NOTE: The official TWRP image 3.3.1-0 will only decrypt devices on the 1st April 2019 security patch state when fastboot booted. The official TWRP image 3.3.0-0 will only decrypt devices on the 1st February 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-5 will only decrypt devices on the 1st January 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
17.04.2019 3.3.0-0
Decryption on devices running firmware 1.62.xxx.y with security patch state of 1st February 2019 when fastboot booting the twrp.img
Future TWRP.img files can be flashed via the "Install Recovery Ramdisk" option inside TWRP´s advanced settings (for now the twrp.zip is also still available)
If you don´t flash magisk there is also option to "Fix Recovery Bootloop" inside TWRP´s advanced settings to be able to boot to system
you are able to take screenshots via power + home button
busybox is included instead of toybox
NOTE: The official TWRP image 3.3.0-0 will only decrypt devices on the 1st February 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-5 will only decrypt devices on the 1st January 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
01.01.2019 3.2.3-5
Add support for successfully decryption devices on firmware 1.57.xxx.y with security patch state of 1st December 2018
NOTE: The official TWRP image 3.2.3-5 will only decrypt devices on the 1st January 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
01.01.2019 3.2.3-4
System is no longer being mounted R/W when booting TWRP
NOTE: The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
01.01.2019 3.2.3-3
Add support for successfully decryption devices on firmware 1.53.xxx.y with security patch state of 1st December 2018
NOTE: The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Older versions:
05.10.2018 3.2.3-2
[Fix] TWRP Image 3.2.3-2 successfully decrypts devices on 1st September Security patch state! Also see the information below.
[Tweak] resetprop included statically, remove dependencies for it thanks @Captain_Throwback, @topjohnwu and @nkk71
NOTE: The official TWRP image 3.2.3-2 will only decrypt devices on the 1st Sepember 2018 security patch state when fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-2 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
07.09.2018 3.2.3-1
[Fix] MTP now enabled/working! (@Captain_Throwback)
[Fix] Vibration feedback now enabled/working (@notsyncing)
[Fix] Maximum brightness fixed - you need to manually adjust brightness in Settings using the slider to update (@Captain_Throwback)
[Tweak] Zip now automatically unroots the device when flashing to allow device to reboot to system normally if root isn't immediately flashed afterwards (@osm0sis)
[Tweak] /data/cache contents now mounted to /cache on flashed version (@Captain_Throwback)
NOTE: The official TWRP image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer, however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
07.08.2018 3.2.3-0
Official TWRP release
NOTE: The official TWRP image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer, however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Unofficial Changelog:
21.07.2018 3.2.2-0
Initial Release
28.07.2018 3.2.2-1
Decryption is now working
02.08.2018 3.2.3-0
fix system not getting mounted by magisk installer!
fix no OS message upon reboot
flashable installer for permanently installing TWRP!
05.08.2018 3.2.3-1
fix system not being mountable as R/W in twrp
display a message asking you to reflash magisk after flashing twrp installer zip
Download:
Official
twrp.me
NOTE: The official TWRP image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer, however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Unofficial
XDA | AFH
Additional Downloads
Touchscreen hexpatcher | Mirror (AFH) - SEE IMPORTANT NOTES BELOW:
Only needed when on stock kernel without touchscreen fix
Flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes "adb reboot recovery", reboot to recovery from Magisk Manager and reboot to recovery from inside TWRP. To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
Known Issues:
MTP is disabled in official TWRP. This is currently an issue on several A/B devices. - Enabled since 3.2.3-1
Official TWRP can´t decrypt HTC Firmware on Android Pie!
NOTE: The unofficial TWRP image has MTP enabled for fastboot booting ONLY.
fastboot booting TWRP mounts the system RW and breaks ability to take an OTA.
Please take a look at FAQ, found in the 2nd post here. It contains more information
Bug Reporting:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
We need your help!
Join the TWRP Testing group on Slack to help us test TWRP prior to official releases!
Tips on how to build TWRP for the U12+ yourself:
To build TWRP you need to use this branch as your device tree:
https://github.com/freak07/android_device_htc_ime
Additionally you these commits from gerrit to your twrp tree!
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/31760/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/31207/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/31021/
Depending on the base you're building for, you may need to comment/uncomment the PLATFORM_SECURITY_PATCH flag for your respective build if you want to fastboot boot the twrp.img. If the patch level of the image doesn't match the patch level of the current system, decryption will not function when fastboot booting the image. If installed via zip, the patch level doesn't matter, as it is automatically updated from system using @topjohnwu & @nkk71's resetprop.
XDA:DevDB Information
TWRP for HTC U12+ aka Imagine, Tool/Utility for the HTC U12+
Contributors
Freak07, Captain_Throwback, nkk71, topjohnwu, Dees_Troy, bigbiff, _that
Source Code: https://github.com/TeamWin/android_device_htc_ime
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-22
Created 2018-07-21
Last Updated 2020-06-25
F.A.Q.:
Q: Which TWRP.img to choose for my current Security Patch State
A: For the old base 1.15 use on of the unoffical 1.15 release found in the OP.
TWRP Image 3.2.3-1.img decrypts devices, which run firmware on the 1st June Security patch State.
TWRP Image 3.2.3-2.img decrypts devices, which run firmware on the 1st September Security patch State.
The zip installer (also from the 3.2.3-2 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Q: I´m not able to fastboot boot the recovery, because the command won´t execute properly.
A: Update your adb and fastboot binaries to the latest one found here:
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Make sure you´re using the original cable.
Make sure you are in bootloader mode.
Try different USB ports on your machine.
On windows make sure you have the latest usb/mtp driver installed properly when the phone is connected in bootloader mode.
Q: I flashed the permanent twrp installer zip and now my touchscreen is not working.
A: This happens when you´re on stock kernel and did not flash the hexpatch-touchscreen zip found in the OP.
Q: I flashed the permanent twrp installer zip and the hexpatch-touchscreen zip found in the OP. Now commands/actions like
Code:
adb reboot recovery
reboot to recovery button in magisk manager
reboot to recovery button in TWRP
are only booting me straight to the OS.
A: As mentioned in the OP flashing the hexpatch-touchscreen zip will break the reboot to recovery command and associated actions.
To get to twrp reboot to bootloader and from there choose reboot to recovery with volume buttons and confirm with the power button.
Q: I flashed the permanent twrp installer zip, booted to the OS and lost root
A: Directly after flashing the twrp installer zip flash the magisk zip to keep root!
Q: I only fastboot booted TWRP but now my OTA functionality is broken.
A: Fastboot booting the twrp image trips a check, this check isn´t able to determine if system has been modified (because it receives no output) and subsequently assumes it has been modified.
this breaks verity on system and probably vendor. Resulting in non existing OTA functionality.
If you are interested in a more detailed explanation please follow this link:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1301
to check if system has been modified check the following path:
"/sys/fs/" + Current_File_System + "/" + block + "/lifetime_write_kbytes"
Current_File_System is ext4 on the U12+
block is related to your boot_slot. so check the partition table here:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-root-u12-magisk-tips-tricks-t3802583
if you´re on slot A: system_a is sda18
if you´re on slot B: system_b is sda19
Example:
I was on slot B so the file I needed to check was: `/sys/fs/ext4/sda19/lifetime_write_kbytes`
if this file shows 0 system was not modified. Any other value means it was modified and you will not be able to take an OTA!
Same check applied for vendor! you just have to adjust the path.
Slot A vendor: sde19
Slot B vendor: sde40
Example to check if vendor_b has been modified: /sys/fs/ext4/sde40/lifetime_write_kbytes
To restore OTA functionality follow this post:
https://forum.xda-developers.com/showpost.php?p=76606113&postcount=3
or alternatively:
1. after updating your device via RUU or OTA, patch the boot.img with magisk (look at my guide thread)
2. run the following command on either a terminal shell on the phone or via adb shell on your pc(don´t forget to grant su permissions) to obtain an untouched system.img:
dd if=/dev/block/bootdevice/by-name/system$(getprop ro.boot.slot_suffix) of=/sdcard/system.img
3. store this system.img somewhere safe
Additional info:
you can also backup vendor this way!
dd if=/dev/block/bootdevice/by-name/vendor$(getprop ro.boot.slot_suffix) of=/sdcard/vendor.img
Information: Please note that only perm s-off devices are able to flash the vendor.img in fastboot!
Q: Is there a way to restore OTA functionality and keep using TWRP?
A: Yes there is. Please read below! thanks to @osm0sis who came up with the idea!
Temporary Workaround for TWRP mounting /system as RW
the issue linked here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1301, which is causing TWRP not being able to mount system as read-only, results in a non pristine system partition after booting TWRP once.
The following file will allow TWRP to mount system as read-only (and therefore keeping OTA functionality)
That means after the following procedure, you can restore an untouched system.img, keep TWRP flashed on your device and simultaneously be able to take OTAs!
Instructions:
1. Download the following file https://www.androidfilehost.com/?fid=1322778262904004337 and extract it! (also as attachement to this post)
2. Copy/Replace the .twrps files to
/persist (make sure to grant the correct permissions afterwards! 0664 | rw-rw-r-- )
/storage/emulated/0/TWRP
with the one you just downloaded
3. When now booting/flashing TWRP system will get mounted as read only.
4. You can now restore a pristine system.img to your device! TWRP shouldn´t mount it as RW now!
5. Check if everything worked by following the guide above (check file lifetime_kbyte_writes for your active system partition)
A huge thanks to @MassStash for testing all this!
also mine
nice.:good:
noob question: can I format data partition and install magisk without force encryption flag like HTC 10? or is that impossible without decrypt the partition?
wiQbold said:
nice.:good:
noob question: can I format data partition and install magisk without force encryption flag like HTC 10?
Click to expand...
Click to collapse
I didn’t try it.
If you could try it and report back to confirm that would be great :highfive:
Nice work guys. Thanks @Freak07, @Captain_Throwback and all others who are still with as, as well as those who had to leave to soon - you'll be remembered.
Sent from my HTC U12+ using XDA Labs
@Freak07
Followed your instructions, but hangs at downloading 'boot.img' after second step: "fastboot boot TWRP_3.2.2.0_Imagine.img"
I'm Unlocked and Rooted with Magisk.
same here
fastboot boot TWRP.img
downloading...
FAILED: unknown command
schmeggy929 said:
same here
fastboot boot TWRP.img
downloading...
FAILED: unknown command
Click to expand...
Click to collapse
Might be a stupid question but did you try booting in fastboot? AFAIK it only works in fastboot
umaranjum said:
Might be a stupid question but did you try booting in fastboot? AFAIK it only works in fastboot
Click to expand...
Click to collapse
Yes that too, just hangs at booting... It is the same procedure at the U11. You boot TWRP in Bootloader and flash from Download Mode. Fastboot is the command for both.
umaranjum said:
Might be a stupid question but did you try booting in fastboot? AFAIK it only works in fastboot
Click to expand...
Click to collapse
Not the person you replied to, but since I have the same problem, I followed the steps in OP, and since it's only 2 steps, I'm sure the other person performed the "adb reboot bootloader" step.
Ah, Ok. Interesting, it worked the first time for me, have you tried redownloading the TWRP img and trying it again? If so, then it may be a problem specific to your device, in which case @Freak07 should be able to help you out better
---------- Post added at 02:27 AM ---------- Previous post was at 02:25 AM ----------
k_l_o said:
Not the person you replied to, but since I have the same problem, I followed the steps in OP, and since it's only 2 steps, I'm sure the other person performed the "adb reboot bootloader" step.
Click to expand...
Click to collapse
Ah, yes, I forgot about that lol. I do apologise, I'm quite tired. If it still doesn't work after redownloading then you'll need to wait for @Freak07 to help you out, as I mentioned above. Apologies that I couldn't be of more help and I hope you two manage to get it working
k_l_o said:
@Freak07
Followed your instructions, but hangs at downloading 'boot.img' after second step: "fastboot boot TWRP_3.2.2.0_Imagine.img"
I'm Unlocked and Rooted with Magisk.
Click to expand...
Click to collapse
Do you also get the same
FAILED: unknown command
as @schmeggy929?
schmeggy929 said:
same here
fastboot boot TWRP.img
downloading...
FAILED: unknown command
Click to expand...
Click to collapse
To both of you.
Try both bootloader and download mode for booting. Although only bootloader should work for booting.
Make sure you have the latest fastboot and adb drivers!
Try different usb ports.
What happens if you try to fastboot boot a stock boot.img?
Thanks @Freak07, @Captain_Throwback. TWRP_3.2.2.0_Imagine.img is worked.
product: htc_imedugl
current-slot: a
version-main: 1.15.709.6
Great news! Thanks everyone for your hard efforts! Get my U12 at the end of the month so looking forward to flashing. Hopefully Lee will have a nice ROM for us by then too
Freak07 said:
Do you also get the same
FAILED: unknown command
as @schmeggy929?
To both of you.
Try both bootloader and download mode for booting. Although only bootloader should work for booting.
Make sure you have the latest fastboot and adb drivers!
Try different usb ports.
What happens if you try to fastboot boot a stock boot.img?
Click to expand...
Click to collapse
I get a "FAILED (status read failed (Too many links))
Does it matter that I've Magisk already installed which required a patched_boot.img?
Freak07 said:
Do you also get the same
FAILED: unknown command
as @schmeggy929?
To both of you.
Try both bootloader and download mode for booting. Although only bootloader should work for booting.
Make sure you have the latest fastboot and adb drivers!
Try different usb ports.
What happens if you try to fastboot boot a stock boot.img?
Click to expand...
Click to collapse
Tried all available USB ports, two different cables. Where do I get a stock boot img for US Unlocked? Also while in bootloader, the only command that works is "fastboot reboot bootloader". "Fastboot reboot" and "fastboot reboot download" does nothing.
k_l_o said:
I get a "FAILED (status read failed (Too many links))
Does it matter that I've Magisk already installed which required a patched_boot.img?
Click to expand...
Click to collapse
Could you please post everything from your terminal?
And update the fastboot and adb binaries with the one from the following link for your current OS beforehand
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
No it doesn’t matter I did the same.
schmeggy929 said:
Tried all available USB ports, two different cables. Where do I get a stock boot img for US Unlocked? Also while in bootloader, the only command that works is "fastboot reboot bootloader". "Fastboot reboot" and "fastboot reboot download" does nothing.
Click to expand...
Click to collapse
You can extract it from the US firmware zip linked in the firmware thread.
Is fastboot devices showing your device?
Did you update your fastboot and adb binaries to the ones found here for your OS?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Freak07 said:
You can extract it from the US firmware zip linked in the firmware thread.
Is fastboot devices showing your device?
Did you update your fastboot and adb binaries to the ones found here for your OS?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Click to expand...
Click to collapse
Low and behold after updating the binaries twice and redownloading TWRP.img for the third time, it finally booted to TWRP. Cancelled decrypt and kept "Read Only". Flashed your Kernel successfully except for preload error due to not mounted. Rebooted and everything seems good, shows Kirisakura_1.0.
Thanks for the help!
Hello
I would like to migrate my oneplus x from android 6 to oreo 9.
I did all the steps to root my opx and i tried to boot with the correct twrp to let me backup the original img of the phone but I'm freeze at the moment and need your help.
After a lot of tentatives where i got the error "FAILED (remote: dtb not found)" i got the message (with specific image for OOS 3.1.4). OKAY "booting..." but the opx still remain in fastboot mode.
What you can suggest me ?
Thank you
Bye
S87
Which tuto did you applied?
The one to boot TWRP without installing it just to copy your data? You copied some from USB, right?
First, you have to verify if bootloader is really unlocked via the command.
Then, which TWRP did you used?