Develop Bugs

Asus ZenPad 8.0 (Z380KL) Information Repository

Just going to dump all the info I've found about this device into this thread. All the threads pertaining to this thread are in Russian and I can't read Russian, so this might be helpful to any English speaking owners of this tablet.
Special thanks to Telegram user @SSDD_1744 (don't know your XDA/Reddit user, I'm sorry) for basically spoonfeeding me all these instructions!
WARNING: If you need to flash to stock for whatever reason, be sure to download a image file specific to your country. If you don't, you'll hard brick your device that can only be fixed QPST (supposedly).
Rooting:
(Tested on 5.0.2)
Install KingRoot. Let it root your device.
Install Super-SU Me, to get rid of the bloatware that comes with KingRoot.
Installing Xposed:
I used Flashify to flash TWRP. Be sure to flash the right version though (2.8.7.7 v2) or else you won't be able to mount cache.
Then download Xposed (version sdk21 ARM) and flash it.
WARNING: Flash v1 of the modded TWRP and you won't be able install any apps after flashing Xposed.
Unbricking:
Still working on it. Downloaded QPST but have not been able to get QPST 2.7 to read the tablet.

Links:
Discussion:
https://translate.googleusercontent...690491&usg=ALkJrhiWSlkbZ-tUofZx68NPSGIv8pjIPA
Root:
https://translate.googleusercontent...JrhhQszcRvUo8HILThvz57JmsLj4L9g#entry44556703
https://translate.googleusercontent...JrhiCt__6apcRhk-gtcBExYJCnC9nGQ#entry41676452
Instructions for obtaining the rights to Ruth phones / tablets.
Tested on Android 4.4+
perhaps this algorithm works on Android 5+, I have no way to verify
All transactions with their phones / tablets are performing at your own risk !!!
To get started, read this post from start to finish and only then proceed to action!
Introduction
This instruction is written based on my own experience obtaining root on their plates, and then on the Xperia M2, bought plemyashki. For instructions attached versions of applications that were relevant at the time, the new version can download the relevant topics on the forum, there will find all information on how to work with the proposed programs and algorithms for their actions (links to topics added).
For all the action with your phone / tablet you are responsible for yourself!
Download all the necessary tools to obtain Root (of instructions / topics on the forum), obespechte for phone / tablet access to the Internet (Wi-F / mobile data) and let the phone settings / tablet installation from unknown sources.
Needed Downloads
KingRoot_V4.5.0B202.apk (6.76 MB)
Me_5.9.apk-SuperSU (9.07 MB)
V2.49 Beta.apk SuperSU (5.63 MB)
eu.chainfire.supersu.pro.205.apk (52,88 KB)
Next in series:
1. Install KingRoot .
Get Ruth's right, in the device may reboot.
2. Set SuperSU-Me, .
Run the grantor, the program deletes KingRoot and Chinese KingUser with replacement SuperSu.
Remove the longer SuperSu-Me the desired program.
3. Obnovyaem SuperSu to the latest version. Then set PRO-key .
Installing Pro-key Optionally !!! Use Cases SuperSu without installing key .
4. Open SuperSu and on-demand update binary SU normal way. After a successful update, confirm the request to restart.
5. To make sure that everything is done correctly, check the correct installation and operation of Ruth (mount the system partition on the record), I used the Root Checker Pro and Root Explorer , respectively.
The output is a complete rut without kitayschiny with SuperSu Pro. We use and enjoy
Click to expand...
Click to collapse
Unlocking bootloader (haven't tried this):
https://translate.googleusercontent...Jrhh6g4wI-8Hb_LzAcPnIUxYvWNzZ0A#entry46711087
Stock firmware:
https://translate.googleusercontent...?s=&showtopic=703414&view=findpost&p=45272695

Damn, development has really boomed on this little tablet! Finally got it back after a few months (I sent it into Asus to repair it for me).
Stock ROM:
https://www.asus.com/ru/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (I can't get the English version to load, delete the /ru/ and you'll be redirected to the English site)
https://www.asus.com.cn/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (Chinese site)
==== REMEMBER TO DOWNLOAD THE CORRECT COUNTRY OR YOU'LL BE BRICKED) ====
https://yadi.sk/d/b1NMLXHBsNV8C (latest software for the worldwide model)
[http://4pda.ru/forum/index.php?showtopic=703414&st=320#entry50270292]
http://4pda.ru/forum/index.php?showtopic=703414&st=200#entry49389176 (Asus Flash Tool and stock ROM v4.8.2 WW [WorldWide])
Unlocking bootloader:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48200665 (use fastboot oem device-info to check if it's unlocked)
Root:
http://4pda.ru/forum/index.php?showtopic=690491&st=580#entry44778545 (KingRoot - you'll need a 4PDA.ru account to download this)
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (last section of the post)
CM13:
http://get.cm/?device=P024&type=nightly
https://vasy.ru/CM13/
http://forum.xda-developers.com/android/help/asus-zenpad-8-z380kl-custom-rom-t3370277
http://forum.xda-developers.com/android/development/kernel-asus-z380kl-p024-kcal2-t3405595 (Kernel)
Recovery:
https://vasy.ru/TWRP/P024/
http://4pda.ru/forum/index.php?showtopic=690491&st=1220#entry48094504 (TWRP 2.8.7.0)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051
Guides:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (this has a lot of instructions: root, recovery, boot partition restore, adb drivers etc.)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051 (this has a bunch of files, Resurrection Remix [I haven't tested it yet tho], and instructions on getting out a bootloop)
http://4pda.ru/forum/index.php?showtopic=690491&st=1640#entry49724823 (flashing stock software)
If you want to open the engineering menu, type " * # * # 4636 # * # * "
To boot into fastboot, restart/turn on the device and hold volume up. It'll pop you into a menu with three options.
To boot into recovery, from the fastboot screen (three options), use the volume buttons and navigate to the second option "factory reset" and hit power to confirm. It'll boot into recovery.
=====================================================================================
Recommended way to flash ROMs:
1) Download TWRP. Use adb to boot (NOT flash) into TWRP. Flash ROM there.
2) use KingRoot to root. Use Flashify to flash the ROM.
======================================================================================
If you want to go look up some more info or guides, go here:
http://4pda.ru/forum/index.php?act=...=rel&subforums=0&query=z380kl&forums=570&st=0
and use GTranslate to translate the page. The first page is the earliest posts with the keyword, the last page are the latest post.

please add these ROM's for this Device:
Ressurection Remix:
https://www.androidfilehost.com/?w=files&flid=121811
AICP 12.1:
https://www.androidfilehost.com/?w=files&flid=136181

The latest Official ROM P024 model:
http://dlcdnet.asus.com/pub/ASUS/Ee...ser.zip?_ga=1.109506565.1670552787.1483182775
ZenPad 8 Z380KL Firmware: V5.9.0.0 (WW SKU version only)
Improved Item:
1. Update Google security patch
2. Support unlock tool

9008 brick info:
https://4pda.ru/forum/index.php?showtopic=643084
Pertaining to p024:
https://4pda.ru/forum/index.php?showtopic=643084&st=5740
https://4pda.ru/forum/index.php?showtopic=643084&st=3660 (page 179 - 180, 183 - 185 discusses the files needed to unbrick and how you would - CTRL + F Russ and read the people who quote him)
How I bricked: https://4pda.ru/forum/index.php?showtopic=703414&st=180#entry49329798
https://4pda.ru/forum/index.php?showtopic=690491&st=1420#entry48527044 (unbricking files - dead link though)
https://4pda.ru/forum/index.php?showtopic=703414&st=140 (discussing how to fix using the images from the dump)

I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.

Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA

ROMs
LineageOS: https://download.lineageos.org/P024
AICP: https://saki-sss.blogspot.com.by/2016/12/z380k-aicp-121.html
Resurrection Remix: https://androidfilehost.com/?w=files&flid=121811
(made by https://androidfilehost.com/?w=profile&uid=457095661767100043, found from http://andmem.blogspot.jp/2016/05/asus-zenpad-8-z380kl-root-rom.html#chapter-19) - abandoned?

seities said:
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Click to expand...
Click to collapse
probably not. I think it's only compatible with the SD 410.

xDark_ said:
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
Click to expand...
Click to collapse
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.

jutphaas said:
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
Click to expand...
Click to collapse
I don't think unlocking the BL is necessary for flashing LOS. But yes, that's how I get into TWRP as well.

Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.

pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
Can you still access fastboot, then at least you can flash twrp as described before in this thread and install from twrp lineageos p024 (lineage-14.1-20180105-nightly-P024-signed.zip) and Open gapps to get google playstore etc , select Arm, (not 64) then version 7.1, then Pico would work.
If you have twrp, you at least can still use your asus... I have found no way to flash original stock... stock must not be flashed from twrp.
Since you mention twrp already used, you can try: turn your device off, then press volume up then the bootloader menu comes, select 2: reset to enter twrp(where it says reset. if you had flashed twrp, that is how you can get into twrp) from there, install lineage os and gapps from micro sd card
My rom is MMB29M.WW_P024-V5.9.4-20170613

xDark_ said:
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
Click to expand...
Click to collapse
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos

jutphaas said:
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
Click to expand...
Click to collapse
Yes it was. I flashed 15.2 on both stock and LOS. I've heard of some issues with 15.x so you can try .2 or 14.x.

pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
What error was given? What do you see when you connect it to a computer? What does "tablet locked" mean? Would help if you gave some pictures too.
I'm currently in the process of getting the RAW files/service ROMs for AFT but I don't have an ETA on when I'll be able to get that.

No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.

pucci2 said:
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
Click to expand...
Click to collapse
Does it respons to adb devices of fastboot devices in this stage?

no, it is not recognized

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
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 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.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.​
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3​
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.​
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.​Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.​
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!​
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).​Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!​

On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)

GCam settings
But my google camera keep crashing when I want to go into camera settings

Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this

bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.

"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.

Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha

Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!

Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!

Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?

[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL

cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working

H931 Devices Possibly Other Variants Wifi Fix Android 10 Roms (Liquid 10, LineageOs)

Short Story: Updated to pie us99830b kdz after flashing some things and clean flashed 10 roms again and somehow wifi wanted work ok since then. I also made backups but I am not clear if they will work without first getting pie blobs through kdz. This fix is not necessary on all LG V30 variants so first check if your model works with the roms fine. May also want to double check Zachs adb shell commands do not work on your device or do that also just in case (bottom).
Suggestions: This may actually take some time if you run into problems. Might be good idea to throw your sim in another phone so you don't stress. Smoke a bowl or open a beer.
Warning: AOSP rules may apply here although everything seems well with both permissive/enforcing for me. See that thread. Proceed at your own risk. If anytime you are not detected in download mode you must flash an oreo stock twrp zip such as h93120h or us99820e.
Files: Wifi working for me with this method on each 10 rom I have tested(Liquid, Lineage, AEX, ION, Havoc) so find one of those. You may also need us99820b kdz(us99810d if 20b doesn't boot clean some reason), the h93030q twrp zip, kernel(huamea 1.9.3 suggested) and h930 22j modem (https://drive.google.com/file/d/16o93WU262HWv2fKPYnMxC81GY6bJ3Txd/view?usp=sharing).
Quick Steps:
20b kdz partion all boot to setup screen then power down+fastboot+install/boot twrp+ magisk-decrypt-ak3remover zips+boot to setup screen again(don't setup) then power down+download mode+ 30b kdz partition all. Decrypt error for me first boot with 30b kdz so "reset phone" may be needed if greeted with that screen. Get to actual setup screen on 30b then power down+fastboot+twrp(cancel on encrpyt error)+format+wipe all(but sd)+reboot recovery. Then finally your selected poison havoc q+open gapps+magisk+decrypt for a clean flash. After booting in once I then reboot to twrp and flash huamea because it temporarilly removes root which needs to be reflashed.
Troubleshooting Suggested Steps:
Prior Potentially Unecessary Steps*
i. First install the 10 rom without wifi and make a backup or use mine below of chosen rom (in my case us99830b clean flashed to liquid/lineage)
ii. Clean flash h93030q twrp zip +magisk+disable encrypt+22j modem.img boot to startup screen then reboot to recovery
iii. Format data then wipe all but sdcard/otg and restore the Q backup. Goal here is to get the wifi initially clicked in, but the calling quite likely will still not work now. You can attempt to flash some stock modems to see if they work for you but I had no such luck. Reflash 22j modem after if you do test others.
iv. If the 30b kdz has not been booting up flash us99820b kdz partition all then reinstall twrp. If the 20b kdz restarts by itself after booting up you must partition dl all us99810d kdz first before 20b.
Steps
1. Format data then wipe all but micro sd don't reboot
2. Go back and reboot recovery
3. Magisk+disable encrypt
4. Power off then download mode(volume up while plugging in cable)
5. Partition dl all us99830bkdz using patch lgup
6. Let it boot to first welcome screen but don't setup anything
7. power off then fastboot mode(volume down while plugging in cable)
8. In adb & fastboot enter fastboot flash recovery then fastboot boot twrp.img
9. Will get decrypt error still in twrp for second just hit cancel
10. Repeat steps 1 & 2
11. FLash Liquid 10.1+Opengapps or Microg if wanted+ Magisk+ disable decrypt zips and boot it to start screen but don't setup
12. -Optional-Reboot Recovery Flash Humea kernel 1.5-1.9.3 or another to stabilize wifi/ better battery life(could possibly be done in prior step, may possibly lose root) and reboot
13. Andy's Fingerprint fix for internal error promp at startup(some roms ok without): Download osmosis busybox and magisk props config hide. Reboot then type "su" in any terminal then "props", follow prompts and select lg-v30 h930. The error should go away on boot.
*The prior steps here initally fixed wifi for me but I still didn't have calling, so I chose partition dl all partitions(only way kdz seems to boot) using patched lgup back to us99830b to test again which I assumed would cancel this procedure out so alas still not 100% sure if required. A dev has said though if you get wifi on your device once you will always have it. Wifi has been sticking for me afterwards until flashing any oreo kdz then I must re follow quick steps.
Backups - magisk w/ huamei Kernel 1.5, opengapps, fingerprint fixed
LineageOs 17 https://drive.google.com/drive/folders/1uQSDWDYFjGlEQ-gdyyn8QVgT5tB6Cjku?usp=sharing
Liquid 10 https://drive.google.com/drive/folders/1w9e_oLWpDR5bWk5jhs4xs1H9Q-AOv0NI?usp=sharing
Zachs Faster Wifi Fix for some lucky LG V30 users:
" - you need a kernel with dm-verity disabled (custom kernel, etc.) - for now the one of the haumea_I.base kernels allow this process
- Magisk must be installed (root permissions)
- get into a shell and become root (adb shell -> su ; or via other means)
- cp -a /vendor/etc/wifi/WCNSS_qcom_cfg.ini /mnt/vendor/persist-lg/wifi/WCNSS_qcom_cfg.ini
- in my example wlan_mac.bin is copied to /storage/emulated/0/joan_int/wlan_bins/wlan_mac.bin (that's internal storage and a newly created folder joan_int and subfolder wlan_bins)
so the final command to "fix" all is
cp -a /vendor/etc/wifi/WCNSS_qcom_cfg.ini /mnt/vendor/persist-lg/wifi/WCNSS_qcom_cfg.ini
cp /storage/emulated/0/joan_int/wlan_bins/wlan_mac.bin /mnt/vendor/persist-lg/wifi/wlan_mac.bin
chmod 644 /mnt/vendor/persist-lg/wifi/wlan_mac.bin
you copy over the WCNSS_qcom_cfg.ini file to the expected place (the symbolic link is wrong)
and copy over the missing wlan_mac.bin also to the expected place"
wlan_mac.bin here https://drive.google.com/file/d/1GM-IBe0CJ9hA4s2TAzas8IJcN67FOMR3/view?usp=sharing
Shouts out to @ChazzMatt , @SGCMarkus, @kherio, Andy, Zach, Chiru, Harris, and others on telegram for the group think. Any difficulities after following these steps you can hit up @tyl xda / Andy on telegram, he was able to use a slightly differed spin using persist lg files which may work for you. I will try to update as things get figured out

Question Latest Twrp pros and cons

Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.

you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting

hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.

so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself

So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)

Development [RECOVERY][3.7.0_12-8][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too.
As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
Download the twrp-installer zip
Flash it with Magisk manager or some other kernel flash utility
Reflash your custom kernel and Magisk.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
Don't reboot
Rename downloaded Magisk.apk to Magisk.zip
Open Magisk app
Select Modules tab
Click "Install from storage"
Select Magisk.zip
2. Option for users with other custom recoveries but without root:
Download the twrp-installer zip
Reboot to recovery
Flash it with "adb sideload twrp-installer*.zip"
Reboot to recovery
Reflash your custom kernel and Magisk.apk if previously installed
3. Option is universal:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Go to Advanced > Flash Current TWRP
Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps.
Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
Reboot to bootloader
Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.
TWRP Updates:
Download and flash the twrp-installer zip
After that reflash your custom kernel and Magisk if previously installed
ROM Updates:
Please follow the official update instructions for your ROM!
If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.
In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!
Instructions that work for me (on LOS based ROMs):
Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
Reboot to system
If Gapps packages keep crashing:
Reboot to TWRP
Flash Gapps again
Reboot to system
For OOS updates should work out of the box, but if you have issues you can follow these steps (I haven't tested them):
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
About backups/restore:
Restore data only WITHOUT pin/pattern set.
If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.
Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to system.
In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
How to use MTP, adb and fastbootD:
Windows:
Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.
To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.
Steps for choosing a specific driver (no the exact wording):
Connect phone in specific mode
Open device manager
Right click on phone either under "Android device" or "USB device", depending on mode
Select "update driver"
Select 2. option "browse my computer"
Select "pick from available drivers"
Pick driver according to above description
Linux:
Intall the fastboot and adb packages for your distribution
Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/nilz3000/android_hardware_oplus
Bugs:
Permanent installation alongside TMO stock isn't possible
Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
In case you notice anything else please let me know.
If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.
Thanks to:
@Nebrassy for the original device tree
@osm0sis for the zip installer
TWRP team
LineageOS

Thank you for this! Will try tomorrow.

Ah man this is dope. Thank you bud!!!

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.

Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...

vipinpvarghese said:
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
Click to expand...
Click to collapse
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.

der_akinator said:
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
Click to expand...
Click to collapse
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?

vipinpvarghese said:
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
Click to expand...
Click to collapse
Yes, but it was the same ROM I reinstalled after wipe.

der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse

der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
Sorry i forgot about recovery log

EugenStanis said:
Sorry i forgot about recovery log
Click to expand...
Click to collapse
recovery.log
Zippyshare.com - Free File Hosting
www1.zippyshare.com

Anyone tested it with stock OOS13?

der_akinator said:
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
Run "fastboot boot boot.img" with the TWRP boot image.
Go to Advanced > Flash Current TWRP.
After that is done, if you were using a custom kernel, reflash it now.
If you were using magisk, reflash it now.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/LineageOS/android_hardware_oplus
Bugs:
Please let me know. I have not encountered anything major yet.
Thanks to:
Nebrassy
TWRP team
LineageOS
Click to expand...
Click to collapse

For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.

Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Here is a link to the github issue, maybe it helps you solving the problem.
createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project
Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...
github.com

tnchng said:
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Click to expand...
Click to collapse
I use C.63 and have not tested with other firmware versions.

der_akinator said:
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Click to expand...
Click to collapse
Strange, i have never ever in my life used multiuser