{
"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"
}
Enjoy Your Asus Zenwatch 3-Swift-AND-FEEL THE SPEED
Please read the instructions and notes before flashing anything.
Code:
###Disclaimer###
I am not responsible if your phone will be damaged, broken, boot looping. YOU are choosing to make these modification.
WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
Requirements
- An unlocked bootloader
- adb and fastboot drivers
- TWRP recovery
You can download adb and fastboot package from here. https://developer.android.com/studio/releases/platform-tools.html#download
--------------------
HOW TO FLASH THE ROM
0- Attach your devices to your PC and enable USB Debugging
1- Boot your device with TWRP from
Custom-TWRP-thanks to @Maxr1998
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot boot name-of-the-twrp.img
Or
fastboot flash recovery name-of-the-twrp.img
2- Now move the build/ROM to your watch
3- Make a backup - there's always 1% chance something goes wrong.
4- Full wipe is recommended....Wipe data/Factory reset
5- Flash the ROM
6- Reboot
7- Setup your initial settings
8- GO TO MY KERNEL THREAD AND DOWNLOAD THE LATEST VERSION AND FLASH THAT.
9- Done
--------------------
HOW TO ACHIEVE ROOT
- Reboot into TWRP
- Copy the root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package inside your device
- Flash the root-wear. zip and reboot
- Open busybox and install
- Done
--------------------
HOW TO ACHIEVE ROOT AFTER FLASHING THE NEW BOOT IMAGES
- DOWNLOAD THE LATEST VERSION FROM (KERNEL THREAD)
- Reboot into TWRP
- Flash the new kernel and reboot
- Complete your device setup
- Reboot into TWRP again
- Flash root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package
- Reboot
- Open busybox and install
- Done
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
KERNEL/BOOT IAMGES FOR LATEST UPDATE
-NOTE: YOU NEED TO FLASH THE ROM FIRST (Setup your initial settings) AND THEN FLASH THE LATEST KERNEL FROM KERNEL THREAD
ROMs-ANDROID_WEAR_2.0 [DEODEXED][ODEXED] [LATEST]
Short changelog-[DEODEXED] [27/8/2018]
- Based on latest release NWD1.170623.001- June_1_2017 security patch
- Kernel is compiled with LINARO GCC: 4.9.4-Optimized/based on latest available source 3.18.24 Kernel
- All *apk system/data, system/app, Framework & priv-app zipalign & optimized for better RAM utilization
- Can be root - Flash the following Root/BusyBox if you want to achieve root access.
- dm-verity disabled
- forced-encryption disabled
- SELinux permissive
- init.d script support
- Tweaked for Best Performance
- adb is enabled by default
- Update script
- Tweaks to achieve better battery life
- Clean
------------------------------------------------------------
Download-Link [LATEST-27/8/2018]
BUILD_WEAR_2.0 [DEODEXED] /ROM
MD5:0ceb5c2c3261cb0026b1365940efc839
------------------------------------------------------------
BUILD_WEAR_2.0 [ODEXED] /ROM
MD5:131ab240ec04f8a5ecbf7acb6d42ad51
------------------------------------------------------------
Download-Link
ROOT AND BUSYBOX_1.5_AND_2.0
------------------------------------------------------------
------------------------------------------------------------
ROMs-MWG68_ANDROID_WEAR_1.5
Download-Link
Deodexed/ROM
MD5:3913568ed1d59d90340962b24a3a46b7
Odexed/ROM
MD5:ee3dbf24fcc19a713ddcf819e24c43bb
----------------------
Kernel Source
https://github.com/toffyjan/Asus-zenwatch-3-kernel
----------------------
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF COFFEE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE-HEREhttps://www.paypal.me/JANJANXDA
paypal.me/JANJANXDA
----------------------
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 thanks for script and twrp recovery
@superR for the kitchen
@Captain_Throwback
@SuperThomasLab for great tools
-Take a look here. And support the dev.
@Xmaster24 for system-less root-
Willi Ye for his great app
-Take a look here. And buy the donate version to support the dev.
Please always support devs and others (soon).
Thanks! What's the decryption key? Apparently I need that to download.
ups gonna fix it soon.
go gO
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
jobarr said:
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
Click to expand...
Click to collapse
Offcourse flashing with TWRP..You need to wipe your data too. And fast boot takes some time. 5-10 minutes. I tested on two watches and it works. Be patient
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
janjan said:
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
Click to expand...
Click to collapse
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
jobarr said:
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
Click to expand...
Click to collapse
Tell me what you did. You procedure please.
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
jobarr said:
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
Click to expand...
Click to collapse
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Maxr1998 said:
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
Click to expand...
Click to collapse
I will check it out. need to prepare my self for my exam ..I try to
janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
Yes. Ahhh....ok, lemme try that.
janjan said:
I will check it out. need to prepare my self for my exam ..I try to
Click to expand...
Click to collapse
Sure, school's always first. Good luck in your exam!
Maxr1998 said:
Sure, school's always first. Good luck in your exam!
Click to expand...
Click to collapse
Thank you. I didn't add too much right now. But we will do that. My last exam in wireless communication.
janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
It still won't leave the ASUS screen after 5 minutes. :/
jobarr said:
It still won't leave the ASUS screen after 5 minutes. :/
Click to expand...
Click to collapse
Try to flash the kernel after flash the build. Or
Flash the root after flashing the build or
Wipe everything also your system and then flash the ROM. You have to wipe everything.
I just test again and it seems working without and issue
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
jobarr said:
Thanks! What's the decryption key? Apparently I need that to download.
Click to expand...
Click to collapse
Maxr1998 said:
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
Click to expand...
Click to collapse
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
janjan said:
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
Click to expand...
Click to collapse
Yeah, dm-verity is a pain.. Shouldn't SuperSu also patch dm-verity? Might be worth a try as well.
Related
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
{
"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:
/*
* 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 doing this to your device
* 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.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.1_10-A11_2b1_ianmacd.img
twrp-a71-3.5.1_10-A11_2b1_ianmacd.tar
Multidisabler zip by Ianmacd
VBMeta disabler
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
17/03/21: Release for Android 11 BL
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71
reserved 1
reserved 2
Sorry for the delay, this TWRP should work perfectly with Android 11 BL
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
donkeyman1234 said:
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
Click to expand...
Click to collapse
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
ban.codrut said:
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
Click to expand...
Click to collapse
I haven't used the Link to Windows feature, I don't really have a good understanding of what you mean.
ShaDisNX255 said:
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
Click to expand...
Click to collapse
I took a shot of log.
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
viktor92 said:
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
Click to expand...
Click to collapse
Yes, you must format and flash multidisabler.
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Pupet_Master said:
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Click to expand...
Click to collapse
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
ShaDisNX255 said:
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
Click to expand...
Click to collapse
Thanks Friend
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Nobby52 said:
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Click to expand...
Click to collapse
Yes, you have to go back to the main menu
Thank you, I'll try it again.
Norbert
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Nobby52 said:
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Click to expand...
Click to collapse
What ROM are you trying to root?
Are you Rooting with Magisk or Super SU? Do you install SUper SU App or Magisk Manager after?
About the reset, did you flash the multiboot disabler after flash the root zip file?
I root the original Samsung Stock Rom. "A715FXXU3BUB5_A715FOXM3BUB6_DBT". I followed the instructions here exactly.
First unroot and debug mode
1.) download mode
2.) with Odin TWRP + VBMeta-Disabler
3.) TWRP started, wipe, then yes, then back to install, Multidisabler.zip flashed.
4.) restarted
That was it
I don't have a Super_SU or Magisk installed
greeting
Norbert
{
"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"
}
Mostly copied from @asineth
Disclaimer: You decided to flash your phone. I'm not responsible for bricking phone or data loss.
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Downloads:
Ziped images for suggested install:
lineage-17.1-20210329-UNOFFICIAL-sofiar-images.zip
sha256sum: c57d69ade235f5c76c6eea038ad29f81e522ef713ea00b89c10010a52d6cf17f
Build for TWRP/sideload:
lineage-17.1-20210427-UNOFFICIAL-sofiar.zip
sha256sum: 9c2ada552cdb3ea29ffe63f175fe514daae429c1a727cd41a574e46e97f9ffe9
lineage-17.1-20210329-UNOFFICIAL-sofiar.zip
sha256sum: dae9ec116de163a46efea1a1316a86dfdffda625cc568109c268f255722134e4
Lineage 18.1 - not tested:
https://mega.nz/file/8gonBIgD#6Kon0qwOZS8WdrUAgQqAPJjO7qy1tDiKcua_EMjHYOA
Last updated: 2021.04.27
This ROM includes:
FDroid
FDroidPrivilegedExtension
Flashing:I recommend GNU/Linux for this.
1. Flash TWRP
2. Extract the zip and open a shell with ADB and fastboot.
3. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
4. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
4. Wipe userdata.
5CODE]fastboot -w[/CODE]
If you are on the Moto G8/G Fast and your display cutout is misbehaving, enable your overlay like so:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
Update:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Working:
Display
Touchscreen
Wi-Fi
Bluetooth (including audio)
Headphones via 3.5mm
Internal Speaker
Moto Actions
Calls/SMS/LTE/VoLTE on Verizon
GPS
Notification LED
Hotspot
Bugs:
After turning hotspot off, phone reboots
Inbuild screen recording app broken, phone reboots
Source:
LineageOS
Device tree
Vendor tree
Kernel tree
Telegram:
https://t.me/MotoG8Official
Credits:
@Vachounet - helped a lot, original device/vendor tree, TWRP build
@kjjjnob - some LineageOS changes to @Vachounet's tree
@asineth
LOS team
XDADevDB Information
[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1, ROM for the Moto G Power
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: stable
Created 2021.03.15
Last Updated 2021.04.27
I downloaded and installed this yesterday. So far, I haven't encountered any issues or found anything that doesn't work. Good job!!!!
tcaudill01 said:
I downloaded and installed this yesterday. So far, I haven't encountered any issues or found anything that doesn't work. Good job!!!!
Click to expand...
Click to collapse
Cool, thanks for info!
Did you just dirty updated or wiped?
sifrax said:
Cool, thanks for info!
Did you just dirty updated or wiped?
Click to expand...
Click to collapse
I always use the recovery program and go all the way back to stock before installing a ROM. It takes more time and is more complicated that way but if I encounter a problem, I know it's the new ROM and not carryover garbage from the old one.
So far, everything is working. VoLTE, GPS, QS Tiles, etc. Battery life seems good. Performance is good. No crashes or reboots.
Seems to be solid.
Thank you. Your work and efforts are appreciated.
I'm gonna dirty flash on top of the dpcioc build from the previous thread. I had to wipe data to get that one to boot coming from the asineth build. I'll let you know what happens.
EDIT: Doesn't work. lol
Hi I'm new to custom roms. What is the difference between the first zip file with images and the 2nd zip file on this post? Thanks!
Never mind. I posted my question before the files downloaded and clearly see the differences afterwards.
Update: Great success!!! Had 0 issues installing this. Thank you for the code as well!
I finally tried to install. Dirty flash over asineth's LOS 17.1.
Sideload did not worked phone rebooted and entered into TWRP. So I tried flashing from fastboot and that worked. I lost apps, but it remebered my PIN.
I have only one issue - hotspot works, but when I turn it off, phone reboots.
sifrax said:
I finally tried to install. Dirty flash over asineth's LOS 17.1.
Sideload did not worked phone rebooted and entered into TWRP. So I tried flashing from fastboot and that worked. I lost apps, but it remebered my PIN.
I have only one issue - hotspot works, but when I turn it off, phone reboots.
Click to expand...
Click to collapse
I never use hotspot so I hadn't checked it out. I tried it and my phone reacts the same way as yours does.
SO as I understand there is no need a computer for this
SO this my very first time doing this and just wanted to be clear do I or do I not need a computer
Aasdnivj said:
SO this my very first time doing this and just wanted to be clear do I or do I not need a computer
Click to expand...
Click to collapse
Even though if you have unlocked phone I'd still recommend use computer and first zip with images.
New build 2021-03-25
https://mega.nz/file/VopiVQST#bAJQ2-3hI-LbED2uPoCXoEEA0HoyGw0h50ESr7H3A4A
SHA256: d2c474b5d0ec40ad0f807e0a3dc2c0fbfabfa7fe04bc8c0243ce72b8faadfc9b
sifrax said:
New build 2021-03-25
https://mega.nz/file/VopiVQST#bAJQ2-3hI-LbED2uPoCXoEEA0HoyGw0h50ESr7H3A4A
SHA256: d2c474b5d0ec40ad0f807e0a3dc2c0fbfabfa7fe04bc8c0243ce72b8faadfc9b
Click to expand...
Click to collapse
Just installed today right before you posted this new build! Its working so far, thank you! Whats new in the build?
Banana_sam said:
Just installed today right before you posted this new build! Its working so far, thank you! Whats new in the build?
Click to expand...
Click to collapse
Hi, it's just updaed LOS. Nothing regarding device.
I'll try to merge github repos with some updated and then buid new version later.
sifrax said:
Downloads:
Ziped images for suggested install:
https://mega.nz/file/VopiVQST#bAJQ2-3hI-LbED2uPoCXoEEA0HoyGw0h50ESr7H3A4ASHA256: d2c474b5d0ec40ad0f807e0a3dc2c0fbfabfa7fe04bc8c0243ce72b8faadfc9b
lineage-17.1-20210315-UNOFFICIAL-sofiar-images.zip
uloz.to
SHA256: b8708803104fa831490255fc0c7e3fb0fd5cee9934d0d402e761b73648c42ab4
Build for TWRP/sideload:
520.91 MB file on MEGA
mega.nz
SHA256: 04d8417608166dadb3276725d032167ce702bdc8621065c7129b44508abd0f9c
lineage-17.1-20210315-UNOFFICIAL-sofiar.zip
ulozto.net
SHA256: 895a0e088d3bd9ba93ed29a4b04dbc8c77bb2d3f61aa9313fa6207e91dc90a76
Last updated: 2021.03.25
Click to expand...
Click to collapse
No idea how these files differ, which one do I use or how.
sifrax said:
This ROM includes:
FDroid
FDroidPrivilegedExtension
Click to expand...
Click to collapse
No idea what this means or why is it important and listed as second most important paragraph.
sifrax said:
Flashing:
1. Extract the zip and open a shell with ADB and fastboot.
Click to expand...
Click to collapse
Don't know what that means.
sifrax said:
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
Don't know what `fastbootd` mode is.
sifrax said:
3. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Doesn't work, after reboot the command line says "waiting for any devices". Can't continue.
Every year I try some Android device and venture to XDA to try some custom ROMs. It never works.
mcsoap said:
No idea how these files differ, which one do I use or how.
No idea what this means or why is it important and listed as second most important paragraph.
Don't know what that means.
Don't know what `fastbootd` mode is.
Doesn't work, after reboot the command line says "waiting for any devices". Can't continue.
Every year I try some Android device and venture to XDA to try some custom ROMs. It never works.
Click to expand...
Click to collapse
This is a very stable and well presented ROM. It is also very easy to install.
I'm not trying to be a ****, but with all the questions you have, you obviously have no idea what you are doing! If other people are successfully installing and using a ROM and you can't, the problem is not the ROM.
For starters, is your bootloader unlocked? If not, you need to do that before trying anything. If you don't know how, use search.
Most of your answers are here
"Moto G Power Guides, News, & Discussion"Do your homework first and read everything you can.
So after a few days everything still seems really good. One flaw I've just realized is that screen recorder doesn't work and forces the phone to restart after launching.
Not really a deal breaker for me since I very rarely use the app and its not really necessary for my purposes. Just thought I'd test it out, since I think I remember seeing in another thread here how this was happening with another custom rom for this device
Banana_sam said:
So after a few days everything still seems really good. One flaw I've just realized is that screen recorder doesn't work and forces the phone to restart after launching.
Not really a deal breaker for me since I very rarely use the app and its not really necessary for my purposes. Just thought I'd test it out, since I think I remember seeing in another thread here how this was happening with another custom rom for this device
Click to expand...
Click to collapse
This is true. The ones from the play store will work.
Banana_sam said:
So after a few days everything still seems really good. One flaw I've just realized is that screen recorder doesn't work and forces the phone to restart after launching.
Not really a deal breaker for me since I very rarely use the app and its not really necessary for my purposes. Just thought I'd test it out, since I think I remember seeing in another thread here how this was happening with another custom rom for this device
Click to expand...
Click to collapse
OK, thanks for information. I can verify that the bug is there, it restarted.
I merged github repos with some more updated (Odin1101) and it's compiling.
mcsoap said:
No idea how these files differ, which one do I use or how.
No idea what this means or why is it important and listed as second most important paragraph.
Don't know what that means.
Don't know what `fastbootd` mode is.
Doesn't work, after reboot the command line says "waiting for any devices". Can't continue.
Every year I try some Android device and venture to XDA to try some custom ROMs. It never works.
Click to expand...
Click to collapse
Sorry to hear, but you know as it was suggested to you - try to study a little bit more before. Hope you can make it next time.
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.