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

[Recovery][J710F/FN/GN/MN/K] [Build 3][3.2.3-0] TWRP for j7xelte (Galaxy J7 2016)

Team Win Recovery Project 3.2.3-0
This is for the Exynos SM-J710F, SM-J710FN, SM-J710GN, SM-J710MN, SM-J710K models only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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, and root your device.
DOWNLOAD
Build 3 3.2.3-0
Older builds:
Build 2 3.2.3-0
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://odindownload.com/
FULL STEPS FOR ROOTING
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_(version).zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with Magisk:
Download the latest Magisk.
Without exiting TWRP, transfer the Magisk zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
KNOWN ISSUES
You need to wipe Data when on stock ROM
Changelog
Build 1: Initial release
Build 2: Update to M10 kernel and android-8.1 source (from android-6.0)
Build 3: Fix MTP problems and /vendor (invalid argument) + upstreamed M10 kernel to 3.18.134 with google recommended changes to kernel
NOTE: If you're on stock Oreo rom always make sure your system is read only. Don't let it be r/w
SOURCE CODE:
TWRP (android-9.0)
Device tree (android-8.1)
Kernel: (pie)

why is not on the official web?
idk this seems pretty sketchy

M4T145 said:
why is not on the official web?
idk this seems pretty sketchy
Click to expand...
Click to collapse
I can't instantly get official i can upload pictures btw

Is it support Android 8.1.0 Firmware?

TRalperenTR said:
Is it support Android 8.1.0 Firmware?
Click to expand...
Click to collapse
Yes but make sure you leave system read only and flash magisk instantly to fix dm verify

Thanks man. It's worked! Every features is working. But why does it say E: on the console? I didn't understand.

TRalperenTR said:
Thanks man. It's worked! Every features is working. But why does it say E: on the console? I didn't understand.
Click to expand...
Click to collapse
I don't know. Its a twrp bug maybe. Also download it again i built it using the M10 kernel now but it also says /vendor invalid argument

...

It is working fine checked it

This TWRP doesn't install Oxygen Kernel. It says "Recovery Busybox Setup Failed."

I have already installed official twrp from website do i have to reinstall fresh on just download a zip for flash without installing magisk plus kindly upload a video for step by step process.
By the way a quick question is kernel 3.18.135 is latest or 3.18.14

Sulltan Mehmood said:
I have already installed official twrp from website do i have to reinstall fresh on just download a zip for flash without installing magisk plus kindly upload a video for step by step process.
By the way a quick question is kernel 3.18.135 is latest or 3.18.14
Click to expand...
Click to collapse
3.18.135 newer then 3.18.14
If you have other twrp extract the .tar archive and move .img to phone and goto Install on twrp select Install Image and Click on it. Select recovery and swipe to confirm. Done

Hi, the link of the latest build is down, can you re-upload please?

I saw in other tutorials that when in stock 8.1 rom you need to erase all data from internal memory. If i do this, there is no longer a, /system folder so there is no rom and bootloop happens.
Do i need to do factory wipe instead? I know i have to wipe data because Its encripted and twrp cant access internal memory.
Im asking what kind of "wipe data" i need to do

just format data to decrypt
link please

bro it says download file does not exist on google drive

download link ??

https://drive.google.com/open?id=1Xq4TAkcs9plY3zfGHiall21a3GgjdgHS
---------- Post added at 17:28 ---------- Previous post was at 17:28 ----------
saquib996 said:
bro it says download file does not exist on google drive
Click to expand...
Click to collapse
Ofogh said:
download link ??
Click to expand...
Click to collapse
https://drive.google.com/open?id=1Xq4TAkcs9plY3zfGHiall21a3GgjdgHS

[RECOVERY] [UNOFFICIAL] LR.Team TWRP 3.3.1-1119 for onclite by wzsx150

Disclaimer:
HTML:
/* Your warranty is now void! I'm not responsible for bricked devices, dead SD cards or anything else that may occur to you and / or your device.
* Do it at your own risk!
This recovery was not made by me, i'm just sharing it in easier ways to download. The guy behind this is wzsx150, thank him for it.
After a lot of pain researching and trying to download from Baidu servers i finally managed to get this custom TWRP to get rid of force encryption on stock MIUI because this recovery can successfully decrypt with no need to do a format data.
Just installed magisk v20.2 on stock MIUI global 11.0.4 and it works. :good:
Info
- Based on TWRP 3.3.1
- Build date: 2019.11.19
- Model: Redmi 7, Red Rice 7
- Developer: wzsx150 (profile)
Install Instructions
Warning: unlocked bootloader needed!
Fastboot
1. Download IMG file below
2. Rename file to recovery.img and put it into your adb path (if you don't have adb check this link)
3. Reboot your device into fastboot mode by holding down vol - and power button while device is off and connect to PC
4. Open cmd in your adb path and run the following command: fastboot flash recovery recovery.img
5. Run fastboot reboot, and hold down vol + key until device enters into twrp
Custom Recovery
1. Download ZIP file below to internal storage
2. Reboot to recovery
3. Install zip
4. Reboot to recovery
Downloads
IMG: https://drive.google.com/uc?id=16zXoYeviDUeV9zsSeDjyi_P8NnQkJhLr&export=download
ZIP: https://drive.google.com/uc?id=1ZF4C5-B9rlHKJVO0GbtS_ZjT5VlX1taH&export=download
Special Thanks
- TeamWin for building TWRP for a lot of devices, including this one
- wzsx150 and LR.Team for making this mod
- Firmwarex.net for providing a free Baidu account to download from their servers
Source: https://www.weibo.com/6033736159/IgY1Ex98h?from=page_1005056033736159_profile&wvr=6&mod=weibotime

Works backups AND restore opción?

mcf7 said:
Disclaimer:
/* Your warranty is now void! I'm not responsible for bricked devices, dead SD cards or anything else that may occur to you and / or your device.* Do it at your own risk!
This recovery was not made by me, i'm just sharing it in easier ways to download. The guy behind this is wzsx150, thank him for it.
After a lot of pain researching and trying to download from Baidu servers i finally managed to get this custom TWRP to get rid of force encryption on stock MIUI because this recovery can successfully decrypt with no need to do a format data.
Just installed magisk v20.2 on stock MIUI global 11.0.4 and it works. :good:
Info
- Based on TWRP 3.3.1
- Build date: 2019.11.19
- Model: Redmi 7, Red Rice 7
- Developer: wzsx150 (profile)
Install Instructions
Warning: unlocked bootloader needed!
Fastboot
1. Download IMG file below
2. Rename file to recovery.img and put it into your adb path (if you don't have adb check this link)
3. Reboot your device into fastboot mode by holding down vol - and power button while device is off and connect to PC
4. Open cmd in your adb path and run the following command: fastboot flash recovery recovery.img
5. Run fastboot reboot, and hold down vol + key until device enters into twrp
Custom Recovery
1. Download ZIP file below to internal storage
2. Reboot to recovery
3. Install zip
4. Reboot to recovery
Downloads
IMG: https://drive.google.com/uc?id=16zXoYeviDUeV9zsSeDjyi_P8NnQkJhLr&export=download
ZIP: https://drive.google.com/uc?id=1ZF4C5-B9rlHKJVO0GbtS_ZjT5VlX1taH&export=download
Special Thanks
- TeamWin for building TWRP for a lot of devices, including this one
- wzsx150 and LR.Team for making this mod
- Firmwarex.net for providing a free Baidu account to download from their servers
Source: https://www.weibo.com/6033736159/IgY1Ex98h?from=page_1005056033736159_profile&wvr=6&mod=weibotime
Click to expand...
Click to collapse
Thanks a lot ? so this should work to install any custom rom? Like the pixel experience one?
Sent from my Xiaomi Redmi 7 using XDA Labs

Jojethegamerpro said:
Works backups AND restore opción?
Click to expand...
Click to collapse
I haven't tested but it should work

SammyInTheCity said:
Thanks a lot ? so this should work to install any custom rom? Like the pixel experience one?
Click to expand...
Click to collapse
If you're planning to install a custom rom, any custom recovery should work, including this one.
The main advantage of using this recovery is that you can bypass the stock rom (maybe stock based roms too) force encryption to access your partitions on recovery.

mcf7 said:
If you're planning to install a custom rom, any custom recovery should work, including this one.
The main advantage of using this recovery is that you can bypass the stock rom (maybe stock based roms too) force encryption to access your partitions on recovery.
Click to expand...
Click to collapse
Okay thanks, I have my bootloader locked at the moment, but when I finally am able to unlock it I'll definitely use this
Sent from my Xiaomi Redmi 7 using XDA Labs

Thank you for sharing

Ask password for decryption
But my phone isn't encrypted
Tried my lock screen password it didn't work
Tried to remove all passwords but still asks for password

hamedhd said:
Ask password for decryption
But my phone isn't encrypted
Tried my lock screen password it didn't work
Tried to remove all passwords but still asks for password
Click to expand...
Click to collapse
Which recovery did you used before this? And what's your rom?
For the first time i used LR.Team's recovery i installed recovery, did a format data(due to the password issue as you), installed miui global and magisk and the system booted properly and after that recovery didn't asked for password anymore and i've been able to mount partitions and do other stuff.

I can't flash gapps using this twrp, fix it please

Me_Only said:
I can't flash gapps using this twrp, fix it please
Click to expand...
Click to collapse
I'm not the dev behind this project, i'm just sharing wzsx150's work in an easier way to download. You can contact him on the source link at the bottom of OP.
I only tested this twrp with stock rom which doesn't need gapps and encountered no issues.

mcf7 said:
I'm not the dev behind this project, i'm just sharing wzsx150's work in an easier way to download. You can contact him on the source link at the bottom of OP.
I only tested this twrp with stock rom which doesn't need gapps and encountered no issues.
Click to expand...
Click to collapse
same here but the custom roms that doesn't include gapps sucks, that's the problem with this twrp it cant flash gapps, thanks for the response bro.

Realme X2 1993 development

I open this thread because in my opinion the development situation of the various versions of the device is very confusing. I seem to have understood that as regards the unlocking of the bootloader with a working fingerprint, the situation is evolving well only on the China and India version while on the European version nothing moves ... In my modest opinion, Realme deciding to treat those who buy its phones in Europe as users of its lower series devices compared to other areas of the world are wrong because little development leads to a few posts in the various forums and few voices in google searches that each of us does when deciding what to buy ... What do you think you realme device owners in Europe?

I have the 1993ex version and the FP is working fine after a16

hammerheading said:
I have the 1993ex version and the FP is working fine after a16
Click to expand...
Click to collapse
Thanks for the information ... What procedure did you use to unlock the bootloader?

I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device

Bolumstar said:
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Click to expand...
Click to collapse
So you too like me, although there is news of the working fingerprint on the EU, believe that it is still not worth unlocking.
I ask it because I repeat following the various treadhs on the forum it gets confused. It is sometimes indicated that the finger epint works and that for example magisk can work in normal mode and not core only ... This would already be a lot, to say yes it could use the viper4android.

surferbyter said:
Thanks for the information ... What procedure did you use to unlock the bootloader?
Click to expand...
Click to collapse
I used this guide, it works the same for X2.

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?

surferbyter said:
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
Click to expand...
Click to collapse
First time i flashed the twrp i folowed this but now i simply skip the vbmeta and flash twrp directly from bootloader and it works fine.

Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu

woocashewski said:
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
Click to expand...
Click to collapse
never installed a gsi, if I'm not mistaken it takes the image of the vendor ... if you can give me a link to a guide to get started? Thanks in advance...

Howto thread is on this forum...

woocashewski said:
Howto thread is on this forum...
Click to expand...
Click to collapse
I'm doing something wrong because i get bootloop everytime. i tryed to follow the guide with different gsi but no luck. Can you give a quick step how you did it ?

Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...

surferbyter said:
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
Click to expand...
Click to collapse
I've been there, i think the problem was the adb. I used the Minimal adb and it worked, give it a try

first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition

woocashewski said:
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
Click to expand...
Click to collapse
So gsi roms also have fingerprint problems ... However, more than a custom rom, I was interested in coloros with root ...
I can't give up the fingerprint though because some applications of the company I work for use it for authentication ...

I managed to root, magisk 20.3 zip flash on twrp, on the European version a17 with this guide:
https://forum.xda-developers.com/showpost.php?p=81579961&postcount=44
To make the vbmeta flash command work I used the minimal adb version 1.43, with previous versions it doesn't work.
The fingerprint works very well and energy consumption has not changed compared to use with locked boot.
After carrying out all the procedure, the magisk manager indicates the certified safety net unlike the play store which is instead not certified. To have it certified, you need to download the Device ID app, copy the GSF code that gives you the result by opening it and insert it on the page of this link:
https://www.google.com/android/uncertified/?pli=1
After having it delete the data of google service framework and google play store, force the arrest of the second and reopen it ...

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63

Sandalwood83 said:
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Click to expand...
Click to collapse
Ok my bad then, i follow more than one guide so im not sure were i got the apk from. anyway good job finding it for future unlocks!

ROM Stock EU Version
Here the ROM Stock EU https:// drive.google.com/file/d/1-GpV3YBMCCCrQPvCKqqK3cYRXmBMzTCy/view?usp=drivesdk
Just copy the link

Development [Samsung m33] [Recovery] [TWRP] [Testing] [15 april 2023]

Code:
Code:
/*
* Your warranty is now void!!!
*
* If sh!t happens, i am not responsible for your bricked device.
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications,
* Do at your own risk!!!
*/
Version and device Information:​
Status: Testing
Device: Samsung m33
Codename: m336BU
Android version: android-12 (M336BUXXS4BWB1)
Release Date: April 15, 2023
INSTALLATION​
Connect to pc and boot into stock recovery
Factory reset
Reboot into download mode.
flash twrp.tar into the ap slot
reboot to recovery
After that flash samsung multidisabler zip
Reboot to recovery from main menu (not just reboot)
(optional) Backup boot, data, super and dtbo
Reboot to system
Downloads:​TWRP Image: twrp-12.1_3.7.0-v000-m33-20230408.tar.md5
Multidisabler: multidisabler-samsung-3.1.zip

wud u also be interested to look into working custom roms for m33 cuz my phone overheats really bad even with optimization and root

ok so i tried to flash with odin but didnt reset phone cuz its custom recovery and people say it shudnt be a problem. anyway when i tried to flash the ap file odin just crashes so i dunno what to do. so now im gonna try to uninstall magisk, then patch the firmware back to stockwith home_csc, then install twrp and then reinstall magisk again and hopefully my data doesnt get wiped but i have the pics saved so its just a huge hassle if that happens.

im very happy to say that my data has been wiped and the recovery file keeps crashing odin. pls offer help if theres any to offer asap cuz i dont wanna lose progress again when i installed everything again

fluffyball21 said:
im very happy to say that my data has been wiped and the recovery file keeps crashing odin. pls offer help if theres any to offer asap cuz i dont wanna lose progress again when i installed everything again
Click to expand...
Click to collapse
Okey, i will fix the isuue asap.

Shibu Shaji said:
Okey, i will fix the isuue asap.
Click to expand...
Click to collapse
hey so i just had to rename the img file inside tar to recovery.img and pack it back to tar.md5 and it flashed. But the phone goes into bootloop after that and cannot be used unless i flash my old recovery file. also im on custom gsi rom android 13 with patched recovery for fastbootd
GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.
CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dyn...
github.com

hey btw im also trying to make my own twrp for the phone but mine also bootloops after installation. i also tried other twrp for phones with exynos 1280 like a33 and a53 and they both recognize my device as a33 or a53 on pc when flashed but twrp shows black screen i dunno what else to do at this point

There is really so much need of a custom Rom for this device.

fluffyball21 said:
wud u also be interested to look into working custom roms for m33 cuz my phone overheats really bad even with optimization and root
Click to expand...
Click to collapse
Please could you tell me the steps to install twrp.. and also share me working twrp and gsi for this Device I'm really tired of this buggy One Ui

sunnypoddar1919 said:
Please could you tell me the steps to install twrp.. and also share me working twrp and gsi for this Device I'm really tired of this buggy One Ui
Click to expand...
Click to collapse
There's no working twrp as of now but u can patch the recovery IMG of ur device with the patch recovery link I pasted above. Then u can use fastbootd on ur device then download a working gsi from this list then flash it
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Keep in mind if u don't know what ure doing and don't have backup then if bootloop happens u wud have to reset the device and flash stock firmware through bootloader so continue at ur own risk

fluffyball21 said:
There's no working twrp as of now but u can patch the recovery IMG of ur device with the patch recovery link I pasted above. Then u can use fastbootd on ur device then download a working gsi from this list then flash it
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Keep in mind if u don't know what ure doing and don't have backup then if bootloop happens u wud have to reset the device and flash stock firmware through bootloader so continue at ur own risk
Click to expand...
Click to collapse
could you tell me how can i patch my device recovery because it's first time i'm dealing with samsung for custom roms..i have rooted an another samsung device but for that TWRP was already available

sunnypoddar1919 said:
could you tell me how can i patch my device recovery because it's first time i'm dealing with samsung for custom roms..i have rooted an another samsung device but for that TWRP was already available
Click to expand...
Click to collapse
U need to have stock firmware for ur device then extract the ap file from that zip file. Then extract recovery.img.lz4 from ap file then follow the tutorial in this guide and do as it says. After all that's done ull get a zip file and u can flash that via odin by putting it in ap file slot
GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.
CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dyn...
github.com

i have flashed the patched recovery by doing all these steps, could you tell me now how can i flash gsi next by the way i have downloaded pixel experince plus (unofficial from your link that you have provided)

sunnypoddar1919 said:
i have flashed the patched recovery by doing all these steps, could you tell me now how can i flash gsi next by the way i have downloaded pixel experince plus (unofficial from your link that you have provided)
Click to expand...
Click to collapse
Follow this guide
How to Flash a GSI on an Android Device
Follow this guide to flash a GSI on your Android device.
www.makeuseof.com
To get into fastbootd u need to go to recovery mode then select enter fastbootd

fluffyball21 said:
Follow this guide
How to Flash a GSI on an Android Device
Follow this guide to flash a GSI on your Android device.
www.makeuseof.com
To get into fastbootd u need to go to recovery mode then select enter fastbootd
Click to expand...
Click to collapse
When ever i use adb reboot bootloader device boot into download mode and fastboot commands are not working there so i simply can't access fastboot even also adb reboot fastboot or adb reboot fastbootd not working when giving these commands device simply just reboots , please can you tell me how you got into recovery and then into fastboot mode after flashing patched recovery in brief ...And also i think my recovery isn't patched or did not worked after patching may be the script is not working or i made any mistake while using the script so will it work if you attach the patched recovery of your m33 5g device if i flash that using odin?

sunnypoddar1919 said:
When ever i use adb reboot bootloader device boot into download mode and fastboot commands are not working there so i simply can't access fastboot even also adb reboot fastboot or adb reboot fastbootd not working when giving these commands device simply just reboots , please can you tell me how you got into recovery and then into fastboot mode after flashing patched recovery in brief ...And also i think my recovery isn't patched or did not worked after patching may be the script is not working or i made any mistake while using the script so will it work if you attach the patched recovery of your m33 5g device if i flash that using odin?
Click to expand...
Click to collapse
Reboot to recovery from phone then choose enter fastbootd option if it is there. If it is not then u need to patch the recovery again and download that then flash that with Odin. I don't have the patched file with me now so in the meantime try again

fluffyball21 said:
Reboot to recovery from phone then choose enter fastbootd option if it is there. If it is not then u need to patch the recovery again and download that then flash that with Odin. I don't have the patched file with me now so in the meantime try again
Click to expand...
Click to collapse
tried , tried and tried and now i'm tired i think for me it's not possible

U just need extract it then flash it with odin in ap slot also while having auto restart off in options

fluffyball21 said:
U just need extract it then flash it with odin in ap slot also while having auto restart off in options
Click to expand...
Click to collapse
if auto restart has to be off then how would i restart into recovery from download mode means which button combination i have to press

sunnypoddar1919 said:
if auto restart has to be off then how would i restart into recovery from download mode means which button combination i have to press
Click to expand...
Click to collapse
U gotta press volume down and power after it finishes flash then immediately switch to volume up and power key combination when the screen turns black. If u failed to get fastbootd u need to do it again by either reboot to bootloader from recovery or pressing volume down and power on bootscreen then pressing volume up and down while USB is connected to computer and reflash. Once u do it successfully I think it wud be there for the next time without issues