Develop Bugs

[D5503] Lollipop 5.1.1 goes AICP 13.1 Oreo 8.1 /// Beginners Link Collection

Hello hello,
this will be my "live" thread of bringing AICP 13.1 to my xperia z1c, I found some Guide's that I will follow and I will share with you all the links and knowledge I gained as a newbie that I used to understand and fix my problems on the way.
Maybe this will help you, too.
Main Tutorial: LINK
Target of all this: LINK
My Device:
Sony XPERIA Z1C, 14.6.A.1.236 , Lollipop 5.1.1
My best hint: read carefully, take your time to understand what you're trying to do and do your own research!
Hopefully you will get a aicp custom rom out of it.
_____________________________________________
_____________________________________________
General information: Android 5.1.1 cannot be rooted due to its high security standards, therefore we will downgrade to a lower security stock rom and create root access there. Root access will be needed as well as an unlocked bootloader to install real recovery (TWRP) which is the tool to flash custom roms like aicp. But the aicp custom rom will not have a good working camera, don't ask me why, but the camera seems to be a really difficult thing from the point of developer's view, let's accept this. Aside of that disadvantage, this custom rom is a very nice software and it makes my z1c kind of new. I don't use my camera anyway often at all.
During all this flashing thing I had a very big ??? while implementing real recovery. I was able to flash the .236.ftf but not the openbootloader.ftf as described in section 5 in the main tutorial. The result was twrp boot failed.
Error description:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
boot stock rom works
My solution:
I restarted from scratch and finally with the kind of messed up secquenceI got it:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
flash openbootloader works
flash twrp works
boot twrp works
UPDATE 06.12.2018 as a solution for REAL RECOVERY with working camera <<< RECOMMENDED
0. boot into rom works
1. flash openbootloader works
2. boot into rom works
3. flash .236.ftf works
4. boot into rom & check camera works
3. flash twrp ( business as usal ) works
4. boot twrp ( First boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
5. full wipe, flash aicp-rom, flash gapps, flash magisk-root, boot system works
6. enjoy Oreo 8.1 & camera check !!! works !!!
This routine worked straight forward for me where I started from scratch with my second device.
Flashing aicp was pretty easy, good to know for flashing the rom was full wipe = advanced wipe and select everything except of micro sd
To complete my aicp 13.1 Oreo 8.1 device the camera problem has to be fixed ( Saving the taken picture fails, display goes into freeze, no chance to solve this with camera mods, camera apps )
But @lm089 gave me the right hint, and finally this was my solution! Thanks again @lm089!!
Have fun with your new >> SONY XPERIA Z1 COMPACT <<
How to update TWRP
1. Turn Off your device
2. Start device in fastboot mode by connecting via usb cable to your pc and press Vol- until blue led tuns on
3. use fastboot flash recovery twrp.img to flash it
4. boot twrp ( This first boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
How to update to aicp 14.0 pie 9.0
starting with the running and latest aicp 13.1 oreo 8.1 rom above I just followed the Instructions here. As a specialty I had to install the Magisk Manager App manually into the rom to get root. Downloading supersu.apk from www.supersuroot.org works fine as well.
Your fastboot connection doesnt work for some reason though u had this workin fine in the past? maybe u had a windows update. install your drivers again.
>> LETS KEEP THIS DEVICE ALIVE <<
_____________________________________________
_____________________________________________
More helpful links that I used:
Debug apps by creating logs
what is adb? an xda tutorial
ADB working Download Link and ADB Article on xda
xda flashtool error during setup: click
[NOOBIE] Basic adb commands and device partition overview
Latest TWRP 3.2.3-0 for z1c
root solution using flash tool
Restore DRM functionality after UB
If TA Backup dry restoration restoration fails: Solution and Download *.dll
Boot into recovery or fastboot mode
How to install TWRP
Magisk beats superSU
How to Install Custom ROM using TWRP for Android!
change boot animations
[TUTORIAL] Design Your Own Bootanimation
Backup & Restore Your ROM With TWRP
Terminology: odex and deodex
If the camera goes into freeze or saving the picture fails: This was my solution! /// But you better go straight with the steps of my update 06.12.2018, field tested!
THANKS A LOT TO @colaigor for his [BEGINNERS GUIDE]

Ok. So i dont have much time now but i can give some short directions.
1. Get unlock codes from sony for bootloader unlock
2. Instal adb and fastboot at your system(PC)
3. Instal z1c drivers
4. Instal flashtool
5. Unlock bootloader,root,flash recovery(search forum for "real recovery" ),flash root solution
6. Flash wanted rom,gaps
P.P. On second thought u dont need flashtool. All can be done with adb and fastboot commands from terminal

There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?

derjango said:
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
Click to expand...
Click to collapse
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.

Ok thank you :good:

flashtool log of openbootloader.ftf failed:
01/015/2018 13:15:58 - INFO - Device connected in flash mode
01/017/2018 13:17:19 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
01/017/2018 13:17:19 - INFO - Preparing files for flashing
01/017/2018 13:17:19 - INFO - Please connect your device into flashmode.
01/017/2018 13:17:19 - INFO - Using Gordon gate drivers version 3.1.0.0
01/017/2018 13:17:20 - INFO - Opening device for R/W
01/017/2018 13:17:20 - INFO - Device ready for R/W.
01/017/2018 13:17:20 - INFO - Reading device information
Click to expand...
Click to collapse
solved, I skipped step 5.2, flashing the .236.ftf in advance
but how can I start TWRP?
doesnt work with POWER + Vol-, vibrate & release power
I tried to flash the following recovery solution using this command:
smartphone in fastboot mode (blue LED enabled)
fastboot flash recovery recovery.img
TWRP from step 5.1 of the GUIDE
TWRP 3.0.2
My formerly flashed .236.ftf rom works fine, but I cant start TWRP the device goes directly to my rom

zlata said:
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Click to expand...
Click to collapse
Thats where I'm stuck right now, any ideas how to fix?

okay got it, basically i do not know what the problem is but:
after BLU
flash .236 :good:
flash openbootloader
flash twrp :good:
--> failed to install openbootloader and probably thus twrp failed
solution: I skipped to flash .236 as recommended by the author of the GUIDE (step 5.2)
flash open bootloader :good:
flash twrp :good:
--> failed to start twrp, though it was installed successfully
flash .236 :good:
flash openbootloader (failed again, but it's already on the device and I guess I could have skipped this here)
flash twrp :good:
first boot of twrp is successful :good:
And basically the author explained it in his text, FIRST INSTALL OPEN BOOTLOADER BEFORE WRITING STH TO RECOVERY PARTITION

I think you should use Aicp 14 pie instead of 13.1 Oreo
I feel Aicp 14 PIE is very stable and flash port camera stock this link https://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/port-stock-camera-nougat-roms- t3628791

Nice thread, thank you! Wish I had that when I started rooting and flashing

@lm089 Haha it's quite some work to get into it, right? I just saw that we are running on the same device & custom rom, how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj

derjango said:
how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
Click to expand...
Click to collapse
Had this situation twice with 2 different oreo ROMs. Both times I solved it following a rather strange sounding suggestion I found on the AICP 13.1 discussion thread. The basic idea is to go back to a stock Sony ROM. Boot into it and make sure the camera is working which for me was the case both times. Then - if necessary - re-root your phone (on first occasion I flashed a pre-rooted .236 version but that caused some extra trouble so next time I decided to flash an unrooted version). And from then on it's the standard way as you described it in your OP.
Good luck!

Okay, thanks a lot for your hint! Unfortunately the camera mod didn't fix the problem, my android-task for this evening is defined:
AICP 13.1 Oreo 8.1 on z1c, root, ulb, magisk 17.1
1. backup my system (done)
2.0 flash stock rom lollipop 5.1.1 (14.6.A.1.236.ftf) with flashtool via usb (done),booting the os for the first time takes quite long (~10m), check camera in the os (done)
interesting fact: recovery is deleted by flashing the rom via flashtool - I thought I can go the lazy way and skip the step of installing twrp again into recovery
2.1 okay, let's do it: install twrp (done) and boot into twrp, NOT into ROM!! (done) (Vol- & Power, wait for vibration & release Power but keep Vol- until TWRP starts up)
3. flash aicp 13.1 following this (full wipe as an advanced wipe: select all EXCLUDING THE SD STORAGE)
Again here, I recognized the first boot of the rom takes quite longer.
4. check camera (done)
!!!! IT WORKS !!!!
(I did it two times)

alright, lets start flashing my second device - now I know how to do it
Thanks guys!!

derjango said:
!!!! IT WORKS !!!![/SIZE]
Click to expand...
Click to collapse
Weird, isn't it?

lm089 said:
Weird, isn't it?
Click to expand...
Click to collapse
Totally But hey, it's a solution
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too

derjango said:
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
Click to expand...
Click to collapse
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?

lm089 said:
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
Click to expand...
Click to collapse
Yes, its used as an external storage

derjango said:
Yes, its used as an external storage
Click to expand...
Click to collapse
ok, that's something different; adoptable storage means that your SD or part of it is setup to extend internal storage. If you can access all of your SD from TWRP then it is indeed formatted a external storage.

1) How to unlock bootloader:
https://developer.sony.com/develop/...ed/unlock-bootloader/how-to-unlock-bootloader
2) Download Platform-tools (adb & fastboot) r.26.0.2 as latests version does not work (or just for me):
https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
3) Download TWRP 3.2.3-0 https://androidfilehost.com/?fid=11410963190603854057 and place file in Platform Tools folder on PC
4) Restart in fastboot mode and flash revovery:
fastboot flash recovery Z1C_twrp_3.2.3-0.img
fastboot reboot
5.1) Download AICP Oreo 8.1 http://dwnld.aicp-rom.com/device/amami/WEEKLY/aicp_amami_o-13.1-WEEKLY-20181204.zip and place file in Platform Tools folder on PC
5.2) Download Gapps Pico https://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico and place file in Platform Tools folder on PC
5.3) Download stable Magisk 17.1 https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip place file in Platform Tools folder on PC
6.1) Load TWRP. Advance>ADB Sideload (for Oreo)
adb sideload aicp_amami_o-13.1-WEEKLY-20181204.zip
(do not restart)
6.2) Repeat Advance>ADB Sideload (for Gapps)
adb sideload open_gapps-arm-8.1-pico-2018XXXX.zip
(do not restart)
6.3) Repeat Advance>ADB Sideload (for Magisk)
adb sideload Magisk-v17.1.zip
(restart)

Alcatel 1x DEVELOPMENT: Kernel, TWRP, Pie ROMs, Guides

ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )

Downloading, will post results!!! Thanks!

milankragujevic said:
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Click to expand...
Click to collapse
Not working twrp not working touch screen
I have twrp all work i Russia

milankragujevic said:
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Click to expand...
Click to collapse
Could it work with alacatel 1 (5033a)? It has the same chipset but differs in other characteristics.

Hey, are you still building a Lineage OS?

Los link estan caidos. Instale el twrp pero queda en bootloop twrp. Saque el boot.img con el twrp para parchearlo con magisk pero al flashearlo con cmd vuelve a quedarse en el twrp. Podrias pasar el boot.img stock? Gracias

Flash recovery

AUTH files doesn't work with A variant (5059A).

January 2020 and the link is gone. (I can host it if you like. Message me.)

The files are back up. Sorry about the inconvenience.

NP. Thanks.

Update links PLS
Hello? Does anyone have the DA and Auth files? The links are broken and I cant find online, help pls my phone is hard bricked. Thanks.

T3ll3S said:
Hello? Does anyone have the DA and Auth files? The links are broken and I cant find online, help pls my phone is hard bricked. Thanks.
Click to expand...
Click to collapse
Links are back, the server had failed and I moved the files to another datacenter which took 3 days.
Here's a MEGA link just in case, if this happens again: https://mega.nz/file/i3BhASJJ#pNzwAsflvcvdfr3pGzUfbNhe3fHUCnfyoAR_O4IsFAE

Hi again, does anyone of you know how to fix this error, im very scared that my phone wont show any screen again.
This is what happened: I tried to install Android 10 GSI and bootlooped so I went to TWRP and used my backup but from no reason the phone died during the backup and when I powered it on it vibrates but it doesnt show any image at all and takes a bit longer to vibrate.
The error on SP Flash Tool is STATUS_BROM_CMD_FAIL (0xC0060005). What do I do? When I try to flash it turns the LED on but then it turns off and turns on again but gives this error. If also there is a way to boot to bootloader directly tell me PLSS. Its Hard Bricked.

T3ll3S said:
Hi again, does anyone of you know how to fix this error, im very scared that my phone wont show any screen again.
This is what happened: I tried to install Android 10 GSI and bootlooped so I went to TWRP and used my backup but from no reason the phone died during the backup and when I powered it on it vibrates but it doesnt show any image at all and takes a bit longer to vibrate.
The error on SP Flash Tool is STATUS_BROM_CMD_FAIL (0xC0060005). What do I do? When I try to flash it turns the LED on but then it turns off and turns on again but gives this error. If also there is a way to boot to bootloader directly tell me PLSS. Its Hard Bricked.
Click to expand...
Click to collapse
You did not flash correctly. The device isn't hard bricked, you have to turn it off (take it apart and disconnect the battery then reconnect it but don't turn on, keep the back cover off because you will surely need to repeat this many times), go to Options, Download and enable "Storage checksum" and "USB checksum", and then start flashing and then plug in the phone while SPFT is trying to flash. When SPFT starts flashing do not touch it, when it flashes the phone will reboot. You also need a proper stock ROM.
You can also just literally use the Mobile Upgrade S Gotu2 tool from Alcatel: https://mega.nz/file/DjpzTRDB#vC3SrO5hQr1Nzn32lWxVGLhmclfSpPF6CsIWHRaTsP8 and restore the stock ROM that way.

I cant with SP Flash Tool It gives the same error and with the other softwate it tels that i am at the latest version

T3ll3S said:
I cant with SP Flash Tool It gives the same error and with the other softwate it tels that i am at the latest version
Click to expand...
Click to collapse
You can, you are just doing it wrong. Check the checksum options I mentioned and retry.

Do i need to touch in any button before i flash? The other software why it tells that im on the newest version? What is the error about? I cant boot onto nothing it doesnt even show a screen but i will try harder

T3ll3S said:
Do i need to touch in any button before i flash? The other software why it tells that im on the newest version? What is the error about? I cant boot onto nothing it doesnt even show a screen but i will try harder
Click to expand...
Click to collapse
Yes, I clearly told you:
In SP Flash Tool: Go to Options, Download and enable "Storage checksum" and "USB checksum".
THEN flash.

I enabled but still no results. The button i was talking about is on the phone do i need to touch the phone or just put the usb?

fail installing Magisk

I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me

IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:

marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!

marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)

bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:

marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??

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

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

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

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

Is it support Android 8.1.0 Firmware?

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

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

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

...

It is working fine checked it

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

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

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

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

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

just format data to decrypt
link please

bro it says download file does not exist on google drive

download link ??

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

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

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

Works backups AND restore opción?

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

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

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

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

Thank you for sharing

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

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

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

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

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