Database Info

[BOOTLOADER] Zenfone 6 a601cg bootloader unlock guide

Method is a little bit different .Usage is harder
It shows lines instead of screen while booting - fastboot -recovery. Example
But i have solution for it.
Dont worry it wont damages your device. You have to wait until your device boots and it will be normal
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,. Please
* do some research before unlocking it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, I will laugh at you.
*
*/
Prerequisites:
Install the Intel USB Driver and ASUS PCLink
Download all the required files
Extract the archives
Installation:
Put your device to fastboot mode
Flash fastboot%2Fzf6
fastboot flash fastboot fastboot%2Fzf6.img ** Jellybean Fastboot doesnt have any function itself. It will show only ASUS logo. You can use fastboot commands
Reboot Bootloader
fastboot reboot-bootloader
Flash bootloader files
fastboot flash dnx dnx_fwr_ctp_a600cg.bin
fastboot flash ifwi ifwi_ctp_a600cg_unlock.bin
Reboot bootloader
fastboot reboot-bootloader
Flash your previous droidboot/fastboot
fastboot flash fastboot fastboot.img
Flash TWRP
fastboot flash recovery "twrp-image".img
Reboot your phone
fastboot reboot
Enable USB Debugging then reboot recovery
adb reboot recovery
Wait until screen shows blue lines
Connect your device to pc
Type adb shell on cmd
Here is example codes for flashing:
twrp wipe data
twrp wipe cache
twrp install /sdcard/"example-rom".zip
twrp install /sdcard/"gapps".zip
If you dont have computer to do this twrp steps. There is a app called Auto Flasher Rom flash utility but its risky.
For locking: Just change ifwi. all goes with same method
Downloads
TWRP-3.0-M-2.0-recovery-T00F.zip (other versions untested + we need twrp version 3+
Fastboot
Bootloader Tools

thank you
---------- Post added at 09:58 AM ---------- Previous post was at 09:14 AM ----------
fastboot flash fastboot fastboot%2Fzf6.img
waiting for asus logo after restart

mdikmetas said:
thank you
---------- Post added at 09:58 AM ---------- Previous post was at 09:14 AM ----------
fastboot flash fastboot fastboot%2Fzf6.img
waiting for asus logo after restart
Click to expand...
Click to collapse
Information added about fastboot

worked now all thank you

thanks m8, helped me a lot

Thank you

Help me please
Method is a little bit different .Usage is harder
It shows lines instead of screen while booting - fastboot -recovery. Example
But i have solution for it.
Dont worry it wont damages your device. You have to wait until your device boots and it will be normal
Hey..im new in here..i've got problem when tried to follow your guide...my zen 6 a601cg shows line until now..almost 4 hours...its show that colouring lines,thats all..i'm very sure i'll follow ur guide correctly but after flashing twrp then reboot,the lines not disappear until now..help me please..
Sorry for my poor english..Thanks in advance..

I can't extract the archives because there is a password.
Could you give the password to extract the files please?
Thank you

After unlock, is there some way to remove the lines and show the logo and boot animation again?

emandreatta said:
I can't extract the archives because there is a password.
Could you give the password to extract the files please?
Thank you
Click to expand...
Click to collapse
I think you downloaded archives are corrupted. There is no encyription
emandreatta said:
After unlock, is there some way to remove the lines and show the logo and boot animation again?
Click to expand...
Click to collapse
It is only possible with soft reboot (or locking )

help required
i have asus zenfone 6 a600cg
I got the issues when I got an update and I started the update but the battery was low so the update could not install fully and in between it got bricked.
Now I cannot go into fastboot or the recovery or the droidboot.
when I press the power and volume up button it starts and shows me Asus logo only then it does not move further.
When I connect it to the PC the USB connected sign is shown in white colour.
I tried using the xfstk and load the file for that procedure but it was shooting error of win x200015..... Something.
Not the phone is really unusable so please help me.

[RECOVERY][STOCK]TWRP 3.3.1-0 UNOFFICIAL

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 recovery
* before using 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.
*
*/
Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June/July patch)
- Touch not working when installed
- Please report any other bugs
Install guide:
Installing is currently not recommended because touch is not working on the installed version!
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode from adb
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it
Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button
If it keeps booting into TWRP and not System try
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Download
Changelogs:
3.3.1-0 03.08.2019
- Initial Release
Source code:
https://github.com/Schritti/device-sony-mermaid
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
Thanks to:
@MartinX3 for helping me developing the TWRP
@Oshmoun for providing device trees for Ganges and Mermaid
@naoki2010 for Testing
XDA:DevDB Information
TWRP, ROM for the Sony Xperia X10 Plus
Contributors
Schritti, MartinX3, Oshmoun, Marijn
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-08-03
Created 2019-08-03
Last Updated 2019-08-05

Reserved

Reserved

Woohooo!
First!

My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.

sickkside13 said:
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
Click to expand...
Click to collapse
All variants are supported

I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?

clothtalklp said:
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
Click to expand...
Click to collapse
It's normal, that the screen is black in fastboot mode. If the LED is Blue then it's alright.
When you're in fastboot mode (Blue LED) check the windows device manager, you might install the driver again for fastboot. If it shows a device called "Android" you have to right click it and install the correct driver.

I just got the phone unlocked so i will boot into TWRP and install it and debug the touch. I have the feeling that it might be just missing file.

I just tested the installed version of TWRP and touch works just fine. The TWRP on itself is little slow. Decryption is broken and we see just bunch of junk folders in internal storage as expected.
But decryption shoudlnt be an issue after i bake TWRP into my AOSP images.
Rebooting into OS is totally broken and even cleaning misc doesnt help. Boots to TWRP all the time. Again most likely just an issue that it was not installed in boot.img right away but had to be added.

So about unlocking - my device/version isn't supported to unlock. Any hints?

mad-murdock said:
So about unlocking - my device/version isn't supported to unlock. Any hints?
Click to expand...
Click to collapse
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.

Haxk20 said:
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Click to expand...
Click to collapse
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.

mad-murdock said:
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
Click to expand...
Click to collapse
Sadly I do not think so. We would love another dev helping on SonyOpenSourceDevices or even custom ROMs but sadly if the phone is not unlockable there is nothing you can do sadly. I heard stories of people having carrier phones sim locked and after unlocking that they were able to unlock BT so you could possibly try that if the phone is locked to 1 carrier. If not then there i s really nothing you can do. I'm sorry.

Hi,
first off a big thank you!
I would like to root my xperia 10 plus I4213. I tried to do my homework before posting here, but since I am not knowledgeable on the subject, can someone confirm that these are the right steps:
1. Enable in phone third party apps, unlock developer settings, enable adb.
2. Boot in fastboot mode. That can be done in terminal, not by using buttons as it used to.
3. unlock bootloader . My understanding if that now, that can be achieved either via terminal or via windows newsflasher program.
4. Flash recovery from this thread
4. Boot into system and install magisk manager .
5. Install via recovery Magisk zip.
6, Boot into system and use magisk manager to enable root and set settings.
Should I install latest magisk 20.1 or an earlier version?
Thank you.

Problem with TWRP
Why is the device memory data encrypted even though the device doesn 't have a password?

reintal said:
Why is the device memory data encrypted even though the device doesn 't have a password?
Click to expand...
Click to collapse
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.

Haxk20 said:
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Click to expand...
Click to collapse
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.

reintal said:
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
Click to expand...
Click to collapse
We are mainly focus on making AOSP 10 stable now and TWRP is not on top of the list to fix now. And TWRP doesn't support Android 10 yet so we can't even begin.

[UNOFFICIAL][DECRYPTION WORKS] TWRP 3.3.1 for UMIDIGI F1 [20191103]

Introduction
This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.
Known Bugs
- Screen may flash on the password-input UI. Anything else is fine though.
This TWRP has been tested with official ROM and my LineageOS 17 port (https://forum.xda-developers.com/android/development/unofficial-lineageos-17-0-umidigi-f1-t3997827) and it works fine.
This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.
Why Bother
Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.
Instructions
1. Unlock bootloader
2. Enable ADB debugging in system
3. Execute "adb reboot bootloader" while having your phone connected to PC
4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"
5. Reboot phone while holding Volume Up + Power buttons
Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.
Downlaods & Sources
20191103: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191103-twrp
- Fixed issues with Magisk and OpenGAPPS
20191102: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191102-twrp
Device Tree: https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0
Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery

Updated to 20191103

I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.

mrmazak said:
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
Click to expand...
Click to collapse
Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`

hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks

Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.

mrmazak said:
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
Click to expand...
Click to collapse
Cause i test it without changes , it reboot to system
I think because they have different kernels

I am unable to install twrp.
When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...
Am I doing something wrong?

no fastboot response
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...

tarvoke said:
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
Click to expand...
Click to collapse
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Try installing:
- https://androidmtk.com/download-15-seconds-adb-installer
- https://androidmtk.com/download-mtk-usb-all-drivers
- https://www.androidweblog.com/download-mediatek-usb-vcom-drivers/
Start the process from device on using adb commands to always allow access to the pc. I mean:
Code:
adb devices
and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then
Code:
adb reboot bootloader
while on fastboot follow with
Code:
fastboot devices

SubwayChamp said:
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Click to expand...
Click to collapse
thanks!
adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.
this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.
(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)
like I said, pilot error lol. but thank you again for the reply!

I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?

opticyclic said:
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
Click to expand...
Click to collapse
While in fastboot the first you should do is see if device is detected by pc with
Code:
fastboot devices
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
If your device is detected then you can flash the recovery as you were trying to do it with
Code:
fastboot flash recovery recovery.img
and then you can reboot directly to it without need to reboot to system previously and this will prevent TWRP from being overwritten, with
Code:
fastboot boot recovery.img

hmm, so when I checked the udev rules, it already had one for MTK/mediatek - and the USB vendor is '08ed' in fastboot as well as in regular adb, so it wasn't a problem with udev/plugdev.
which I guess may mean the lunix generic android drivers for fastboot might be... "lacking" - I'll have to scrounge up a win7 laptop and try the recommended windows drivers.

SubwayChamp said:
...
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
...
Click to expand...
Click to collapse
I don't think it was anything to do with the path as it output the file transfer size.
I think it was a combination of the following:
I wasn't pressing the right combinations of buttons after flashing.
i.e. holding VOL UP and pressing POWER on the screen saying "Your device has been unlocked and can't be trusted".
Rebooting might (?) have been reverting the recovery.
I was originally trying this on the firmware that was shipped 2019012414 but after flashing 2019090418 with SPFlashTool I had more success.
I also able to reboot to recovery directly after flashing with fastboot with the following:
Code:
fastboot oem reboot-recovery
Whichever was the key I can now reboot to recovery from adb too.
:good:

Your twrp eliminates fingerprint authentication.
I discovered something interesting, your twrp only works on my device, no other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.

LyrielAlk said:
No other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
Click to expand...
Click to collapse
Try to clean flash last vendor build with spflash tool. First boot need stock recovery.
You don't need custom recovery to achieve root.
Maybe give a try to SNwriter (I never needed it though and can't help here).

Both of those twrp are not sticking. I have flashed with spoken flash tool v5 1944 win and I fastboot cmd with the same results.

Thanks
Gracias for this master ?

good
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
good idea

[RECOVERY][UNOFFICIAL] TWRP for OPPO A57

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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.
*
*/
Bugs
You tell me ;D
Install guide
See #2
Downloads
3.6.0_9-2
Source Code
https://github.com/omnirom/android_bootable_recovery
https://gitlab.com/TipzTeam/oppo-msm8937/recovery_device_oppo_A57
Donations
https://paypal.me/TipzTeam

Install guide​First-time installation (Windows)​
Power off your device
Press and hold Power, Vol +, Vol - while plugging your OPPO A57 into your computer
Unzip the file you've downloaded
Open MiFlash and select the extracted directory
See if your computer has detected you device. If so, click flash.
Wait until it say "Done".
Unplug your device. Press and hold Power Button, Vol +, Vol - until you feel a vibration and then the oppo splash screen
You should now be in the recovery.
First-time installation (Linux)​
Install edl
Power off your device
Press and hold Power, Vol +, Vol - while plugging your OPPO A57 into your computer
Unzip the file you've downloaded
Check lsusb and see if your computer has detected you device.
Run the following command in Terminal:
Code:
edl qfil <qfil_package_path>/rawprogram0.xml <qfil_package_path>/patch0.xml <qfil_package_path>
Unplug your device. Press and hold Power Button, Vol +, Vol - until you feel a vibration and then the oppo splash screen
You should now be in the recovery.
For others​
Extract the "recovery.img" file from the file you've have downloaded
Push the file to your device
Power off your device and boot into recovery mode
Click on "Install", then "Install Images"
Find the new recovery image and click on it
Select "Recovery" and swipe the bar at the bottom
Reboot into Recovery once the flash is done

Is this project treble enabled?
If yes, can you tell me the ways to install Gsi?

maharjanujwol said:
Is this project treble enabled?
If yes, can you tell me the ways to install Gsi?
Click to expand...
Click to collapse
No, this phone doesn't have any ROM.

Update for fully English version coming soon!

need A57 stock recovery image file. please anyone?

engr. mkhalid said:
need A57 stock recovery image file. please anyone?
Click to expand...
Click to collapse
Why would you want that?

TipzTeam said:
Why would you want that?
Click to expand...
Click to collapse
Do u have the unofficial version of twrp for oppo a57?

ninja711 said:
Do u have the unofficial version of twrp for oppo a57?
Click to expand...
Click to collapse
This is unofficial, wdym?

New TWRP update!
3.5.2_9-0 (Sep 12, 2021)
TWRP 3.5.2
Download

New TWRP update!
3.6.0_9-0 (Dec 25, 2021)
TWRP 3.6.0
Update to Android 9.0
Support vendor partition
Fix ramoops
Support NTFS
Add logcat support
Download

New TWRP update!
3.6.0_9-1 (Jan 24, 2021)
Fix decryption after Android Pie update
Allow wiping of vendor partition
Rename Modest to EFS
Download

New TWRP update!
3.6.0_9-2 (Jan 25, 2021)
Fix SD Card after Android Pie update
Allow rebooting to EDL mode and bootloader mode
Download

tipzrickycheung said:
Allow rebooting to EDL mode and bootloader mode
Click to expand...
Click to collapse
So we can now boot into fastboot mode the commands doesn't seem to work.
Everything except a few returns something like "remote command not found".
Code:
fastboot devices
works fine & shows the connected device but
Code:
fastboot oem device-info
doesn't.
Is it because the device doesn't have fastboot binaries or something like that?

impawstarlight said:
So we can now boot into fastboot mode the commands doesn't seem to work.
Everything except a few returns something like "remote command not found".
Code:
fastboot devices
works fine & shows the connected device but
Code:
fastboot oem device-info
doesn't.
Is it because the device doesn't have fastboot binaries or something like that?
Click to expand...
Click to collapse
This device has its bootloader commands removed, which is a build flag of LK (Little Kernel, used on almost all QCOM device).
We can't compile our own for the A57 since it has secure boot on.

大家有A57刷机包吗

Hi @tipzrickycheung , thank you for TWRP.
I saw a screen on Telegram where you installed Magisk too. But if I try to install magisk.zip or to flash a patched boot.img from EDL, I get stuck in a boot loop and have to reinstall a stock rom.

Tupolef said:
嗨 @tipzrickycheung，谢谢你使用 TWRP。
我在 Telegram 上看到一个屏幕，你也安装了 Magisk。但是，如果我尝试安装 magisk.zip 或从 EDL 刷入已打补丁的 boot.img，我就会陷入引导循环，不得不重新安装一个 stock rom。
Click to expand...
Click to collapse
你做完了吗？我现在也发生这种情况，一旦安装了 magisk.zip，它就会卡在“当前映像（启动/恢复）已被破坏，无法启动...”

oddhw said:
你做完了吗？我现在也发生这种情况，一旦安装了 magisk.zip，它就会卡在“当前映像（启动/恢复）已被破坏，无法启动...”
Click to expand...
Click to collapse
I went back to a Stock Rom and I didn't find any other solution. It wasn't my device, so I will not try again.

[RECOVERY] [jasmine_sprout] Sky Hawk Recovery Project v2.2 [04-03-2020]

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
SHRP is inspired by Material design 2 to bring the newest design to the native TWRP. SHRP provides much more along side of it's rich UI experience. New dashboard makes it very easy to interact with TWRP. SHRP got some cool features like Whole new theming section ,Flash Magisk (root or unroot), Camera2api enabler Directly from dashboard, Password protection etc. It's all started , lot more to come.
- Themes
- List view mode along with grid dashboard
- Status bar customization
- New rounded icons added on dashboard
- Notch mode with toggle to disable
- Dark mode or pure white, it's on you
- Navigation bar customization
- Settings + Advanced Settings
- Flash Magisk
- Clear fingerprints.
- Flash ViperFX
- Recovery Locking , Pin or Pattern lock
- CPU core lock/unlock
- Language changing
- Hal3 / CameraAPI2 enabling/disabling
- Oreo+ Reboot menu style
- Redesigned lock screen interface
- Flashlight
- Magisk manager - Enable, disable or delete magisk modules right from SHRP
- and many more, flash right now to find out
1. Make sure you have a custom recovery installed
2. Download the latest SHRP recovery for your device
3. Boot into recovery
4. Flash shrp recovery zip
5. Reboot to recovery.
6. Done
It may happen that after installing the recovery, the device could no longer boot into the ROM, for this you just need to install magisk.
Decryption may not work.
It may happen that the recovery freezes on the logo, to resolve it check this thread here.
No other bugs
DOWNLOAD NOW
Github
Website
ScreenShots
Telegram Group
EpicX
DNI9
Giovix92
TeamWin
osmOsis
VR25
Topjohnwu
Mauronofrio
DarthJabba9
Special Thanks
Pritish
Kirill
Burak D.
ZJRDroid
LayeardDevMod
Please inform if we forgot to mention your name here , thanks !
​
Maintainer: XRed_CubeX
Based On: TWRP
TWRP Version: v3.3.1-0
XDA:DevDB Information
[RECOVERY] [jasmine_sprout] Sky Hawk Recovery Project v2.2 [04-03-2020], ROM for the Xiaomi Mi A2
Contributors
XRed_CubeX
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: TWRP
Version Information
Status: Stable
Created 2020-03-11
Last Updated 2020-03-14

Reserved
Changelogs:
SHRP V2.2 104011032020:
Fixed the bug that recovery did not create the SHRP folder and therefore the themes did not work.
Added support for F2FS.
Added IMG file.
SHRP V2.2 Official:
Initial build

nice recovery

Clean, clear and nice set of features.
Really like this one, thanks!
Hm, but I really do miss the option to wipe vendor.
Not possible, also not after mounting.

it is wanted, it is not included, however, in a future update I can add it

I flashed this zip via a official twrp (booted the official twrp via "fastboot boot twrp.img" command).
so the problem i'm facing is that after FLASHING any recovery other than by using "FASTBOOT BOOT COMMAND" the recovery gets stuck at the loading screen/ The recovery logo.
It's the same issue with all three recoveries I tried
e.g.: pitch-black recovery, Official TWRP, and this recovery all gets stuck at the logo
can anyone help me

Nikhil Chandran said:
I flashed this zip via a official twrp (booted the official twrp via "fastboot boot twrp.img" command).
so the problem i'm facing is that after FLASHING any recovery other than by using "FASTBOOT BOOT COMMAND" the recovery gets stuck at the loading screen/ The recovery logo.
It's the same issue with all three recoveries I tried
e.g.: pitch-black recovery, Official TWRP, and this recovery all gets stuck at the logo
can anyone help me
Click to expand...
Click to collapse
Use the .img files with fastboot only to boot into recovery.
Then use the .zip recovery file from within the booted recovery to flash permanent twrp, after the ROM installation.

Phil_Smith said:
Use the .img files with fastboot only to boot into recovery.
Then use the .zip recovery file from within the booted recovery to flash permanent twrp, after the ROM installation.
Click to expand...
Click to collapse
I tried to flash the recovery like you said I'm on PEX Q.
And I booted to the official twrp (via command) then flashed this recovery and it back-up ed the boot img from both slots and replaced with this recovery and after that when I try to go to the recovery the it does go to the recovery but it's not loading after the logo, it's stuck at the logo, so I tried to boot the phone it went to fastboot without booting the phone. So I dirty flashed the ROM now it's booting but I lost magisk root and even after trying to flash magisk over and over I can't get root ( I think I tried on both slots ) still not getting root or loading the recovery after the logo

Nikhil Chandran said:
I flashed this zip via a official twrp (booted the official twrp via "fastboot boot twrp.img" command).
so the problem i'm facing is that after FLASHING any recovery other than by using "FASTBOOT BOOT COMMAND" the recovery gets stuck at the loading screen/ The recovery logo.
It's the same issue with all three recoveries I tried
e.g.: pitch-black recovery, Official TWRP, and this recovery all gets stuck at the logo
can anyone help me
Click to expand...
Click to collapse
This happens when starting from the Stock ROM without doing fastboot -w.
This command must be done only with PLATFORM TOOLS!!! And not with Minimal fastboot or 15 seconds Adb installer.
The default Stock ROM has the data encrypted and gives problems when starting recovery when installed but not when it is started temporarily. You can try doing "Format data" from the Normal TWRP and then try installing other Custom Recovery. I have had this problem in the past and solved it with fastboot -w but I have not tested format data with TWRP.
P.S: This also happens with ROM encrypted with FBE. (eg PE Fan Edition)
TWRP 4pda is compatible with FBE

XRed_CubeX said:
This happens when starting from the Stock ROM without doing fastboot -w.
This command must be done only with PLATFORM TOOLS!!! And not with Minimal fastboot or 15 seconds Adb installer.
The default Stock ROM has the data encrypted and gives problems when starting recovery when installed but not when it is started temporarily. You can try doing "Format data" from the Normal TWRP and then try installing other Custom Recovery. I have had this problem in the past and solved it with fastboot -w but I have not tested format data with TWRP.
P.S: This also happens with Roma encrypted with FBE. (eg PE Fan Edition)
TWRP 4pda is compatible with FBE
Click to expand...
Click to collapse
What happens when I use the fastboot -w
Can I use this fastboot -w command without formatting data, becouse I formatted everything when coming from the stock rom / unlocking the bootloader.
Can I get your recoveries img file, the zip doesn't contain a img version

Nikhil Chandran said:
What happens when I use the fastboot -w
Can I use this fastboot -w command without formatting data, becouse I formatted everything when coming from the stock rom / unlocking the bootloader.
Can I get your recoveries img file, the zip doesn't contain a img version
Click to expand...
Click to collapse
I am about to release an update of the SHRP and I will add the img.
Fastboot -w will format data and decrypt too.

XRed_CubeX said:
I am about to release an update of the SHRP and I will add the img.
Click to expand...
Click to collapse
May I know when?.
Cuz I'm going to format everything and start over

Nikhil Chandran said:
May I know when?.
Cuz I'm going to format everything and start over
Click to expand...
Click to collapse
Now, check out sourceforge

XRed_CubeX said:
Now, check out sourceforge
Click to expand...
Click to collapse
Thanks I'll check with the fastboot -w command
To fix the issue
Update:
Tried to boot via fastboot command it's stuck on the logo ( haven't tried fastboot -w command yet).
Twrp is booting without an issue

Nikhil Chandran said:
Thanks I'll check with the fastboot -w command
To fix the issue
Update:
Tried to boot via fastboot command it's stuck on the logo ( haven't tried fastboot -w command yet).
Twrp is booting without an issue
Click to expand...
Click to collapse
Do fastboot -w

XRed_CubeX said:
Do fastboot -w
Click to expand...
Click to collapse
Just formatted everything and also used the fastboot -w command and now everything works fine. The only thing left is that learning about the 2 slots. Also everytime I flash something like magisk or save a screenshot a red error line appears saying "failed to mound '/vendor ' (device or resource busy)

this is normal, it means that the vendor partition was used after a flash and recovery should be restarted

Nikhil Chandran said:
Just formatted everything and also used the fastboot -w command and now everything works fine. The only thing left is that learning about the 2 slots. Also everytime I flash something like magisk or save a screenshot a red error line appears saying "failed to mound '/vendor ' (device or resource busy)
Click to expand...
Click to collapse
About a/b and so forth:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

Phil_Smith said:
About a/b and so forth:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks the guide was very helpfull :laugh:

Best custom recovery
I was searching a custom recovery, when i try these i love it !!!!!
GOOD JOB!!!!:good::good::good: