Since there hasn't been any up-to-date TWRP for the Z2 Tablet recently, I finally compiled a new one, which can also handle Android 10 encryption.
I have only tested it on Android 10, but I assume it should work on Android 9 as well (please report if you try).
For older Android versions, I recommend using older TWRPs.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Download
https://www.androidfilehost.com/?w=files&flid=313349
Use "castor_windy" for the WiFi variant, and "castor" for the LTE variant!
Installation
fastboot flash recovery twrp.img
Sources
Manifest for TWRP:
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
Kernel source:
https://github.com/AICP/kernel_sony_msm8974/tree/q10.0
Device tree source:
https://github.com/SpiritCroc/android_device_sony_castor_windy/tree/TWRP-9.0
https://github.com/SpiritCroc/android_device_sony_castor/tree/TWRP-9.0
Contributors - huge thanks for their work on TWRP for related devices!
@NeoArian
@115ek
Thank you for the update SpiritCroc!,
Have ran through all the basic functions in TWRP, and have not had any issues. Will test further in the next week, but so far working great for me. Thank you again!!!
Working fine, I flashed the latest build with it.
Only an error message on a recovery map file when booting to TWRP.
Thank you !
Working great on castor, flashed the latest build with it.
I flashed the Recovery, but I can't seem to boot into it. What is the button combination in order to boot into recovery mode?
KOAO said:
I flashed the Recovery, but I can't seem to boot into it. What is the button combination in order to boot into recovery mode?
Click to expand...
Click to collapse
Turn on the device, and when the sony screen comes up and the LED flashes magenta, press any volume button. Then, the LED should switch to yellow and TWRP should come up.
This procedure requires support for booting to recovery from your ROM (or more precisely, your kernel/bootimage), so it might be different based on what you use.
If you use a ROM which works with other recoveries but not this one, please report, then I'll put a note in the first post - I have only tested it with AICP 15.0 so far.
SpiritCroc said:
Turn on the device, and when the sony screen comes up and the LED flashes magenta, press any volume button. Then, the LED should switch to yellow and TWRP should come up.
This procedure requires support for booting to recovery from your ROM (or more precisely, your kernel/bootimage), so it might be different based on what you use.
If you use a ROM which works with other recoveries but not this one, please report, then I'll put a note in the first post - I have only tested it with AICP 15.0 so far.
Click to expand...
Click to collapse
I use the stock rom, since I had to downgrade to 4.4.2 in order to backup the TA Keys before unlocking the bootloader. Maybe that's why it doesn't work?
KOAO said:
I use the stock rom, since I had to downgrade to 4.4.2 in order to backup the TA Keys before unlocking the bootloader. Maybe that's why it doesn't work?
Click to expand...
Click to collapse
If you are on SONY'S OS i.e. STOCK ROM with STOCK KERNEL, you should be using NUT'S Dual Recovery. Search NUT'S Dual Recovery on XDA, then you can select our tablet.
Here's the link - https://forum.xda-developers.com/showthread.php?t=2794175
Hope this helps...
_Sherrif said:
If you are on SONY'S OS i.e. STOCK ROM with STOCK KERNEL, you should be using NUT'S Dual Recovery. Search NUT'S Dual Recovery on XDA, then you can select our tablet.
Here's the link - https://forum.xda-developers.com/showthread.php?t=2794175
Hope this helps...
Click to expand...
Click to collapse
Huh, alright. Didn't think I'd need this since this existed, first time dealing with a sony device, very complicated lol. But thank you nonetheless!
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
flymetothemoon said:
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
Click to expand...
Click to collapse
I have the same problem.
flymetothemoon said:
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
Click to expand...
Click to collapse
hunterb21 said:
I have the same problem.
Click to expand...
Click to collapse
Thanks for reporting, I guess it only works for newer Android versions then. Updated the OP.
flymetothemoon said:
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
Click to expand...
Click to collapse
Could you please post a link to TWRP 3.3.2.1 since I can't find it anywhere?
ad_on_is said:
Could you please post a link to TWRP 3.3.2.1 since I can't find it anywhere?
Click to expand...
Click to collapse
Sure. It was in the CarbonROM thread:
https://forum.xda-developers.com/xperia-z2-tablet/development/7-x-x-carbonrom-cr-5-1-t3654983
The one for windy you find here: https://mega.nz/#F!3NYBQKCA!jO0NQBZr08RaYqIbU7whxA
I am also coming from Carbon ROM and it is really not working... I now tried via Fastboot to install another older TWRP version. But the tablet is not reacting on 'adb reboot bootloader' (it shows the device for 'adb devices'). All it shows is a black screen and the blue LED light. Any idea how to flash the older TWRP version without bootloader? Normal Carbon ROM is working fine... Thanks!!!
emartino said:
I am also coming from Carbon ROM and it is really not working... I now tried via Fastboot to install another older TWRP version. But the tablet is not reacting on 'adb reboot bootloader' (it shows the device for 'adb devices'). All it shows is a black screen and the blue LED light. Any idea how to flash the older TWRP version without bootloader? Normal Carbon ROM is working fine... Thanks!!!
Click to expand...
Click to collapse
I tried with the Sony-Emma Tool which of course removed Carbon ROM - but left the bootloader as it was. So ADB / Fastboot is still not working. How did all th others that were involved solve the corrupt bootloader?
emartino said:
I am also coming from Carbon ROM and it is really not working... I now tried via Fastboot to install another older TWRP version. But the tablet is not reacting on 'adb reboot bootloader' (it shows the device for 'adb devices'). All it shows is a black screen and the blue LED light. Any idea how to flash the older TWRP version without bootloader? Normal Carbon ROM is working fine... Thanks!!!
Click to expand...
Click to collapse
@emartino,
If you are seeing a BLACK SCREEN with BLUE LED you are in Download mode (FASTBOOT mode). Try "fastboot devices" without quotes, and you should see the device serial number, or the tablet ID number. If you do not see the device number, you will need to install the fastboot drivers. They are different than the adb drivers. This can be done through device manager for WINDOWS. Info available in the forums if you need assistance with fastboot driver install.
To install TWRP, place the TWRP.img you want to use in your ADT-BUNDLE/sdk/platform-tools folder, or whatever your path is. Then open an elevated cmd prompt, while the tablet is in DOWNLOAD MODE, and enter this command "fastboot flash recovery recoveryname.img" no quotes. The recoveryname is the name of the TWRP img file you have downloaded and put in your platform-tools folder. After the flash completes enter "fastboot reboot-recovery" must put the DASH between reboot and recovery. This will boot into TWRP.
I may have given a little more instruction than you needed, but wanted to be clear.
Hope this helps....
ALSO, i seen requests for the older TWRP. Here is a link to my SHARED GOOGLE DRIVE folder. The older TWRP will be in the folder labeled the same. https://drive.google.com/drive/folders/0BwBZlgiV0lNiV2x5SFYwMGlmNUU?usp=sharing
Everything in my shared folder was shared within XDA. Original authors and devs can be found in the threads. Locate them and hit the thanks button for them sharing their work.
Thanks for the great description! As ADB was working I neglected to verify in the Windows Device Manager if the Fastboot drivers were also ok. And they were not... With the help of Zadig I then solved this driver-issue. Now fastboot was working fine and I could flash recovery with success. Only the mentioned 'fastboot reboot-recovery' was not available in the 'Minimal ADB and Fastboot' Version of fastboot, but this was then available once I installed the Android Studio + SDKs...
But still one thing is missing - I still cannot enter TWRP. Neither via the fastboot command, nor with Power-On + VolumeUp or VolumeDown... I always end up with the Android 6 standard Sony UI. Any additional idea what could have gone wrong? I even tried various TWRP versions (3.1, 3,2, 3.4), none could be started.
emartino said:
Thanks for the great description! As ADB was working I neglected to verify in the Windows Device Manager if the Fastboot drivers were also ok. And they were not... With the help of Zadig I then solved this driver-issue. Now fastboot was working fine and I could flash recovery with success. Only the mentioned 'fastboot reboot-recovery' was not available in the 'Minimal ADB and Fastboot' Version of fastboot, but this was then available once I installed the Android Studio + SDKs...
But still one thing is missing - I still cannot enter TWRP. Neither via the fastboot command, nor with Power-On + VolumeUp or VolumeDown... I always end up with the Android 6 standard Sony UI. Any additional idea what could have gone wrong? I even tried various TWRP versions (3.1, 3,2, 3.4), none could be started.
Click to expand...
Click to collapse
@emartino,
So when you flash the TWRP recovery img, through fastboot, then reboot to recovery or power off and then on when the led turns PINK (i think that is the color) start tapping the volume up button and the led should turn orange and boot to TWRP. I may have the colors off. But when you attempt to boot to TWRP what exactly does it do? Does the system boot to AICP or stock android recovery or what? Sorry not understanding the Android 6 Sony UI. Also, do you know the firmware you are running? If your not sure, no big deal, just tell us if when you turn the device on, does it show the SONY name in the center with XPERIA across the bottom?
Wait!!!!! are you installing TWRP on SONY Stock OS???? The versions of TWRP here are for custom roms. If you are using AICP or similar custom rom, then the above questions will help us narrow down the issue.
Hi, i can't boot into recovery after flashing.
When I try to boot directly into recovery, I get the following message:
Code:
% fastboot boot TWRP-3.4.0-sc-1_castor_20200606_1421.img
Sending 'boot.img' (13266 KB) OKAY [ 0.418s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Could you please help?
Related
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
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
You did the unlock bootloader bit in settings?
ReneX10 said:
You did the unlock bootloader bit in settings?
Click to expand...
Click to collapse
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
GigahurtzUK said:
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
Click to expand...
Click to collapse
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
ReneX10 said:
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
Click to expand...
Click to collapse
No other devices to test with.
I will have to try linux then. I just need a usb to make a linux live usb
Cheers
GigahurtzUK said:
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
Click to expand...
Click to collapse
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Is this the norm when changing recovery.img?
M_Kay said:
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Click to expand...
Click to collapse
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
noob2016 said:
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
Click to expand...
Click to collapse
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Thanks for the fast reply and help
M_Kay said:
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Click to expand...
Click to collapse
1st thanks for fast reply and help
im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP
i will report back after. Thanks
Works
Thanks it worked on pico gapp but not in aroma
followed the erase command and install TWRP again.
Many thanks
TWRP not working in Aroma Gapp need fix
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
noob2016 said:
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Thanks
robin0800 said:
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Click to expand...
Click to collapse
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
noob2016 said:
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
Click to expand...
Click to collapse
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
I will try
robin0800 said:
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
Click to expand...
Click to collapse
Thanks for the reply and also on my other post.
Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.
Many thanks.
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
msiviter said:
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
robin0800 said:
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.
Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.
Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.
Thanks for trying to help.
Yey!!!
robin0800 said:
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!
Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.
Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.
Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!
Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.
ROM for Sony Smartwatch 3 [LCA43, Android 5.1.1]
ROM Features:
Stock LCA43 base
Disabled OTA updates
Custom Kernel tetra_2.x
TWRP recovery
Tweaks
Click to expand...
Click to collapse
Versions
v 2.0
Kernel tetra_2.27.1
Minor tweaks
v 1.0
Stock LCA43 base
Kernel tetra_2.22
Disabled Low Bit Ambient Mode (thanks to andrewia)
Minor tweaks
Click to expand...
Click to collapse
Installation:
Put ROM to your virtual SDCard
Boot into TWRP recovery
Select "Install", and choose ROM zip file
After installation completed- reboot watch
If necessary - make full wipe
Click to expand...
Click to collapse
Downloads
SW3_rom_v2
TWRP recovery
Click to expand...
Click to collapse
Big thanks to scrubber for his ROM backup!
Code:
[COLOR="Red"]DISCLAMER[/COLOR]
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you getting fired because the alarm app failed. Please do some research if you
have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you.
If you like my work- Donate to me
Contributors:
alex6600
scrubber
Version Information
Status: Stable
Created 2016-04-27
Last Updated 2016-05-11
Reserved by OP
thanks alex6600.
can you upload original kernel to ?
edit : found on 4pda https://mega.nz/#!Rt8hBS5T!MHOufeqXYJqrcShyXG2_f3uLO7_ZlP_H6T0cVm0R4Hk
thanks again.
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
All is working well so far!
crunchybutternut said:
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
Click to expand...
Click to collapse
I honestly tried to use Marshmallow. Compiles kernels dozens of times. But no luck.
Reboots and lags does not suit me.
And decides to use 5.1.1, as more stable.
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
mount("ext4", "EMMC", "/dev/block/platform/sdhci.1/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
Click to expand...
Click to collapse
Fails saying device is busy, or is not ready...???
Hobbzey said:
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
Fails saying device is busy, or is not ready...???
Click to expand...
Click to collapse
Did you mount system in twrp before install?
Sent from my HTC One_M8 using XDA-Developers mobile app
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Hobbzey said:
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Click to expand...
Click to collapse
Rounded screen corners is a kernel feature, not ROM.
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Hobbzey said:
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Click to expand...
Click to collapse
Rom include kernel v. 2.22.
Today I posted 2.23 in kernel thread.
Sent from my HTC One_M8 using XDA-Developers mobile app
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
asecob said:
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
Click to expand...
Click to collapse
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Do you plan feature 6.0.1 update? What are benefits over stock...?
crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Thank you for your help, but unfortunately my watch didn't pass the white screen saying fastboot. PC was saying "waiting for device" for so much time. Am I doing something wrong?
crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
It's OK actually, just after twrp flash, I have "VIRTUAL SDCARD" on my windows pc, I put the zip and I flashed it in recovery.
Thanks
mickael91210 said:
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
Click to expand...
Click to collapse
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
alex6600 said:
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
Click to expand...
Click to collapse
Thanks.... I was editing my post in the same time....
Thank you
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
KittenSauce said:
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
Click to expand...
Click to collapse
Webserver was in the planned maintenance. Now everything is working as it should.
SuperSu work fine. You can download SuperSu_2.46 here
Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
please help me!
infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....
Which TWRP are you flashing and what rom were you on before the speed bump
NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.
Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!
tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
All function in a normal TWRP
Multi-language support
Support USB OTG!
Support decrypt /data!
Tips:
For unknown reason, after formatting userdata in TWRP, you won't be able to boot stock MIUI as encryption will fail. The fix is flashing factory images via MiFlash or just flash factory userdata.img via fastboot.
Decrypt Oreo userdata is NOT supported, I'll release an Oreo compatible build after it's a thing.The latest version already supports decrypting Oreo data
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery twrp.img" in command line
5. Reboot and enjoy it
Download:
https://twrp.me/xiaomi/xiaomiminote3.html
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/TeamWin/android_device_xiaomi_jason
Thank you for your work.Do you think you will continue this project?
We will be pleased if you continue...Best regards...
Great is this TWRP with OTG, thankyou very much!
Not working otg for me!!
Enviado desde mi Mi Note 3 mediante Tapatalk
Somebody has Test with xiaomi.eu rom 8.1.11? Touch in recovery works?
Does OTG still work with one of the newer dev ROMs installed?? After installing Xiaomi.eu ROM 8.1.11, OTG stopped working for me with a different TWRP version, TWRP_3.2.1-3_jason-v2, that I downloaded from another site.
@dianlujitao could you please update this recovery to the latest source? Thank you very much!
quyleanh said:
@dianlujitao could you please update this recovery to the latest source? Thank you very much!
Click to expand...
Click to collapse
yea would be very nice!
Vihru said:
yea would be very nice!
Click to expand...
Click to collapse
Here are links to newer builds I've come across.
http://www92.zippyshare.com/v/9LsITy1z/file.html
https://yadi.sk/d/Z9ollcvX3RbiZg
https://mega.nz/#F!CUhgUIia!_QSBBwWFvtgtP3DuIl4SmQ
Pumpino said:
Here are links to newer builds I've come across.
http://www92.zippyshare.com/v/9LsITy1z/file.html
https://yadi.sk/d/Z9ollcvX3RbiZg
https://mega.nz/#F!CUhgUIia!_QSBBwWFvtgtP3DuIl4SmQ
Click to expand...
Click to collapse
https://xiaomi.eu/community/index.php?threads/43306/
Here's another one, Im using this and it works so far I used it.
Skickat från min Mi Note 3 via Tapatalk
exionen said:
https://xiaomi.eu/community/index.php?threads/43306/
Here's another one, Im using this and it works so far I used it.
Click to expand...
Click to collapse
That's the second (direct) link I posted.
Its better you post the authors threads so users can read what to expect and the authors gets credited for their work
Skickat från min Mi Note 3 via Tapatalk
Wish someone could bring the Red Wolf Recovery Project to our Mi Note 3 devices...
Do the same thing as red wolf.
Twrp_3.2.1-0
yadi.sk/d/Z9ollcvX3RbiZg
hello,
I am not allowed to start a new topic (at least not yet) so I will ask here, maybe someone can help me.
I have unlocked my MiNote3 (official way). I have installed all needed drivers on the PC (win 7) and tried to install latest TWRP on the phone.
I managed to install it but is not booting in TWRP when I press power and Vol+ or any other buttons combination.
Any idea why is not working?
I also tried to install another ROM (global developer instead of stable) but the phone is not entering in EDL mode. It's just restarting.
Any idea why?
Thanks
I am using this TWRP and the unlock pattern always appears before starting the android. Do you know how to turn it off?
nicolae.fratila said:
hello,
I am not allowed to start a new topic (at least not yet) so I will ask here, maybe someone can help me.
I have unlocked my MiNote3 (official way). I have installed all needed drivers on the PC (win 7) and tried to install latest TWRP on the phone.
I managed to install it but is not booting in TWRP when I press power and Vol+ or any other buttons combination.
Any idea why is not working?
I also tried to install another ROM (global developer instead of stable) but the phone is not entering in EDL mode. It's just restarting.
Any idea why?
Thanks
Click to expand...
Click to collapse
When you flash TWRP using adb and if everything went well type after this command :
fastboot boot twrp.img
You need to immediately after flashing twrp ,boot into it and set it up so on the next restart it wont get overwritten by stock recovery.
So the full process should be like this :
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img
Yep i use that one too. Works like a charm!
dimi89 said:
When you flash TWRP using adb and if everything went well type after this command :
fastboot boot twrp.img
You need to immediately after flashing twrp ,boot into it and set it up so on the next restart it wont get overwritten by stock recovery.
So the full process should be like this :
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
Thank you for advice. It's working now but the TWRP doesn't stay installed.
After first reboot in Miui Stable is deleting it.
I tried everything but is just removed.
Shall I install custom rom (from Xiaomi.eu) when I enter first time in TWRP?
Will there be any issue when booting after the new ROM will be installed?
I just want to avoid bricking the devices.
Has anyone had trouble with the screen not registering touches in TWRP? I tried two different versions of TWRP and when my phone boots into it, the screen won't respond to any presses. It only worked the first time when I flashed xiaomi.eu.
Edit: I've realised that TWRP is unresponsive only if my phone doesn't vibrate when it restarts prior to entering TWRP. When it's unresponsive, I force a restart into TWRP by pressing the power button and volume up button simultaneously. The phone is never unresponsive when booting normally, so it's not clearly a hardware issue. However, it occurs in two different builds of TWRP that I've tried. Any suggestions?
Edit 2: I see I'm not the only one. https://xiaomi.eu/community/threads/twrp-3-1-1-0-no-working-touch-with-new-roms.42800/