Related
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
some news...
some news... i have successfuly install TWRP and maked a backup of system/data/boot if anyone want to play with backup or try to flash it i can upload it (it's a 5gb folder, tell me wich file hosting you want)
i have try after backup to flash the CM rom and some Flyme but i have always the same error: "could not find 'meta-inf/com/google/android/update-binary' in the zip file"
Any suggestion?
ps: if anyone has a TWRP backup of his pro 5 i can try to restore on my...
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Toroman said:
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Click to expand...
Click to collapse
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
mobilezonerm said:
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
Click to expand...
Click to collapse
In this thread there is a link:
http :// forum.xda-developers. com/meizu-pro-5/development/rom-cyanogenmod12-1-temasek-unofficial-t3358744
http :// xep.8800.org/ pro5/
But also on the Canonical site:
https ://wiki.ubuntu. com/Touch/ Devices
(Sorry for the spaces the policy doesn't allow me to post urls yet.)
I somehow thought that we can use official Flyme download from the Meizu website and the official Ubuntu turbo image without the need of installing TWRP or anything - and flash both via USB.
Functionality with TWRP would be a plus.
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Pleytos said:
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Click to expand...
Click to collapse
Well the power + up gives (a kind of) recovery that shows a screen with the Ubuntu logo in the center - nothing else. I believe the android version has a different recovery?
Ah I never saw that screen. Yes Android/Flyme has a different screen: like this
You can try to to use the Ubuntu recovery to flash a Flyme Rom. I did it with TWRP, but never tried it with the Ubuntu recovery.
The Flyme Rom replaces the recovery and boots with both TWRP and the Flyme recovery, maybe even with a Ubuntu recovery (I can't image it to be that different.).
Edit:
You might want to back up your current recovery. I just flashed the recovery from Canonicals website, and its just the English/Chinese Flyme one.
just a moment... thank's Pleytos, but we need the TWRP backup folder... on yours link there are the CM rom and on the Canonica site there are only the update.zip....
Keep in mind, also the partitons are different on Pro 5 Ubuntu, for this the best is to have the entire backup of an android phone, both CM rom and Update.zip are not flashable by TWRP (i have try)
and Toroman the recovery that you see is the original recovery, if you flash the recovery on Canonical website you have the screen posted by Pleytos BUT with this recovery you obtain only the unlock of ADB in recovery and, as you can read from the screenshoot to make an update you have to put a "update.zip" on root directory of the phone that, unfortunally in ubuntu edition, is read-only file system... i have just unlock it from linux terminal with a "remount,rw" but if you try to copy update.zip (many versions) to root fonder there aren't space enough...
I've make lot of try in this day and i have find two possible solutions:
- flash a rom with MultiUpgrade 4.8.5 (official software used by Meizu, that not start because some token is missing)
as reported in a big russian forum
- make a total erase of internal memory and rewrite it with a image from android Pro 5 phone (TWRP Backup)
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
All done... guide in details:
- on windows install driver: Samsung_USB_Drivers_for_Mobile_Phones_1.5.9.0
- on linux: run from terminal "$ sudo add-apt-repository ppa:ubuntu-sdk-team/ppa" and "$ sudo apt-get install phablet-tools"
- download from here (http://people.canonical.com/~plars/touch/recovery-turbo.img) the recovery image with unlocked ADB
- turn off the phone and turn on with volume down pressed to enter in fastboot mode
- in windows go to the folder where you have fastboot / in linux open the terminal and give "sudo -s"
- make a flash of recovery (fastboot flash recovery recovery-turbo.img)
- now download the TWRP recovery (i've used the 3.0.0 on this forum) and from terminal flash it (fastboot flash recovery "nomerecovery")
- now you have to copy first a CM rom on the phone or sd, before flash the CM rom erase completely the system partition, flash it whit TWRP and only after you are able to flash Flyme rom
keep in mind to make a full backup by TWRP and save it on external archive before operate. (it's less complicate for future restore and help you if something goes wrong)
if someone need the backup of Ubuntu for his phone, ask me...
Ubuntu Dump
mobilezonerm said:
if someone need the backup of Ubuntu for his phone, ask me...
Click to expand...
Click to collapse
Hello, can you provide me full Ubuntu dump? Im very interesting to install native Ubuntu touch on Meizu Pro 5. Share the link, for example, on Mega or Google Drive
Need you help
mobilezonerm said:
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
Click to expand...
Click to collapse
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
mobilezonerm said:
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
Click to expand...
Click to collapse
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
tamyou2020 said:
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
Click to expand...
Click to collapse
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Hi , Am running Ubuntu over windows ( virtual box ) we can go with team viewer , or if you want i can install Ubuntu in separate machine , Please let me know how we can communicate
Pleytos said:
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Click to expand...
Click to collapse
Hi,
I've been away for some time, and I can see some nice progress in making Android work on the Ubuntu edition.
I might be repeating myself but it would be ideal if we (who own the Ubuntu edition) can go back and forth seamlessly. Unfortunately my flashing skills are buried in the ancient time of the HTC HD2 so I need some assistance (as probably more of us do). Here are some questions, I appreciate the effort and the help (assume I'm using Ubuntu on the desktop) (if something is easier in windows - please note). This would be a full circle:
1 Is it possible and how to make a COMPLETE backup of the Ubuntu edition phone (including the recovery and everything) to be able to get back to the factory condition (and using what tools/steps). I think I have read somewhere that OTA updates does not work with custom recovery or something similar.
2 after making the backup from question 1 - assume flashing official flyme to make it like a factory android device. (orig.recovery, OTA and so)
3 flash ubuntu back using backup provided with one.
I guess the ubuntu edition has the bootloader unlocked factory default.
Info on flashing CM or similar can than be like flashing it on original android - assuming (2) is working
As already said, just a remainder - Ubuntu recovery screen that came with the original phone is just ubuntu logo on the center on the screen - I don't know if it is important for any feature (OTA or something)
Best regards!
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Toroman said:
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Click to expand...
Click to collapse
Actually this is most interesting! I would love to buy this phone, ubuntu edition. But since it would be my primary device and ubuntu touch not quite there yet, I'm not. That page about dual boot seems outdated though. And it is about nexus devices
Being able to have dual boot with android or even as someone said above have a back up and every 2 months restore ubuntu and check the progress would be great.
Hey there,
I need help, hope you have some for me . I want to use the 6.0.1. OpenKirin OmniROM on my phone and struggle even figuring out a way to get there.
I just bought a used ALE-L21 DualSIM phone with the B602 Build and EMUI 4.0.3 installed. The device is not rooted, nor has its bootloader been unlocked. The EMUI update service does not offer me any patches.
Could someone please line out to me which steps I have to take in order to root my ALE-L21 and get this ROM to work?
Disclaimer: No, I'm not just a lazy moron who does not want to read other topics on this forum - I'm a mere user with less-than-average knowledge of Android development or stuff like that. And I just can't make complete sense of the various posts I've found, since English is not my mother tongue and there seems to be a whole bunch of ways to do certain things with a phone. Well, since obviously I don't want to brick my new phone, I'm not too sure how to best puzzle together the pieces this Forum offers me. It would be insanely helpful if I could get a list that reads out something like:
1. Action - Source (for needed files, e.g.) - Result, on to step 2
2. Action - Source (for needed files, e.g.) - Result, on to step 3
3. ... and so on...
Okay, just so you see that I'm not entirely lost, I'm gonna show you the picture which is currently in my mind.
From what I understand so far, there's the following steps to get there (please rectify or rearrange steps as far as needed):
1. Update the device to Vanilla EMUI 4.1, Build B895 or B896 (I am currently downloading the B896 Build from this forum - which one is recommended? My phone is DualSIM)
2. Unlock Bootloader (What's the best way to do it? Huawei CS? Heard it's not even sure you get an answer. DCUnlocker? Wants money... Please help me clarify)
3. get TWRP 3.1.1.0 (I already have the IMG file, how do I get it to run on my phone?)
4. Root the device (I'd like to go with MAGISK, does anyone have a link for a MAGISK build confirmedly working on ALE-L21?)
5. Do some magic with TWRP (Which steps exactly?)
6. Flash the ROM Zip file via TWRP
7. Flash Gapps via TWRP
Is that about it?
As I said, please feel free to add to/adjust my list!
Thanks in advance,
Pako
If you haven't already install minimal adb tools on computer (windows) found here :
http://bit.ly/2jxX4ya
You then need to unlock bootloader using minimal adb tools and the unlock code
Unlock Code:
http://bit.ly/2z9EFhV
Unlock Bootloader Method in this thread here:
http://bit.ly/2oIASBs
After you are done unlocking the bootloader
Install twrp find that here :
http://bit.ly/2ok9BTi
There was a tool that was here somewhere to install twrp but I will link to my copy here
http://bit.ly/2ATBgRP
What you do is put the twrp image file in data folder
then change the name of the twrp file to TWRP_3.1.1-0_ALICE.img or
edit the install.bat file line data\fastboot.exe flash recovery data\TWRP_3.1.1-0_ALICE.img to the name of your twrp file
Once twrp is installed then you can pick which rom you want
The 6.0 roms arent going to be supported anymore so i suggest going for 7.0 ROM
I'm on AOSPA which is the cleanest and has good battery life
To install 7.0 rom you need B895 or B896 found here on the first post:
http://bit.ly/2jypIij
this is installed through twrp (which is accessed when Phone is off by holding volume up + power then let go once it vibrates or connect the phone to the computer and then type adb devices then adb reboot recovery in minimal adb tool)
once in twrp you need to install the B895.zip or B896.zip file then reboot your phone will boot into emui
you need to install twrp again as B895 or B896 wipes it
After installing twrp you can then install any custom rom of your choice
let the rom boot and then go back into twrp and install gapps found here: "http://bit.ly/1JOWjUqi recommend nano or even pico pick am64 7.1
I would also recommend installing Galactic forced deepsleep http://bit.ly/2ANVdbS
Hey there,
thank you very, very much for your comprehensive walkthrough! (Almost*) everything worked to perfection and I am now a happy user of OpenKirin's OmniROM 6.0.3. mod! Yeah, no 7.x... but I'd prefer to wait with that until the "issues" section of AOSPA does not contain any relevant things anymore. OmniROM seems to have no issues anymore, so I'm content with my choice. I will now follow your last advice and flash the Deep Sleep Mod to improve my device's battery life, and then I'm just happy.
* = The only issue I encountered was when having flashed TWRP, the device booted to the crappy EMUI eRecovery instead of TWRP. I solved this issue using this advice from another thread.
So, once again, thank you! All you xdaDevs, keep on developing ways to improve people's lives with their android devices!
Cheers,
Pako
Since for quiet some time I've tried several methods described here in the forums and elsewhere, I though it is worthwhile to log the one that really worked:
First of all you need to follow the installation instructions.
Second, I'd recommend to refrain from all the Windows-based tools or most of the Android apps (for the exception used here see below). You should also be aware that it is not necessary to flash a new KDZ as several people are suggesting here in the forums, nor is it necessary to update the firmware on your stock device upfront.
Third, it's always a good idea to backup the device (in case something goes wrong) and foremost your data (to be reused on the updated device, since the update will destroy all your data).
You'll need to perform the following steps:
A fix for the radio/modem can be obtained on XDA. I used version 21C which is the latest version that works from Android 5.X upwards.
Install/flash TWRP using Autorec from @bender_007. I recommend to follow this instruction. All other variants/suggestions did not work for me.
Copy the necessary files to your device using adb (radio fix, latest LineageOS, GApps nano in my case)
First install RADIO_D855_21C... then follow the steps starting at "Installing LineageOS from recovery" in the official installation instructions.
Hope this helps -mgw
Not even a month ago my Nexus 6P went to bootloop. After a few days of failed attempts and all hopes lost I finally managed to install the fix that deactivates the A-57.
To be able to do all this I downloaded and installed the factory image from the Google site, then launched the command "Flash-All.bat" followed by the installation via ADB of the fix and the recovery TWRP.
Before all this mess I used the LineageOS ROM, while now I'm on official firmware, which among other things I can't even update by installing the latest security patches because the modified boot image is overwritten with the one that requires the use of the whole SoC, A-57 included, with the inevitable return of the bootloop.
I was wondering if there is any modified version of the LineageOS ROM that allows unlucky Nexus 6P users like me to be able to easily use and update the aforementioned ROM, without the risk of finding the phone in bootloop at every start.
I also wondered if after installing the XDA fix that disables the A-57 you can update the device with the latest patches, since maybe I may also have something wrong too.
My question is if a 6P with the BSD fix installed is condemned to remain "as is" forever or if can still receive updates.
You dont have to bother with the terrible stock os. Just use further lineage os.
Howto in short:
1. flash twrp 4 cores from here: https://basketbuild.com/devs/osm0sis/osmods
2. flash latest lineageos from official lineage download site with twrp
3. after flashing now every single time a linegage os image, you have to run N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip from the link above
Thats all. Just use the N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip to configure every single time your lineageos to use 4 instead of 8 cores.
More detailed howto: https://forum.xda-developers.com/nexus-6p/general/bootloop-death-blod-workaround-zip-t3819515
Since Official TWRP as of 2019-06-19 still does not support decryption of PIE /data partition, I decided, on behalf of developer of Unofficial TWRP 4pda version MOD EDIT: LINK REMOVED d4e8ede8f1f2 and with his approval, to present his project here.
The version being presented is a branch of Team's Win Recovery Project 3.x, based on Android One Pie kernel, and is licensed under the GPL (version 2) license agreement.
Neither developer nor OP creator (translator from Russian) are responsible for any harm to electronic devices or financial losses inflicted with improper usage of this software.
Proceed on your own risk.
Please get acquainted with Team Win Recovery terms and usage.
Sources:
OMNI TWRP repository..
TWRP Device configuration for Xiaomi Mi A2.
Developer forum (4pda, in Russian):
MOD EDIT: LINK REMOVED
Downloads (Google Drive):
TWRP 3.3.1-5 jasmine_sprout unofficial (2019-06-29)
Note 1: TWRP Image cannot be uploaded to local repository as a single archive due to xda limitations on file size, thus dev's Google Disk is used;
Note 2: This thread is somehow not thanked and thus is periodically drowning below other less-functional TWRP clones; do not hesitate to promote the product after successful usage, - it is for free.
Features :
1. Pie-based kernel with full decryption support for stock Androids 9 and 10:
- in case Mi A2 is not locked by PIN, password or graphic key, decryption and mounting of /data partition is made automatically,
- otherwise appropriate unlocking sequence is to be made by user in TWRP loaded into phone.
2. Slot (A/B) switching works.
3. MTP / ADB sideload and USB OTG read/write work.
4. All variants of MiA2 screen panels are correctly supported (no "black screen" bug).
5. In current version /system partition is mounted as "/system" (not as "/system_root") to comply with script of OpenGApps installer.
Usage Notes:
- Mi A2 must be fully unlocked to use TWRP; "Usb-debugging" must be switched on in phone; see Guides in this forum;
- ADB / fastboot must be properly installed and approved in phone; (see Platform tools, - r29.0.1 as of 2019-06-08, - and Guides in this forum);
- recommended booting sequence
Code:
adb devices -l
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.3.x-x-jasmine_sprout-unofficial.img
1st command lists attached devices supporting ADB interface, and is used to check that phone is connected properly and that no other devices are connected. simultaneously, - read result in CMD. Most of ADB commands need "USB debugging" in ON state. If issued for the 1st time from this PC, will rise a prompt on phone, - need to approve.
2nd command reboots phone into bootloader, - wait till phone shows fastboot screen.
3rd command lists attached devices supporting fastboot interface., - read result in CMD and ensure it shows same signature as was displayed after 1st command in ADB.
4th command boots TWRP into phone.
Example 1 (pull camera photos directory):
1. boot into TWRP (do not forget to unlock TWRP and thus decrypt /data if phone is secured by PID or other method);
2. type "adb pull -a /sdcard/DCIM/" in CMD shell in platform-tools dir of PC - to save all photos to current dir.
Example 2 (pull current /boot image to PC ):
1. Boot into TWRP;
2. To learn which slot is active, see "Reboot" page in TWRP
(another way is to switch phone to bootloader mode and type "fastboot getvar current-slot" in CMD in platform-tools folder in PC).
3. in CMD shell in platform-tools dir of PC type:
- if active slot is A: "adb pull /dev/block/mmcblk0p62 ./boot_a.img";
- if active slot is B: "adb pull /dev/block/mmcblk0p63 ./boot_b.img";
Example 3 How to re-flash /persist partition using TWRP and ADB commands' script
How to install TWRP as permanent one:
As stock Mi A2 ROM comply to GSI A/B slots partitioning scheme, there is no /recovery partition, and thus no place for TWRP to be successfully flashed via fastboot (or MiFlash).
If you use "fastboot flash twrp-3.3.x-x-jasmine_sprout-unofficial.img" command, you will just substitute content of /boot_X partition with TWRP in current slot X, thus spoiling ROM, which is obviously not what you've intended.
If you want to embed TWRP into phone permanently instead of stock recovery:
- boot into TWRP, and then
- install "twrp-installer-3.3.1-5-jasmine_sprout-unofficial.zip" via booted TWRP;
- this installation will patch /boot image (similar to how MagiskManager patches /boot image to embed Magisk).
Custom ROMs usually have a custom recovery (mostly various TWRP builds) embedded into boot image from scratch, you may opt to substitute such with this one.
Update 2019.06.24:
Code of PBRP by @Manish4586, has been updated today to sources of TWRP fixes by MOD EDIT: DOWNLOAD LINK REMOVED
Update 2019.09.12:
I beg everybody (and 1st of all d4e8ede8f1f2) pardon for postponing update of this thread, since improved version 3.3.1-5 was available as of 2019.06.29.
Changes in 3.3.1-5:
1. new kernel v. 4.4.184 based on official MiA2 Pie kernel;
2. Merging with official TWRP code changes:
2.1. Fix compilation in android-9.0 repos.
2.2. Properly localized string instead of using English.
2.3. ext4crypt: support synthetic keys v3 on May update
Notes from d4e8ede8f1f2 on decryption in 3.3.1-5:
This version supports decryption of data partition encrypted in FBE (File-Based Encryption, introduced since Android 7) scheme only, as being used by stock MiA2 ROMs.
This {limitation} became deficiency since some custom ROMs, e.g. AEX, implemented older and stiffer FDE (Full Disk Encryption, introduced in Android 5) scheme.
One can check which encryption scheme is implemented in current ROM, for example, issuing ADB command: "adb shell getprop ro.crypto.type". Replied "file" means FBE, while "block" means FDE.
hii!
im at 3.2.3.0 with RR pie atm, may i just use the installer.zip after flashing my rom?
then setting the other slot and reboot recovery to there, installing opengapps and magisk, yeah?
i mean, without flashing the .img
ty!
Gesendet von meinem MI A2 mit Tapatalk
worked perfect, ty!!!
Gesendet von meinem Mi A2 mit Tapatalk
Is it possible to use this version of TWRP to encrypt my phone? Currently, I am using havoc OS. If I try to encrypt from system settings in the normal way it does not work (simply reboots with no change).
I was thinking perhaps I could flash stock OS, encrypt phone from system settings, flash your custom TWRP and then use it to flash custom OS. Hopefully that would maintain encryption and I would not have to wipe system and data and unencrypt?
As far as I know. no custom ROMs support encryption yet. Although your question in "Havoc OS" thread was not answered, you could use search in this thread, which would show you latest answer from OP on this issue: https://forum.xda-developers.com/showpost.php?p=79826439&postcount=1347
Bonjour,
On wich partition do I install Recovery ?
I just want to flash PBR and magisk root on stock rom.
With stock ROM you cannot {flawlessly} flash TWRP, just boot into it via fastboot and make backups, pull system images (for example, pull current stock boot image to PC for patching it in Magisk in phone and thus getting root), etc., etc.
To install Magisk and get permanent root on stock you do not need TWRP at all, if you can fetch stock boot image downloading it from here or taking from stock ROM fastboot-image. Please carefully read Guides here on how to get root,
As for custom ROMs, these usually already have a TWRP in their boot images, but anyway go to the thread dedicated to selected custom ROM and carefully read OP instructions.
See IMPORTANT NOTICE added to OP
Aerobatic said:
With stock ROM you cannot {flawlessly} install TWRP, just boot into it via fastboot and make backups, pull system images (for example, pull current stock boot image to BB for patching it in Magisk in phone and thus getting root), etc., etc.
To install Magisk and get permanent root on stock you do not need TWRP at all, if you can fetch stock boot image downloading it from here or taking from stock ROM fastboot-image. Please carefully read Guides here on how to get root,
As for custom ROMs, these usually already have a TWRP in their boot images, but anyway go to the thread dedicated to selected custom ROM and carefully read OP instructions.
Click to expand...
Click to collapse
Merci beaucoup for your answer.
If I have good understood ,Ishould not install custom recovery but I Can install magisk via adb sideload ?
I try Havoc rom but I had a lot of bugs ...
bancelin said:
... Can install magisk via adb sideload ?I try Havoc rom but I had a lot of bugs ...
Click to expand...
Click to collapse
I've already written to you that TWRP is not needed to get root, and recommended to read Guides, Why should I (or anybody else) type here content of already published Guides?
Read this: https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
Find (please be informed "Search this forum" in the upper right corner of the window really works in XDA) stock and/or patched boot image for the version of stock ROM you want to root. Images for 10.0.13.0 are here: https://forum.xda-developers.com/showpost.php?p=80065352&postcount=7, stock boot image for patching with Magisk can also be taken (as I have already written) from corresponding stock fastboot image: https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.
Nobody will do your homework for you.
Updated header with info on and links to twrp-3.3.1-5-jasmine_sprout-unofficial
Aerobatic said:
Update 2019.09.12:
[...]
1. new kernel v. 4.4.184 based on official MiA2 Pie kernel;
2. Merging with official TWRP code changes:
2.1. Fix compilation in android-9.0 repos.
2.2. Properly localise string instead of using English.
2.3. ext4crypt: support synthetic keys v3 on May update
Notes from d4e8ede8f1f2 on decryption in 3.3.1-5:This version supports decryption of data partition encrypted in FBE (File-Based Encryption, introduced since Android 7) scheme only, as being used by stock MiA2 ROMs.
This {limitation} became deficiency since some custom ROMs, e.g. AEX, implemented older and stiffer FDE (Full Disk Encryption, introduced in Android 5) scheme.
One can check which encryption scheme is implemented in current ROM, for example, issuing ADB command: "adb shell getprop ro.crypto.type". Replied "file" means FBE, while "block" means FDE.
Click to expand...
Click to collapse
I am running AEX (v6.7) and my encryption scheme is "FDE". So I needed to run v4?
But neither v4 nor v5 works with this ROM.
MMN said:
.... So I needed to run v4?...(
Click to expand...
Click to collapse
No, v5 is better than v4, except it still does not support legacy FBE encryption.
I meant that the developer of This TWRP just wrote comments on legacy FBE encryption while releasing 3.3.1-5, probably being asked by someone about this issue. As he have not released newer version in 4 months, probably nobody else asked him to. His 4pda-mail is in the 1st paragraph of OP, so you can try to ask him to help.
Aerobatic said:
No, v5 is better than v4, except it still does not support legacy FBE encryption.
I meant that the developer of This TWRP just wrote comments on legacy FBE encryption while releasing 3.3.1-5, probably being asked by someone about this issue. As he have not released newer version in 4 months, probably nobody else asked him to. His 4pda-mail is in the 1st paragraph of OP, so you can try to ask him to help.
Click to expand...
Click to collapse
Thanks for the answer!
But maybe a demand is not necessary. Which ROM do you use? Stock or Custom?
Maybe my installation steps are wrong:
I currently installed AEX (Pie) with official TWRP installer (zip). After slot change, I installed GApps and Magisk.
If I encrypt my system (settings - security - encryption), then I can not access /data with official TWRP (because it can not decrypted).
If I flash your v4/v5-TWRP via "fastboot flash boot trwp-v4|v5.img" a decryption does not work also.
If my doing is correct, I will contact the developer at pda.
MMN said:
...Which ROM do you use? Stock or Custom? ... If my doing is correct, I will contact the developer at pda.
Click to expand...
Click to collapse
I'm on rooted stock.
Yes, you can ask d4e8ede8f1f2. But IMHO, as it is obviously the problem of AEX (I mean, - using legacy encryption, - as usual problem of most of other custom ROMs is - not using any encryption at all), - you'd better search for solution in AEX-dedicated theads.
Aerobatic said:
Since Official TWRP as of 2019-06-19 still does not support decryption of PIE /data partition, I decided, on behalf of developer of Unofficcial TWRP 4pda version d4e8ede8f1f2 and with his approval, to present his project here.
Click to expand...
Click to collapse
Hello Aerobatic, I'm interested to find a way to backup my personal data, personal apps and their settings, etc. not so interested in Android and it's setting as much, then later be able to restore the backup onto the phone after a fresh install. Would I be able to use this version of TWRP to do that on Android Pie (Android One) for my Mi A2?
I've not found a solution yet to do this and it gets rather tedious to have to enter all the apps, settings, etc. from scratch each time.
nadia p. said:
Hello Aerobatic, I'm interested to find a way to backup my personal data, personal apps and their settings, etc. not so interested in Android and it's setting as much, then later be able to restore the backup onto the phone after a fresh install. Would I be able to use this version of TWRP to do that on Android Pie (Android One) for my Mi A2?
Click to expand...
Click to collapse
Have you tried to backup /data to attached USB-OTG "drive"?
Aerobatic said:
Have you tried to backup /data to attached USB-OTG "drive"?
Click to expand...
Click to collapse
I never knew what a "USB-OTG" drive was until I looked it up. In the past I had a USB-micro to USB-B cable that I used on my previous Google/Nexus phone but I don't own one of these cables (USB-C to USB-B) to connect to Mi A2.
I was trying to see if there was a way to do this over wi-fi or bluetooth directly to a computer. Or somehow through ADB push/pull commands. But I've not found a good solution yet. I've just transferring the data manually from the phone to the computer for now. I'll look into purchasing one of the cables and trying to backup that way using your version of TWRP.
nadia p. said:
..I was trying to see if there was a way to do this over wi-fi or bluetooth directly to a computer. Or somehow through ADB push/pull commands...
Click to expand...
Click to collapse
After booting into TWRP you can try to "ADB root" and then pull. Or use 3rd part apps like MyPhoneExplorer.
Worked like a charm!
onimorza said:
Worked like a charm!
Click to expand...
Click to collapse
He-he, and still showing zero rating for the thread, and it will sink again below partially operative clones.... Do I need to attach something to OP?