Database Users

[HOWTO] Running CTS on TF101

Running the Android Compatibility Test Suite on TF101​
Background: what CTS is
The Android Compatibility Test Suite is an automated test harness which tests one or more devices to ensure that they offer a fully-compliant running environment for 3rd-party applications.
Passing these tests is required to use the Android brand name for retail devices and it's also the basic prerequisite for acquiring a Google Play license for OEMs.
Background/2: what CTS isn't
As of the current CDD (Compatibility Definition Document) the CTS still doesn't enforce stability or performance requirements for devices, even though some of its tests are taxing enough for the device to expose subtle problems. Some performance tests are nevertheless included, but they're not run by the main CTS plan, nor are they part of the current CDD.
Background/3: why it's important for TF101 users
Given the way the CTS stresses the system, it is useful as a standardised testing procedure for some of the problems some users are currently experiencing with ICS on TF101. It also can help ensuring that the device works as intended with (most) 3rd-party applications straight out-of-the-box.
Requirements: host
The host should be a Linux-based workstation with the Java 6 JDK installed (either Oracle's or OpenJDK - IBM JDK or GNU gcj are not supported, while Oracle/OpenJDK JDK 7 are untested), a fully working installation of the Android SDK and about 3 or 4 GB of disk space available for downloaded media files.
Test results are best viewed with a recent version of Firefox, otherwise you can post-process them into an HTML file using an XSLT 2.0 engine (tested with Saxon).
Requirements: target device
The target device should be a completely stock and unrooted TF101 running 9.2.1.24. It is possible to run the CTS on custom roms, but the tests assume that the device is running a user build (not eng, not even userdebug) in secure mode. YMMV, expect unpredicted failures.
Required files
You're going to need the following files from the CTS downloads page:
Android 4.0.3 R2 Compatibility Test Suite (CTS)
CTS Media 1.0
The following files are optional:
Compatibility Test Suite (CTS) User Manual (if you want more information about the test harness)
Android 4.0.3 R1 CTS Verifier (used to perform user-assisted tests - I didn't run this yet, if you feel brave go ahead and post the procedure you used)
You may also need a log collecting application, even though the CTS should be capable of collecting device logs on its own (it didn't work for me). LogDog (if you have it) is strongly recommended.
Host-side setup
Download the required files and unzip them into a folder of your choice, then change the first line of media/copy_media.sh from:
Code:
#!/bin/sh
to:
Code:
#!/bin/bash
so that the script runs successfully on Debian-based systems (the script is full of bashisms which make dash complain and exit with multiple errors).
Ensure the user you'll be running CTS under has the proper privileges to run adb.
Device setup
First and foremost: perform a full Factory Data Reset (either through the Settings menu or using the VolDown+Power chord at boot time and selecting "Wipe Data").
As soon as the system boots after the wipe, perform the first run wizard selecting English (US) as the system language, connect the device to a wireless network, do not add any Google account (yet), and then reboot the device again to regain access to the system bar widgets (known 9.2.1.24 bug).
Once the system is back up, open Settings and perform the following actions:
disable Quick Settings (ASUS customized setting → ensure Use ASUS Quick Setting is unchecked)
disable System bar lock (ASUS customized setting → System bar lock → ensure Enable system bar lock is unchecked)
disable ASUS Sync (Accounts & sync → ensure Launch ASUS Sync is unchecked)
disable the internal GPS to save battery (Location services → ensure GPS satellites is unchecked)
deactivate all screen locks (Security → Screen lock → None)
temporarily enable Unknown sources (Security → ensure Unknown sources is checked)
under Language & input, ensure that the default input method is Android Keyboard
enable USB debugging (Developer options (dismiss the nag dialog) → ensure USB debugging is checked)
enable Allow mock locations (Developer options (dismiss the nag dialog) → ensure Allow mock locations is checked)
Now go back to Accounts & sync, turn off synchronization and add the Google Account you normally use for Google Play, but don't restore anything, nor accept to synchronize anything - you're going to need this just to install WakeLock.
Close the settings, open Google Play Store, go to its settings and deactivate automatic updates and the infamous auto-add for widgets, then install WakeLock.
Now go back again to Settings → Accounts & sync and nuke the account you just set up.
At this point, you're ready to upload CTS test files, so connect the device via USB to your host, disconnect any other Android device (emulators included!), ensure adb is on your PATH and then run the following commands from the directory where you unpacked the CTS archives:
Code:
cd media
./copy_media.sh all
This will upload the CTS media files (Big Buck Bunny) on the device, it will take a bit of time.
When it's done, you have to install the instrumentation apks:
Code:
cd ..
adb install android-cts/repository/testcases/CtsDelegatingAccessibilityService.apk
adb install android-cts/repository/testcases/CtsDeviceAdmin.apk
Now back on the device, open Settings again and perform the following actions:
enable Accessibility → Delegating Accessibility Service
go to Security → Device administrators → check all android.deviceadmin.cts.* administrators
This is a good time to install LogDog and reboot the system if you wish.
After that, go back to Security and ensure that Unknown sources is unchecked.
Unplug the device from USB and charge it fully.
After the device is charged, plug it back to the host, go to Settings → Developer options (again, dismiss the nag dialog) → ensure Stay awake is checked even though it won't work.
Launch WakeLock, select FULL_WAKE_LOCK as lock type, deselect "Show notification?", select "Start on boot?" and then "Acquire lock".
>>> Press the Home button to go back to the home screen.
Congratulations, you're ready to start the test harness.
Running CTS
On the host, run android-cts/tools/cts-tradefed. It will detect the device and print its android device id, then wait for a command.
To start the full CTS suite, issue run cts --plan CTS. It will take several hours and the battery will barely last for the entire duration. DO NOT INTERACT WITH THE DEVICE IN ANY WAY WHILE THE TESTS ARE RUNNING!.
After the test is finished, just type exit to terminate the test harness utility. Test results will be in android-cts/repository/results/<start time>/testResult.xml, open it with Firefox to see them or process them with saxon-xslt to produce an html file.
If you were running LogDog during the tests, archive the logs now and transfer the log archive to the host.
Post-run caveats
Wipe the device to ensure that any leftover is cleared. If you wish to run the tests again, restart from the "Device setup" step.

reserved for future notes

Thanks for the in-depth guide, very interesting!

Hi all,
imagine I run CTS and 15 tests fail. Can I run only those 15 tests and not the hole CTS?
Thanks!

GnobarEl said:
imagine I run CTS and 15 tests fail. Can I run only those 15 tests and not the hole CTS?
Click to expand...
Click to collapse
IIRC there is a way to tell tradefed to run a specific test, but I don't have the CTS documentation and tradefed itself ready at hand.
Try issuing 'help' at tradefed's prompt, it should provide with the necessary syntax to run a single test instead of a full-blown test plan.

Hi,
you can do something like "add --derivedplan -result fail" and run only failed tests. The problem is that creats another report, and not update the first report.
I wanted to have only one report in the end.
thanks for your reply.

FRP Destroyer - flashable zip

FRP Destroyer
Frp destroyer implements a method discovered by Zillinium to remove FRP Locks on Android device's that have a custom recovery.
Image's,
{
"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"
}
FRP Lock is what stops people from factory resetting their device by asking you to Log In to the last Account used on the device, this will help to do a proper factory reset.
Instructions,
Download FRP Destroyer.zip
Place FRP Destroyer on a micro SD Card.
Place the Card into your device.
Reboot the device into a Custom Recovery
Select Flash Zip or Install
Navigate to & select FRP Destroyer.zip
Flash FRP Destroyer.zip
Version Explanation,
Version (1.1) - Only destroy FRP Partition.
Version (3.0) - Destroy FRP Partition & Props.
Version (FRP + DM Verity + Force Encrypt) - Destroy FRP Partition, Disable DM Verity to help with boot errors, Disable Force Encrypt.
​
​
XDA:DevDB Information
FRP Destroyer, Tool/Utility for all devices (see above for details)
Contributors
Zillinium
Version Information
Status: Beta
Current Beta Version: 3.0
Beta Release Date: 2019-04-10
Created 2019-04-10
Last Updated 2019-04-10

Cab you help me with putting an Alcatel signature to the files so I can flash it by adb sideload and standard recovery. The device has no adb or fastboot that works and all the exploits I have seen to get in to chrome and use other software to get into settings etc - have been patched.
adb sideload sends the file and it fails on the signature missing

It is working. I hope it will work forever in my SM-J320FN with a custom rom which has always been blocked by frp lock. Thank you!

It's great bcz now i can have a custom recovery and a google account added at the same time

Is there a updated version? I am getting "signature verification failed" and "error 21" on a Samsung Galaxy Tab S6

It not works for me
It not works for me. Please can you help me? Thank you.
This is the output:
E: footer is wrong
Update package verification took 0.1 s (result 1).
E: signature verification failed
E: error 21
Installation aborted
ro.boot.bootdevice is 7824900.sdhci
All same for 3 zip files. Only the file with DM and Encrypt does not have the final string that starts with ro.boot etc.
Sorry for my bad English.

For anyone interested: @Bambii posted all the FRP_Destroyer versions here. I managed to overwrite my FRP partition on my ASUS ZenPad 8.0 Z380M (P00A) with FRP_DestroyerVersion (3.0).

Thanks so much for the file @Zillinium and others here. However, I'm in a bit of a quandary. I've got a Samsung Galaxy S7e with FRP lock on it, and this prevents me from Odin-flashing TWRP. I've tried the approach involving a Combination ROM but, to no avail, though I turned on Dev Options and USB Debugging, OEM unlocking is not there. When I try flashing a full stock ROM back to the phone, FRP Lock is still on. So, although I'd like to try FRP Destroyer, I can't get the custom recovery loaded, so that I can flash your file. Do you know of any other work-arounds?

stteve23 said:
Is there a updated version? I am getting "signature verification failed" and "error 21" on a Samsung Galaxy Tab S6
Click to expand...
Click to collapse
Same problem here.

Hi @Conzentroid, I ended up trying out one of the YouTube FRP Bypass methods and it worked for me. But, just as a precautionary note, some of these methods involve downloading apps that have trojans (stay away from the channel called ExPerT RoM). I downloaded software and it triggered viruses on three different virus checkers. Instead, I used the channel "Mohammed Ali" for my model. Although some of the steps were slightly different, it worked like a charm and FRP was removed. You do need a SIM set with a pin code though.

SM-G935V, flashed with a combo bin that loads TWRP
Did a factory wipe
Reboot into TWRP
Install off of SD Card the 3.0zip file, it began to run but got stuck
Reboot into TWRP
Install off of SD Card the 1.1 zip file and it runs,confirms writing zeros on FRP
Switch phone to download mode and install factory files with Odin
FRP still engaged

Ok so finally got it fixed with some help.
Here's what I don't understand and I'm hoping someone can educate me on.
The way it finally worked was to install a ATT ROM and it happened to finally allow me to use the emergency dialer to enter the developer diagnostic mode and using Z3X clear the FRP via it's ADB scripts
However earlier, the only way for me to enter the diag mode was to 1st load a combo file that would get me into the phones Factory Binary recovery mode, then I could access a dialer to access the diag mode (the VZW oem ROMS i had would not allow me to access the diag mode via the emergency dialer) from there I could run ADB scripts that would report they were communicating with the phone and clearing the FRP, but each time I rebooted the FRP was still engaged.
Why is it that it only worked entering the diag mode via a OEM rom and not when in the diag mode from Factory Binary?

Ironically, the most exploitable applications to utilize when attempting to circumvent the FRP feature of a device that is running the Android OS project are both Google Assistant along with TalkBack. It is a certainty of hacking or re-engineering operations to first and foremost identify the inherently usable characteristics of any and all recipients; hence, the previously mentioned applications are programmed in such a way as not to refuse the User. The following are instructions for accessing the Systems application to disable the functional components of FRP which present themselves in this assigned example:
DEVICE: T-Mobile REVVL 6 Pro 5G
OBJECTIVE: Disable Google Services and Android Setup/ Enable Android Accessibility Suite applications
Click Vision Settings at the rebooted device setup START screen.
While in TalkBack New Features Tutorial; use backwards L-Shaped finger gesture to promptly access Android Accessibility Suitesettings option.
(a). Click WHILE USING THE APP or ONLY THIS TIME.
(a.i). (IF: Required to use Google Sign-in): Click Back Button towards TALKBACK New Features Tutorial.
(a.ii). Repeat "Step"2.".
(a.iii). Click Use voice commands to command TalkBack Settings.
(a.iiii). While in TalkBack Settings; click Advanced Settings.
(a.v). (THEN: Skip to Step 5.): While in Advanced Settings; voice command for Google Assistant).
While in TalkBack mode; Use backwards L-Shaped finger gesture to promptly access Use voice command to control TalkBack menu.
Click Use voice commands to access Google Assistant.
While in Google Assistant mode; voice command for Settings application.
While in Settings; click Apps & notification menu.
While in Apps & notifications menu; click See All (X) Apps.
While in App info menu; click Android Setup.
While in Android Setup; click FORCE STOP.
Click Back Button towards App info menu.
While in App info menu; scroll to click Google Play services.
While in Google Play services; click DISABLE.
Repeat Step 10. .
While in App info menu; scroll to click Accessibility.
While in Accessibility menu; click Accessibility Menu.
While in Accessibility Menu; toggle Accessibility Menu shortcut to ON and promptly access Use accessibility button to open settings option.
(a). Promptly, click ALLOW to access "Allow Accessibility Menu to have full control of your device?".
While in Use accessibility button to open settings option; click GOT IT.
Click Back Button towards START screen.
Click Accessibility Menu shortcut icon.
While in Accessibility Menu shortcut; click Google Assistant.
(a). While in Google Play services required settings options; click Settings.
(b). While in App info via Google Play services; click ENABLE.
(c). Click Back Button towards START screen.
While in START screen; click START.
While in Copy apps & data settings option; click Back Button towards Connect to Wi-Fi.
While in Connect to Wi-Fi settings option; click Set up offline.
(a). Promptly, click CONTINUE to access "Set up offline?" settings option.
While in Date & time settings option; click Next.
While in Google Services; click More and Accept.
While in Set screen lock security settings option; click Skip.
(a). Promptly, click Skip to access "Skip PIN setup?".
Enter Home Screen.
REMINDER: The instructions provided herein are not to be assumed for use in all the involving situations which expect to circumvent the FRP feature. Each device has its quirks whilst persistence will bring about the accomplishment of the objective.
DO IT! DID IT! DONE!

SumWestAfricanGUY said:
Ironically, the most exploitable applications to utilize when attempting to circumvent the FRP feature of a device that is running the Android OS project are both Google Assistant along with TalkBack. It is a certainty of hacking or re-engineering operations to first and foremost identify the inherently usable characteristics of any and all recipients; hence, the previously mentioned applications are programmed in such a way as not to refuse the User. The following are instructions for accessing the Systems application to disable the functional components of FRP which present themselves in this assigned example:
DEVICE: T-Mobile REVVL 6 Pro 5G
OBJECTIVE: Disable Google Services and Android Setup/ Enable Android Accessibility Suite applications
Click Vision Settings at the rebooted device setup START screen.
While in TalkBack New Features Tutorial; use backwards L-Shaped finger gesture to promptly access Android Accessibility Suitesettings option.
(a). Click WHILE USING THE APP or ONLY THIS TIME.
(a.i). (IF: Required to use Google Sign-in): Click Back Button towards TALKBACK New Features Tutorial.
(a.ii). Repeat "Step"2.".
(a.iii). Click Use voice commands to command TalkBack Settings.
(a.iiii). While in TalkBack Settings; click Advanced Settings.
(a.v). (THEN: Skip to Step 5.): While in Advanced Settings; voice command for Google Assistant).
While in TalkBack mode; Use backwards L-Shaped finger gesture to promptly access Use voice command to control TalkBack menu.
Click Use voice commands to access Google Assistant.
While in Google Assistant mode; voice command for Settings application.
While in Settings; click Apps & notification menu.
While in Apps & notifications menu; click See All (X) Apps.
While in App info menu; click Android Setup.
While in Android Setup; click FORCE STOP.
Click Back Button towards App info menu.
While in App info menu; scroll to click Google Play services.
While in Google Play services; click DISABLE.
Repeat Step 10. .
While in App info menu; scroll to click Accessibility.
While in Accessibility menu; click Accessibility Menu.
While in Accessibility Menu; toggle Accessibility Menu shortcut to ON and promptly access Use accessibility button to open settings option.
(a). Promptly, click ALLOW to access "Allow Accessibility Menu to have full control of your device?".
While in Use accessibility button to open settings option; click GOT IT.
Click Back Button towards START screen.
Click Accessibility Menu shortcut icon.
While in Accessibility Menu shortcut; click Google Assistant.
(a). While in Google Play services required settings options; click Settings.
(b). While in App info via Google Play services; click ENABLE.
(c). Click Back Button towards START screen.
While in START screen; click START.
While in Copy apps & data settings option; click Back Button towards Connect to Wi-Fi.
While in Connect to Wi-Fi settings option; click Set up offline.
(a). Promptly, click CONTINUE to access "Set up offline?" settings option.
While in Date & time settings option; click Next.
While in Google Services; click More and Accept.
While in Set screen lock security settings option; click Skip.
(a). Promptly, click Skip to access "Skip PIN setup?".
Enter Home Screen.
REMINDER: The instructions provided herein are not to be assumed for use in all the involving situations which expect to circumvent the FRP feature. Each device has its quirks whilst persistence will bring about the accomplishment of the objective.
DO IT! DID IT! DONE!
Click to expand...
Click to collapse
Ok so I've tried this and it will not let me open any of but I can get to settings

[Guide] Root Pixel XL Android 11 (R)

[Guide] Root Pixel XL Android 11 (R) Unlock/Lock Bootloader + Install Custom ROMS + Update Magisk/Systemless Root​
Introduction
This Guide is for Google Pixel XL owners that want to Install/Flash Custom ROMs, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimers
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel XL phone with an unlocked bootloader.
An Android 11 (R) Custom ROM(s) (Update(s) 9. below).
A Computer with the latest working SDK Platform-tools r. 34.0.3 installed.
Important Notes:
If you use the Linux or Windows version of SDK Platform- tools r. 34.0.3 you must set the environment variable - See Note(s) for instructions on setting the enviroment Variable
If you have any problems with SDK Platform-tools 34.0.3. You can get SDK Platform-tools 33.0.3 here.
Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
Update Platform Tools, regularly, for optimal performance.
Need Google's USB Drivers for your Pixel Phone?
NEW
"...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
Updates
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Alpha
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta - app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
TWRP - TWRP Android 9 for marlin
Waiting for T.W.R.P. for Android 11 (R). (Q)
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.2 14Feb
SDK Platform-tools - r34.0.3 May 22, 2023
Custom Kernels
Google Pixel XL ROMs, Kernels, Recoveries, & Other
ElementalX Kernel Manager
My other guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Credits/Thanks/Recognitions
@topjohnwu - Magisk
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Open a Command Prompt/Boot Bootloader/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt to test ADB.
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Backup your data/Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number 7 times or until you see you're a Developer.
Tap back > Developer Options and toogle OEM Unlock on and, toggle USB Debugging on.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
This will erase all user data from the device!
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Important: Do not relock your bootloader until you have returned the device to Stock..
Boot bootloader
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times or until you see'You are a Developer. Tap Back > Developer options and toggle OEM Unlock off.
Install/Flash Custom ROM with @badabing2003 PixelFlasher
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones. by badabing2003
Install/Update Magisk Modules
Download Modules
Fox Magisk Module Manager Releases
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Fox2Code/FoxMagiskModuleManager
Open Fox2Code/FoxMagiskModuleManager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Fox2Code/FoxMagiskModuleManager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs for Pixel XL
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMS
Google Pixel XL ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
[OFFICIAL] LineageOS 18.1 for the Google Pixel XL by npjohnson
[ROM][11.0] crDroid 9.99 [UNOFFICIAL][marlin/sailfish] By blckbear
Themes, Apps, and Mods
Google Pixel XL Themes, Apps, and Mods
Other: TWRP Backup
TWRP Android 9 for marlin
Waiting for T.W.R.P. for Android 11 (R).

Has anyone tried using the current TWRP and Magisk?

I don't think those steps for rooting with canary give us full root, I was able to install adaway, but if i try to use a root uninstaller to remove Chrome (system app) it shows "Rooted, but cannot grant RW permissions on /system"
It seems no app can obtain root access to /System, i tested it with Root Explorer and the "mount /R/W" button does nothing when trying to mount the /System folder.

shiodooru said:
Has anyone tried using the current TWRP and Magisk?
Click to expand...
Click to collapse
Yes. Didn't work, just rebooted twice (I think) then booted directly into android.

Therev86 said:
I don't think those steps for rooting with canary give us full root, I was able to install adaway, but if i try to use a root uninstaller to remove Chrome (system app) it shows "Rooted, but cannot grant RW permissions on /system"
It seems no app can obtain root access to /System, i tested it with Root Explorer and the "mount /R/W" button does nothing when trying to mount the /System folder.
Click to expand...
Click to collapse
I have the same problem with AdAway too. I'm guessing that we don't have write access.

Trylr said:
I have the same problem with AdAway too. I'm guessing that we don't have write access.
Click to expand...
Click to collapse
I got Adaway to work, you have to open Magisk Manager, tap Settings and then tap
"Systemless Hosts" then reboot and run Adaway again

Therev86 said:
I got Adaway to work, you have to open Magisk Manager, tap Settings and then tap
"Systemless Hosts" then reboot and run Adaway again
Click to expand...
Click to collapse
Hey that worked. Thanks.

I have 10 on my phone. I just took the OTA a few hours ago. This may be a bit off topic but I can't get picture to play on Amazon video or Google movies only audio and captions. Hulu YouTube and Netflix work fine.
EDIT: AFTER A RESTART ALL VIDEO APPS WORK FINE. I'M THE dumbass ?

Useless without twrp

There is an installer for TWRP, "twrp-installer-3.3.1-0-marlin.zip" but because it doesn't follow the naming convention for all the previous releases "twrp-pixel-installer-marlin X.X.X" it appears at the bottom of the list of installers instead of the top.

Is anyone having good results with the battery life? It sucks for me.

H0wdy said:
Is anyone having good results with the battery life? It sucks for me.
Click to expand...
Click to collapse
I'm on Android 10, rooted with Magisk and I don't notice any bad battery life. Might be time for a battery replacement. I just got my battery replaced about 2 weeks ago.

Hi
Why the pixel imprint suddenly gone from my pixel xl?

I used your guide to unlock bootloader and get root on Android 10 and it worked perfectly. Thanks.

Trylr said:
I'm on Android 10, rooted with Magisk and I don't notice any bad battery life. Might be time for a battery replacement. I just got my battery replaced about 2 weeks ago.
Click to expand...
Click to collapse
The battery life only got bad after I upgraded, so I doubt it's hardware.

H0wdy said:
The battery life only got bad after I upgraded, so I doubt it's hardware.
Click to expand...
Click to collapse
How long have you been on Android 10? It always takes a few days at least for everything to settle down. More battery usage early.

salpsuc said:
There is an installer for TWRP, "twrp-installer-3.3.1-0-marlin.zip" but because it doesn't follow the naming convention for all the previous releases "twrp-pixel-installer-marlin X.X.X" it appears at the bottom of the list of installers instead of the top.
Click to expand...
Click to collapse
Wait, so that newest version of twrp does work with 10 on pixel XL?
Sent from my Pixel XL using XDA Labs

It works but it cannot decrypt. You will have to remove any passwords/patterns before booting into it

AP2FTW said:
Wait, so that newest version of twrp does work with 10 on pixel XL?
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
No, sadly we're still waiting. I was just offering a correction.

so i did the magisk patched method but i still don't have root in magisk? i took the boot.img out of the factory image and did it as i was told to...
anything i'm missing?
it's flashing it to boot_a, is it supposed to do something else?

(HELP) Rooting Samsung S7 Edge without Wipe

Hello XDA community,
Im a noobie when it comes to rooting, thats why i need help...
I deleted some files that i want to recover on my Samsung S7 Edge 2-3 years ago, this device has Android 7.0. (Never updated)
There is a lot of apps such as Disk Digger that offer you to recover every single file but the device must be rooted to access 100% on the internal memory.
Right now my Samsung S7 Edge is not rooted but i need to root to recover this files, so my question is, there is anyway of rooting without factory reset, or there is anyway of doing a fully backup of the internal memory of my device without touching the partitions so then i can try recovering my files later with this apps?
I hope someone can help me...
Regards

It's pretty disappointing that nobody ever responded to this considering how big is a community it is and how popular the S7 Edge was. I know this is pretty old and hopefully you were able to resolve this before this message but I'm going to respond to this just so you don't feel like your question wasn't acknowledged at all. I have an S7 Edge through Verizon which uses the Snapdragon processor. And I will find a link to post for you that although the method says it's discontinued I rooted my phone through this method and it works fine. The only reason that you would have to wipe your phone is if you're changing firmware as far as I know. I've rooted my phones and did not have to wipe them. I kept all the data and everything.
Before I lift this you are also asking about an application that you could use to back up your phone and that would be Samsung smart switch. It has a companion app for the desktop and it sinks to the phone and it'll make a backup of your data.
Now on to the root method all props and praise goes to the people that worked to give this to the people I'm not good at doing all this **** and I'm not meaning to step on any toes I'm just trying to help you since nobody did for two ****ing years.
To root
1. Download PrinceComsys Odin
Odin.Prince.Comsy.zip
drive.google.com
2. Download the engboot.
Engboot Download
Nougat_S7_Edge_EngBoot.tar.md5
drive.google.com
3 make sure you have adb and fastboot installed on your computer (goggle them)
4. Root file
Download the file below.
Nougat_S7_Root_2_82_All_Carriers_V2.zip | by jrkruse for Galaxy S7 Edge
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
BELOW IS THE ROOT AND MOD FOR THE PHONE!!!!!
Follow this method to root:
1. Shut off the phone and boot into download mode (volume down, home, and power). Use Odin And Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
2. When the phone reboots, unlock developer options by going into the phone settings scroll down to 'about phone' find the build number and tap on it repeatedly after several times it will unlock Developer Options then back out once and in your settings you should have a new option on the very bottom called developer options go into that and enable USB debugging and Disable Verify Apps Over USB.
Plug the phone into the computer and make sure you have adb and fastboot installed to this location
C:\Users\YOUR PROFILE\AppData\Local\Android\Sdk\platform-tools
go to that folder and inside it hold shift and right click then click on 'open command window here'
then in command prompt type
adb devices
then hit enter.
The computer should automaticly detect and run adb
3. Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.zip and hold shift and right click then click on 'open command window here'
In the command window type root.bat then press enter from your PC.
4. This will install root when done phone will reboot
5. The process wipes dalvik cache so it will take a few minutes to reboot
6. If having problems getting Grant SuperSU dialog to come up you can delete the SuperSU app and root will be granted instantly to all root request
Give phone a few min to settle open developer options set animation scales .05 and others to .05
Give phone a few min to settle open developer options set animation scales .05 and others to .05
ODIN FAILED TO WRITE ERROR
Did you get this Failed To Write Message in Odin?
----------------------------
Odin Error Message:
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
SOLUTIONS
Did you:
? Open Odin as Administrator?
? Try the Prince Comsy version?
? Enable Developer Settings?
-Open Settings > About Phone > Tap Build Number 7 Times
? Enable OEM Unlock?
-Go Back to Settings > Tap Developer Options > Tap OEM Unlock
? Enable USB Debugging?
-Tap Developer Options > Tap USB Debugging
NOTHING WORKS
Did you try every single thing but nothing works?
Well, did you right click "Odin" each time you go to open it and then click "open as administrator"?
Sometimes you have to try several different versions of Odin.
But I have found that Odin3 v3.12.7 was the one that would work when the others had not.
I always would forget to also open Odin as Administrator.
It's a pain in the neck to have to remember to open as admin every time.
But you usually have to do it.
Did you check that ADB had started? Maybe that might be the reason it won't work?
But I doubt it! But you just never know and I am just trying to help you get it flashed.
It's a very quick flash and you can see that the PDA load was very quick as well.
But as far as the errors, you just have to keep trying...
Which I mean, you sometimes have to open, close, reopen Odin when it doesn't work.
Sometimes that helps, sometimes it doesn't.
It's all about the right Odin version at the time
making sure the cord is good
Opening Odin as Admin
And keep trying again after restarting your phone by holding the download mode button sequence again.
============
Congratulations! You are ROOTED but you're not done
Follow these instructions next
On your phone, open the SuperSU app (installed during the root process) and tap on Settings. Half-way down under Security, tap on "Enable su during boot".
This option will ensure that startup scripts that are installed during this process get to do their job correctly.
Download the fix or fix+debloat script flashable ZIP package appropriate for your model of phone and copy this file to your device:
S7_VOLTE_ICON_FIX_ALL_VARIANTS or S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0) (any Samsung Galaxy S7 or S7 Edge)
turn off auto update of time and date in your phone settings, then set your year to 2013,
Launch FlashFire app on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step.
Locate the flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked.
Tweaks to Root
Debloat and fix several issues with the phone (CPU lag issues, poor battery performance, phone becoming too hot, Wi-Fi not saving passwords, hotspot/tethering not working,
VoLTE icon appearing, searching for service issues, MMS not working, unauthorized security nag notification, etc.):
Full notes on what this flashable update does:
Adds a rotate button to the native gallery app
.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
after you flash your stuff change the date back. and you're good.
I know this all seems like a lot and it seems very confusing but it's pretty easy if you just follow the directions this will not wipe your data. Please do research, read through the forms and just tried to get as much knowledge as you can before you go about doing this it's an easy process but it's better to go in with more knowledge, I hope this helps. If you have to reinstall the firmware make sure that you install CSC home so you don't lose your data

[GUIDE/TUTORIAL/HOWTO] Huawei Honor 5X from Stock to Android 10

[GUIDE/TUTORIAL/HOWTO] Huawei Honor 5X from Stock to Android 10
[GUIDE/TUTORIAL/HOWTO] Huawei Honor 5X (kiwi) from Stock to Android 10 / LineageOS 17.1 in 2023
Complete guide to install Android 10 on your Huawei Honor 5X.
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About phone > Model number, make sure it is one of these models:
- KIW-L24
- KIW-L22
- KIW-L21 (Qualcomm Snapdragon)
Not 100% sure for following models:
- KIW-L23
- KIW-AL10
- KIW-AL20
- KIW-CL00
- KIW-UL00
- KIW-TL00
- KIW-TL00H
- KII-L05
- KII-L22
- KII-L21
I wrote tis tutorial with KIW-L21.
See all my tutorials at https://github.com/djibe/Android-tutorials
Netflix and Disney+ are working.
CHANGELOG
v1. Initial release
1) WHAT YOU NEED
- djibe Honor 5X pack: https://bit.ly/honor5xdjibepack or https://anonfiles.com/EfHbPev2z2/djibe_Honor_5X_pack_zip or
(Contains TWRP Recovery 3.4.0-0 + Magisk root + Huawei USB drivers x32/64 + fastboot + cited files for root)
+ ROM LineageOS Unofficial 17.1: https://forum.xda-developers.com/t/rom-10-0-lineageos-17-1-unofficial-for-honor-5x.4212671/
Download latest build here: https://mega.nz/file/tbUliQ7Q#7f7Byu1QuuYNkojPnu5MDevPyCx6oMxXxQsjgjciCsE
+ BitGApps ARM64 10: https://github.com/BiTGApps/BiTGApps-Release/releases
+/- extra apps: https://bitgapps.github.io/addon/ARM64.html
+ a microSD card formatted in FAT32: copy ROM, GApps (+ Magisk). Insert it in phone
+ Charge phone to 100%
2) INSTALL DRIVERS
Install Huawei USB drivers.
Then plug phone to PC and let the install go on.
3) BACKUP YOUR DATA
When your phone is connected to Windows, search for all .jpg, .mp3, .mp4 files on your phone and make copies on your PC.
Then, with your Google Account (Whatsapp and co) or an app like Backupyourmobile, backup all your SMS, MMS, contacts.
Make sure the backup is located on microSD card.
4) UNLOCK BOOTLOADER
Update your Honor 5X to the latest official Android 6 Marshmallow (MM).
In Android, go to Settings > Updater. Make sure you have latest version.
Go to Settings > About phone.
Tap 7 times on Build number to unlock Developer options.
Go to Settings > Developer options.
Switch ON "Enable OEM unlock" and "USB debugging".
You must pay to unlock bootloader as Huawei closed the official website.
List of services offering unlock codes for money:
- DC Unlocker ($4 + VAT): https://www.dc-unlocker.com/supported_models_1/huawei_phones
- MinistryOfSolutions ($4): https://ministryofsolutions.com/huawei-bootloader-unlock-paid-service-html
Follow steps to get a paid unlock code. Here are the steps for DC Unlocker.
Go to DC Unlocker website: https://www.dc-unlocker.com/supported_models_1/huawei_phones
Download latest Client for Windows and install it.
On phone, launch Dial pad and type: *#*#2846579#*#*
ProjectMenu opens.
Go to Background Settings > USB Port Settings > select Manufacture Mode and Close.
### If you restart phone before the end of the process, you have to do this again.
Connect Honor 5X to PC.
Go to Windows Device Manager.
In the Modems section, Android Adapter Modem is listed.
In the Ports section, Android Adapter PCUI (COMn) is listed.
### If not, you must check USB drivers installation again.
Launch DC Unlocker.
- Select manufacturer: Huawei phones
- Select model: Auto detect (or Huawei Qualcomm Android phone)
Click magnyfying glass button.
DC Unlocker returns:
Code:
Found Applications port COM3
Found Diagnostics port COM5
Found Phone : HUAWEIKIW-L21
Model : Huawei Qualcomm Android phone
IMEI : xxx
Serial NR. : xxx
Firmware : xxx
Hardware ver. : HL3KIWMAD
Now go to DC Unlocker shop: https://www.dc-unlocker.com/buy
You need 4 credits ($4) for operation 24: Huawei Qualcomm Read Bootloader Code (up to Android 8)
Set subscription as:
Item: New user account
User name: YOUR CHOICE
Credits: 4
I used Credit card.
Note down purchase informations, we will need these in DC Unlocker.
Back to DC Unlocker.
Go to Server panel.
Fill User name and Password with data from your receipt.
Click Check login.
Go to Unlocking section and click Read bootloader code button.
DC Unlocker returns:
Code:
Reading bootloader code...
Bootloader code : xxx
Note down Bootloader code carefuly.
On phone, launch Dial pad again and type: *#*#2846579#*#*
ProjectMenu opens.
Go to Background Settings > USB Port Settings > select Google Mode and Close.
Go to my djibe/flash folder.
In the address bar, type cmd and confirm with keyboard Enter key.
Enter command:
Code:
adb devices
Authorize USB debugging from phone.
Enter command again (use arrow up key to print last command):
Code:
adb devices
Command returns
Code:
List of devices attached
W6HDU16325009900 device
Then:
Code:
adb reboot bootloader
Phone switches to white screen in FASTBOOT&RESCUE MODE.
To check that fastboot USB drivers are OK, type:
Code:
fastboot devices
### If command doesn't print a line like: 516b3414 fastboot, you have to fix USB drivers.
Now enter THE command:
Code:
fastboot oem unlock FILL_WITH_YOUR_UNLOCK_CODE
Confirm with enter and wait a moment ... till success is confirmed :
"(bootloader) Unlock success , the device will reboot and factory reset
OKAY [ 0.046s]
Finished. Total time: 0.046s".
Keep Windows command opened and let phone reset Android.
4) FLASH RECOVERY
Configure Android rapidly.
Unplug phone and replug USB.
Go to Settings > About phone.
Tap 7 times on Build number to unlock Developer options.
Go to Settings > Developer options.
Switch ON "Enable OEM unlock" and "USB debugging".
Back to Windows command, type:
Code:
adb reboot bootloader
Twice to authorize USB debugging from phone again.
Now that you are back to bootloader, enter:
Code:
fastboot flash recovery twrp-3.4.0-0-kiwi.img
Confirm with Enter.
Terminal confirms : "Finished. Total time: 2.711s".
And now:
Code:
fastboot boot twrp-3.4.0-0-kiwi.img
### If phone goes in a bootloop, disconnect phone and force shutdown holding Power button.
Welcome to TWRP 3.4 recovery.
TWRP asks for Keep System Read Only ? Swipe to Allow Modifications.
### You don't see this warning screen? Then you'll get "TWRP unable to mount storage" while trying to wipe partitions.
### > in TWRP, go to Reboot > Recovery so Recovery will refresh and popup the partition writing privilege.
In TWRP home screen, go to Wipe > Format data.
This will remove encryption.
Type yes and confirm to format partition.
Go to Reboot > Recovery.
Back to TWRP, go straight to Backup menu.
Select Boot, Data, System, Custom, OEMinfo, EFS and Firmware partitions.
Tap on Select Storage and set Micro SD card.
Swipe to Backup and wait during backup.
### If MicroSD card is too small. Backup on data partition and after backup has ended, go to Mount and connect phone to PC to retrieve TWRP backup folder.
### Store this backup (aka nandroid backup) somewhere safe before going further.
5) WIPE PARTITIONS
Go to Wipe > Advanced Wipe and check Cache, Data, Internal Storage, System and Swipe to Wipe.
6) FLASH ROM, BITGAPPS +/- MAGISK
Back to TWRP Home menu. Then tap on Install > select Storage MicroSD > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > BiTGApps*.zip,
Optional: Add Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Android 10 is installed !
Wait for the phone to boot during 10 minutes.
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magisk via TWRP recovery
Do not connect to Android account.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
Open Files app > Install Magisk.apk.
Then in Magisk goto Settings > Hide magisk app and give it a name, switch Zygisk option ON.
Go to Modules Tab > Install from Storage: MagiskHidePropsConfig and safetynet.
Go to Developer options to disable Android debugging (ADB).
Reboot phone.
You can use yasnac app to check Safetynet passes.
Then with Files App: install netflix and disney+ if needed.
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About phone.
Tap 7 times on build number.
Back to Settings > System > Advanced > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
That's it.
Enjoy ;-)
djibe
Thanks: @BadDaemon, LineageOS team, TWRP team, BitGapps team, TopJohnWu (Magisk)

Thanks for this updated tutorial. I might be like a lot of others who only recently purchased this smartphone. I think they cost a little more now then the $34.95 I paid a month ago.
Huawei Honor 5X 4G LTE Android 5.5" Dual-SIM 16GB Unlocked Smartphone 886598039147 | eBay
Find many great new & used options and get the best deals for Huawei Honor 5X 4G LTE Android 5.5" Dual-SIM 16GB Unlocked Smartphone at the best online prices at eBay! Free shipping for many products!
www.ebay.com
I originally purchased to I could try the freemobile SIM, but unfortunately it requires VOLTE. I also tried T-Mobile data only SIMS with it, but they seem to be shut down as I am still using the stock image.
I opted to use Ministry of Solutions as it was only $4 and DC seems to require the user to go through a process and Ministry of Solutions pretty much does all the work. The process just required me to do the following:
Go to their website and pay $4 via paypal for the service,
Contact them to let them know you paid for the service and schedule a time to get it done. I just used email.
Install teamviewer and provide the access information for them to access your system remotely.
Be available to configure the phone so they can do their work.
Wait for them to get done with the process and provide the unlock code for you.
The unlock code will also be included on paypal upon completion of their work.
So far I have only unlocked the bootlader and installed TWRP and will finish the process when I have time. I am just happy to have noticed that this tutorial is up to date and has links to all the resources needed to do the upgrade.

Hi @comm-ents, thanks for sharing.
I would not let anyone come on my computer but it is nice to have this alternative.
This phone is still damn cool, even though Honor closed their unlock site.

djibe89 said:
Hi @comm-ents, thanks for sharing.
I would not let anyone come on my computer but it is nice to have this alternative.
This phone is still damn cool, even though Honor closed their unlock site.
Click to expand...
Click to collapse
I wasn't too concerned as I currently use Linux Mint for work and Windows mostly for playing games so there isn't much there to compromise. I will be using them again if needed as they only did what was needed to get the code. I am pretty sure that a copy of Windows installed in Virtualbox would also work for increased security.
Just be aware that most compromised information isn't done while you're watching but behind the scenes so you're always taking a risk when connected to a remote site.
I suppose not having to pay $4 to get the unlock code would be nice, but it is just $4 to get even more benefits out of a very inexpensive dual SIM phone. Maybe if I am lucky it will be even more useful once I replace the Stock ROM with something a bit more up to date.

I am not able to install the lineage rom as I just get an error.
updater process ended with error 7 with my KIW-L24. I also tried to remove the assert lines as some instructions suggest should be done and it looks like the install went ok, but It ends up in a boot loop.
After trying the process twice just in case I made a mistake, I found that but removing the assert lines from the file, the install seems to complete, but I am no longer able to use TWRP from the phone as the touch screen doesn't work any more and Lineage doesn't boot either.
The only reason I can think of that the install doesn't work is because there is something that is different about the phone I have like it is a newer revision. It seems that the partition sizes might be different and when I remove the assert lines the install just writes to a partition that is too small to hold the data and it ends up overwriting itself so it is basically corrupted in the process. Just a theory, but I haven't had any luck with anything but the stock firmware.

comm-ents said:
I am not able to install the lineage rom as I just get an error.
updater process ended with error 7 with my KIW-L24. I also tried to remove the assert lines as some instructions suggest should be done and it looks like the install went ok, but It ends up in a boot loop.
After trying the process twice just in case I made a mistake, I found that but removing the assert lines from the file, the install seems to complete, but I am no longer able to use TWRP from the phone as the touch screen doesn't work any more and Lineage doesn't boot either.
The only reason I can think of that the install doesn't work is because there is something that is different about the phone I have like it is a newer revision. It seems that the partition sizes might be different and when I remove the assert lines the install just writes to a partition that is too small to hold the data and it ends up overwriting itself so it is basically corrupted in the process. Just a theory, but I haven't had any luck with anything but the stock firmware.
Click to expand...
Click to collapse
Sure of your model ?
Info about kiwi | LineageOS Wiki
wiki.lineageos.org

djibe89 said:
Sure of your model ?
Info about kiwi | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Yep. Model number KIW-L24.

comm-ents said:
Yep. Model number KIW-L24.
Click to expand...
Click to collapse
Format Data
Wipe all partitions
Reboot recovery
Flash
Leads to Error 7 ?

djibe89 said:
Format Data
Wipe all partitions
Reboot recovery
Flash
Leads to Error 7
Click to expand...
Click to collapse
Yes.
The first issue is that when I try to format Data I get: Unable to wipe '/data' -- unknown file system 'auto' Unable to format to remove encryption. I found a suggestion to format the /data partition manually from adb shell which works.
The Lineage from wasn't the only Install I the error 7 with though as ResurrectionRemix-M-v5.7.4-20161220-kiwi also gave the same error 7.
Now the touch screen isn't working again in TWRP because I accidentally installed the wrong version of Lineage. with the assert lines removed. It would be nice to know how I can do a restore from the command line, but the TWRP command line guide isn't much help. It is just too much of a PITA that once I can get stock back on it I will just sell it while I'm ahead.

Sometimes you have to manually reformat.
Go to Wipe > Advanced wipe > Cache > Change partition
Too bad you didn't succeed

I was able to unlock the boot loader and still have a rooted phone. What I had hoped to do is use it with a T-Mobile data only plan and a SIM from FreeMobile provides a few hundred minutes a month for free.
I don't know why I get the Error 7, but you can't just remove the assert lines as the install might seem to have worked, but that is only because it just proceeds to install even though there might be something wrong and the install just messes up the phone.
I am still using the phone right now to test as a hotspot. The real reason that SIM didn't work in the phone is because of something on T-Mobiles end so it actually works in the phone now and since it is rooted I can make other changes that actually allow it to work as hotspot without limitations.
I should be able to find another dual SIM phone that can be rooted, but I am not sure there is anything that also supports Volte.

Is there otherway to unlock bootloader without paying 4 dollar. My country has restriction. i cant pay.

neysariy said:
Is there otherway to unlock bootloader without paying 4 dollar. My country has restriction. i cant pay.
Click to expand...
Click to collapse
No way.
Or tell us if a miracle happened

In djibe Honor 5X pack, you said it contains Huawei USB drivers x32/64 but i didnt found it. Only driver that worked is:
Support area | files.dc-unlocker.com
files.dc-unlocker.com
Please add to your pack if you forgot that

In my phone there is not "unlock oem" option. What shoud i do. It that important?

Dc unlocker say error conection to server. I dont know why.

I'll dig into it. Thx

This guy in telegram can unlock bootloader of huawei phones very fast @fullkade_huawei_support

.

neysariy said:
In djibe Honor 5X pack, you said it contains Huawei USB drivers x32/64 but i didnt found it. Only driver that worked is:
Support area | files.dc-unlocker.com
files.dc-unlocker.com
Please add to your pack if you forgot that
Click to expand...
Click to collapse
Pack updated with USB drivers. Sorry for that