Database Info

[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J4+/J415F/FN/G/DS

Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"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 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
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.
NOTE: ON ANDROID 5.1.1> 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.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
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

kapmino269 said:
Thank you very much for building twrp but there are bugs :
1- After I make steps all is done I power off it but when I open it isnot boot & i see a message All the words I understood that "you flash unauthornized boot.img & recovery img and return the phone to the company to fix the phone" and phone didnot boot I recognize that when I open internet in phone samsung detect the change in phone so i solved it by:
:good: I repeat the steps but after i connect to internet , i activate magisk and close wifi and download afwall on my sdcard from appkpure by pc and install the app an enable firewall and solved but there message that rules not apply but in fact it is applied and all is done . SOLVED
2-When I close phone and recharge it, it isnot recharged but it continue rebooting not to system but just recharge windows and poweroff and agian to recharge window And so on .
I coulding solve but I sure the error is in boot.img or in another . NOT SOLVED
Sorry for my english.................
Click to expand...
Click to collapse
Thanks for all the info, but does TWRP actually boot?

kapmino269 said:
Twrp is very very good and backup and restore and mount are good but there are bugs in system not in recovery addition the last:
3- the percentage of battery when charging,it isnot change . NOT SOLVED
What is the reason ?
Click to expand...
Click to collapse
Percentage doesn't change in twrp or when power off?

kapmino269 said:
SORRY MR ashyx there isn't bugs in system my charger was cut and it is the reason of rebooting to recovery. But bugs in recovery brightness control and backup encryption.
And your build is good ask twrp.me to make it official.
Click to expand...
Click to collapse
You will need to Format (not wipe) /data to remove encryption and mount the data partition. Samsung encryption isn't supported yet by TWRP.
Brightness isn't a deal breaker, but I'll look into it.
Could you do me a favour and post the recovery.log so I can check it over?

kapmino269 said:
And I forget said that all afwall versions above 2.9.9 doesn't work and Samsung will lock the phone and you should download afwall with date 5/2018
Click to expand...
Click to collapse
What do you need AFwall for?

kapmino269 said:
To prevent Samsung apps detect the change on the boot.img and recovery.img and so on and I told you at first that after flashing and activate magisk I set wifi on and when I power off the device and open it ,I couldn't open phone on any mode ,there is message apear to me told if I boot to system it said as I remember and I understand that "there is boot.img flash to phone by unauthorized way please return device to company or someone you buy the device from him to fix the phone " and replacing when reboot recovery boot.img by recovery. img and as I remember the screen was blue and the text was written in black and red. so I flash sammobile stock with Odin and repeat your twrp installing steps and activate magisk and close wifi and put afwall 2.9.9 (above versions didn't work ) and the error didn't appear again .
Click to expand...
Click to collapse
I don't think that you need AFwall. When you see that message boot to TWRP and format your device, install Magisk and the Oreo encryption disabler.
This should prevent this message appearing again.
Also disable securitylogagent apk.

Can this be used to flash GSI?

Jason Grewal said:
Can this be used to flash GSI?
Click to expand...
Click to collapse
As posted in the OP :
Update 8/12/2018
Current status - Beta (Tested working)
Treble supported
Bugs: brightness slider
Click to expand...
Click to collapse

kapmino269 said:
sorry I see another error in restore in TWRP .
all partitions restored but when I finish restore twrp said unable to mount /system and I couldn't reboot system
Click to expand...
Click to collapse
Have you tried backing up only system again then immediately restoring?
Also which media are you restoring from?
Also need the recovery log after failure.

kapmino269 said:
A1 :No , I will try backup system and system image only.
A2 :I restore from usb otg .
A3 :It success in restore efs boot vendor and others but system not mount and tried to return system again .
££i flash sammobile rom and install magisk as you tell and restore all phone partitions Except system and system image ££ The phone open again.
###I will try restore system again and i will sent you recovery.log BUT WHICH MEDIA I SHOULD USE USB OTG OR SDCARD ###
I am sorry for disturb.
Click to expand...
Click to collapse
Can you try backing up just system, not system image to internal storage then try restore?

kapmino269 said:
ok, I will try .
I would ask you about something else but sending you private message unanable I need to ask you but i couldnot because the question is about something else twrp for j415f how to send the issue to you
Click to expand...
Click to collapse
If it's related to this device then just post it. I don't accept pm's.

kapmino269 said:
A-Restoring system only and other partition is done and succeed and faster from internal storage but if i copy it to pc or sdcard Is all files will copied or not or Error will apper after copy (restoring again).
Thanks for your help .
1- it is related to j415f some apps like busybox and linux deploy and afwall(new version) grant root access but didnot run.
2- #
Another problem :
no,it isnot .it related to wlan monitor mode for gt-i9500 (internal (bcm4335 ) or external (TL-WN22N) ) , I tried linux deploy kali hunter nexmon others ,and please reply if you could help me or reach me to someone help me .
#
please reply me quickly about (2) to delete it
SORRY I havenot any way to reach you except this .
Click to expand...
Click to collapse
1. Isn't really related to twrp but magisk itself. Better posting in the magisk thread.
2. Unfortunately can't help you with this as I don't mess around too much with that kind of stuff.

I wouldnt dare to do anything on this before everything is 100% clear and failproof. This phone behaves like its about to collapse every second idk why but it feels like that

kapmino269 said:
Thank you very much for your help and your interest .
Please ,Can you fix restoring system from usb otg ? and all files you need from me i will send you it ,
you must make your twrp ideal and make it official in #twrp.me# like Alberto86(recognise developer) : make gt-i9500 twrp and ge officialty .
surendrajat(member ) : Make SM-J737S twrp it is in #twrpbuilder.github.io#
I think you should publish the recovery in this sites at the nearest time. I think also you should make video on youtube to make your project spread out faster ,because there are people donot know xda ,I tried to make video but my presentation was very bad so i delete it from youtube .
And Sorry for distrubt
Click to expand...
Click to collapse
I don't think there is anything to fix regarding the restorating of a backup from OTG.
It's just simply a case of some media is not suitable for backup and restore.
I've even seen reports of certain MicroSD cards causing issues with TWRP.
It's likely that if you try a different USB stick you won't have any issues.
As regarding making it official. I will consider it. However I have many, many builds of TWRP for a lot of other devices that are not official either.
This is due to the fact I do not like the convoluted system of getting it made official.
I have discussed this previously with teamwin and asked for a proper submissions page to no avail.

kapmino269 said:
Ok as you like but you can improve twrp .
I mean :
1 -Could you compress encryption disable and
rmm bybass and recovery in twrp.tar file to flash it by odin in one step wihout following install steps that you write , Steps may be difficult with others , With me I try serval times to success and i know some skills about android but others may donot know .
2 - Why your twrp depend on magisk install
,if magisk doesnot install phone doesnot reboot system , I think twrp should not be depend on root & If some one need twrp and doesnot need root.
3 - Busy box i cannot install it in my phone why ,?
Click to expand...
Click to collapse
No I cannot make an all in one to flash in ODIN.
Firstly because its not possible. Odin cannot run scripts, only recovery can.
Secondly if people cannot follow instructions then maybe they shouldn't be attempting to modify their device.
TWRP doesn't depend on Magisk, your device does.
Samsung incorporate many security hurdles to prevent hacking and modification.
These security blocks need to be patched or the device will not boot.
These blocks can be patched manually, however Magisk can patch most of these during the root process.
I have no idea why you cannot install busybox on your device as you have not provided any info of the issue.
In any case busybox is included with Magisk. To use it install the busybox module by osm0sis.

kapmino269 said:
picture
Click to expand...
Click to collapse
I see what your saying, however I will keep things as they are. I'd prefer people to have an understanding of what they are installing and I believe it's simple enough.
Unfortunately I can't help with the busybox issue. However as I stated you can use the busy module provided by osm0sis.
He keeps everything up to date and is highly recommended.

kapmino269 said:
I face issue :
I test j4+ snd s4 security in lookscreen :
1- In j4+ : if I delete /data/system/locksetting.db or all contain locksetting name in twrp buy terminal or file manager or script.
2 -add delete *.key on s4 .
Is there solution from system or twrp to prevent lock screen crack or it hash stolen to crack not tell me (chattr).
Thank you
Click to expand...
Click to collapse
If I'm reading it correctly you want a way of preventing the lockscreen credentials from being deleted.
The only way is to remove TWRP Tbh so no one had access to the file system.
Also this isn't really a twrp related issue and a little off topic.
However I have been looking at possible ways to password TWRP thus preventing access at all.
But even that could be circumvented by simply flashing another version of TWRP.
The only safe way is to remove twrp, unroot your device and disable OEM unlock.

kapmino269 said:
1 - I donot have any ways to reach you and you is the developer of twrp for j4+ and Know all about it and you donot accept pm , I could make
thread and you answer me in it but this issue in twrp so all is well .
2 - I want twrp and root ,Is there any solve ,I have idea may success sent me it may be sucess or not
it is
1- make data partition not mount or read only on twrp .
2- when I need to install something I will mount it by writing command in system terminal only (that command or script or program doesnot be found in twrp ) to be mounted in recovery mode .
3- I mean that data not mount in twrp without enable mounting in system and twrp doesnot have permission to mount data without system access .
but how this will acheive without you man .
another idea the same but replace mounting by read only
Click to expand...
Click to collapse
If you don't want data to be mounted in twrp then why not just leave it encrypted. Then only you have access to it via the OS?
Failing that just remove the mount entry for /data from the fstab.
This way data will only be available and mountable by using terminal commands.
The other way is to only install twrp when you need it.
For example you could use a script which you could run to flash twrp when booted to the OS each time you need it or if you prefer use something like flashify.
When you are done with twrp, simply use the restore option to restore the stock recovery.
This way only you have access to /data.

how to do this on galaxy J4?pls. help
i have a lock bootloader in download mode

Has anyone tried any gsi?
I tried havoc os 2.0 didn't work.

Step by step guide "Flashing OTA beta/stable update using OrangeFox Recovery Project"

Step by step guide "Flashing OTA beta/stable update using OrangeFox Recovery Project"
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Credits to @ronks888
@madsponge26
Details about OrangeFox Recovery Project, contributors, FAQ. The thread can be located here https://forum.xda-developers.com/po...cial-orangefox-recovery-project-beta-t3853233
DOWNLOADS
OrangeFox TWRP https://drive.google.com/open?id=1IZrV1VmWkqJOZccxbylbGw_0W4FwInFH
Force Encryption Disabler https://drive.google.com/file/d/1InT96d0tZ0eIIUNRDNuzKlaEKD02yLLM
Magisk v18 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
MIUI ROM https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Step by step Guide flashing OTA update using OrangeFox Recovery Project​
But before proceeding, make sure you did all of the steps here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
1. Preparation for the OTA update
-BACKUP YOUR IMPORTANT DATA FIRST
-Download the latest release of OrangeFox Recovery (found above)
-Download your MIUI Full ROM (See above)
1.1 Flash the OrangeFoxRecovery.zip using your current custom recovery
-Reboot to OrangeFox Recovery
1.2 Go to the settings and enable these MIUI OTA settings
-Support MIUI Incremental OTA
-Include system in OTA survival
-Incremental OTA signature verification
-Aggressive stock recovery deactivation
-Disable DM-Verity
-Disable Forced Encryption (Some devices bypass this option, there will be a step on how to fully disable forced encryption later.
1.3 Go to the WIPE menu and tick wipe data, cache and dalvik
1.4 Flash your full MIUI ROM (stable/beta). After the ROM is flashed, OrangeFox will start the "OTA_BAK" process, which will backup your system and boot partitions into the /sdcard/Fox/OTA directory. You must NOT delete any of the files in the /sdcard/Fox/OTA directory. If you do, then incremental OTA updates will most definitely fail.
1.5 Reboot your phone and start to use your phone normally
1.6 When MIUI notifies you that there is an update, download the update, using the MIUI updater app and allow it to reboot automatically to OrangeFox
-If an error shows that the data partition is still encrypted, then time for step 2
-If the ota update succeeded, then Congrats just wait around 5-10 minutes to boot. Ignore the next step
2. Transfer folders Fox and rom_downloads from internal storage to sdcard (Please don't get confused by this, it is explanatory.)
-If you done downloading the OTA, transfer rom_downloads from internal storage to sdcard
-Transfer Fox from internal storage to sdcard, DO NOT SKIP THIS OR YOU'LL BRICK YOUR DEVICE
-Make sure the Force Encryption Disabler and Magisk is in the sdcard. We gonna need it.
2.1 Reboot to OrangeFox
2.2 Wipe Data ONLY, Don't forget to transfer the Fox from internal storage to sdcard or you'll lose the ota survival
2.3 Flash Force Encryption Disabler
2.4 Reboot recovery
-If no pop-up was shown to decrypt data, then Encryption is disabled.
2.5 Reboot the device
2.6 Transfer folders Fox and rom_downloads from sdcard to internal storage
2.7 Go to MIUI updater app then press reboot to flash ota update Don't forget to transfer the Fox from sdcard to internal storage or you'll risk your device to brick because ota_bak never existed during ota update
-Make sure you have 15% battery life or connect it to a plug
2.8 Say your prayers that it worked
2.9 If the ota update succeeded, without bootloop or errors was shown during the flash. Then you are good.
-Takes time to boot after the ota update? Just wait around 10 minutes, in this process, the data partition gets force encrypted again and needed to be disabled again via custom recovery. After boot, you can proceed again to disable force encryption via OrangeFox.
-New ota update? Just repeat the step 1.6
Questions? Feel free to message or reply this thread.

Great job.… :good:
Try modifying /system partition (like removing a bloted system app or editing build.prop) after step 1.5 then update OTA through rest of the process if it get flashed or not.... Let me know, it'll be great help for me!!
Sent from my POCOPHONE F1 using XDA Labs

nilg0lap said:
Great job.… :good:
Try modifying /system partition (like removing a bloted system app or editing build.prop) after step 1.5 then update OTA through rest of the process if it get flashed or not.... Let me know, it'll be great help for me!!
Sent from my POCOPHONE F1 using XDA Labs
Click to expand...
Click to collapse
Alright, will try it for the next test.

nilg0lap said:
Great job.… :good:
Try modifying /system partition (like removing a bloted system app or editing build.prop) after step 1.5 then update OTA through rest of the process if it get flashed or not.... Let me know, it'll be great help for me!!
Sent from my POCOPHONE F1 using XDA Labs
Click to expand...
Click to collapse
Ohhh yeah... About that...
Even though you modified something in the system partition (like flashed a custom kernel, have Magisk/SuperSU installed), it will get removed because of the OTA update and will be replaced by stock kernel, and a non-rooted system. But about removing bloated system app, I will try that next time.
You could try it, before proceeding to step 1.6, you can back-up your system apps using Titanium back-up or other apps available on the play store. Or just BACKUP everything via OrangeFox. If anything gets wrong or something, at least you have a backup to restore with.

Everything you flash on the system (custom kernel, Magisk/SuperSu, performance mod, tweaks, will be wiped.
Just flash it again and everything would be fine.

Sir, is this still working on latest developer rom (9.4.26) ?
Do you prefer R9.0 over R9.0.1 ? Had read that latter has bugs.
Or safest method as of now is from this post via official twrp ? --> https://forum.xda-developers.com/showpost.php?p=79461706&postcount=186
Please help sir as I really want to be on stock miui w/ magisk & OTA support.
Thanks in advance kabayan!

19iceman32 said:
Sir, is this still working on latest developer rom (9.4.26) ?
Do you prefer R9.0 over R9.0.1 ? Had read that latter has bugs.
Or safest method as of now is from this post via official twrp ? --> https://forum.xda-developers.com/showpost.php?p=79461706&postcount=186
Please help sir as I really want to be on stock miui w/ magisk & OTA support.
Thanks in advance kabayan!
Click to expand...
Click to collapse
Backup first. Then try the Twrp with working decryption

[GUIDE][OP7][9.0/10.0/11.0] Unlock Bootloader | TWRP | Root with Magisk | Update

Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
This thread is dedicated to newbies and rooting, so if you're familiar with the whole procedure, you're done
Just ask questions about every step and you'll receive help!
Downloads
TWRP Installer ZIP and TWRP IMG for Android 9/10: https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
TWRP for Android 11(including instructions, thank's to @Nebrassy ): https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
TWRP Installer ZIP = For example twrp-3.4.0-10-guacamole-unified-installer-mauronofrio.zip
TWRP IMG = For example twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
Check for Pie or Q TWRP IMG! If you have Android Pie, choose Pie TWRP IMG, if you have Android Q, choose Q TWRP IMG.
The TWRP Installer ZIP works on Android Pie(9)/Q(10)
Magisk ZIP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hints
If you need to update TWRP or Magisk, always keep older versions of both in hand(Magisk canary or beta may have issues)
Remove your lockscreen protection which also removes encryption to prebvent mounting issues within TWRP
Before proceeding
Your Windows PC should already recognized your device with the USB cable
Use an USB cable provided with the phone
Make sure your Windows Explorer is set up to have file extensions enabled to avoid file name issues
This process will FORMAT/WIPE/DELETE your internal storage and every file of your phone, so please back it off your device at first!
Also keep a boot.img from your current system in place if anything went wrong so you can flash it via fastboot, see "Rooting without TWRP" for how to get it.
Rooting with TWRP (Android 9/10)​
Steps for unlocked bootloader with TWRP AND Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP installer ZIP" and "Magisk ZIP" to the phones internal storage.
5. Copy the "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP installer ZIP" from your phones storage from step 4.
13. Hit "install" and navigate to the "TWRP installer ZIP" file and select it for installation(dont boot the system now!).
14. Go back and flash "Magisk ZIP" the same way as for TWRP Zip otherwise your device will not boot!
15. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP and Magisk:highfive:
Steps for unlocked bootloader with TWRP WITHOUT Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP IMG" to the phones internal storage.
5. Copy the latest "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP IMG" from your phones storage from step 4
13. Navigate to advanced menu within TWRP, click on "Install Recovery Ramdisk" and select the "TWRP IMG". This will patch the boot image which does Magisk otherwise.
14. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP:highfive:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting without TWRP (Android 9/10/11)​
Also useful to get stock recovery and kernel --> Recovery is within boot.img on A/B devices like OP7
Refer here for unlocking the bootloader.
1. Download the payload dumper tool to your PC from here and extract it
2. Download the FULL OxygenOS Rom zip(The version your phone is running) and extract the payload.bin
3. Put payload.bin to "payload_input" folder o the extracted tool
4. Run payload_dumper.exe from the tool's folder
5. Extracted img files are in "payload_output" folder
6. Now you have your own boot.img for your Rom
7. Copy it to your phone
8. Patch the boot.img with Magisk directly on your device: Magisk Manager App -> hit install after your Magisk version -> hit "Select and Patch a file"
9. Copy the patched boot.img (it should be in the Download folder of your device named something like "magisk_patched-22100_bjjRn.img") back to your PC
10. Reboot your device to fastboot
11. Flash the patched magisk_patched-22100_bjjRn.img
Code:
fastboot flash boot_a magisk_patched-22100_bjjRn.img
fastboot flash boot_b magisk_patched-22100_bjjRn.img
12. Reboot your device. Now you have your phone rooted without the need of TWRP (Check with Magisk Manager App)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update your rooted OxygenOS (Android 9/10)​Steps for UPDATE OxygenOS via OTA and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
3. Go to Android settings -> system -> system update and hit "Download & Install Now", don't reboot yet!
4. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
5. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit "install to inactive slot"
6. Reboot your device
7. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via OTA and you keep TWRP and Root:highfive:
Steps for UPDATE OxygenOS via local upgrade and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version ->hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via local upgrade and you keep TWRP and Root:highfive:
If you have any issues, just feel free to ask!

@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.

Kollachi said:
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Click to expand...
Click to collapse
I made it a little bit more clear, thanks, that's an common issue across several devices and requested often enough

Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel

AxelM said:
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
Click to expand...
Click to collapse
There's something different after unlocking the bootloader(which is the same). Twrp and magisk installation is different due to treble.
For EFS you can backup with twrp or local terminal
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=512

Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?

Camack said:
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Click to expand...
Click to collapse
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard

strongst said:
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
Click to expand...
Click to collapse
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?

Camack said:
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Click to expand...
Click to collapse
You need to do all steps. I recommend to flash the custom kernel when you've sucessfully booted the device at first.

Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well

murti52 said:
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
Click to expand...
Click to collapse
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

strongst said:
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.

murti52 said:
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
Click to expand...
Click to collapse
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.

strongst said:
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
Click to expand...
Click to collapse
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.

murti52 said:
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
Click to expand...
Click to collapse
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

strongst said:
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?

murti52 said:
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
Click to expand...
Click to collapse
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.

strongst said:
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
Click to expand...
Click to collapse
Then there must be some issue with my flashing sequence. Btw, The service centre repaired the issue and i have rooted it and using bluespark with stock rom. I'll give the zip another try later on when a new update comes. Thanks for the help

I believe the default file system is ext4, is there any benefits changing it to f2fs?

Jacckz said:
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Click to expand...
Click to collapse
A good and quick overview and comparison with oneplus 7 pro https://sparrowsnews.com/2019/08/13/difference-between-f2fs-and-ext4-file-system/

Gapps installation problem - LineageOS 16 + Oneplus 7 Pro

I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks

Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps

oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...

cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work

liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....

cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.

liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.

Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.

cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?

Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.

Need custom recovery for Mobiistar C1 shine 4g mt 6739 device

Need custom recovery for Mobiistar C1 shine 4g mt 6739 device as m stuck need it urgently and want install android 10 gsi image my device has arm32 a only architecture some suggest me some good and lite gsi images please firstly I need custom recovery twrp please someone help.

It would be hard to support a 2018 device I guess.

[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com

i can upload recovery.img file for if you want

its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible

Again: You request a TWRP build for your device going to this thread
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com

any custom recovery bro sorry for that (twrp)

my phone back running again i have flashed it with stock firmware recovery images i have attached earlier and so does phone details screenshot now present situation is 8.1 not rooted stock recovery and firmware so i hope if anyone can help i will be glad

installed latest magisk apk and .zip also by patching boot.img file and flashing that with sp tool to install magisk and got root privilege's

all now i want is proper running and fully functional custom recovery to install custom roms and mods

copvaibhav said:
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Click to expand...
Click to collapse
I am not responsible for any wrongdoing by you. Always have ROM stock files. Any error, install stock recovery again.
First you need to unlock the bootloader if necessary! Unzip file attached and look 2 files.
Then, the installation plan:
0) Flash the TWRP with SPFT or fastboot;
1) Enter TWRP IMMEDIATELY without starting in the system, otherwise TWRP can revert to the stock;
2) When asked to enter the password, select Cancel;
3) Load the file with Magisk (look for any magisk19.zip for TWRP and the decryption file for EXTERNAL memory;
4) Flash Magisk immediately and then install the file data_decrypt_Mobiistar_C1_Shine.zip immediately;
5) Make FORMAT DATA - bottom left button - Type: YES. Go back to the TWRP menu;
6) Make Wipe: data, cache, dalvik (reset to factory settings! Save your data!);
7) Reboot to TWRP (password must not ask);
8) Restart on the system, root is received.

thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap

copvaibhav said:
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
Click to expand...
Click to collapse
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.

lopestom said:
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
Click to expand...
Click to collapse
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do

copvaibhav said:
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
Click to expand...
Click to collapse
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/

thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful

copvaibhav said:
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
Click to expand...
Click to collapse
Look correct app to know about your device: Treble Info
You need try install AOSP 8 & 9: https://github.com/phhusson/treble_experimentations/releases
Look "bugs"; try solving; keep your time with experiments.....
After you can try LOS, RRMix, Havoc, etc.....
About this thread/ask help about Custom Recovery so Solved. @jerryhou85
Good Lucky!

system-arm-aonly-vanilla-nosu.img.xz
system-arm32_binder64-aonly-vanilla-nosu.img.xz
bro which file shpuld i download as i told you mine is 32bit arm a only (what is arm first link and arm32binder64 aonly difference) kindly tell.
just to clarify i have download both removed.xy from ext. and flashed from recovery system image but phone goes into fastboot after reboot and when rebooting in recovery at the top it shows no os installed.

lopestom said:
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Click to expand...
Click to collapse
Sir it's stuck on password screen touch not working please fix it, I will always be grateful to you.

Honey2012 said:
Sir it's stuck on password screen
Click to expand...
Click to collapse
The first start need choose the CANCEL. I think you not know about TWRP (unofficial) and the process with device/TWRP without encryption/decryption process.
If you want that so send me some device to develop/have the possibility of getting that option.
Honey2012 said:
touch not working please fix it, I will always be grateful to you.
Click to expand...
Click to collapse
As you read, I not have your device in my hands!
Many 32bits and few 64bits devices have problem with touch screen from kernel. That's not my error! It's from device company.
I not know about touch screen work or not since copvaibhav not write about. But I won't fix this. There is also the possibility to use OTG and plug in a USB Mouse to use in TWRP.
There are solutions to fix the touch screen but I don't have the device and I don't have time to do it. Search and you will know. So solve it yourself and thank your self for it.
Ask copvaibhav for more process and using TWRP.