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/
Related
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
Unofficial TWRP 3.2.0-0 Mi Note 2 (scorpio)
Unofficial TWRP build for the Mi Note 2.
TWRP 3.1.1-0 Changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Compatible with TWRP Backup and Recuse Tool for PC
Download Link
twrp-3.2.0-0-scorpio.img
Update 14/07/17
Update TWRP to 3.2.0.0
Update 14/07/17
Update TWRP to 3.1.1-0
New streamlined kernel
Add F2FS support
Improved Android 7.0 Miui compatibility - If issues persist please let me know
Update 30/05/17
All features working as expected
Screenbrightness adjustment is now responding accurately with a suitable default brightness
Updated kernel.
Much quicker booting.
Installation Guide
Once you've got you're bootloader unlocked with MiFlash and run through all the Xiaomi hoops to unlock your bootloader and have a fastboot installed on your PC:
Simply place the download where you like and then open a command prompt and type
fastboot flash recovery /path/to/twrp-3.1.1-0-scorpio.img
BONUS THEMES & File Manager
Plus as a special treat I'm including a full guide below to use Materialised Theme and Aroma File Manager both working within TWRP 3.1.1-0
Themes available from here
1. Install the latest TWRP linked above.
2. Download one of the themes above (see screenshots below for recommendations)
3. Download Aroma File Manager for TWRP from here
4. Once booted into TWRP select Install and choose the theme.zip you've downloaded.
5. You will instantly see the theme applied
6. Click Install again and this time select "materialised_aromafm_200-b7.zip"
7. Once that zip has completed installing open the Materialised Options (the art palette icon on the top right)
8. Tick the box that says "Use Aroma File Manager"
9. Press back and select "File Manager" from the list.
10. Swipe to start Aroma File Manager
11. Enjoy!!
See attached thumbnails for themes in action.
Source:
https://github.com/stonetrapping/twrp_android_device_scorpio
Special thanks to:
z31s1g for the wonderful themes and the Aroma File Manager
Thanks, dude !
Working OK for both MIUI and AOSP based ROMs?
Working with ASAP and MIUI and encryption all round.
That's great! Thanks for sharing
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
stephendt0 said:
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
Click to expand...
Click to collapse
You can keep dm-verity. After flashing I'd suggest leaving fastboot and booting straight into recovery via fingerpress.
Flashing SuperSU or Magisk or similar should ensure survival of TWRP if it's being overwritten.
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
1. I've noticed the slow speed too, I'm 100% sure why it's happening but I have some ideas.
2. The same ideas will hopefully address this issue.
It was a quick and dirty port since there was no native TWRP, I haven't had the time yet to improve it but I'll build an updated release based on 8.2.5.0 sometime soon and look to making it official.
Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Thanks, StoneTrapper !!
I will check later after flashing new version !
StoneTrapper said:
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Click to expand...
Click to collapse
Really fast at boot, maybe because is a release from the future (30052017 )
great job, thanks man!
Can not use usb otg function ...
Can not use usb otg function ...
Otg function, no work
[email protected] said:
Can not use usb otg function ...
Otg function, no work
Click to expand...
Click to collapse
I've had no issues with USB-OTB, with any standard formatted flash drive (FAT32, NTFS, EXT4).
This is also the first I've heard of anyone having such an issue.
Does the OTG drive mount successfully in whatever ROM you're using? Is it attached prior to booting to TWRP? Can you provide additional information.
TWRP doesn't like remounting the same USB multiple times - i.e if you unplug the USB while in TWRP, and then reattach the same drive it won't remount it.
Sorry to feedback lately because I was too busy in past 2-week.
Well, new TWRP is working well.
The only one problem: If I want to upgrade firmware, TWRP will be replaced by MIUI stock recovery after flashing new version of MIUI ROM.
It's pretty annoying because I need to get into fastboot mode then flash TWRP. After that, entering TWRP and flash lineage OS ...
Is it possible to be fixed in next coming version ?
Kris
May I know how to flash the TWRP rom?
I'm on MIUI.eu ROM, can I flash full global MIUI original ROM with TWRP without bricking the phone ??
Before on Redmi note 3 u can't flash original ROM without bricking the phone, u needed special TWRP (zxc version) or modify the ROM
Can you explain me ?
Envoyé de mon Mi Note 2 en utilisant Tapatalk
Link down.
chemha said:
Link down.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
StoneTrapper said:
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
Click to expand...
Click to collapse
It does not work. No download link found
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:
[I]#include <std_disclaimer.h>
/*
* Your warranty is not 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 recovery
* 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.
*
*/[/I]
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels (Not Android 10), if not please file a request to the maintainer.
To follow up, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS
[STABLE]
3.3.1-0: Initial official release!
Download:
https://twrp.me/google/googlepixel3a.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Beta
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27
Created 2019-06-27
Last Updated 2019-11-15
Reserved
Incredible job thank you!
Thank you for all your guys hard work. I can't imagine the work involved
Congratulations and thank you for your time and effort.
This is awesome brother,,,if it werent for you we would not have a custom recovery! Thank you!
Thanks mate
Thank you!!!!!!!!
Shoud we allow Modifications or Keep Read Only when we boot for the first time?
WOOHOO!!! Thank you for this, it's so exciting!!!
Quick question: the instructions say there is also a zip to download but I didn't see it in anywhere. Do we really need it? TWRP did boot up temporarily just fine!
zombioptic said:
WOOHOO!!! Thank you for this, it's so exciting!!!
Quick question: the instructions say there is also a zip to download but I didn't see it in anywhere. Do we really need it? TWRP did boot up temporarily just fine!
Click to expand...
Click to collapse
Read the note
Fentadroid said:
Read the note
Click to expand...
Click to collapse
Ah yes... My bad!
Thank you for TWRP mate
Sent from my Pixel 3a using Tapatalk
Great job, now all we need is some proper rooting/with magisk, and everything will be golden!
jayyskittles said:
Great job, now all we need is some proper rooting/with magisk, and everything will be golden!
Click to expand...
Click to collapse
Magisk pushed a cannery build that roots for the Pixel 3s on Q4 last night.
Also, the Magisk dev has a Pixel 3 on Q4 (not 3a) that is his daily driver. So because of the similar file systems, it's good news for us on P3a.
Edit:
https://twitter.com/topjohnwu/status/1144159892430659584?s=09
12paq said:
Magisk pushed a cannery build that roots for the Pixel 3s on Q4 last night.
Also, the Magisk dev has a Pixel 3 on Q4 (not 3a) that is his daily driver. So because of the similar file systems, it's good news for us on P3a.
Edit:
https://twitter.com/topjohnwu/status/1144159892430659584?s=09
Click to expand...
Click to collapse
Does that canary build work for us?
jayyskittles said:
Does that canary build work for us?
Click to expand...
Click to collapse
Only if we get a Q compatible twrp. Or if someone can provide the Q beta 4 boot.img
jayyskittles said:
Does that canary build work for us?
Click to expand...
Click to collapse
For root It should even without TWRP. Pull the boot.img from the beta, modify it with Magisk Manager then Fastboot flash the modified boot image.
I have not tried it yet. I am still trying to spell canary correctly. :laugh:
Not sure how many of you have tested this thing out, but I can confirm it works on the stock rom. I had to root for a Titanium Backup, so I flashed Magisk through TWRP and rebooted just fine.
Finnaly!! Good work to OP who worked hard to get us this TWRP!
12paq said:
For root It should even without TWRP. Pull the boot.img from the beta, modify it with Magisk Manager then Fastboot flash the modified boot image.
I have not tried it yet. I am still trying to spell canary correctly. :laugh:
Click to expand...
Click to collapse
I wanted to try it tomorrow, but it seems ill better wait for a new update on the canary build:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md
-> see the notes for the latest build. Afaik we need logical partition support or root will not work (correctly)
I'm also thinking if i can just pull boot.img via twrp backup (then extract if needed) or should i pull it via fastboot.
Really the userdata wipe holds me back (when OEM unlocking the device.)
Guess i will wait when root is successfully reported on P3 by topjohnwu, just to be sure.
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?
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>
/*
*
* 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.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.4.0-0-def-test2.img
XDA:DevDB Information
TWRP, Tool/Utility for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-29
Created 2020-08-29
Last Updated 2020-09-14
So who is going to be the 1st to try this? I am afraid to muck up my phone
jharkness316 said:
So who is going to be the 1st to try this? I am afraid to muck up my phone
Click to expand...
Click to collapse
I'm not the first to test it, but I booted into it and flashed some stuff. It won't brick your phone, thats for sure.
Does this mean we can finally do backups of our roms like other phones along with installing like other roms?
I thought that I read there was no way to do an Android 10 backup due to different? ways of the architecture of Android and permissions.
It works
jharkness316 said:
Does this mean we can finally do backups of our roms like other phones along with installing like other roms?
I thought that I read there was no way to do an Android 10 backup due to different? ways of the architecture of Android and permissions.
Click to expand...
Click to collapse
Ive tested it on my Motorola one Hyper (Model: XT2027-3) and it works!
After booting into the twrp.img file you can make a backup.
Cause of a stupid mistake i had bricked my phone, but the backup i made fixed to normal again.
Ive installed magisk 20.4 and the 'Disable_Dm-Verity zip' after that, no problems at all.
Joepeke3 said:
Ive tested it on my Motorola one Hyper (Model: XT2027-3) and it works!
After booting into the twrp.img file you can make a backup.
Cause of a stupid mistake i had bricked my phone, but the backup i made fixed to normal again.
Ive installed magisk 20.4 and the 'Disable_Dm-Verity zip' after that, no problems at all.
Click to expand...
Click to collapse
Thank you so much
This weekend's project
Booting TWRP is working for me but can't seem to flash it permanently no matter what I try. I even booted into TWRP and flashed the TWRP image file. Any ideas?
Edit: HELP! I tried flashing the latest OmniRom through TWRP and the phone no longer turns on. There's no response when I connect it to my PC or power directly. Please, please, please help me.
2nd Edit: The dev helped me get phone working again. This recovery doesn't seem to play nice with my variant.
Update : https://drive.google.com/file/d/1s1uPhCMuybw7ognlvUGWi5MEaVEa4XgQ/view?usp=sharing
Fix booting TWRP when flashed
vache said:
Update : https://drive.google.com/file/d/1s1uPhCMuybw7ognlvUGWi5MEaVEa4XgQ/view?usp=sharing
Fix booting TWRP when flashed
Click to expand...
Click to collapse
Can confirm, it does persist.
Very good! it works normally!
m666p said:
Can confirm, it does persist.
Click to expand...
Click to collapse
I have to flash it on fastbootd?
Zaisxda said:
I have to flash it on fastbootd?
Click to expand...
Click to collapse
Yup or regular fastboot
m666p said:
Yup or regular fastboot
Click to expand...
Click to collapse
And can i flash omnirom via recovery?
Zaisxda said:
And can i flash omnirom via recovery?
Click to expand...
Click to collapse
Yup, just wipe and flash it twice.
m666p said:
Yup, just flash it twice.
Click to expand...
Click to collapse
how twice? can you explain more?
Zaisxda said:
how twice? can you explain more?
Click to expand...
Click to collapse
Go the the omnirom thread, I was just talking to someone else about it.
MicrosoftBug said:
Booting TWRP is working for me but can't seem to flash it permanently no matter what I try. I even booted into TWRP and flashed the TWRP image file. Any ideas?
Edit: HELP! I tried flashing the latest OmniRom through TWRP and the phone no longer turns on. There's no response when I connect it to my PC or power directly. Please, please, please help me.
2nd Edit: The dev helped me get phone working again. This recovery doesn't seem to play nice with my variant.
Click to expand...
Click to collapse
i've also got a brick here now for the same reason. didn't realize it was a specific variant, especially since flashing unofficial with fastbootd worked fine before. can i get some help?
ashkitten said:
i've also got a brick here now for the same reason. didn't realize it was a specific variant, especially since flashing unofficial with fastbootd worked fine before. can i get some help?
Click to expand...
Click to collapse
Check the OmniROM thread.
Sent from my BLA-L29 using Tapatalk
MicrosoftBug said:
Check the OmniROM thread.
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
thank you! i didn't see that.
TWRP can't decrypte the data when Omni have system password.