Since there aren't any (recent) TWRP builds any more for our devices, I built an new image by using the binaries from [NUT]'s XZDualRecovery and the kernel from CyanogenMod 's latest Recovery. Additionally, I added some features and wrote an automated installer, for easy and foolproof installation.
It should work with all custom built ROMs, like Cyanogen, Omni, PAC, etc., but won't work with unmodified stock-kernels.
WARNING: Installing this and especially (mis)using TWRP has the potential to brick your device and/or causing a complete loss of your data! No guarantee, use your common sense! You have been warned..
Automatic installation (easier and safer): Just download the proper the zip-file for your device, boot into the current recovery (e.g. CyanogenMod Recovery from nightly builds, old TWRP or CWM) and install it!
Manual installation (only needed if no recovery is installed yet, or automated installation fails):
download the proper zip-file for your device
open a terminal/console
type (and allow):
Code:
su
goto the download directory, probably:
Code:
cd /sdcard/Download
unzip the installer (or use a file-manger):
Code:
unzip TWRP-*.zip
run (this is the dangerous part, make sure it's written correctly!):
Code:
dd if=twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Special thanks to [NUT] for allowing me to use his binaries and the TeamWin Recovery Project for creating this great tool!
ADB (conditions for access in TWRP): Make sure that you have enabled "Android debugging" and "Root access" for ADB in the Developer options of your ROM. Additionally, you need to connect your tablet once while Android is running and authorise ADB first, in order to be able to use it later in TWRP!
Changelog:
2015-08-23:
based on TWRP 2.8.7.0 and latest XZDualRecovery/CyanogenMod Recovery
added automated zip-installer
added CM's mkfs.f2fs (allows to format/create F2FS partitions)
added support for flashing and backing up recovery images
XDA:DevDB Information
[RECOVERY] TWRP (pollux/pollux_windy), Tool/Utility for the Sony Xperia Tablet Z
Contributors
BlackAfghan, [NUT], Dees_Troy, TeamWin Recovery Project, CyanogenMod
Source Code: https://github.com/TeamWin/Team-Win-Recovery-Project
Version Information
Status: Stable
Current Stable Version: 2.8.7.0
Stable Release Date: 2015-06-22
Created 2015-08-27
Last Updated 2015-08-27
Thank you, looks great with @z31s1g's reworked stock theme!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tapatalked that shiznit.
Thanks! Is working perfectly on my pollux! (and finally we have something dedicated to this model)
Sent from my A0001 using XDA Free mobile app
CyanogenMod Recovery installation works now!
Sorry, I found a bug in the installation procedure, which prevented automated flashing when CyanogenMod Recovery was used..
So if you are still with bare CyanogenMod Recovery, and haven't performed a manual installation yet, please download it again!
Thanks a Million for the fix
BlackAfghan said:
Sorry, I found a bug in the installation procedure, which prevented automated flashing when CyanogenMod Recovery was used..
So if you are still with bare CyanogenMod Recovery, and haven't performed a manual installation yet, please download it again!
Click to expand...
Click to collapse
It works!!! At last i got twrp on my cyanogenmod 12.1. Thanks a lot @BlackAfghan :highfive: :laugh: :highfive:
Keep getting 'error: device unauthorized. Please check the confirmation dialog on your device.' whenever I try to send anything through adb from my computer. I have updated to the latest adb, as older ones seemed to show me the device as being offline when using this version of TWRP.
Any ideas?
georgecarstoiu said:
Keep getting 'error: device unauthorized. Please check the confirmation dialog on your device.' whenever I try to send anything through adb from my computer. I have updated to the latest adb, as older ones seemed to show me the device as being offline when using this version of TWRP.
Any ideas?
Click to expand...
Click to collapse
Did you enable "Android debugging" AND "Root access" for ADB in the Developer options?
BlackAfghan said:
Did you enable "Android debugging" AND "Root access" for ADB in the Developer options?
Click to expand...
Click to collapse
Yes, but this happens while being in TWRP. The first time I am seeing this type of message when trying to push files from my computer to a device that is in recovery mode.
georgecarstoiu said:
Yes, but this happens while being in TWRP. The first time I am seeing this type of message when trying to push files from my computer to a device that is in recovery mode.
Click to expand...
Click to collapse
OK, I solved it. It's no bug, it's a feature..
You have to connect and authorise it first, while the ROM is running. Than it also works in TWRP next time!
I don't know if that behaviour really makes sense, but I guess Google or CyanogenMod intended it that way.. That would also explain why you needed a more recent version of ADB.
This recovery is based on Android 5.1.1, unlike the older TWRP builds which were based on 4.3 or even 4.2.
Maybe the TWRP-team can add that authorization dialogue in a future release.
BlackAfghan said:
OK, I solved it. It's no bug, it's a feature..
You have to connect and authorise it first, while the ROM is running. Than it also works in TWRP next time!
I don't know if that behaviour really makes sense, but I guess Google or CyanogenMod intended it that way.. That would also explain why you needed a more recent version of ADB.
This recovery is based on Android 5.1.1, unlike the older TWRP builds which were based on 4.3 or even 4.2.
Maybe the TWRP-team can add that authorization dialogue in a future release.
Click to expand...
Click to collapse
Thought so too eventually, although it doesn't make perfect sense. It is especially bad when you realize this after you have wiped the system clean in preparation for a clean install of a new ROM. Good that I had a USB stick and OTG adapter cable around, otherwise it would have been impossible.
The more interesting thing is how exactly does TWRP know that a computer is authorized or not and does this information actually survive a wipe of the system before the actual flash of a new one?
edit....
Just signed up to say thank you for this! Excellent work!
Any change this will be updated to the latest version?
Verstuurd vanaf mijn LG-H815 met Tapatalk
*justintime* said:
Any change this will be updated to the latest version?
Verstuurd vanaf mijn LG-H815 met Tapatalk
Click to expand...
Click to collapse
https://dl.twrp.me/pollux_windy/ - Seems you need to be on a MM rom for 3.x versions
scoobyjenkins said:
https://dl.twrp.me/pollux_windy/ - Seems you need to be on a MM rom for 3.x versions
Click to expand...
Click to collapse
No that's not working on Pollux (tablet LTE) when updating in Cyandelta twrp thinks it's a pollux_windy device.
And won't update. Because of Pollux update file.
*justintime* said:
No that's not working on Pollux (tablet LTE) when updating in Cyandelta twrp thinks it's a pollux_windy device.
And won't update. Because of Pollux update file.
Click to expand...
Click to collapse
Why not use a pollux one for pollux https://dl.twrp.me/pollux/ ? 3.0.2.0 works perfectly on CM13.1.
Rootk1t said:
Why not use a pollux one for pollux https://dl.twrp.me/pollux/ ? 3.0.2.0 works perfectly on CM13.1.
Click to expand...
Click to collapse
Haha nice..... Strange thing is on twrp.me Pollux is not mentioned in the device list. That's why I thought it was not available.
Thanks.
Can someone help me? I am unable to flash this recovery.
First i tried to root my Tablet Z (WiFi) with the Kingsroot and SuperSU Me method but i got stuck in a bootloop after the reboot.
But now i have rooted my device but i am unable to flash this recovery to use cm13.
My bootloader is unlocked and i gave the manual installation a try with the android terminal and it said it copied some files but nothing is happening.
I am unable to boot into TWRP
checks0n said:
Can someone help me? I am unable to flash this recovery.
First i tried to root my Tablet Z (WiFi) with the Kingsroot and SuperSU Me method but i got stuck in a bootloop after the reboot.
But now i have rooted my device but i am unable to flash this recovery to use cm13.
My bootloader is unlocked and i gave the manual installation a try with the android terminal and it said it copied some files but nothing is happening.
I am unable to boot into TWRP
Click to expand...
Click to collapse
for cm13 you need to use 3.x.x twrp.img.
Rootk1t said:
for cm13 you need to use 3.x.x twrp.img.
Click to expand...
Click to collapse
No, CM13 works fine with TWRP 2.8.7.0, as long as you don't use Adopted Storage!
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* 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.
*/
Unlocked Bootloaders Only!
Nightlies: http://download.cyanogenmod.org/?device=huashan
ChangeLog: http://www.cmxlog.com/12.1/huashan/
Report bugs only if:
- You are using the stock kernel
- You don't any mods/tweaks installed like xposed, etc.
- You searched in the thread for a solution or isn't a know bug.
- You have a log (if apply).
Please don't spam with useless posts here. Talk about Cm12.1 and do questions here: http://forum.xda-developers.com/xperia-sp/help/qa-cyanogenmod-12-1-t3070956
Don't ask for eta's! Be patient!
Screenshots: http://forum.xda-developers.com/devdb/project/?id=9523#screenshots
Thanks to:
-All the Cyanogenmod Team
-uberlaggydarwin
-asanan1
-Adrian DC
-Dark Passenger
XDA:DevDB Information
Cyanogenmod 12.1, ROM for the Sony Xperia SP
Contributors
Mrcl1450
Source Code: https://github.com/CyanogenMod/android_device_sony_huashan
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2015-04-29
Last Updated 2015-07-24
Instructions:
- Boot into Recovery
- Full Wipe (dalvik, system, data, cache)
- Flash Rom
- Flash Gapps (optional)
- Reboot
Note: You don't need to clean install if you are updating the rom.
Change to F2FS File System: This will delete all you user data!
- Reboot into recovery
- Plug the usb cable to computer
- Use the following adb commands
- adb shell mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/Cache
- adb shell mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/Userdata
- Reboot
How to do a logcat1º Download Logviewer and extract the files.
2º Connect the phone to pc an check if you have usb debugging active
3º Opening logview.bat it will ask for adb path (adb is in the logview folder)
4º Now you should see the log spamming about sensors. Right click in the message and press "Hide with this tag". Do this for the 5 sensors messages and you should be good to start logging.
5º Now go to the menu adb and click reset logs. After this reproduce the bug.
Example:
Camera app is crashing.
-Click reset log.
-Open camera.
-Disconnect device from pc to stop logging
-Go to file, save, give a name.
6º Send me the log.
All good now.
Thank you:good:
Why did u move the thread
daniyal.dssb said:
Why did u move the thread
Click to expand...
Click to collapse
Because CyanogenMod is considered original development
Can you please explain how to install the 'Alternative Recovery' in detail. I am getting bootloop when it try to install XZDualRecovery.
Steps taken:
1. After installing this ROM, we get simple CM Recovery.
2. Downloaded the installable zip of Xperia SP Dual Recovery. After getting installed, the phone reboots and gets stuck in bootloop.
Can you please help?
anmolkakkar said:
Can you please explain how to install the 'Alternative Recovery' in detail. I am getting bootloop when it try to install XZDualRecovery.
Steps taken:
1. After installing this ROM, we get simple CM Recovery.
2. Downloaded the installable zip of Xperia SP Dual Recovery. After getting installed, the phone reboots and gets stuck in bootloop.
Can you please help?
Click to expand...
Click to collapse
Did you tried the installer method?
CM12.1 for LBL is almost here. Tomorrow we should have the first test build in cm test group. I know I said yesterday but I'm still fixing build errors, sorry.
I will not create a thread until I have sure the rom is working.
Join us here
Mrcl1450 said:
CM12.1 for LBL is almost here. Tomorrow we should have the first test build in cm test group. I know I said yesterday but I'm still fixing build errors, sorry.
I will not create a thread until I have sure the rom is working.
Join us here
Click to expand...
Click to collapse
@Mrcl1450 i think you should tell us how we flash the imgs you stated ! like philz huashan once they are only recoveries and not kernels !
Theliakos said:
@Mrcl1450 i think you should tell us how we flash the imgs you stated ! like philz huashan once they are only recoveries and not kernels !
Click to expand...
Click to collapse
Done
You going to add it here ?
According to the battery log, whenever wifi is turned on and turned off, the battery log says that the wifi is still on despite the wifi switched off via the toggle.
It's a bug?
Mrcl1450 said:
Did you tried the installer method?
Click to expand...
Click to collapse
I had installed using the install.bat file only which comes in the zip package of the recovery. But got stuck in bootloop.
Can anybody help
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
Android_trucker said:
According to the battery log, whenever wifi is turned on and turned off, the battery log says that the wifi is still on despite the wifi switched off via the toggle.
It's a bug?
Click to expand...
Click to collapse
Nope, that is not a bug. If you go to Advanced settings inside the Wifi, you will see a few options.
Firstly, Turn off the 'Scanning Always' option.
Secondly (the reason why Wifi always shows 'ON' under Battery tab), switch 'Keep wifi on during sleep' to 'Never'. Doing this, after sometime when you check back, you'll be able to spot the difference. Wifi module actually is turned off after changing the above mentioned setting.
anmolkakkar said:
I had installed using the install.bat file only which comes in the zip package of the recovery. But got stuck in bootloop.
Can anybody help
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
Nope, that is not a bug. If you go to Advanced settings inside the Wifi, you will see a few options.
Firstly, Turn off the 'Scanning Always' option.
Secondly (the reason why Wifi always shows 'ON' under Battery tab), switch 'Keep wifi on during sleep' to 'Never'. Doing this, after sometime when you check back, you'll be able to spot the difference. Wifi module actually is turned off after changing the above mentioned setting.
Click to expand...
Click to collapse
Fyi I have turned off "scanning always on" for location - however I didn't change the wifi keep as always on when sleeping, will do that and see if it makes a difference.
...I did this ->Flashed stock rom-->root-->installed xzdualreocvery-->flashed -20150425- rom-->reboot--> flashed supersu-->reboot-->lost xzdualrecovery-->intalled it again--> booted to recovery and tried flashing gapps but failed in both twrp and philz touch....and im unable to boot to CWM as CM recovery still exists....how to solve this?.....should i have to flash a cm11 based 4.4.4 rom before flashing your rom?.....which 4.4.4 rom should i download?.... Pls help dev.....
First LBL test build is now up in the test group.
Join us here
backstaber said:
...I did this ->Flashed stock rom-->root-->installed xzdualreocvery-->flashed -20150425- rom-->reboot--> flashed supersu-->reboot-->lost xzdualrecovery-->intalled it again--> booted to recovery and tried flashing gapps but failed in both twrp and philz touch....and im unable to boot to CWM as CM recovery still exists....how to solve this?.....should i have to flash a cm11 based 4.4.4 rom before flashing your rom?.....which 4.4.4 rom should i download?.... Pls help dev.....
Click to expand...
Click to collapse
Try the other way (mentioned at second post) to flash recovery imgs using Rashr then flash GApps
OsGhaly said:
Try the other way (mentioned at second post) to flash recovery imgs using Rashr then flash GApps
Click to expand...
Click to collapse
No flash tangerine via rashr,don't flash rashrs recovery as it changes the fota
kunal9007 said:
No flash tangerine via rashr,don't flash rashrs recovery as it changes the fota
Click to expand...
Click to collapse
And where do i get this tangerine kernel?.....n why is not right to follow the xzdualrecovery method??.....
This is the OnePlus 5's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Thaaaanks but has anyone rooted there op5 with this yet? Does it actually work? Probably does but just would like to make 110% sure
icem8n said:
Thaaaanks but has anyone rooted there op5 with this yet? Does it actually work? Probably does but just would like to make 110% sure
Click to expand...
Click to collapse
This tool cant directly root your phone, but it can unlock your bootloader and help you to flash a twrp. If you want to root your phone you can flash twrp and then flash the root zip through twrp
Bootloader successfully unlocked
I´ve also flashed this Chinese TWRP with your tool due to my eagerness
and finally rooted with Magisk
@mauronofrio your efforts are really appreciated
Deacon-Frost said:
Bootloader successfully unlocked
Click to expand...
Click to collapse
Perfect:good:
Awesome looking tool. I'll be downloading and donating as soon as I get my OP5 on Monday.
I plan on running stock software for awhile but can I simply unlock, flash TWRP, and flash the same SuperSU I always use for custom ROMs?
biglilsteve said:
Awesome looking tool. I'll be downloading and donating as soon as I get my OP5 on Monday.
I plan on running stock software for awhile but can I simply unlock, flash TWRP, and flash the same SuperSU I always use for custom ROMs?
Click to expand...
Click to collapse
Yes, i don't know if there are a supersu specific version must be flashed, but yes, unlock the bootloader, flash the twrp and then flash supersu or magisk. I don't know if you need to disable dm-verity before reboot but i think yes
was impatient... and got everything working... unlocked, TWRP recovery, and then Magisk rooted. woot woot.!!
now hopefully there is a working xposed
AznMTboy said:
was impatient... and got everything working... unlocked, TWRP recovery, and then Magisk rooted. woot woot.!!
now hopefully there is a working xposed
Click to expand...
Click to collapse
Perfect:good:
Made a backup before flash xposed
perfect！thank you！
Which version of magisk 13 you use?
Gesendet von meinem Nexus 6P mit Tapatalk
cant install twrp
i cant install twrp and also cant root the phone, some one can help me? i try all i can to get it work....
this is what i get always..
hounter17 said:
i cant install twrp and also cant root the phone, some one can help me? i try all i can to get it work....
this is what i get always..
View attachment 4192075 View attachment 4192076
Click to expand...
Click to collapse
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
Craxx said:
Which version of magisk 13 you use?
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
I have not tested it, i think the last should work
mauronofrio said:
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
the problem is that i can get it flashed
Click to expand...
Click to collapse
hounter17 said:
mauronofrio said:
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
the problem is that i can get it flashed
Click to expand...
Click to collapse
You are the first until now. To flash the twrp you need to have an internet connection, because the tool before download the recovery and then flash it. If you have made all of this try to delete the downloaded recovery and flash it again (maybe the download has failed). To delete the downloaded recovery you need to go in the advanced options and use the "Delete Files" (top right of the page) button to delete what you want (in this case you need only to delete TWRP recoveries). Tell me if you solve
Click to expand...
Click to collapse
Someone said that TWRP will only survive for one reboot. I've flashed yesterday that Chinese TWRP and rooted with Magisk. My experience is that TWRP will stay. I've booted today three times into TWRP. Everything seems to be as normal as it should be.
Deacon-Frost said:
Someone said that TWRP will only survive for one reboot. I've flashed yesterday that Chinese TWRP and rooted with Magisk. My experience is that TWRP will stay. I've booted today three times into TWRP. Everything seems to be as normal as it should be.
Click to expand...
Click to collapse
Perfect so the problem is another one. When the twrp is booted for the first time it automatically delete or hide the stock recovery so if you flash the twrp and you boot directly from fastboot to twrp, the twrp will survive but if you flash the twrp and power one normally the phone the stock recovery will be restored. So when you flash the twrp, directly boot in it, from the tool you need to check "And boot it" option to boot it directly after flash.
mauronofrio said:
hounter17 said:
You are the first until now. To flash the twrp you need to have an internet connection, because the tool before download the recovery and then flash it. If you have made all of this try to delete the downloaded recovery and flash it again (maybe the download has failed). To delete the downloaded recovery you need to go in the advanced options and use the "Delete Files" (top right of the page) button to delete what you want (in this case you need only to delete TWRP recoveries). Tell me if you solve
Click to expand...
Click to collapse
i try all and it tucks here:
View attachment 4192182
Click to expand...
Click to collapse
hounter17 said:
mauronofrio said:
i try all and it tucks here:
View attachment 4192182
Click to expand...
Click to collapse
i'm unable to load this image and please be more specific, when you got this problem?
Click to expand...
Click to collapse
mauronofrio said:
hounter17 said:
i'm unable to load this image and please be more specific, when you got this problem
Click to expand...
Click to collapse
im sorry about the troubles... i unlock the bootloader i enable usb debuging and i reboot it in fastboot mode. them i use the tool to flash the recovery but when the cmd screen gets on it stucks and doesnt finish the process...
i dont know what to do in this point
i also see that in fastboot mode screen appear that the product name was "QC_reference_phone" and the bootloader and the baseband brands are empty.
the device state was "unlocked"
Click to expand...
Click to collapse
Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
158 views, 20 downloads and not one reply.
Smashing guys. :good:
4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?
Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!
notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.
It will not work on SM-A750FNXXU1ARIC?
Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse
sorry
ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542
ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop
A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes
A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot boot twrp.img
Now you are booted into TWRP, but it is NOT permanently installed. To install it permanently, use the "Flash current TWRP" option in the Advanced menu. This will install the currently booted TWRP permanently to both slots. NOTE: If you were previously rooted, you will need to re-install the root apk/zip as the TWRP install will overwrite it!
Alternate Installation Method (requires prior TWRP installation, or if fastboot booted into TWRP already, start at step 3):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select "Install Recovery Ramdisk" from the partition list and swipe to flash
(Optional) If previously rooted, re-install root apk/zip, as the TWRP install will overwrite root.
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
3.5.2_11-2:
Add vendor_boot to partition list
3.5.2_11-1:
Update super and qti_dynamic partitions size
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
USB-OTG not working
Battery Status not working
TWRP Upstream
Android 12 decryption only works if no password/PIN/pattern is set (i.e. only default password)
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse
mine
I'll take 2
Maybe 3 to be safe
Thank you for this! Great to see a twrp thread
Pinch me, I must be dreaming!
Edit: it works, but how to enter it again?
Captain_Throwback said:
USB-OTG not working
Click to expand...
Click to collapse
Is it temporary? Or at the moment it can not be fixed?
P.S. Thank you for your release!
dron39 said:
Is it temporary? Or at the moment it can not be fixed?
P.S. Thank you for your release!
Click to expand...
Click to collapse
It seems you asked the same question twice, but the answer is that the OP has the current status. If there are any changes in the future, it will be updated.
Undead_Son said:
Pinch me, I must be dreaming!
Edit: it works, but how to enter it again?
Click to expand...
Click to collapse
Once you're booted into TWRP, you can use the "Flash current TWRP" option under Advanced to install it permanently. If you were rooted, you'll then have to re-flash the root apk/zip.
Captain_Throwback said:
If you were rooted, you'll then have to re-flash the root apk/zip
Click to expand...
Click to collapse
What is partition to where it should be flashed?
You wrote that we will need to reflash root (.apk or .zip). But what if I have also custom kernel installed (Kirasakura) ?
Shuld I "permanently" install recovery on stock kernel or it doesn't matter ? I just want to clarify, because as far as I understand magisk patches boot.img ?
And each time after firmware update we will need to reflash twrp, correct?
And I haven't found information about our device on twrp.me (Devices->Asus). Will you add it there later?
dron39 said:
What is partition to where it should be flashed?
Click to expand...
Click to collapse
I don't understand your question. When you flash the root apk/zip, it'll take care of flashing where it's supposed to go. You don't have to worry about any partitions.
dron39 said:
You wrote that we will need to reflash root (.apk or .zip). But what if I have also custom kernel installed (Kirasakura) ?
Click to expand...
Click to collapse
I don't know about custom kernel, but you can always flash it again after you re-flash the root zip to make sure it persists if you're unsure. Flashing it again won't hurt anything.
dron39 said:
Shuld I "permanently" install recovery on stock kernel or it doesn't matter ? I just want to clarify, because as far as I understand magisk patches boot.img ?
Click to expand...
Click to collapse
It's up to you whether you want to install TWRP permanently, but the instructions focus on fastboot booting. I'm not sure how Magisk is relevant here, as that has no effect on TWRP.
dron39 said:
And each time after firmware update we will need to reflash twrp, correct?
Click to expand...
Click to collapse
Yes, but if you install the update in TWRP, you can choose the option to "Automatically install TWRP after zip" to keep TWRP if you have it permanently flashed.
dron39 said:
And I haven't found information about our device on twrp.me (Devices->Asus). Will you add it there later?
Click to expand...
Click to collapse
This is a prerelease version. The Android 11 TWRP tree hasn't been officially released. The ZF8 page will be there once the release is official. There's already a markdown patch ready for that time.
What does "unable to locate storage device" mean?
Hi,
I unlocked my device with the asus unlocker and rooted succesfully.
But when I try flash TWRP with fastboot I get:
Sending 'boot.img' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Has anybody an idea whats the issue here?
Regards,
Hyper
HyperCriSiS said:
Hi,
I unlocked my device with the asus unlocker and rooted succesfully.
But when I try flash TWRP with fastboot I get:
Sending 'boot.img' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Has anybody an idea whats the issue here?
Regards,
Hyper
Click to expand...
Click to collapse
Are you sure you're in bootloader, and not fastbootd? Also please confirm that you're attempting to fastboot boot as per the OP instructions.
Captain_Throwback said:
Are you sure you're in bootloader, and not fastbootd? Also please confirm that you're attempting to fastboot boot as per the OP instructions.
Click to expand...
Click to collapse
Yes, I was in fastbootd
Thank you so much, it is working very well
New test version uploaded. Thanks to @micky387 for his help with the TWRP tree!
With newest version MTP does not work anymore.
I deleted the device and the new detected device name is different. It was "Zenfone 8" before and now "Asus_I006D"
HyperCriSiS said:
With newest version MTP does not work anymore.
I deleted the device and the new detected device name is different. It was "Zenfone 8" before and now "Asus_I006D"
Click to expand...
Click to collapse
I changed absolutely nothing related to MTP, and it continues to work fine here.
The device name in TWRP was always ASUS_I006D. If you happened to connect the device to your PC in Android first, then that's probably why it showed up as "ZenFone 8". But when you deleted it the TWRP default got set as the name.
Can anyone else confirm whether MTP is working for them on the latest version? If you're using Windows, it's possible some update broke something on your end.
Yes, Microsoft often messed with the MTP drivers. In the device manager I deinstalled everything related to the Zenfone and reinstalled, but still does not work.
TWRP throws some errors. Maybe this is the issue? I also reinstalled it again.
HyperCriSiS said:
Yes, Microsoft often messed with the MTP drivers. In the device manager I deinstalled everything related to the Zenfone and reinstalled, but still does not work.
TWRP throws some errors. Maybe this is the issue? I also reinstalled it again.
Click to expand...
Click to collapse
That looks very broken. But a screenshot is very unhelpful to determine root cause. The OP makes it clear that logs are required to get assistance. So please provide a recovery log and logcat so that I can review the problem.
Is Android working okay? Seems like something else is going on there. Did you install anything? I'm going to need more details of how exactly you got to this point.