Database Develop

[TWRP][64 bit][3.2.1_r12][UNOFFICIAL]Moto Z2 Play[Albus]

TWRP 3.2.1_r12 Moto Z2 Play (albus)​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03

I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.

Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?

Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx

JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.

3.1.2_r18 version released. Check download link in OP

hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?

fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok

rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.

I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?

Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.

kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.

Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.

kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?

Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.

kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.

I make a full backup, so can I restore that backup file after LineageOS?

This works when go command fastboot boot .... ?

I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...

Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).

[RECOVERY][OFFICIAL] TWRP for Galaxy S9 and S9+ (Exynos)

Team Win Recovery Project
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
#include <std_disclaimer.h>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy S9:
https://twrp.me/samsung/samsunggalaxys9.html
Galaxy S9+:
https://twrp.me/samsung/samsunggalaxys9plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - Discussion, Testing, Feedback and Support
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
To contribute:
TWRP Code Review
Github pull requests will be ignored.
XDA:DevDB Information
TWRP for Galaxy S9 and S9+, Tool/Utility for the Samsung Galaxy S9+
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2018-03-15
Last Updated 2018-08-15

Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Apr 18, 2018 (twrp-3.2.1-2):
Refactor USB configurations (fixes ADB)
Remove /cpefs from filesystem table (fixes /cpefs warning/error)
Rebase Kernel to ARCC. (fixes I/O performance issues)
Use correct OTG mount path
Enable software encryption support (general AOSP only, Samsung method remain unsupported)
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
USB connection fixes
Mar 14, 2018:
Initial version

Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Since Android O, Samsung introduced a new security feature, Remote Mobile Manager (RMM) aka Remote Lock Control (RLC). This feature allows stronger theft protection but unfortunately it also imposes a burden on users like you.
Samsung added a 7-day buffer period for enterprises or device owners to spot a missing/rogue device so they can use this feature to lock the device remotely.
In this 7-day (Prenormal) period, you can NOT flash any custom binaries including but not limited to this TWRP. OEM Unlock option won't appear, either.
(You will meet "custom binary blocked due to remaining installment balance" or "custom binary not allowed" error when you try)
The 7-day timer will start/reset once you completed the setup wizard. After 7 days (168 hours), RLC service will send an inquiry to Samsung's server. If your device is "clean", the RMM state will become "Normal".
Then you can enable "OEM Unlock" option and flash TWRP. Be careful, DO NOT reboot to a stock ROM before you flash patch in part 2 of this guide or you will have to go through another
Whether you have RMM problem or not depends on your model, region and/or carrier.
If you don't have any wait period to enable OEM Unlock option, congratulations but please do NOT mislead other people.
NOT EVERYONE IS AS LUCKY AS YOU.
If you don't have RMM problem when you get the device, it is unlikely that you will get any RMM problems later.
But note that this problem applies to MAJORITY of people.
Note that the special patch will freeze RMM, FRP and OEM lock state.
This is an anti-stupid measure to prevent careless users from enabling security measures which are not compatible with custom binaries.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings, remove all Samsung and Google accounts and if your device is registered to an enterprise, de-register it.
3. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
NOTE: You will be asked to do a factory reset, that's normal.
BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS.
You should take a look at the whole guide and be prepared to use reboots as chances to flash or reboot into TWRP.
4. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
5. Download and extract Odin (Samsung's Flash Tool) to your computer.
6. Download a .tar image of TWRP.
7. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
8. Open Odin and place that TWRP tar file in the [AP] slot.
9. Connect your phone.
10. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
11. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP:
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO".
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.
Now you may want to flash a root solution (Magisk, SuperSU, etc) or custom ROM but keep in mind that:
1. This thread does NOT provide technical support to any root solution or ROM unless the problem is DIRECTLY related to TWRP and there is no other solution without modifying TWRP itself.
Please contact developer of respective ROM or root solution for technical support.
2. Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection". https://www.samsungknox.com/en/blog/real-time-kernel-protection-rkp
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.

Awesome work Jesse. Thank you!

Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk

@jesec hey mate, happy to see you again (S7 ROM)
Sorry i don't have this device but my friend will try soon

spackeddie01 said:
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
Click to expand...
Click to collapse
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.

BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset.
Click to expand...
Click to collapse
Please boot to recovery instead of system.
Be aware that Android Verified Boot requires data to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data,*all*state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot) It is normal to get such prompt.

Got twrp installed formatted data, rebooted twrp, do we need Dm-Verity? If so how to get it on as MTP is not working, or OTG, and system bootloop so can't get back in to do it that way.

BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
Click to expand...
Click to collapse
You have to flash dm-verity/magisk.

****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.

iamnotkurtcobain said:
Awesome work Jesse. Thank you!
Click to expand...
Click to collapse
Dis you try treble AOSP ?

giorgior.r said:
Dis you try treble AOSP ?
Click to expand...
Click to collapse
I can't. This TWRP is for 9+. I have a normal S9.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
BokkieAndijk said:
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
Click to expand...
Click to collapse
You formated system it seems.
Steps are:
-flashing TWRP
-boot into TWRP
-format Data
-reboot recovery
-install magisk
-reboot

iamnotkurtcobain said:
You have to flash dm-verity/magisk.
Click to expand...
Click to collapse
pls can you give me a link to the packages you have used?
Thanks.:good:

Nice to see you doing work on the S9 @jesc

deleted

@jesc good to see you in the s9 forums. Great work as usual

Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.

BokkieAndijk said:
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
Click to expand...
Click to collapse
check in this site
https://www.sammobile.com/firmwares/database/SM-G965F/

Flashed twrp then flashed no dm verity - seemed to flash ok - but saw one error message that says "failed to mount '/cpefs' - I haven't seen that error before but thought it might be important. THis message happens after the flash has finished -(after it says updating partician details)
Tried to flash magisk after I flashed twrp and phone bootloops had to flash stock in odin

Honor 9 Lite TWRP 3.2.1-0 available

Now (20180512) is TWRP for Honor 9 Lite WITH de-/en-cryption avalaible !!!
https://forum.xda-developers.com/9-...rp-3-2-1-0-t3789306/post76496923#post76496923
You can use with delivered encrypted "data"-partition
My special thank's : @Pretoriano80 for this good work ! :good:
**************************************************************************************************************************
Phone Unlocked AND FRP Unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
##########################################################
This was the first TWRP (without de-/en-cryption) that's work on Honor 9 Lite (state: deprecated)
##########################################################
This TWRP is deprecated
TWRP for Huawei LLD-AL10
The good news: a TWRP for the Honor 9 Lite is available!
The not so good: everything you do with your phone, you do to your own risk !!!
My Test on Honor 9 Lite LLD-L31
flash custom-recovery und -system, reboot, phone start's as new, change language ... (only minimal-settings doing)
flash this trwrp, boot to twrp, settings, format data & reboot from twrp to twrp, backup test 1 <- attention-point "Format Data"
reboot to system, all settings doing, boot to twrp, backup test 2
reboot to system, a few apps install, boot to twrp, backup test 3
Recovery Test : right now restore "backup test 1"
reboot to system, check : everything as well, as it was at the time - "YES"
reboot to twrp, restore "backup test 3"
reboot to system, check : everything as well, as it was at the time - "YES"
So this twrp works except for the limitations described by the developer. By ME !
More testing not doing by now. If you need this TWRP, download and test self.
what does that mean By ME : i have a H9L from February 2018 with LLD-L31 8.0.0.127 (C432)
(my test is a cookbook recipe - step by step / short what i am doing)
Acknowledgments :good: :laugh:
My special thanks for this original Chinese TWRP for free use goes to: "weibo.com/xinkid520"(developer), "Team Win Recovery Project" and @ChinHon.
Developer-text translation (chinese->german->english) :
[FIRE] Honor 9 Youth Edition TWRP3.2.1 EMUI8.0 Third Chinese English Recovery First Edition TWRP3.2.1
Based on the latest TWRP 3.2.1 Android 8.1 source code compiler customization; test model LLD-AL10 pass.
Testing for other models is normal and common. <- LLD-L31 is other model !
The data can not be decrypted automatically. You must manually format the data partition before you can use the data and the SD card.
Back up the data in advance on the computer.
Note: MTP mode for copying files is not supported, but adb-push.
Perfect support for flashings and ADB commands.
Rooting is now more convenient. Zip files can be processed and also such custom Roms installations.
It supports internal and external card backup and recovery.
The Chinese standard language also supports English.
This restore does not support the official update package, including an OTA upgrade
Link for downloading huawei-lld-twrp3.2.1-8.3.28.img : https://www.androidfilehost.com/?w=files&flid=261005
I write in the hope that is short and helpful
Append 20180507:
Now is TWRP with de-/encrypt in short time available (i am test beta-version)
I wish reset my "data" to factory-settings(crypt)
I use recovery_ramdisk_BKL-L04_nocheck (thank's @Atarii) for install my FULL-Update
After this reboot my phone, FULL-Update is installed AND "data" is crypted (factory-state)
Now work twrp (new twrp in test-version !) WITH de-/encryption.
I hope in next days comming new thread from developer in this forum.
The new TWRP is in standard-look and -feeling and -language.
Append 20180512:
Now (20180512) is TWRP for Honor 9 Lite WITH de-/en-cryption avalaible !!!
https://forum.xda-developers.com/9-...rp-3-2-1-0-t3789306/post76496923#post76496923
You can use with delivered encrypted "data"-partition

Hi.
Where do you get it?
Have you a link to the sources?
Please provide more infos.
Thank you for your afford.
Greetings
Vsrookie

Its not official till now. And as the one before me... Without sources i find it cimplicated to install...
The Features are the same as for the honor view 10 twrp... And that is official...

@JamesBott has described in detail where the recovery is coming from.
It was developed for the honor 9 youth edition and the honor 7x. If you want to know more,
contact the developer xinkid520 at baidu. However, you must know how to speak Chinese.

ChinHon said:
@JamesBott has described in detail where the recovery is coming from.
It was developed for the honor 9 youth edition and the honor 7x. If you want to know more,
contact the developer xinkid520 at baidu. However, you must know how to speak Chinese.
Click to expand...
Click to collapse
Hi.
Which details? I think there is a missing link.
Where was this twrp announced for the first time?
Whatch out for the stickies.
Greetings
Vsrookie

Maybe you should open your eyes or take glasses to read.
The link to the developer is on the screenshot.
The first announcement is here.

ChinHon said:
Maybe you should open your eyes or take glasses to read.
The link to the developer is on the screenshot.
The first announcement is here.
Click to expand...
Click to collapse
Yes, it is written among all the other information somewhere. But the topic says TWRP for H9l... And this is not true and could lead to unwanted results. And that's a fact, too.

ladies and gentleman !
please - do not split our hair
look on my first line : "TWRP for Huawei LLD-AL10"
line 4 : "My Test on Honor 9 Lite LLD-L31"
deeper by : Developer-text translation (chinese->german->english) :"
[FIRE] Honor 9 Youth Edition TWRP3.2.1 EMUI8.0 Third Chinese English Recovery First Edition TWRP3.2.1
Based on the latest TWRP 3.2.1 Android 8.1 source code compiler customization; test model LLD-AL10 pass.
all information is available ! only what is missing : "source-code" !
i am sorry - my chinese reading is nothing!
if everyone here how can read chinese ? please - go to developer-home-page and look for source-code !
if source-code available - write link here and i update my post #1 with this source-code-link !
make peace - not war :good:
CALL - TO ALL how have download this twrp and tested on own phone ???
please write short message here : i am tested on LLD-L31 (or other) and this work/not work
i see download number, not see "tested/work/notwork" (download's now : 53 + "x" from first link "MediaFire")
thank's for your help :good:

ChinHon said:
Maybe you should open your eyes or take glasses to read.
The link to the developer is on the screenshot.
The first announcement is here.
Click to expand...
Click to collapse
Sorry, but why so rude? Please calm down.
It is a simple question.
What i see is a link to androidfilehost, uploaded by the OP.
I really appretiate that the OP uploaded it.
But where has the Original dev announced the recovery. Did he made the devicetree public?
Greetings
Vsrookie
Ps: Did you also tried to restore the backuped partitions?

@vsrookie
YES - i use this twrp on my H9L !
YES - i have 4 Backup's
YES - Restore work fine!
bevor 1/2 hour i kill my "user-data", boot to twrp, Restore last Backup and phone work!

sorry double-save from post #10

Sorry, didn't mean no harm.
Here is the link to the first release:
https://weibo.com/xinkid520?is_hot=1
See the third posting on this page.

JamesBott said:
sorry double-save from post #10
Click to expand...
Click to collapse
Guys I am unable to backup anything via TWRP(both alpha build as well as this thread TWRP) .
It shows error like Permission Denied. Cant create TWRP/Backups/........... folder

@VigneshS007
Hi.
you use twrp from link on post #1 ?
you read post #1 : format "data" and follow that what in developer-text written ?
what's your phone ? LLD-L31 ?
the msg "permission denied..." say "i will save and have no right"
My Test on Honor 9 Lite LLD-L31
the core/attention -Point is line 2
-> flash this trwrp, boot to twrp, settings, format data & reboot from twrp to twrp, backup test 1 <- attention-point "Format Data" <-
i am Format Data, not wipe, not other >>>make Backup from your data BEVOR Format !!! After is to late : erased !<<<
after this have twrp permission to write on Data
Thank's for your msg

JamesBott said:
@VigneshS007
Hi.
you use twrp from link on post #1 ?
you read post #1 : format "data" and follow that what in developer-text written ?
what's your phone ? LLD-L31 ?
the msg "permission denied..." say "i will save and have no right"
My Test on Honor 9 Lite LLD-L31
the core/attention -Point is line 2
-> flash this trwrp, boot to twrp, settings, format data & reboot from twrp to twrp, backup test 1 <- attention-point "Format Data" <-
i am Format Data, not wipe, not other >>>make Backup from your data BEVOR Format !!! After is to late : erased !<<<
after this have twrp permission to write on Data
Thank's for your msg
Click to expand...
Click to collapse
Okay i will try that once i am ready to format my data partition. Thanks for ur help

VigneshS007 said:
Guys I am unable to backup anything via TWRP(both alpha build as well as this thread TWRP) .
It shows error like Permission Denied. Cant create TWRP/Backups/........... folder
Click to expand...
Click to collapse
Internal or External Media choosen to save?
With the internal filemanager you can go to the location and give the folder chmod 755...

Darkest-Dark said:
Internal or External Media choosen to save?
With the internal filemanager you can go to the location and give the folder chmod 755...
Click to expand...
Click to collapse
Not working on both storages... ???
Darkest dark i will contact u in Telegram now

@VigneshS007
your phone "LLD-L31" ?
you use this twrp Link for downloading huawei-lld-twrp3.2.1-8.3.28.img : https://www.androidfilehost.com/?w=files&flid=261005 ?
is not the first offered, is 2nd offered !
what the first factory-OS on your phone Android 7 or 8 ?
i think, the first factory delivered Android 7, actual delivered Android 8 : it's differend boot, recovery ...
example
7 : fastboot flash recovery recovery.img
8 : fastboot flash recovery_ramdisk recovery.img
8 is new OS, google make more for "self-health, security .. "
In order for us to help, we need to know what kind of model you have with which OS

JamesBott said:
@VigneshS007
your phone "LLD-L31" ?
you use this twrp Link for downloading huawei-lld-twrp3.2.1-8.3.28.img : https://www.androidfilehost.com/?w=files&flid=261005 ?
is not the first offered, is 2nd offered !
what the first factory-OS on your phone Android 7 or 8 ?
i think, the first factory delivered Android 7, actual delivered Android 8 : it's differend boot, recovery ...
example
7 : fastboot flash recovery recovery.img
8 : fastboot flash recovery_ramdisk recovery.img
8 is new OS, google make more for "self-health, security .. "
In order for us to help, we need to know what kind of model you have with which OS
Click to expand...
Click to collapse
My device is LLD-AL10. COMES WITH ANDROID OREO out of the box. Twrp flashing working fine.. but backup only not working.

@VigneshS007
your device is same as my, only other country
your OS is same as my
twrp-developer write " test model LLD-AL10 pass."
i think, this twrp https://www.androidfilehost.com/?w=files&flid=261005 from post #1 must work by you
the ATTENTION-POINT is "flash this trwrp, boot to twrp, settings, format data & reboot from twrp to twrp, backup test 1 " (line 2 from post #1)
go step by step ending by "backup test 1"
if backup NOT work return to settings: mount NOT ro ? format data : read twrp-lines "format data real?" and "you must reboot from twrp to twrp"
if rebootet from twrp to twrp and backup not work - return to beginnings : flash twrp
I know, it does not help you : i must 3x flash twrp before backup work !

[GUIDE][SM-T510] Unlock/Root - Tab A 10.1 (Android 10)

This are exactly the steps I did to root this device.
Pre-requisites
. Odin 3.14.4
. Latest MagiskManager(Im using 8.0.2)
. bootloader unlocked
. Firmware that matches the version installed on your device.
. Lz4 extractor : https://github.com/lz4/lz4/releases
. TAR.MD5_PACKAGER
First at all, remember to unlock T510 bootloader
The firmware which is based is this : SM-T510_1_20200702122203_r4oibm2ll7_fac.zip
. Extract AP_T510XXU3BTFN_CL19000394_QB32592397_REV02_user_low_ship_meta_OS10.tar.md5
. Extract boot.img from .tar.md5
. lz4.exe -d boot.img.lz4
boot.img
. Copy MagiskManager-v8.0.2.apk to your tablet and Run it.
- Magisk > Install > Recovery Mode Selected > Next > Method > Select and Patch a File > boot.img > LET'S GO > "All done!"
File called : magisk_pached.img
. Copy to PC
- copy magisk_patched.img boot.img
copy boot.img to TAR_MD5_PACKAGER\parts\
. TAR.MD5_PACKAGER.bat > "1" > boot.img > "Y" > "2" > "1" > "Y" > "4"
in TAR_MD5_PACKAGER\packaged\ : boot.img.tar.md5
. Run Odin
Plug USB > should say "Added!!"
. Volume Up and Power until you get into recovery menu > reboot to bootloader
- Connect USB
- Run ODIN
. In Odin : AP > boot.img.tar.md5
Options > Delect "Auto Reboot"
Click Start . Make sure the operation succeeds.
Unplug your device and reboot.
. Ask for Factory data reset > Factory Reset
. Reboot System now
. Volume Up + Vol down + Power
. Setup WiFi
. Install and run MagiskManager-v8.0.2.apk
. Tablet will ask Reboot System now
Click to expand...
Click to collapse

Great! I somewhat did the same method for rooting/twrp installing. I was on latest Android 10 build(September patch perhaps). I download the latest firmware and unzipped it then I further extracted AP_T510XXX......... .tar.md5 using zarchiver which have me AP_T510XXX........ .tar. Instead of extracting boot image I patched the whole thing with megisk and flashed it from AP from ODIN. When tablet booted installed megisk manager apk and saw that tablet was rooted.
You can further flash TWRP image using flashify but then stock ROM may not boot. Anyway moving further if you want to flash GSI, first flash Lineage or Nexus Rom and then A64b GSIs can be flashed.

Thanks both! i will take a look when i am at home, i tried to patch AP_T510XXX......... .tar.md5 with magisk but i didnt extract it before and it hold on boot, i try to extract first like @Mrigendra10 then patch it and then odin...

i like the guide but the wording need some improvement newer members to understand it clearly just my 2 cents thanks for guide.

Help me out here, I did everything correctly and installed it with Odin, it was a success, but when I installed magisk on my tablet again, nothing new happened, didn't ask me to reboot and I tried an app that requires root but said I wasn't rooted. Help please.

Used a root checker, says a super user app was found, that being Magisk. says root unavailable and no su binary .

Hi, just to be sure
Odin > Options > Delect
means 'Deselect' and not 'Select'?
Thx!

cera33 said:
Hi, just to be sure
Odin > Options > Delect
means 'Deselect' and not 'Select'?
Thx!
Click to expand...
Click to collapse
Yes, it does

I was able to complete everything step by step and used a root checker and it states "Root access is not properly installed on this device. Any idea what may have gone wrong? Do I just start over and try again?

same here. can not root SM510. tried linegae, nexus and stock from. any video root with magisk with rambus on and saftety net passed?

Same..

Hey, just some notes to clear up any confusion about Magisk on the T510. The tablet doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And per the Magisk installation instructions:
Pay special attention to the Ramdisk info. If the result is Yes, congratulations, your device is perfect for installing Magisk! However, if the result is No this means your device’s boot partition does NOT include ramdisk. This means you will have to go through some extra steps to make Magisk work properly.
If your device does not have boot ramdisk, read the Magisk in Recovery section after installing. The information in that section is VERY important!
If you are using a Samsung device and the SAR result is Yes, please check its own section.
If you are using a Huawei device and the SAR result is Yes, please check its own section.
Click to expand...
Click to collapse
In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Each device has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick Google search should easily get you this info of your device. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into actual recovery mode, continue to press volume up until you see the recovery screen.
After installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Recovery Mode)
Click to expand...
Click to collapse
I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk.
I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid. Usunoro...
On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.
(P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)
Fur and Purrs --
--
King Cheetah

wolfyj1 said:
I was able to complete everything step by step and used a root checker and it states "Root access is not properly installed on this device. Any idea what may have gone wrong? Do I just start over and try again?
Click to expand...
Click to collapse

[TWRP & Custom ROM]Huawei Y6 MYA-L11

Introduction
This ROM is working for Huawei Y6 MYA-L11
I fixed cellular network (SIM card recognition), but i don't know how to fix other issues as it don't boot up if i put some huawei libraries.
Huawei Y6 2017 (Huawei Nova Young) don't have official page, not even a custom ROM, nothing, so i needed to take action on this and free ourselves from huawei terrible practice to lock everything.
So here it is, finally custom ROM to this shady model name and device.
[What don't work]
- Back camera
- Back flashlight
- And front camera is capturing in upside down
- NFC
- Easy button (won't be recognised as it's huawei specific hardware code)
- GPS is kinda shady, don't know if it works or not
[What work]
- Everything else
---------------------------------
Everything you do with your device, you do at Your own!
Credits goes to:
@salembream [Bootloader unlock]
@SGS3_0 & @shanman-2 [TWRP]
@shivom007 [DotOS ROM]
@indestructible master [Porting ROM and putting all together on this device to work for this model]
Let's get started.
--------------
[Unlock bootloader]
First we unlock bootloader on huawei that ask us for code.
We need to bypass it.
Drivers
Download file MYA-L11_FT_Drivers
Unzip it.
Exctract and run Huaqin_Android_Driver_All-in-One.zip, to install necesary drivers.
Restart PC to apply drivers
SP flash tool
Open SP flash tool
note: these files are in _MAYA_L11 sub-folder of SP flash tool
a. select Download Agent : "MTK_AllInOne_DA.bin"
b. select the scatter file: "MT6737T_Android_scatter.txt"
Backup proinf partition
a. Press on Readback tab.
b. Press on "Add" button.
c. Double click on the new entry, and chose where you want to save the backup.
d. Select Type: Hex.
Region EMMC_USER
Start Address: 0x80000
Length: 0x300000
e. Press Read Back button " the green arrow "
f. now make sure your phone is turned off,
press and hold the down volume button and plug the USB cable..
keep pressing the volume down button untill the backup process is done.
Flash the new proinfo partition
a. Download the file: proinfo_0x80000.zip (and unzip it)
[ note: you may edit it using hex editor and replace the serial keys from your backup. ]
b. Make sure to turn off your phone and disconnect the USB.
c. In SP flash tool press " ctrl + alt + v ", to enable the advanced mode.
d. from "Window " in menu bar select " Write memory"
e. New tab will be available "Write memory "open the it.
f. Set File path: the downloaded file from above "proinfo_0x80000"
Begin address: 0x80000
Region : EMMC_USER
"by DRAM"
g. click on write memory
h. now as before press and hold volume down button on your phone and plug the USB cable.
i. keep pressing the volume down button untill the flash is done.
Unlock the phone
a. make sure to enable "OEM unlock" from developer option in your phone.
b. boot your phone to bootloader " fastboot" .
c. from your PC open the "minimal adb tool " or what you have ..
d. type this command :
fastboot oem unlock 5A4CB78CF6711B04
e. done !! your phone will report now and it will do a full factory reset and will delete every thing .. so make sure to have backups
f. and don't relock bootloader (huawei problems), as it can brick device, live with unlocked bootloader
--------------
[TWRP]
Flash TWRP recovery
now with unlocked bootloader, time to flash twrp recovery
in booted android go to developer options>enable USB debugging
and also enable/check OEM unlock (so you can modify partitions)
download twrp-3.2.1-1.zip (note: older version also available: twrp_3.1.1.zip)
unzip file and flash in bootloader mode
Code:
fastboot flash recovery recovery.img
You can rename .img file as you want.
or use SPFlashTool.
Boot into TWRP recovery
To boot into recovery, first you need to completely turn off phone.
Then hold volume up + power button.
Release volume up and power button, moment when you see warning for unlocked bootloader (as if you hold longer it will bring you to huawei erecovery)
It should boot TWRP, but don't enjoy yet, when you see TWRP boot logo, tap on screen (anywhere) as much as you can (and as fast), because TWRP have some touch issues (buttons dont work, slider slides but dont react to it)
If slider and button works fine then you can procced, you successfully flashed TWRP.
--------------
[Flashing custom ROM]
Backup
First you need to backup everything.
Go to Backup
And check all boxes (because huawei have hardware specific code for their stock ROM and you dont want to screw up anything, or lose some important partitions)
Swipe to backup.
Save it to somewhere safe (on PC)
Preparation for flashing custom ROM
Download Huawei MYA-l11 DotOS v1.2.zip
Download gapps: https://opengapps.org/
(Download ARM64, 7.1, Pico)
Put those 2 files in SD card or internal memory.
Now boot into TWRP, and go into Wipe>Advanced Wipe
Check Data
And click button (above slider) Repair or Change File System
Click Change File System
And then choose EXT4
Reason for doing this is because huawei f2fs is encrypted, and if you flash it without this, it will be stuck on asking you for password, and you would have to reflash stock recovery and all can get messed up, just follow these instructions
And then, again, go to Wipe, and wipe Data, Cache, Dalvik and System (clean flash)
Flashing custom ROM
Now go into Install and choose downloaded ROM zip and flash it.
Then flash gapps, and when finished Wipe Dalvik/Cache
Reboot into system
If you encounter google wizard stops working, remove SIM card, finish wizard without setting up wifi, or any account (do it manually)
When wizard is finished, bring back SIM card and sign in Google acount from settings
That's it, enjoy in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FULL BRIDGE RECTIFIER !!!
--------------
[Bug fixes]
NVRAM warning 0x10 in wifi settings
Download FIX NVRAM.zip
Flash it via TWRP.
Done.

Cool! Can you port (again .-.) LineageOS 14.1 yo Y5? I can be the ROM tester.

luisl173 said:
Cool! Can you port (again .-.) LineageOS 14.1 yo Y5? I can be the ROM tester.
Click to expand...
Click to collapse
can you check this, is that your phone?
LineageOS 14.1 (Android 7.1.2)
for Huawei Y5
konstakang.com
or check other link too
How to Install Lineage OS 14.1 On Huawei Y5 II (Android 7.1.2 Nougat)
Good News for all Huawei Y5 II owners. Now you can install the latest Lineage OS 14.1 on Huawei Y5 II based on Android 7.1.2 Nougat. Lineage OS is a new Open Source project morphed after the death of CyanogenMod OS. However, the man behind the LineageOS seems to be the CEO of Cyanogen.inc S
www.getdroidtips.com

Hi, is there any news about this custom rom?

indestructible master said:
can you check this, is that your phone?
LineageOS 14.1 (Android 7.1.2)
for Huawei Y5
konstakang.com
or check other link too
How to Install Lineage OS 14.1 On Huawei Y5 II (Android 7.1.2 Nougat)
Good News for all Huawei Y5 II owners. Now you can install the latest Lineage OS 14.1 on Huawei Y5 II based on Android 7.1.2 Nougat. Lineage OS is a new Open Source project morphed after the death of CyanogenMod OS. However, the man behind the LineageOS seems to be the CEO of Cyanogen.inc S
www.getdroidtips.com
Click to expand...
Click to collapse
No i meant Huawei Y5 2017 but i found a rom for it

I followed the steps to flash the custom ROM in my Huawei Y5 2017 MYA-L13 HWMYA-L6737, but it failed so I modified the updater-script file to be able to proceed and the ROM was flashed successfully. It seemed to be these models were equivalent according to this comparison...
However, when I finished the initial wizard I came across problems with detecting the SIM card: it was inserted but it wasn't recognized... Also about the WiFi at first it appeared to work as I was able to detect and connect to my access point, but immediately it was disconnected again and again.
So in the end, it failed and I needed to restore my device with a TWRP backup I did.çI just wanted to share this.
Is there a way to make SIM card to be detected somehow?
Thanks in advance

metafaniel said:
I followed the steps to flash the custom ROM in my Huawei Y5 2017 MYA-L13 HWMYA-L6737, but it failed so I modified the updater-script file to be able to proceed and the ROM was flashed successfully. It seemed to be these models were equivalent according to this comparison...
However, when I finished the initial wizard I came across problems with detecting the SIM card: it was inserted but it wasn't recognized... Also about the WiFi at first it appeared to work as I was able to detect and connect to my access point, but immediately it was disconnected again and again.
So in the end, it failed and I needed to restore my device with a TWRP backup I did.çI just wanted to share this.
Is there a way to make SIM card to be detected somehow?
Thanks in advance
Click to expand...
Click to collapse
Hi, how did you modify the updater-script file in order to install on HWMYA-L6737?