Database Users

[SOLVED][REQ] Stock RAMDISK or BOOT image for A3(2016) - SM-A310F

Hello,
I am just new with Samsung smartphones, previously I was on some other devices such Nexus which are easier to mod.
I would like to tweak the kernel( I already got the sources) to add few things but I need for that eventually the ramdisk and the kernel image to make a boot image.
I wanted to download the latest firmware, hoping a default boot image was integrated in it and that I could unpack but I got issue and connection loss so I can't even take a look at it.
I think I will be able to get the boot image with the dd command but to do so I need to be in a mod recovery(such twrp) and currently I can't.
Thx u

Firstly you've created a voting thread. If this is a standard question I suggest in future you leave the options at default.
Why can't you use TWRP?
My build also supports raw image backup of the boot partition.

Sorry about creating wrong thread type
I have extended this feature to include BOOT
Click to expand...
Click to collapse
Woot Yeah I didn't know about that!
So I can just get the current boot image, unpack it, replace with my kernel image, repack and done.
And then flash the boot image throw a zip install or your extended function.
Btw, I am was looking over the net but couldn't find an exact answer to this extra Q, is there any fastboot mode ? So I can just boot in a custom kernel image before flashing it.

Yep, just backup the boot partition using twrp.
Locate the boot image backup in the twrp backup folder.
Unpack it, make your mods, rename it boot.img, copy it to internal or external storage and flash it with TWRP using the INSTALL button.
Samsung devices dont have a fastboot mode.

@ashyx answered my questions, thx to him!

>Samsung devices dont have a fastboot mode.
My latest Samsung Tablet has a fastboot mode but it was manufactured around the end of 2012 ... So it is not quite recent

I've never known a Samsung device to use FASTBOOT, so that's news to me.
Samsung uses its own proprietary ODIN mode.
Which device is this?

Ahhah you gonna say I am half of a lier.
It was my nexus 10. Built by Samsung and running the 5250 exynos chip

[HOWTO] Flash TWRP and Flash CM+GApps [Meizu M2 Note]

Hi to everybody
I'm doing this thread because I've seen that there's a lot of confussion about how to install all this things properly, and I think that concentrating the wide-spread information could help you to get rid of this. First of all I have to thanks @aaawqw and @Moyster for their great efforts.
This is going to be a recopilatory of several sources and personal tips to help you to do this the easiest way. I'm not responsible of bricked phones nor your personal problems.
Please, read the full tutorial before doing anything, to avoid bricks and those things.
PREPARE THE RECIPE
Download these files:
- Unlocking bootloader tool: HERE
- TWRP image from Moyster (creator of LOS14 for our device): here
- If you want to install a modified version of FlymeOS, use this one from Romul35 from 4PDA: here. Original post
- Last LineageOS 14 build: from this thread. PLEASE DON'T FORGET TO THANK THE DEVELOPERS
- GApps: here I recommend the nano option. Choose ARM64 and Android version 6.0.
Put those three last files into your internal memory. If you've got an microSD card, I recommend you to put them into it (it's safer and easier).
UNLOCKING THE BOOTLOADER
To unlock the bootloader go to:
- Kevin.MX @aaawqw) post: here
Finally we have a guide to unlock the bootloader of Meizu m2 note. We need Mediatek SP Flash Tool, MTK phone drivers and the images/bin files for unlocking. No modaco superboot, no fake tutorials any more
Now here's the guide:
1. Download the files I provide
Then unzip it. You'll get a folder with FlashTool, Phone drivers and unlock images.
2.Install drivers for Mediatek platform.
3.Flash the temp-unlock-secro.img via Flashtool. (secro row)
4.Flash secro.img, lk.bin, preloader_meizu6753_65c_l1.bin via Flashtool. (secro, lk and preloader rows respectively)
5.Disconnect USB data cable and power on the phone. If you see the "=>Normal boot" sign(it's quite small.......) in the left bottom cornor of the screen, then the unlock is done. You can now flash things in whatever way you like. The guide is over~~~
The full tutorial is here
The unlock tool is here
Thank you for testing&trying!
If you've seen this spoiler and didn't thank Kevin, please go to here and thank him. This motivates him and gives him the recognisement he deserves.
- Robot Hijau 97 Youtube video: here It isn't in English, but may help if you find any problem or get lost during the unlocking. Leave him a like if it helped you.
This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights )
THIS METHOD DOES WORK FOR M571H MODEL. DON'T WORRY, THE ONLY ONE THAT GIVES SOME ISSUES IS THE M571C.
The great user @aaawqw states "And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions"
Tips to unlock the bootloader easily:
- If you're going to do it from a Windows 10 or 8 pc, have in mind that to install unsigned drivers you'll have to unlock the feature in your pc. A guide to do this: here
- Select the images to flash and hit the Download button before connecting your Meizu (pressing Vol Down button). This will help you if it turns on and off and makes the flashing impossible.
- Download the guide or see the video to correctly follow all the steps. You don't want to lose your phone, don't you? Don't try to mix guides, because you may skip a step and brick your phone. The video and Kevin.MX guide are the same procedure, they both are safe.
INSTALLING TWRP
Once done this part, we'll proceed with the installation of TWRP recovery image. There are two ways, choose the easier to you:
- Flash TWRP from SP Flashtool (original idea from @widagdag. The post: here)
+Turn off your device
+ By using your pc or laptop, extract the TWRP zip for meizu m2 note, there's a file "recovery.img"
+ You can flash it via SP flash tool (clicking the recovery, then select the file)... then click Download, wait until finished!! (Check symbol)
+ You can reboot ur device now, unlocked bootloader and installed twrp!
*The profit is u didn't need to root first and install any flash tool such as Rash, FlashFire, Flashify, etc. saving you some time
Click to expand...
Click to collapse
- Flash the recovery image from Flyme:
+ Get root access (if you do, skip this step). You can get it downloading Kingroot: here. Just install this apk and follow the steps
+ Unzip TWRP zip into a known folder
+ Download Flashify from the Playstore
+ Grant superuser access
+ (Optional) make a backup of your current recovery going to backup tab
+ Tap Recovery Image
+ Choose a file
+ Find TWRP img that you unzipped before and flash it
Click to expand...
Click to collapse
INSTALLING CM AND GAPPS
We're close to the end of this post. The final step: installing your desired ROM and GApps. I will flash CM from the thread whose link is at the download section.
I hope you've put it into your memory (internal/external) as we said
Ok so:
- Turn off your phone
- Go into the TWRP recovery (Vol up+power)
- (Optional but recommended) Make a backup of Flyme, just in case you don't like the new ROM and would like to go back to Flyme. If it takes up too much memory, move it to your pc after making the backup.
- Go to Wipe menu
- Go to advanced wipe
- Select these:
+ System
+ Cache
+ Dalvik Cache
+ Data
- Swipe to do the wipe
- Go to install.
- Select your zip image (in my case the cm13 I downloaded).
- Install also the GApps zip file you downloaded
- Restart to System, and check what you've done.
Some final tips:
- Make the backup, seriously, it takes 10 min and you'll have a Flyme backup if you don't like CM.
- If you want to transfer all your apps and their data from Flyme to your new ROM, use Titanium Backup.
- If you want to install Xposed Framework, it's the same procedure: enter into TWRP, tap install, select the zip and swipe.
- This won't delete your images or videos, but I would recommend to transfer them to a microSD card or your PC.
- Yes, you need to do all this to install a custom ROM. Yes, even unlocking the bootloader. Don't try to skip a step if you aren't sure about what you're doing.
I think that's all, I'll update this post if I lost anything.
I hope this helped you to move into CM world. If you have any doubt don't hesitate to ask.
I know this seems exhausting, but trust me, it worths it. Welcome to the custom ROMs world in your Meizu M2 Note. Let the magic begin.
ADDITIONAL GUIDES
RELOCKING THE BOOTLOADER
If you want to relock the bootloader just follow this simple steps:
Flash the original recovery image from Flashtool of from Flashify (the steps are the same as installing TWRP). You can find this image here
From there, install an update.zip (download them from the official flyme web: here and put it into the storage )
Now you have flyme again with a locked bootloader.
INSTALLING FLYME WITH TWRP
It's very important that you don't install an update.zip from the original Flyme page, because you will cause a bootloop. To get the flyme updates, you can follow one of these two methods:
METHOD 1: 4PDA
-Download the modified zips from 4PDA: here]. Translate it to English. It's on custom firmware>Flyme
-Flash them from TWRP
METHOD 2: DO IT YOURSELF
-Download the update.zip file from the Flyme page
-Open it and remove the preloader- files
-Flash it from TWRP. It will give you an error: IGNORE IT.
Reboot and done, you've got Flyme and TWRP.
UNBRICK A PAPERWEIGHT
BIG THANKS TO @numpea FOR THIS:
This just a firmware that has all the partitions and can be used to unbrick to device using SPFlashtool
Here is the link:
FIRMWARE
- Flash temp_unlock_secro.img with sp flashtool like you do when unlocking the bootloader.
- When done, disconnect the device and add the firmware to sp flashtool. You need to select "format all+download", click on "Download" and connect the device. The flashing process will start. After it finishes, the device will start again.
You wil notice that you lost your imei number you can add it back by:
Using MTK Engineering Mode (does not requires root)
Open engineering mode » Click on Engineer Mode (MTK) » Swipe left to Connectivity » click on CDS Information » Radio Information
Click on phone 1 if you want to change your sim 1 or choose Phone 2 to change sim 2 IMEI, follow this guide:
For Phone 1: “AT+ EGMR=1,7,”YOUR NEW IMEI NO” (make sure you add a space in between AT+ & EGMR)
For Phone 2: “AT+ EGMR=1,10,”YOUR NEW IMEI NO” (make sure you add a space in between AT+ & EGMR)
Using Chamelephon (requires root, but much more easier)
Just copy the IMEIS from the phone's box and put them into the app.
hope this is helpful
Click to expand...
Click to collapse
I'll keep updating the info!

Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !

Moyster said:
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Click to expand...
Click to collapse
Moyster xDD :laugh::laugh: Thanks to you, without you this wouldn't have been possible

Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.

Xtian Rey said:
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Click to expand...
Click to collapse
Very true, thanks a lot. I introduced the platform and the Android version of GApps

Thanks nice guide... Very useful for everyone who want play and modified the M2 note.

"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.

Mr0oHo0 said:
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Click to expand...
Click to collapse
I include this on the guide. I read it bricked the phone in several cases, but I'm glad yours didn't.

Thanks for your guideline , it helps a lot !

Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Another thing is, Kingroot is not suggested. It cannot be detected by Flashfire and some other tools. And cannot be replaced by SuperSU. So Kingo Root+SuperSU might be better.

aaawqw said:
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C shoukd use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Click to expand...
Click to collapse
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers

This unlocking guide only works for M571 model.
Click to expand...
Click to collapse
Mine is M571H, can I proceed?

Qeemi said:
This unlocking guide only works for M571 model.
Mine is M571H, can I proceed?
Click to expand...
Click to collapse
Mine too and it worked. I can't assure you anything, but I think that the problem are m571C which are different. Good luck if you're going to give it a try!

Moyster said:
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
Click to expand...
Click to collapse
See it. I'll give a try on m2 note(M571C, China Telecom). At least try to build twrp But seems my pc's hdd is not enough No space for source code

little problems.
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?

dinkan01 said:
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
Click to expand...
Click to collapse
hi,which build of cm 12 you put in phone?

M571U
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much

venturaj said:
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
Click to expand...
Click to collapse
It won't, the only problematic model is the M571C, have fun

LBA97 said:
It won't, the only problematic model is the M571C, have fun
Click to expand...
Click to collapse
How can I check which model my m2 note is..?

[email protected] said:
How can I check which model my m2 note is..?
Click to expand...
Click to collapse
Check the store page you bought it from. If you bought it from China, then probably it's a M571C. Good luck

[marmite] Android 7.1.1 TOS118C fastboot/recovery images

For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS118C.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
INCREMENTAL UPDATE (OFFICIAL) (DRIVE MIRROR LINK by me) (from TOS089A to TOS118C / from decf3a575d to aa4d5d86bc)
In the post below you can have some information on how to grab OTA links from the WileyFox BSP server. Have fun, and don't forget to debloat your system

How to grab the official OTA from BSP's server
In the OP, I left a link to the official incremental update right from the OTA server (which I'll talk about a bit later). If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
... Or you can just wait til someone mirrors it, like I already did
Lastly, as a side note, I'd also like to comment the following, regarding BSP:
Wileyfox's devices software is now in charge of this company, called BSP.ninja and that clearly defines themselves as a company to "launch an Android device without knowing where to start". It's said to be formed by former Cyanogen employees, or, at least Ricardo Cerqueira @aremcee (which btw, is also in charge of the Open Source code available in BitBucket for the Wileyfox devices), since he's the owner of the domain. In any case, what I want to say is that the code is being done quite possibly by the very same people that did the job at the now dead Cyanogen, so it shouldn't be a reason to worry. Also, it'd be awesome if the team released a working device tree so that the community could bring custom ROMs just like you (the team) used to do.

linuxct said:
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
Click to expand...
Click to collapse
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?

boa05 said:
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
Click to expand...
Click to collapse
Correct. I'm preparing a new version of my debloater tool, and I'll briefly explain in it's thread how to move from TOS089A to TOS118C without losing anything in rooted and/or debloated devices. Stay tuned!

Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.

zerospaced said:
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
Click to expand...
Click to collapse
I also skin my phone through substratum (the default orange theme is disgusting), I use magisk and plenty of other tools both systemless or even require modifying the system partition (like Wileyfox debloater), and, using the instructions I wrote in this post here I've found no single problem upgrading my device from a debloated, rooted and themed TOS089A to TOS118C to then debloat, root and theme it again. It's true you will need to install your substratum themes again, but the rest should work perfect.

I've tried the recovery update on my Swift 2X but can't get it to boot. I have TWRP installed (3.1.0-0) and it's rooted via SuperSU. Do I have to unroot first?
Edit for more info: I did the OTA upgrade from the stock CyanogenOS ROM to 7.1.1 TOS089A. Then I installed TWRP and flashed SuperSU. The OTA to TOS118C predictably doesn't work. Flashing the recovery image via TWRP seems to go fine but I'm stuck at the white "Wileyfox powered by Android" screen. Tried wiping Cache/Dalvik but no dice.
Edit 2: flashing Magisk afterwards seems to make it work.

I try to install the ZIP via TWRP and after the process ends the phone reboots but it remains stuck at the "WileyFox" white screen.
EDIT: I tried the fastboot one and it worked. Sometimes is hard to understand our devices

I'm guessing it's some kind of dm-verity issue? Flashing in TWRP worked for me when I flashed Magisk 12.0 afterwards, which seems to take care of dm-verity. Linuxct suggested installing Magisk in his debloat thread and I thought "what's the harm". Now I'm a happy camper.

Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.

Will this Firmware work on my Swift 2 Plus?

Cappucinto said:
Will this Firmware work on my Swift 2 Plus?
Click to expand...
Click to collapse
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.

Afifus said:
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Click to expand...
Click to collapse
Thank You so much

Installed it via fastboot and now iam stuck in a bootloop :S
EDIT: Did a factory reset in recovery! Works now.

Swift 2 Plus on 13.1.5 Cyanogen. Which method is best to install Android 7.1.1 TOS118C manually. The phone is stock, not rooted. Thanks

gaborkov9 said:
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Click to expand...
Click to collapse
If you use the
Code:
adb reboot "dm-verity enforcing"
can you remove the dm-verity menu on boot or do you need it left as after bootloader unlocked?

TOS373J?
Anyone have the images for the latest update?

TOS373J OTA
other link

Pooh042 said:
TOS373J OTA
other link
Click to expand...
Click to collapse
doesnt work gives me instal error 7 when i try to instal it

DarthBraindrain said:
doesnt work gives me instal error 7 when i try to instal it
Click to expand...
Click to collapse
what is your current firmware version?

[SHARED][TWRP][UNOFFICIAL 4pda version] for Mi A2 (jasmine_sprout) by d4e8ede8f1f2

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?

[ROOT][TB-X505X] Rooting Lenovo Tab M10 TB-X505X

This guide is now obsolete. Please check my new guide. It has a custom recovery for this device as well as a rooting guide. Refer to this guide only for installing adb and unlocking bootloader.
This rooting guide is for the Lenovo Tab M10 X505X only.
I plan to work on a custom recovery for this tab as well and probably a custom rom in the future.
So please consider donating so that I can keep up the work.
Donations
Google Pay
This will work only on the version "TB-X505X_S001037_200718_ROW". Check it in the Settings > System > About Tablet > Build Number. If it is the newer "X505X_S001038_200819_ROW", do a factory reset and make sure it is the "TB-X505X_S001037_200718_ROW" before proceeding.
Once a custom recovery is made, OTA updates can be applied without losing root. So do not update the tablet until a custom recovery is developed for the device. I plan to develop a custom recovery for it as soon as possible, so please support me.
Anything that goes wrong in this tutorial is not my responsibilty. Proceed at your own risk.
Downloads
patched_boot.img
Step 1. ADB and Fastboot Installation [If adb and fastboot are already installed, skip to Step 2]1. Download the platform tools for your OS from this link.
2. Extract the zip file and place the contents in a folder "platform-tools".
3. To confirm if adb is working, open a command prompt "platform-tools" and run the following command.
Code:
adb version
If it returns the adb version, its done.
Step 2. Unlocking BootloaderWe have to unlock the bootloader inorder to root the device.
Warning: Unlocking bootloader wipes data on the device. It is recommended to backup your data. Proceed at your own risk.
1. Now in the tab, goto Settings > System > About Tablet. Multiple tap the "Build Number" till the developer options are enabled.
2. Goto the developer options and turn on the "OEM unlocking".​3. Power off the device.
4. Turn it on by holding Power Button + Volume Down. Once the screen turns on. leave the power button but continue holding the Volume Down button until the fastboot mode is shown.
5. Now open a command prompt in "platform-tools" and now run the following command:
Code:
fastboot oem unlock-go
Your Bootloader is now succesfully unlocked.​Step 3. RootingNow to root the tab, download the "patched_boot.img" from the top of this post. Copy the file to the "platform-tools" folder.
Make sure the tab is still in the fastboot mode. Otherwise go back into the fastboot mode as instructed before.
Now run the following command:
Code:
fastboot flash boot patched_boot.img
Congratulations, you have rooted your tab.:highfive:
To complete the process, run the following command.
Code:
fastboot reboot
Once the tab turns on, goto this link and download the latest version of Magisk apk and install it. It is required to control the root privileges for other apps.​That's all. You now have a rooted tab.:victory:
If this helped you, hit the thanks button.
And keep tuned for new stuff that are to come for this device.

Thanks for this thread for the TB-X505X.
Shamil Niyas said:
I plan to work on a custom recovery for this tab as well...
I plan to develop a custom recovery for it as soon as possible...
Click to expand...
Click to collapse
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
Shamil Niyas said:
Once a custom recovery is made, OTA updates can be applied without losing root.
Click to expand...
Click to collapse
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.

Yahoo Mike said:
Thanks for this thread for the TB-X505X.
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Click to expand...
Click to collapse
I gave a look at the TWRP image. Unfortunately, X505X does not boot into the recovery image. It would have been great if it worked. I guess it is because of the different processor, as you mentioned.
It is the same for X505X as well. OTA cannot be applied without uninstalling Magisk. So I guess OTAs are a no-go until a custom recovery is developed. The latest update is also just a boot image patch. So there is no way to use magisk on that.
Thanks for the advice.

But i updated to android 10 S001122_200915
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.

Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.

ShAd0W_z0nE said:
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
Click to expand...
Click to collapse
This post has instructions for the X505F, under "How do I root my device?".

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
I'm currently working on the twrp for this device. Once it is finished it should be able to root without downgrading.

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.

Shamil Niyas said:
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Click to expand...
Click to collapse
Thanks sir. Great job and I'm also from kerala, nice to meet you

Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?

jsvenancio said:
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
Click to expand...
Click to collapse
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Twrp for x505f

Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..

tombaldwin6 said:
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
Click to expand...
Click to collapse
Check his new guide, just flash twrp and flash magisk from there

Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?

Tamiiiiiii812 said:
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Click to expand...
Click to collapse
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/

cYBER~VeTeRaN said:
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
Click to expand...
Click to collapse
OMG IT WORKED. Thank you.

Thanks bro. I found what I needed..

Shamil Niyas said:
1. Download the platform tools for your OS from this link.
Click to expand...
Click to collapse
yeah, where is the link?

Booe said:
yeah, where is the link?
Click to expand...
Click to collapse
Just search for platform tools and download it.

Guys, i tried the above mentioned method but my device is showing (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device) after performing a factory data reset the device reboots and the welcome menu shows up after 15-30 seconds the device automatically shut down and again shows the same message (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored onnn this device). this goes again and again......