Database Develop

[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017)

Unofficial release -TWRP recovery for the Galaxy A3 SM-A320F/FL/Y, Exynos7870
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 11/9/2017
TWRP 3.1.1-1 MM build released.
Current status: BETA
Features:
MTP
ADB
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
TWRP Official APP support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-a320f_11917
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Twrp Source : https://github.com/omnirom/android_bootable_recovery
Kernel source : http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-a320f
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.

Reserved.

If anyone has successfully installed this, I'd appreciate if they could post the recovery.log so I can look it over.
Log can be pulled in twrp under ADVANCED/SAVE RECOVERY LOG or on a rooted device go to cache/recovery/last_log
Thanks.

Blimey can no-one find the time to help out here?

I'd love to test this, but first I have to figure out why flashfire isn't working for me.
It only restarts after 20 seconds or so of white text and black background scrolling down, but no backups are written, only a log.

F157 said:
I'd love to test this, but first I have to figure out why flashfire isn't working for me.
It only restarts after 20 seconds or so of white text and black background scrolling down, but no backups are written, only a log.
Click to expand...
Click to collapse
It's already confirmed working I just need someone to post the recovery.log.
40 downloads since posting but no-one willing.

Hello, thank you very much, it worked for me. It was important so I can make a backup of the system. How can I post the recovery log? If you give me the procedure I'll do it.

patci32 said:
Hello, thank you very much, it worked for me. It was important so I can make a backup of the system. How can I post the recovery log? If you give me the procedure I'll do it.
Click to expand...
Click to collapse
Thanks, you're the only one to have made the effort!
You can save the recovery log from TWRP if you go to ADVANCED> SAVE RECOVERY LOG or you can boot to android and go to cache>recovery>last_log.
Please don't post the output here, post as a file or save the output on pastebin.com.
Thanks.

ashyx said:
Thanks, you're the only one to have made the effort!
You can save the recovery log from TWRP if you go to ADVANCED> SAVE RECOVERY LOG or you can boot to android and go to cache>recovery>last_log.
Please don't post the output here, post as a file or save the output on pastebin.com.
Thanks.
Click to expand...
Click to collapse
Here it is.

patci32 said:
Here it is.
Click to expand...
Click to collapse
Nothing there?

ashyx said:
Nothing there?
Click to expand...
Click to collapse
Yes sorry, it says network error when I try to attach the file!
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
I can send it to you by email

patci32 said:
Yes sorry, it says network error when I try to attach the file!
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
I can send it to you by email
Click to expand...
Click to collapse
You can post it here :
http://www.tinyupload.com/

ashyx said:
You can post it here :
http://www.tinyupload.com/
Click to expand...
Click to collapse
Here you go : http://s000.tinyupload.com/index.php?file_id=17704648158807479484
Thanks for your work. An information about my use : when I made a backup, I got a lot of errors like unable to mount the sd card and in the end "back up failed". But the 3 GB file has been created in the right folder, I think I got my backup.

patci32 said:
Here you go : http://s000.tinyupload.com/index.php?file_id=17704648158807479484
Thanks for your work. An information about my use : when I made a backup, I got a lot of errors like unable to mount the sd card and in the end "back up failed". But the 3 GB file has been created in the right folder, I think I got my backup.
Click to expand...
Click to collapse
No idea what's going on with tiny upload. Clicking the download link just downloads the html data of the web page not the actual file!
Thanks for trying any way.
By the way you can't back up data until you remove encryption.

ashyx said:
No idea what's going on with tiny upload. Clicking the download link just downloads the html data of the web page not the actual file!
Thanks for trying any way.
By the way you can't back up data until you remove encryption.
Click to expand...
Click to collapse
You mean I can't use the save file right now ? How do I remove encryption?

patci32 said:
You mean I can't use the save file right now ? How do I remove encryption?
Click to expand...
Click to collapse
See the OP.

ashyx said:
See the OP.
Click to expand...
Click to collapse
I dont get it I'm sorry. I got the save file, you're saying that I can't use it? I should be able to use the file with the restore section no ?

patci32 said:
I dont get it I'm sorry. I got the save file, you're saying that I can't use it? I should be able to use the file with the restore section no ?
Click to expand...
Click to collapse
If the data partition is encrypted then it wont have backed up. The rest of the partitions will have been backed up.
This is the failure you saw when backing up.

ashyx said:
If the data partition is encrypted then it wont have backed up. The rest of the partitions will have been backed up.
This is the failure you saw when backing up.
Click to expand...
Click to collapse
OK understood. Data partition is the sd card or the internal memory ? I assume that the encryption exists for security reasons. Is there anyway to backup everything without desactivating it?

patci32 said:
OK understood. Data partition is the sd card or the internal memory ? I assume that the encryption exists for security reasons. Is there anyway to backup everything without desactivating it?
Click to expand...
Click to collapse
It's internal memory.

TWRP 3.2.0.0 Moto Z2 force [Nash]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly

[TWRP][64 bit][3.2.1_r12][UNOFFICIAL]Moto Z2 Play[Albus]

TWRP 3.2.1_r12 Moto Z2 Play (albus)​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03

I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.

Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?

Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx

JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.

3.1.2_r18 version released. Check download link in OP

hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?

fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok

rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.

I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?

Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.

kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.

Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.

kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?

Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.

kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.

I make a full backup, so can I restore that backup file after LineageOS?

This works when go command fastboot boot .... ?

I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...

Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).

Help-me Please

I used a magisk option to rename / hide it, and ended up losing root, tried to root, but to no avail, magisk manager no longer has the modules, magisk hide, or supersu option. Can someone help me ?

Simply uninstall the Manager and then reinstall it manually (apk in the Magisk zip or from @topjohnwu's Github.

Didgeridoohan said:
Simply uninstall the Manager and then reinstall it manually (apk in the Magisk zip or from @topjohnwu's Github.
Click to expand...
Click to collapse
already tried, and already tried to root again, the process happens without fail, but when you check this without
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danyfenton said:
already tried, and already tried to root again, the process happens without fail, but when you check this without
Click to expand...
Click to collapse
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp

Didgeridoohan said:
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
Yes, I had the manager, I also uninstalled and redo the installation, and without success.
Things I've already done:
- I uninstalled Manager.apk, and reinstalled Magisk
- Redo Root using TWRP.
- I uninstalled Magisk from TWRP via MagiskUnistall.rar file
- Installed Previous Versions of Magisk, like 17.1; 18.1; 19.4 (Beta).
and still unsuccessful, magisk looks like the image I posted above. Worst of all was that I lost root, and even trying to redo the root procedures, does not come back.
I am using google translator, I apologize if the understanding is not so good.

It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.

when I try to install from magisk itself, this error appears.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
OK, when I get home from work I'll try, thanks.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
unsuccessful when using unSU.
succeeded in using it on twrp, restarted the phone, and went back to TWRP, and redid the process, and to no avail.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
- Device platform: armeabi-v7a
- Copying image to cache
1022+1 records in
1022+1 records out
1047368 bytes transferred in 0.016 secs (65460500 bytes/sec)
- Unpacking boot image
Parsing boot image: [/mnt/expand/20683188-08c0-4603-a521-de6372bd2a29/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed

danyfenton said:
unsuccessful when using unSU.
succeeded in using it on twrp, restarted the phone, and went back to TWRP, and redid the process, and to no avail.
Click to expand...
Click to collapse
Didgeridoohan said:
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
I got it, I formatted the phone and redid the whole process. Thanks for the force friend.

danyfenton said:
I got it, I formatted the phone and redid the whole process. Thanks for the force friend.
Click to expand...
Click to collapse
I was just about to come in here and reply to your other message, and I find you got it sorted. Nice.
All I did was point the way, you're the one who fixed it in the end. :good:

Didgeridoohan said:
I was just about to come in here and reply to your other message, and I find you got it sorted. Nice.
All I did was point the way, you're the one who fixed it in the end. :good:
Click to expand...
Click to collapse
thank you for being willing to help, really.

[Release][2022.6.26] Magisk Manager for Recovery Mode (mm)

Magisk Manager for Recovery Mode v7 202206260
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v19.0 - v25.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
- Source code
- Documentation
- Releases
- Original thread
Note: The GUI "Magisk Manager Recovery Tool" project is a different, stand-alone project.
Which is not affiliated with this CLI "Magisk Manager for Recovery Mode" project.
Edit1: Reported as working on Magisk v23.X! Updated the documentation and released a new version
Edit2: Tested and confirmed working on Magisk v25.X! Updated the module's readme, print lines, inner docs...

I might be doing something wrong but it's not working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Poslano z mojega MI 9 z uporabo Tapatalk

mxxt01 said:
I might be doing something wrong but it's not working... View attachment 4997015
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
Sorry, all clear now [emoji16]
I was just about to try in TWRP...
Thanks!
Poslano z mojega MI 9 z uporabo Tapatalk

Rikj000 said:
Magisk Manager for Recovery v5 202004170
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v20.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
Flash this in TWRP each time you want to use it, not in Magisk itself.
You can download the new release from my GitHub: https://github.com/Rikj000/mm/releases/tag/2020.4.17
Original thread: https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Click to expand...
Click to collapse
Thanks this will be handy when experimenting some modules
Sent from my Mi A2 using Tapatalk

Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Same here.
Updater process ended with error: 123

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Click to expand...
Click to collapse
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.

Rikj000 said:
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
Click to expand...
Click to collapse
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?

JamesKinds said:
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
Click to expand...
Click to collapse
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP

Rikj000 said:
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Click to expand...
Click to collapse
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?

JamesKinds said:
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
Click to expand...
Click to collapse
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.

Magisk v20.4 ERROR 123 ((( for Recovery

Latest Magisk Canary, working like a charm, thanks

Rikj000 said:
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Click to expand...
Click to collapse
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Click to expand...
Click to collapse
Upon further inspection might be due to spaces in the zip file name. But magisk script wasnt up to date anyways. So this version will be supported in Magisk for a longer time then the original due to that.

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
Bro, uninstall all versions this mod, reboot system, boot to twrp flash zip, go in twrp to terminal write mm, write q and click enter, boot to system, reboot to twrp go to terminal and type sdcard/mm important sdcard/mm, now should work

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
I found the solution to the installation error eventually. The zip itself MUST be somewhere in internal storage when flashing and cannot be in sd card or otg. And even the old mmfr zip installs for me if I place it in internal storage. So maybe include this in your post. For context, I use Android Q rom with Magisk 20.4.