Database Users

ZUK Z2 Pro Guide to Everything (OTA, Unlock Bootloader, ROOT, Widgets, Gapps)

Hi Folks
I just went through personalizing a brand new ZUK Z2 Pro Z2121 and found a lot of information scattered around the net which I tried to summarize here.
First I noticed my phone was not on the latest Firmware/ROM but the Update function in the settings would not show the SW 2.5.355 to be available.
#-#-#-#-#-# Section 1
Upgrade to 2.5.355
If your phone shipped with something less than the latest Firmware (as of now SW 2.5.355) you may want to update over the air first thing.
The problem is that you need to be in China to receive the update.
Solution:
Install a Free VPN App
(e.g Hola VPN - you will need Google Playstore first - install Playstore via App Center than search for VPN in Google Play)
Select a Server in China
Go to Updates and search for updates. If an update is found download will start.
Unfortunately this may take forever as you are probably using a free VPN server.
But the OTA Tool is not very smart.
If you terminate the running VPN connection while the download is active the download will briefly stop, but then resume (without the VPN).
10min later you should be all set.
#-#-#-#-#-#
Now that you are on the latest SW you may want to unlock the bootloader.
#-#-#-#-#-# Section 2
Unlock Bootloader
Unlocking the bootloader is required if you intend to root your phone.
It will wipe all user data, therefore I recommend to do this first thing.
On your phone go to Settings -> About -> Status to note your 8 digit serial number.
If your serial has less than 8 digits add zeros to the END to make it 8 digits.
While you are in Settings , Enable the Developer Options by going to
Settings -> About and clicking 7 times on ZUI Version.
Then go back to Settings -> Advanced Settings -> Developer Options and enable USB debugging.
We will need this later.
In order to unlock the bootloader you will need to got the zuk website, where you need to register first before you can request to unlock the bootloader.
So go here:
https://passport.zuk.com/wauthen3/wauth/jsp/register.jsp
(use google to translate)
Select Email Registration (upper right corner) and fill in the required data.
Likely a Googlemail Address will not work.
You will receive an Email with a confirmation link.
Now that you are registered, log in and than go to
http://developer.zuk.com/bootloader
(use google to translate)
Click on Carry On.
On the next page select your phone type Z2 Pro.
Enter your serial nuber (8 digits)
Enter an email address where to send the unlock image. It seems that the email address here has to follow some rules.
[email protected] or @Web.net seems to work. A domain name with a hyphen (-) seems to cause problems.
Check the 2 check boxes and click SUBMIT.
If succesful you get a message that the image has been sent to your email address. No message means something went wrong. Likely the email address was not approved.
I had some trouble here at first.
Next things is to get ADB/Fastboot installed on your PC.
All you need to know is found here.
https://forum.xda-developers.com/showthread.php?t=2588979
Safe the email attachment from ZUK you requested earlier (named unlock_bootloader.img) into the directory where adb is installed. (likely c:/adb)
Reboot into bootloader by:
Opening a Command Window and CD into the directory where adb is installed.
Do a
Code:
adb reboot bootloader
If this fails you may need to confirm USB debugging on your phone and try again.
Once the phone is in bootloader mode continue:
This will wipe your phone!!! Factory Reset !!!
Do a
Code:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
The response will look like this
Code:
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
OKAY [ 0.063s]
finished. total time: 0.094s
C:\adb>
Do a
Code:
fastboot -i 0x2b4c oem unlock-go
The response will look like this
Code:
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>
You may need to do a
Code:
fastboot reboot
after this.
In my case the phone rebooted itself.
Credits for this section here.
http://www.theandroidsoul.com/unlcok-bootloader-zuk-z2-pro/
Once the phone boots up it will be in Chinese again.
On the welcome screen tap the bottom of the screen below the highlighted blue text to skip the ZUK login.
To change the language back to English go to Settings.
In the third section choose the last entry. "Advanced Settings" (the gears symbol).
Choose the 2nd menu item.
Choose the first menu item and select English.
While you are in the Settings Enable USB debugging again. See Above. We will need it for the next step.
#-#-#-#-#-#
As a next step we will ROOT the phone by using a TWRP custom recovery image.
#-#-#-#-#-# Section 3
Rooting
I was a bit uncertain if the TWRP image is stable or not, therefore I decided not to flash it, but only to boot into it.
So I use it temporarily only.
First get SuperSU from here
http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
and copy the ZIP file onto your phones internal storage.
Get the recovery here.
https://www.androidfilehost.com/?fid=24591000424960393
Save the image file in the abd directory.
Do a
Code:
fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img
The phone will now boot into recovery. Chinese at first.....
Click on the lower right button to change the language to English.
Click on the lower left button to keep the system read only.
On the next screen click install and navigate to the SuperUser.Zip File that you placed on the internal storage.
Confirm the install and finish rebooting. It will do a short loop and than boot up correctly.
Credits for this section to raimondomartire (the recovery image from here also works)
https://forum.xda-developers.com/zuk-z2-pro/development/twrp-recovery-zuk-z2-standard-pro-t3415395
#-#-#-#-#-# Section 4
Get the Google Stuff to work.
Install Google Play.
On the home screen click on App Center. Select Go to Home Screen.
Search for Google Play and install.
#-#-#-#-#-#
Install Google Contact Sync & Contacts
Thanks to Lucaam pointing us to this
https://forum.xda-developers.com/zuk-z2-pro/how-to/google-contacts-import-sync-t3462124
Install Contacts Sync and Contacts out of the Lenovo_Zuk_Gapp_6.0.zip File in that order.
Thanks to m_atze
Play Store I did already so I don"t use that APK from the ZIP.
#-#-#-#-#-# Section 5
Custom Launcher
Installing a custom launcher seems a bit tricky, as you can not permanently set the new launcher as the default.
You can try in Settings -> Advanced Settings -> Applications
At the very bottom you can find the Preferred Apps section.
Set your Launcher as preferred.
This did not work for me.
Workaround: Install Google Now Launcher from the Playstore -> Open it -> Follow the dialog to Settings -> Select your Launcher - Press Home
It basically takes you to the Settings -> Home which is hidden in the ZUK settings
De-Install Google Now if you don't want to use it.
#-#-#-#-#-# Section 6
Widgets not updating or being empty.
There is an App pre-installed called SafeCenter. It has pretty tough autokill rules, which kills the processes / services needed to update the widgets.
I decided to diable SafeCenter completely, for which I had to use a separate App. The Disable functionality in the settings was not active (grey).
You can use several Apps from the Playstore to do this. I use one called SystemCleanup.
While you are at it. Disable Bug2Go -> according to the internet some tracking/spy App used on Motorola phones before.
#-#-#-#-#-# Section 7
Adblocker AdAway
If you want to use an AdBlocker like AdAway which modifies the /etc/host file you may run into isssues that the Adblocker can not mount the system partion read/write.
In that the host file maybe put into a different location. (e.g /data/hosts) and the original file must be replaced by a link.
Make sure you still have USB debugging enabled. Open a command window and change into the adb intall directory.
Do a
Code:
adb shell
followed by a
Code:
su
Grant permission to adb shell for root access on your phone.
(The command prompt will change from $ to #)
Do a
Code:
mount -o rw,remount -t ext4 /system
to mount the system partion RW.
and create the link with
Code:
ln -sf /data/hosts /system/etc/hosts
In this case I assume the Adblocker will place the hosts file in /data.
Check or Set in the settings of the Adblocker the correct location.
You should do a
Code:
mount -o ro,remount -t ext4 /system
to change back to a read only system partition.
I had to reboot to make everything take effect.
This has been tested with AdAway.
#-#-#-#-#-# Section 8
Finally the Notification LED ....
I am still looking into this, but it seems that the post from Florent here
http://zukfans.eu/community/threads/notification-led-multicolored.275/page-2
provides a solution / workaround. I will provide an update here later.
I hope this is helpful to some of you. Let me know if things can be added or need corrction.
Cheers Ulf
BTW How do I place the attachments (pictures) into the text where they are relevant?

Brilliant write up! Thanks.

Great tutorial! I think you should mirror the tutorial for the Z2 (Plus) section, since it works and there isn't one as complete as this one there! Congratulations!
If you have time, you could also cover custom roms, especially because our phones are ARM64, unlike the majority

did what you said about updating phone. got no update and i'm on ZUI version 2.5.335 ST. is your version just a typo?

When I want to register for unlock the bootloader I get a timeout message in chinese. Is this a known error?

waiting or device
waiting for device
i had to install a fresh windows 7 64 bit version to be able to use fastboot ..
download the zuk z2 pro drivers <- search string google
install adb drivers
after connecting windows promptet me for installing the lenovo bla bla drivers
and i was merily on my way
for mee ik took 2 days to come to that point so i hope this is of help for those who have the same problem on win 10 no dice also after clean install

Thanks to the OP for such a detailed guide.
With regards to unlocking the bootloader, has anybody had success recently using developer.zuk.com?
I have tried multiple times and keeping getting an "Bad Gateway" error.

digitalguy13 said:
Thanks to the OP for such a detailed guide.
With regards to unlocking the bootloader, has anybody had success recently using developer.zuk.com?
I have tried multiple times and keeping getting an "Bad Gateway" error.
Click to expand...
Click to collapse
same "502 bad gateway"

The same from me.
Στάλθηκε από το ZIDOO_X6 Pro μου χρησιμοποιώντας Tapatalk

telefono in brik
Ciao a tutti,
ho installato la zui 2.5.435 st, dopo ho seguito alla lettera le instruzioni per avere i permessi di root.
ho scaricato supersu, e lanciato l'installazione tramite TWRP, il problema che il telefono non si è mai riavviato. rimane con schermo nero.
ho provato due volte ma nulla da fare, devo reinstallare la zui da capo per avere il telefono funzionante.
mi date una mano per avere i permessi di root e poter aumentare la traduzione del telefono in italiano.
grazie mille in anticipo
mirko

mda76 said:
Ciao a tutti,
ho installato la zui 2.5.435 st, dopo ho seguito alla lettera le instruzioni per avere i permessi di root.
ho scaricato supersu, e lanciato l'installazione tramite TWRP, il problema che il telefono non si è mai riavviato. rimane con schermo nero.
ho provato due volte ma nulla da fare, devo reinstallare la zui da capo per avere il telefono funzionante.
mi date una mano per avere i permessi di root e poter aumentare la traduzione del telefono in italiano.
grazie mille in anticipo
mirko
Click to expand...
Click to collapse
English only please.

Brik
Hello to all,
I installed the zui 2.5.435 st, after I followed the instructions to have the root permissions.
I downloaded supersu, and started installing via TWRP, the problem that the phone has never restarted. Remains with a black screen.
I tried twice but nothing to do, i have to reinstall the zui from head to have the working phone.
Give me a hand to have root permissions and to increase the translation of the phone into Italian.
many thanks in advance
mirko
Google traslate,................

Where do I go in the phone settings to update? Running ZUI 2.3.044 ST but dont see an option for Updates anywhere

OTA
Hello,
The solution on OTA is not working on my device. I do not have the system update option. Please help. Thank you!
Kitkat

I'm not receiving the e-mail. It gives me the message e-mail has been sent, but there's nothing in inbox or the spam folder. The registration confirmation e-mail had arrived immediately.
I have tried using a gmail adress, a gmx.com one and a disposable e-mail, but none of them are working out. Any suggestions?

For anyone having issues, e-mail your phone model and serial number to devworld{at}zuk.com
They sent me the image quite quickly.

mkey82 said:
For anyone having issues, e-mail your phone model and serial number to devworld{at}zuk.com
They sent me the image quite quickly.
Click to expand...
Click to collapse
Thank you, I will try this. The link in the first post no longer works....
Edit: I went to the unlock bootloader page, entered everything and was then redirected to the login/register page. It was even possible to switch to English. From there on it was a straight forward procedure, and I quickly got the mail with the bootloader image
---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------
Does OTA updates still work if you unlock bootloader and root the phone?

Hi, is position travel app in this zui version? (settings - >advanced - > lab features - > position travel?) or is it no longer there? Thanks!
Sent from my ZUK Z2121 using Tapatalk

ZUK passport page seems to be down (404). Any idea where I can register now?
Unlock bootloader sends me to Lenovo passport and there is no way to use email for account, it wants phone number. Is that it?

Here :
https://passport.lenovo.com/wauthen/login

Mi A1 uses Full disk Encryption(FDE) or File Based Encryption(FBE) encryption?

Hello,
I remember when i set up A1 in firstboot, it asked if i want to be prompted with a password before booting android, to which i said no.
So this in effect, must have encrypted with the default password on first boot. This lets the system boot, and core services started, if the device gets rebooted
without my knowledge(so that i recieve calls and sms) VS, if it asks password before booting(uses my pin as password instead of default password), the core services arent available untill i put my pin in.
This issue was supposed to get solved through Nougat's FBE.
So my question is that, does Mi A1 uses FBE, so that even if i had opted for my pin as password before booting, i would not be blocked of using core services like phone and sms, with OS waiting at pin prompt?
Thanks.

as i have researched more, A1 does not support FBE.
read this excellent writup
In the above article, it shows how to convert to file based encryption. This option in the developer settings is missing from A1.

this is the first major disappointment with A1. Was shocked on system setup to see this. Didn't expect this from a phone expected to receive updates upto P.

ashjas said:
as i have researched more, A1 does not support FBE.
read this excellent writup
In the above article, it shows how to convert to file based encryption. This option in the developer settings is missing from A1.
Click to expand...
Click to collapse
Why do you think ? What encryption does it use ?

It uses FDE. This can be seen when you reboot the device - the black background and basic keyboard. This is FDE.
FBE would boot the device in an intermediary state with wallpaper, full keyboard.
Now if you ask me FDE seems a bit more secure - you can be sure that everything on the device's data partition is encrypted and the only available function is emergency call.
FBE encrypts certain folders but more code is running at startup so you can in theory receive notifications and stuff for certain apps. I certainly don't need stuff running before i authenticate.

gradinaruvasile said:
It uses FDE. This can be seen when you reboot the device - the black background and basic keyboard. This is FDE.
FBE would boot the device in an intermediary state with wallpaper, full keyboard.
Now if you ask me FDE seems a bit more secure - you can be sure that everything on the device's data partition is encrypted and the only available function is emergency call.
FBE encrypts certain folders but more code is running at startup so you can in theory receive notifications and stuff for certain apps. I certainly don't need stuff running before i authenticate.
Click to expand...
Click to collapse
So when the phone was set up in a way, where there was no password asked during (in the middle of) the boot process, how easy would it be for thiefes to access data stored on a A1 ? And how much would it help them if bootlocker was unlocked ?
When you reboot the phone, and you do not have a FDE password set up, the phone still asks for a PIN aftrer booting, with the text "Unlock for all features and data". This sounds like FBE to me.

- PIN is probably from the SIM card. My A1 never asked anything until i set up a password. But mine came with Android 7.1.1 so it is a possibility that some to come with later versions (that have FBE?)?
- FDE is usually enabled anyway on Android 7.1+ but it has a default password set ("default_password" AFAIR). So if you run TWRP for example, even without installing it,it will acces your data because it knows this default password. If you specify a custom password the disk will not be unlocked without it.
- A locked bootloader brings additional security. The idea behind it is to have a verified boot chain - if someone gets hold of your phone to not be able to flash custom system apps on it.
The partitions are checksummed and verified via dm-verity. So at boot time any unauthorized alterations (done, say, with booted TWRP, installed Magist and root then re-locked bootloader afterwards) will trigger a "System Destroyed" message.
The above will be all disabled if you unlock the bootloader and install TWRP. As for now TWRP (or any other loader) cannot ensure system consistency. It is possible to flash stuff on your device by restarting it and launching TWRP. If you have a strong encryption password set up your data partition will still be inaccesible to them but if you get your phone back and start it up the malware will start and do nasty stuff like siphoning all your data, passwords etc (because you can flash system apps that can see everything on the device).

After restart, it asked me for a PIN and then for SIM PIN, (even when draw pattern was my configured way for unlock). It never again asked me for PIN, only right after reboot. Why else would I be asked for a PIN only after reboot, if not because of FBE?

[RECOVERY][UNOFFICIAL] Red Wolf Twrp for Redmi 5 (rosy)

{
"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"
}
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
https://img.xda-cdn.com/qubervzMG28...%2F%2Fpreview.ibb.co%2FhH5G4a%2FUntitled4.png
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.1
For devices: rosy
Authors build: yshalsager
Developers: @ATG Droid & @dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
Translated to EN & CZ
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences to the official version:
Code:
- get out of here if you are pirating apps. this recovery is not for you
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_026
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Redmi 5 (rosy)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
Contributors
yshalsager, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-02-21
Last Updated 2018-02-21

Did you really try the latest build bro? Beacause I remember this build doesn't work

neetee said:
Did you really try the latest build bro? Beacause I remember this build doesn't work
Click to expand...
Click to collapse
the recovery provided from the link in op works as intended

nofx161 said:
the recovery provided from the link in op works as intended
Click to expand...
Click to collapse
No, it doesn't work as you said. I have tried to flash it via fastboot cmd, but as usual, device can't boot into recovery. It just normal reboot

I think it does not work, I need to update

This redwolf TWRP not working my Redmi 5 ?

edit:
updated image as redwolf binary segfault during build was fixed upstream
! use with caution !
https://drive.google.com/file/d/15WNKe-nFThwKW9PUb_GWhi7OJrzVaoRz/view?usp=sharing

Thank you, vetzki! I changed my twrp (because the password required) for this and now it's finally okay!

hola, realizando la instalacion de una rom por twrp como que la parecer realice un mal procedimiento y el telefono se queda en reinicio infinito, puedo acceder en mofo fastboot y recovery pero no he podido hacer nada pues al intentar instalar alguna room oficial o de miui.eu me arroja error ya sea por twrp o flash saca errores de almacenamiento 0 y al parecer hace falta un archivo .dat en el twrp y flash respectivamente, agradezco su ayuda para saber si se puede hacer algo o el celular ya quedo modo ladrillo

Can't set new password/pin/fingerprint after deleting locksettings.db

As I was trying to update my EEA global stable rom 10.2.7 to the latest release (10.3.3), I followed a guide to accomplish that without losing TWRP and my /data partition. I flashed a zip called DisableForceEncryption_Treble_v18.0.zip after flashing the new rom but before reflashing magisk. As a matter of fact I could boot into the new ROM with all my data intact, but TWRP was overwritten by the official MIUI recovery.
As I flashed TWRP again via fastboot, my device was encrypted again and I had to format my /data partition.
So I restored my /data backup and booted into MIUI again, that asked for my PIN. The PIN I previously set was not working anymore so I had to delete /data/system/locksettings.db and I was able to access the OS again. Funny thing, my fingerprints were still there and still worked to unlock the phone.
Finally, I wanted to create a new PIN or Password. It asked me for a new PIN and then again to confirm it. As it seems to have accepted my newly registered PIN, it does not work when I try to unlock my phone! So I have to delete locksettings.db again (which seems to be the only file I could find that relates to lock settings). Everytime I create a new PIN, it lets me register it but then it's like it doesn't match with what I type when it asks for it to unlock the phone.
What did I do wrong? How I can restore my lock settings?
Thanks for reading so far!

That's weird.
Something similar happened to me a few days ago and I could set a new lock again with no problem.
Does it happen only with PIN? Have you tried with PATTERN?

Schnedi said:
That's weird.
Something similar happened to me a few days ago and I could set a new lock again with no problem.
Does it happen only with PIN? Have you tried with PATTERN?
Click to expand...
Click to collapse
Yes, it happens with PIN, password or pattern regardlessly. Whatever I set, it stores it, but when asked to unlock the screen or enter security settings it just rejects it.
P.S.: This might be unrelated: I don't know if Magisk 19.3 behaves like this or not, but since I installed it the Mi Unlock status is uncertain (it said "Unlocked" before, now it lets me enter on the prompt as it was the first time unlocking the phone). So I rebooted to bootloader and ran "fastboot oem device-info" which correctly reported that my device was unlocked.

Just in case... here is what i found in logcat.
Here is when I create a new PIN:
Code:
:/ # logcat |grep password
06-09 05:07:05.130 1453 1453 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.password.key: open failed: ENOENT (No such file or directory)
06-09 05:07:05.130 1453 1453 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/password.key: open failed: ENOENT (No such file or directory)
06-09 05:14:16.049 1453 5555 W LockSettingsService: Synthetic password not enabled
Then i put it in again to confirm that it is right (it accepts it)
Code:
06-09 05:14:16.902 1453 5555 W LockSettingsService: Synthetic password not enabled
And finally when I click OK and the screen goes back to settings and it shows that I have set a lockscreen password.
Code:
06-09 05:14:22.326 1043 1043 I keystore: del USRPKEY_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.328 1043 1043 I keystore: del USRCERT_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.329 1043 1043 I keystore: del CACERT_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.333 1043 1043 I keystore: del USRPKEY_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.334 1043 1043 I keystore: del USRCERT_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.335 1043 1043 I keystore: del CACERT_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.733 1043 1043 I keystore: del USRPKEY_synthetic_password_743cd98993860e51 1000
06-09 05:14:22.734 1043 1043 I keystore: del USRCERT_synthetic_password_743cd98993860e51 1000
06-09 05:14:22.735 1043 1043 I keystore: del CACERT_synthetic_password_743cd98993860e51 1000
06-09 05:14:22.736 1043 1043 I keystore: del USRPKEY_synthetic_password_743cd98993860e51 1000
06-09 05:14:22.737 1043 1043 I keystore: del USRCERT_synthetic_password_743cd98993860e51 1000
06-09 05:14:22.737 1043 1043 I keystore: del CACERT_synthetic_password_743cd98993860e51 1000
06-09 05:14:22.803 1043 1043 I keystore: del USRPKEY_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.815 1043 1043 I keystore: del USRCERT_synthetic_password_8719d7af3fc103f4 1000
06-09 05:14:22.817 1043 1043 I keystore: del CACERT_synthetic_password_8719d7af3fc103f4 1000
And here is the error when I try to unlock the screen with the (correct) PIN that gets rejected:
Code:
06-09 05:19:37.552 634 634 E GatekeeperHalDevice: verify
06-09 05:19:37.552 634 634 E GatekeeperHalDevice: ret: 0
06-09 05:19:37.552 634 634 E GatekeeperHalDevice: resp->status: -24
06-09 05:19:37.558 2305 2305 D KeyguardSecurityView: [B]reportFailedPatternAttempt[/B]: #2
06-09 05:19:37.591 1453 1543 E UsbDeviceManager: handle message = 6
06-09 05:19:37.592 2305 2667 D KeyguardViewMediator: setKeyguardEnabled(true)
06-09 05:19:37.612 2305 2305 D KeyguardViewMediator: handleKeyguardDoneDrawing
06-09 05:19:37.621 2305 2305 V KeyguardUpdateMonitor: startListeningForFingerprint()

thunderteaser said:
... As I flashed TWRP again via fastboot, my device was encrypted again and I had to format my /data partition.
So I restored my /data backup and booted into MIUI again, that asked for my PIN. The PIN I previously set was not working anymore so I had to delete /data/system/locksettings.db and I was able to access the OS again. Funny thing, my fingerprints were still there and still worked to unlock the phone.
Click to expand...
Click to collapse
Do I understand correctly that you restored a backup of an encrypted data partition to an unencrypted data partition? If so, you will definitely have problems. If your device is encrypted, you probably should try restoring the backup again. If you are not encrypted, then you need to understand that, on lavender, setting pins/passwords, etc., will not work correctly if the device is not encrypted. Why? You would need to ask Xiaomi's programmers. But that is the situation.
In the end, you might need to do a clean flash ...

DarthJabba9 said:
Do I understand correctly that you restored a backup of an encrypted data partition to an unencrypted data partition? If so, you will definitely have problems. If your device is encrypted, you probably should try restoring the backup again. If you are not encrypted, then you need to understand that, on lavender, setting pins/passwords, etc., will not work correctly if the device is not encrypted. Why? You would need to ask Xiaomi's programmers. But that is the situation.
In the end, you might need to do a clean flash ...
Click to expand...
Click to collapse
Thanks for your answer. My backup comes from a /data partition that was originally formatted via TWRP when I unlocked the bootloader and rooted it, so it should be decrypted. If setting a PIN means encrypting data once again, then you are correct, as I backed up my partition with all of my lock settings stored. But to answer your question: I don't know. It just makes no sense to me, as I was able to restore my data and everything works smoothly besides the lock settings. I just know that most of my problems come from having an unreliable TWRP which doesn't support MIUI encryption (I'm waiting for OrangeFox to be released), but other than that I don't understand what is going on with Android security since Marshmallow was released (I'm coming from a OnePlus One stuck on Marshmallow).
So, should I factory reset?

thunderteaser said:
Thanks for your answer. My backup comes from a /data partition that was originally formatted via TWRP when I unlocked the bootloader and rooted it, so it should be decrypted. If setting a PIN means encrypting data once again, then you are correct, as I backed up my partition with all of my lock settings stored. But to answer your question: I don't know. It just makes no sense to me, as I was able to restore my data and everything works smoothly besides the lock settings. I just know that most of my problems come from having an unreliable TWRP which doesn't support MIUI encryption (I'm waiting for OrangeFox to be released), but other than that I don't understand what is going on with Android security since Marshmallow was released (I'm coming from a OnePlus One stuck on Marshmallow).
So, should I factory reset?
Click to expand...
Click to collapse
Rooting the device doesn't mean that it is decrypted. The lavender ROMs have a nasty habit of encrypting the device again when you boot to system (unless you have effectively disabled forced-encryption after formatting data - but this situation can change quickly). If you are not encrypted, then no attempt at securing the phone will work. It will allow you to set a pin/password, but they will always be declared to be "wrong" when you try to unlock the phone. You can easily check whether you are encrypted or not (in the ROM's security settings). Another clue - if you don't see any option of setting a fingerprint, then it means that you are not encrypted. What does the debug screen show when you boot up TWRP? If it shows something like "dm-0" somewhere on the page, then you are encrypted.
The long and short of it is this - if you want to be able to use pins/passwords/fingerprint, then your phone needs to be encrypted. IMHO all these problems with encryption are due to bugs in Xiaomi's Pie firmwares (and this is getting worse by the day). The other possible interpretation is that this is all deliberate - but I am not a conspiracy theorist, so I choose to believe that these problems are not due to malice.
Doing a factory reset is a good way of starting afresh (I don't know whether formatting data again would be better). However, if you do this, don't try to restore the data backup again - you will just return to "square one".
PS: there are already stable betas of OrangeFox for lavender (see my signature) ...

DarthJabba9 said:
Rooting the device doesn't mean that it is decrypted. The lavender ROMs have a nasty habit of encrypting the device again when you boot to system (unless you have effectively disabled forced-encryption after formatting data - but this situation can change quickly). If you are not encrypted, then no attempt at securing the phone will work. It will allow you to set a pin/password, but they will always be declared to be "wrong" when you try to unlock the phone. You can easily check whether you are encrypted or not (in the ROM's security settings). Another clue - if you don't see any option of setting a fingerprint, then it means that you are not encrypted.
Click to expand...
Click to collapse
Thanks for your superclear answer. I still don't get how to check for encryption on MIUI 10. I can't see anything related to encryption in security settings, but I still see the options to add fingerprints. Also, "adb shell ro.crypto.status" fails because there is no such file.
What does the debug screen show when you boot up TWRP? If it shows something like "dm-0" somewhere on the page, then you are encrypted.
Click to expand...
Click to collapse
Can't see any result for dm-* in my recovery log.
The long and short of it is this - if you want to be able to use pins/passwords/fingerprint, then your phone needs to be encrypted. IMHO all these problems with encryption are due to bugs in Xiaomi's Pie firmwares (and this is getting worse by the day). The other possible interpretation is that this is all deliberate - but I am not a conspiracy theorist, so I choose to believe that these problems are not due to malice.
Doing a factory reset is a good way of starting afresh (I don't know whether formatting data again would be better). However, if you do this, don't try to restore the data backup again - you will just return to "square one".
Click to expand...
Click to collapse
So do you think this happened because I originally flashed a lazyflasher version that disabled dm-verity AND force-encryption in the attempt to not lose my data partition when I flashed an updated rom?
PS: there are already stable betas of OrangeFox for lavender (see my signature) ...
Click to expand...
Click to collapse
I will definitely follow its development, thank you so much!

thunderteaser said:
Thanks for your superclear answer. I still don't get how to check for encryption on MIUI 10. I can't see anything related to encryption in security settings, but I still see the options to add fingerprints. Also, "adb shell ro.crypto.status" fails because there is no such file.
Click to expand...
Click to collapse
Send me your recovery log via PM, and I will tell you whether you are encrypted.
thunderteaser said:
So do you think this happened because I originally flashed a lazyflasher version that disabled dm-verity AND force-encryption in the attempt to not lose my data partition when I flashed an updated rom?
Click to expand...
Click to collapse
I am not sure what is the cause. But you might just want to cut your losses and reset to defaults (or, better still, format data, and let MIUI encrypt again when you restart the phone). You will of course lose all your data (and if you format data, you will lose the contents of your internal storage). However, IMHO, life is too short, and setting up a pristine system is much better than the pain endured in trying to fix these fiddly problems (always a good idea to have your data backed up on the cloud anyway - whether it is GDrive or MiCloud). This makes it less painful to set up your phone again from the start.

DarthJabba9 said:
Send me your recovery log via PM, and I will tell you whether you are encrypted.
I am not sure what is the cause. But you might just want to cut your losses and reset to defaults (or, better still, format data, and let MIUI encrypt again when you restart the phone). You will of course lose all your data (and if you format data, you will lose the contents of your internal storage). However, IMHO, life is too short, and setting up a pristine system is much better than the pain endured in trying to fix these fiddly problems (always a good idea to have your data backed up on the cloud anyway - whether it is GDrive or MiCloud). This makes it less painful to set up your phone again from the start.
Click to expand...
Click to collapse
Well, you are absolutely right but I can't stop thinking of it as an entertaining part of being an Android user, or I won't be on xda . I've sent you my log, I really appreciate your help. <3

I'm back here just to update the thread with a solution for encryption problems, hoping it will help people with similar issues.
If you are going to stay on official MIUI 10 global stable and plan to install root/magisk and still lock the device by any means (pin, pattern, fingerprints, face unlock, etc.) your data partition MUST be encrypted. If your data partition is decrypted, the only way to encrypt it properly again would be by flashing a stock data partition via fastboot (using Mi Flash Tool to flash a whole stock ROM from scratch would be even better), so backup everything as you are going to lose your data.
Then, I absolutely recommend flashing the latest OrangeFox recovery by @DarthJabba9 (see his signature), which is the only recovery I found that properly supports MIUI encryption and also supports OTA updates (and has a lot of amazing features too and a pretty cool design!).
Since the fastboot image I flashed was 10.3.2 EU, I wanted to update to 10.3.3 EU via recovery without losing data and encryption. Here is what I did (you may follow these steps as a generic guide to update to any OTA version):
1) In OrangeFox recovery click on the Settings icon on the top right and enter "MIUI OTA" settings
2) Keep everything on, but make sure to untick "disable dm-verity" and "disable force-encryption" as you want to keep them enabled (the MIUI OTA main switch on top will switch off but everything you have set will still be applied)
3) Flash the full recovery ROM zip you want to update to
4) Flash Magisk and everything else you need
5) Reboot
If you did everything correctly, Magisk installer will tell you that it's keeping dm-verity and encryption untouched (this settings are also reflected in Magisk Manager app: in the main screen go to Advanced Settings and you will see both dm verity and encryption settings checked).
Thanks to @DarthJabba9 again for the awesome support! :highfive:

CROSSCALL CORE-X3 L750_02 OTA Update 8.1+

Here is the Orange (French MNO) OTA update. May be someone could use this to make the world better.
We have to start somewhere....
CROSSCALL CORE-X3 L750_02 OTA Update 8.1+
The file is a zip without extension.
CROSSCALL CORE-X3 specifications.

Nice thank you ! How did you manage to get the ZIP ?

Believe me or not, I can't remember...
Once upon a time, late at a full moon night.
But I think I had to open the update client (Mise à jour / Adups FOTA)
Then let it download the update. Then, when I tried to update, it shame fails.
The process includes a reboot, so the file can't stay in RAM.
I managed somehow to grab it to my computer with ADB or something like that.
The 'Disk Usage' app is useful to monitor space take by apps.
Bonne chance.

BREAKING NEWS: Adups FOTA is malware.
To remove this sh¡t:
adb shell pm uninstall -k --user 0 com.adups.fota
adb shell pm uninstall -k --user 0 com.adups.fota.sysoper

I just called the Crosscall support,
A nice guy tells me the society behind the bootloader doesn't want you to unlock it!
He said:
"You own the phone, but what's inside isn't yours! It's the property of the China Empire, including all your data!
You can't complain about AdupsFOTAmalware, because Apple, Samsung, and Ms are all doing the same!
They broke the law so we (Adups) are allowed to broke the law too and steal your data.
He defended his company saying they only sell hardware, not software.

github : bkerler/edl
github : nijel8/emmcdl
github : forth32/qtools

Bootloader Unlocking on older Qualcomm ZTE Devices, /Devinfo partition modification
Warning: This unlocking method might not work on newer ZTE devices with Oreo+ and flagship devices. You have nothing to lose, but it might not do anything. This tutorial is only for Qualcomm ZTE Devices. Unlocking the Bootloader: Warning: This...
forum.xda-developers.com
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Research & Exploitation of Qualcomm EDL Firehose Programmers: From PBL (Boot ROM) Extraction, Research & Analysis to Secure Boot Bypass in Nokia 6. (Part 1)
alephsecurity.com
Android Device Collection - Google Drive
docs.google.com
SERMA SAFETY & SECURITY » Andoid : Sécurité du bootloader et contournement des méthodes d’unlock officielles
www.serma-safety-security.com
[TOOL] Boot.img tools [unpack, repack, ramdisk]
I have not seen this posted anywhere, so I thought I would post it here. This is NOT purely my work, and I do not take credit for it as such. Included in the attached ZIP are the following files: boot_info - prints information about the...
forum.xda-developers.com
fastboot/README.md
EMMC_Block_Read_Write_V2.0
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
https://www.usenix.org/system/files/conference/woot17/woot17-paper-hay.pdf
GitHub - seSuperuser/super-bootimg: Tools to edit Android boot.img. NDK buildable, to be usable in an update.zip
Tools to edit Android boot.img. NDK buildable, to be usable in an update.zip - GitHub - seSuperuser/super-bootimg: Tools to edit Android boot.img. NDK buildable, to be usable in an update.zip
github.com
[TOOL] Boot.img tools [unpack, repack, ramdisk]
I have not seen this posted anywhere, so I thought I would post it here. This is NOT purely my work, and I do not take credit for it as such. Included in the attached ZIP are the following files: boot_info - prints information about the...
forum.xda-developers.com
abootool/config.py at master · alephsecurity/abootool
Simple tool to dynamically discover hidden fastboot OEM commands based on static knowledge - abootool/config.py at master · alephsecurity/abootool
github.com
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
https://cellphonetrackers.org/wp-content/uploads/8x60_msimage.mbn_.txt
using Netcat to transfer Android file system image directly local machine
Netcat provides an efficient means of investigating a network from the back-end side –servers-- and further establish any new connection inside networks...
infosecaddicts.com
adbcommand.com - adbcommand Resources and Information.
adbcommand.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, adbcommand.com has it all. We hope you find what you are searching for!
adbcommand.com
Liste des commandes ADB et Fastboot - L’outil indispensable du Super Utilisateur Android
Voici les commandes pour Adb et Fastboot ainsi que leur description. Cependant, toutes les commandes ne fonctionnent pas sur tous les appareils…
www.android-mt.com
List of ADB and Fastboot Commands - Phonlab
Here are some commands for Adb and Fastboot. I have collected these over the years including some fun OEM commands.
phonlabtech.com
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode. To make sure this guide will work as expect, following requirements are needed: - Know how to trigger the phone to EDL...
forum.xda-developers.com
Most Complete ADB Cheat Sheet
Download the most complete ADB cheat sheet. All you need to to know- the most basic operations to the most advanced configurations.
www.automatetheplanet.com
Signing, Building and Flashing an Image for Secure Boot on the Qualcomm® QCA4020/4024 Platform
developer.qualcomm.com
How to fix Sahara fail error in QFIL - Hovatek Blog
Qualcomm Flash Image Loader (QFIL) is a free tool for flashing Qualcomm-based Android devices. QFIL-flashable firmware come in either Flat
blog.hovatek.com
FP3 custom rom development based on released source code
Hi all, finally, I’ve managed to capture some short uart/whatever transmissions from a booting phone on pin T. Here is a snapshot: The data is still raw samples as I recorded them with a Bitscope Micro. I hope to find time to work on postprocessing soon. Here is the raw data and the...
forum.fairphone.com
http://cobweb.cs.uga.edu/~kangli/src/bootloader.pdf

I found something like this while looting in the config folder :
Code:
CONFIG_HISENSE_ADB_BACKDOOR=y