So apparently after i flash the files and tried to reboot my S7 Edge Exynos it got stuck in loading screen and doesn't enter home page. I guess it's bricked. Is there any way to fix it? Force factory reset or something. Sincerely need help , guess it's an expensive lesson.
Blank. said:
So apparently after i flash the files and tried to reboot my S7 Edge Exynos it got stuck in loading screen and doesn't enter home page. I guess it's bricked. Is there any way to fix it?
Click to expand...
Click to collapse
Use Odin to flash the Xposed uninstaller ZIP.
You probably used the wrong branch of Xposed for your device.
Sent from my Galaxy S7 Edge using Tapatalk.
ianmacd said:
Use Odin to flash the Xposed uninstaller ZIP.
You probably used the wrong branch of Xposed for your device.
Click to expand...
Click to collapse
Almost 100% sure Odin can't install zips.
Sent from my Galaxy S5 using XDA Labs
Rakuu said:
Almost 100% sure Odin can't install zips.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
I used odin to install a zip while applying a root method for galaxy s5. I'm fairly new with all of this, so hopefully I'm not out of place.
krummm said:
I used odin to install a zip while applying a root method for galaxy s5. I'm fairly new with all of this, so hopefully I'm not out of place.
Click to expand...
Click to collapse
It installs .tar.md5s, it's not capable of comprehending zips as far as I know, need a custom recovery or flash fire for zips.
Sent from my Galaxy S5 using XDA Labs
Rakuu said:
It installs .tar.md5s, it's not capable of comprehending zips as far as I know, need a custom recovery or flash fire for zips.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
You know what, you're right. I double checked and the file type is a tar. It just had a similar icon so I was mistaken, my apologies.
Rakuu said:
Almost 100% sure Odin can't install zips.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Damn. That's what the Americans call a brain fart.
OK. Change the advice to 'Use FlashFire if you can boot, otherwise TWRP'.
Sent from my rooted Galaxy S7 Edge using Tapatalk.
ianmacd said:
Damn. That's what the Americans call a brain fart.
OK. Change the advice to 'Use FlashFire'.
Click to expand...
Click to collapse
Not an option if you're already bootlooped, use a custom recovery or reflash stock and start over.
Sent from my Galaxy S5 using XDA Labs
ianmacd said:
You probably used the wrong branch of Xposed for your device.
Click to expand...
Click to collapse
Could you tell me which ones do I need to install? Android Version 6.0.1 , Model SM-G935FD.
Also , do i need to install the .asc files? Which arm version should i install? Thanks a lot. Newbie here.
Blank. said:
Could you tell me which ones do I need to install? Android Version 6.0.1 , Model SM-G935FD.
Also , do i need to install the .asc files? Which arm version should i install?
Click to expand...
Click to collapse
Go to the Xposed for Samsung on Lollipop/Marshmallow thread, scroll down to Version names and you will see which names apply to your device, based on its processor type and version of Android.
Then, follow the Download link and download the file corresponding to your device. Don't forget to install the package installer afterwards.
You don't need to install any .asc files. I don't even know what they are.
ianmacd said:
Go to the Xposed for Samsung on Lollipop/Marshmallow thread, scroll down to Version names and you will see which names apply to your device, based on its processor type and version of Android.
Then, follow the Download link and download the file corresponding to your device. Don't forget to install the package installer afterwards.
You don't need to install any .asc files. I don't even know what they are.
Click to expand...
Click to collapse
Sorry for this long message and thanks for your help. I've checked and i've downloaded the correct files. I didn't wipe dalvik/cache before i flashed it previously but now i did , and then flashed the xposed. It said "failed to mount '/data' (invalid argument)" so i wasn't sure if it succeeded or not hence i flashed the uninstaller to prevent it from bootlooping again. Was It correctly installed?
Blank. said:
I didn't wipe dalvik/cache before i flashed it previously but now i did , and then flashed the xposed. It said "failed to mount '/data' (invalid argument)" so i wasn't sure if it succeeded or not hence i flashed the uninstaller to prevent it from bootlooping again. Was It correctly installed?
Click to expand...
Click to collapse
I doubt it.
What are you using to flash? It sounds as if you're using TWRP and trying to mount an encrypted /data.
ianmacd said:
I doubt it.
What are you using to flash? It sounds as if you're using TWRP and trying to mount an encrypted /data.
Click to expand...
Click to collapse
Yeah I'm using TWRP. Should i not?
Blank. said:
Yeah I'm using TWRP. Should i not?
Click to expand...
Click to collapse
You can't mount /data from TWRP without without removing encryption first, which would entail a full wipe.
Use FlashFire instead. This runs from the booted OS, so any file-system encryption is transparent.
Sent from my rooted Galaxy S7 Edge using Tapatalk.
ianmacd said:
You can't mount /data from TWRP without without removing encryption first, which would entail a full wipe.
Use FlashFire instead. This runs from the booted OS, so any file-system encryption is transparent.
Sent from my rooted Galaxy S7 Edge using Tapatalk.
Click to expand...
Click to collapse
Thanks a lot. I tried flashing it and it said it couldn't be mounted. It finished quickly so i could only catch a glance of it. According to the link your gave me SDK23 is for Android Version 6.0.1 which is correct. What i'm not sure is my OS. It stated that ARM64 is for S7 but is there any chance that ARM might work for me ( provided it wouldn't bootloop)? Sorry for being a pain in the ass!
Blank. said:
What i'm not sure is my OS. It stated that ARM64 is for S7 but is there any chance that ARM might work for me ( provided it wouldn't bootloop)?
Click to expand...
Click to collapse
No chance. You need arm64.
Sent from my rooted Galaxy S7 Edge using Tapatalk.
ianmacd said:
No chance. You need arm64.
Sent from my rooted Galaxy S7 Edge using Tapatalk.
Click to expand...
Click to collapse
Alright. Thanks a lot for the replies mate. I guess i'll try my luck with the next version or just wait for a compatible xposed for 6.0.1 that'll probably take years haha.
Blank. said:
I guess i'll try my luck with the next version or just wait for a compatible xposed for 6.0.1 that'll probably take years haha.
Click to expand...
Click to collapse
You should be able to flash it with FlashFire. I have a G935F and this is how I upgrade Xposed every time a new version comes out.
Whatever problem you have, you should get to the bottom of it now, because you'll still have it when the next version of Xposed is released.
Sent from my rooted SM-T710 using Tapatalk.
ianmacd said:
You should be able to flash it with FlashFire. I have a G935F and this is how I upgrade Xposed every time a new version comes out.
Whatever problem you have, you should get to the bottom of it now, because you'll still have it when the next version of Xposed is released.
Sent from my rooted SM-T710 using Tapatalk.
Click to expand...
Click to collapse
Hmmm. Alright so I've started using Flashfire , and added 'xposed-v85-sdk23-arm64.zip' into the action , with the options of 'Mount /system read/write' and 'Preserve recovery' and i click Flash. It reboots , I install the Xposed 3.0 alpha4. Then there's red words asking if i installed the framework / rebooted it.
Blank. said:
Hmmm. Alright so I've started using Flashfire , and added 'xposed-v85-sdk23-arm64.zip' into the action , with the options of 'Mount /system read/write' and 'Preserve recovery' and i click Flash. It reboots , I install the Xposed 3.0 alpha4. Then there's red words asking if i installed the framework / rebooted it.
Click to expand...
Click to collapse
Uncheck Mount /system read/write and reflash. That ought to fix it.
Related
This is SuperSU that installs always in System-Mode.
Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip
Changelogs here & here
Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT
binaries failed to update
Just installed the lastest security update (6.01) from google on my nexus 6. Flashed v2.66 and binaries will not update. Any suggestions?
Thanks My Brother ?
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
aufarxda said:
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
Click to expand...
Click to collapse
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
fpqc said:
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
Click to expand...
Click to collapse
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
aufarxda said:
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
Click to expand...
Click to collapse
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
fpqc said:
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
Click to expand...
Click to collapse
Well, just reflash last update before this one.
Or, just wait another update with the fix.
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
FernBch said:
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Click to expand...
Click to collapse
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Droidphilev said:
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Click to expand...
Click to collapse
Nice to know.
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
slick97477 said:
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
Click to expand...
Click to collapse
Don't know. Maybe install the app on the zip manually. Update the binary and if updating fails, full unroot and re-root with the new zip.
krazyace35 said:
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
aufarxda said:
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Click to expand...
Click to collapse
Cool thanks for the info
Sent from my HTC One M9 using Tapatalk
---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
krazyace35 said:
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe not avaiable for your phone.
But most Marshmallow phone devs already made custom kernels for their phones.
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
KreAch3R said:
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
Click to expand...
Click to collapse
I moved v2.52 script with little modifications (aside from the ui_print).
I am not sure if there has already been a thread to this issue, if there is please direct me to it.
I am currently using a rooted Galaxy S5 (T-Mobile) Android version 5.0. I have installed Exposed using TWRP recovery with a . I have run into an issue when i reboot my phone. It gets lockedup in the boot screen ( sometimes it will get locked up on the Samsung screen and others it will get locked on the T-mobile screen)
Can someone please direct me to either a helpful thread or assist me on this issue i would be grateful.
You are already in xposed general, you just have to scroll for the right topic for you... There are unofficial versions for your device... See what works for your setup...
Sent from my HTC One M9 using Tapatalk
the error that comes up when installing Expose reads
" E:Error executing updater binary in zip '/external sd card/xposed-v79.0-sdk22-arm-custom-build-by-wanam20151217.zip
????
i have found the correct files that i believe to work. one last question.
will it work on TWRP or do i have to install CWM?
tumtum83 said:
i have found the correct files that i believe to work. one last question.
will it work on TWRP or do i have to install CWM?
Click to expand...
Click to collapse
TWRP is recommended for installing Xposed.
tumtum83 said:
the error that comes up when installing Expose reads
" E:Error executing updater binary in zip '/external sd card/xposed-v79.0-sdk22-arm-custom-build-by-wanam20151217.zip
Click to expand...
Click to collapse
You said your ROM is on Android 5.0, that's SDK21, not SDK22. You must install Exposed for SDK21. And use the custom version which doesn't cause bootloops.
MI3W 64GB/Tapatalk
I have unpdated my phone to 5.1.1 that should be sdk22 correct!?
tumtum83 said:
I have unpdated my phone to 5.1.1 that should be sdk22 correct!?
Click to expand...
Click to collapse
Yes, that's correct.
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread
Oh wowww. Thanks!!
Error in the thread title: 2015.8.4
Yay it's finally here!
I'm already using it and I must say it works fine
Man, this "universal MultiROM support" left me full of hope. I hope it works out. And it was time for a mods manager on Android, thanks topjohnwu
Working great on my N6!
topjohnwu has my vote for President!
(and a well deserved donation)
AMAZING!, now to be sure, if i have a rom and want to integrate Magisk, the correct order of flashing is:
1-rom
2-magisk
3-modded su (magisk compatible)
it's that the way?
topjohnwu said:
....Magisk Is A Magic Mask to Alter System Systemless-ly.
If you are running custom roms, dirty flash the rom again to remove all possible issues. If the rom includes SuperSU, unzip the boot image from the rom zip, and flash it through TWRP, flashify, fastboot etc. to restore to stock ramdisk......
....... you can now download Magisk and flash to your device.
To remove Magisk, restore your boot image back (Magisk will backup your boot image automatically in /data/stock_boot(md5).img.gz), then delete /data/magisk.img.
Click to expand...
Click to collapse
is the following still applicable in the case of custom roms?
smohanv said:
1. Boot in to TWRP
2. go to Advanced / File Manager and delete folder named supersu
3. go to Advanced / Terminal and enter these two commandsecho SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersuThe first one forces systemless, the second prevents /su/xbin_bind from existing.4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.
5. Reboot device and enjoy systemless
6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".
7. I rebooted in to TWRP and flashed xposed 85.1 (also updated with 85.2 later) and installed the apk (Material design apk from this thread)
8. All done and my xposed works.....
Click to expand...
Click to collapse
Awesome....
Sent from my AO5510 using Tapatalk
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
So wait, before i get excited this means things like viper4android can be installed without messing with system?
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
Click to expand...
Click to collapse
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
grep_i said:
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock marshmallow, flashed via twrp, and yes i followed the op correctly. No custom kernel.
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ��
Click to expand...
Click to collapse
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Nezorflame said:
[/COLOR]
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Click to expand...
Click to collapse
The threads download section. Should i have downloaded from phhs thread?
swipp3r said:
The threads download section. Should i have downloaded from phhs thread?
Click to expand...
Click to collapse
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Nezorflame said:
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Click to expand...
Click to collapse
Thanks for trying bro.....
@topjohnwu this new "magisk" method. It doesn't allow Android Pay to work on custom roms like CyanogenMod does it? If I remove SU from CyanogenMod and use your root.
Magisk on (Yu Yureka) ARM64 device
i did a full clean wipe and then flashed rom, magisk and 'Magisk Compatible phh's SuperUser' - in that order. magisk manager app does not open.
Holy crap.. everything universal with support for extensions. This platform could be the beginning of a new era in mods. @topjohnwu amazing work. Don't want to be rude, but personally I think the name of the project is not as awesome as the project itself. "Magisk" sounds a bit cheesy.. :silly:
great work, will try it out soon! one little thing i noticed in the thread title...i guess it should be 2016
Model SM-T805
Model name GALAXY Tab S
Country Germany
Version Android 6.0.1
Changelist 8816210
Build date Tue, 09 Aug 2016 02:36:44 +0000
Security Patch Level 2016-07-01
Product code DBT
PDA T805XXU1CPH5
CSC T805OXA1CPH6
http://samsung-updates.com/details/74794/Galaxy_Tab_S_10.5_LTE/SM-T805/DBT/T805XXU1CPH5.html
https://mega.nz/#!SFEg0JaK!dUi3Wg6S5dhawuI6Z2a3YzpWgS3c_SuiuKC0pK5xdZU
* Mega link updated
Safar_Ibrahim said:
Firmware Version Info
(PDA: T805XXU1CPH5 CSC: T805OXA1CPH6 CHANGELIST: 8816210 BUILD DATE: 09.08.2016)
(Android security patch level: 01.07.2016)
http://samsung-updates.com/details/74794/Galaxy_Tab_S_10.5_LTE/SM-T805/DBT/T805XXU1CPH5.html
https://mega.nz/#!SFEg0JaK
Click to expand...
Click to collapse
Hi, i need the encrypt. code for download via Mega
Anyone have installed MM on T805?
@jarvis said:
Hi, i need the encrypt. code for download via Mega
Anyone have installed MM on T805?
Click to expand...
Click to collapse
I did and it's work great except Adaptive Storage. I tried via ADB and Essential Root app on both doesn't work.
I used Samfirm to download it
Sent from my SM-T815 using Tapatalk
NeWONEx said:
I did and it's work great except Adaptive Storage. I tried via ADB and Essential Root app on both doesn't work.
I used Samfirm to download it
Sent from my SM-T815 using Tapatalk
Click to expand...
Click to collapse
how did you flash this ? i have one file : T805XXU1CPH5_T805OXA1CPH6_T805XXU1CPH5_HOME.tar.md5
i put in which case in odin?
wil123 said:
how did you flash this ? i have one file : T805XXU1CPH5_T805OXA1CPH6_T805XXU1CPH5_HOME.tar.md5
i put in which case in odin?
Click to expand...
Click to collapse
You have to choose "AP" and boot your tab into Download mode.
Sent from my SM-T815 using Tapatalk
I just follow this guide.
http://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
And if it messes up this one.
http://forum.xda-developers.com/galaxy-tab-s/help/stuck-samsung-logo-t3067773
John.
wil123 said:
how did you flash this ? i have one file : T805XXU1CPH5_T805OXA1CPH6_T805XXU1CPH5_HOME.tar.md5
i put in which case in odin?
Click to expand...
Click to collapse
Root and xposed working fully??
NeWONEx said:
I did and it's work great except Adaptive Storage. I tried via ADB and Essential Root app on both doesn't work.
I used Samfirm to download it
Sent from my SM-T815 using Tapatalk
Click to expand...
Click to collapse
Are you getting an error from the above two methods? As an alternative to adaptive storage, does it support the ability to change storage location the way S7 does?
Not error message. When you do all steps nothing happened. I tried the same steps on my tab s2 and it's working fine. But here when you type sm partition disk:179,32 private nothing happening.
And Sdcard still portable.
NeWONEx said:
Not error message. When you do all steps nothing happened. I tried the same steps on my tab s2 and it's working fine. But here when you type sm partition disk:179,32 private nothing happening.
And Sdcard still portable.
Click to expand...
Click to collapse
That's very unfortunate, I was really looking forward to being able to use this feature. How about the ability to change storage location the way S7 does?
Title101 said:
I see. How about the ability to change storage location the way S7 does?
Click to expand...
Click to collapse
It's working fine.
NeWONEx said:
It's working fine.
Click to expand...
Click to collapse
That sounds promising. I don't have an S7 but my understanding is that a lot of apps can be moved using this method. I assume that once an app is moved to the SD card that all its data resides there and f it gets updated through the Google Play store that it will remain on the SD card. Are my assumptions correct? If so, are there any major downsides compared to adaptive storage other then the initial step of having to move the app?
Title101 said:
That sounds promising. I don't have an S7 but my understanding is that a lot of apps can be moved using this method. I assume that once an app is moved to the SD card that all its data resides there and f it gets updated through the Google Play store that it will remain on the SD card. Are my assumptions correct? If so, are there any major downsides compared to adaptive storage other then the initial step of having to move the app?
Click to expand...
Click to collapse
No, it's not like that . It's similar to lollipop when you move app to Sdcard (Obb file) still in internal storage not like adoptive storage. And as you know some apps don't support this feature. Like WhatsApp and many other apps.
I hope if I can figure out the way to activate Adoptive storage.
My tab is only rooted, stock recovery, but it cannot search for new firmware (systems detected as modified). So how can I update it to marshmallow without formatting data and settings?
zooster said:
My tab is only rooted, stock recovery, but it cannot search for new firmware (systems detected as modified). So how can I update it to marshmallow without formatting data and settings?
Click to expand...
Click to collapse
Is it systemless root ?
NeWONEx said:
Is it systemless root ?
Click to expand...
Click to collapse
Nope, stock root...
zooster said:
Nope, stock root...
Click to expand...
Click to collapse
If you download update from Samsung-update.com you can flash it via Odin. It should be one file.
And you won't lose anything except root.
But you have to Backup your data to Sdcard.
Tried Adoptive storage same method as S7 Edge but no luck, anyone got it working ?
Safar_Ibrahim said:
Tried Adoptive storage same method as S7 Edge but no luck, anyone got it working ?
Click to expand...
Click to collapse
Same here +1
Sent from my SM-T815 using Tapatalk
Anyone know if there will be release for the t800?
Sent from my SM-T800 using XDA-Developers mobile app
If I have formatted and installed with encryption disabled, what is the right way to get encryption back?
Can I just go into Settings>Security & Fingerprint>Encrypt Phone and enable it there?
Yup, that should do the trick. Didn't try on T3, but used same method on one of my prev phones.
Did that work?
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
AndreiVolk said:
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
Click to expand...
Click to collapse
I wonder if it works with a non oos rom though
stonew5082 said:
I wonder if it works with a non oos rom though
Click to expand...
Click to collapse
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
AndreiVolk said:
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
Click to expand...
Click to collapse
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
nicknacknuke said:
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
Click to expand...
Click to collapse
Root is not a problem neither. i did it with root enabled.
That twrp error is normal. When you boot in twrp it shows the error that it can't mount data because you're encrypted and you need to type in your password first.
I also suggest you to use blu_spark's twrp because it's always updated. The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
AndreiVolk said:
The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
Click to expand...
Click to collapse
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Didgeridoohan said:
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Click to expand...
Click to collapse
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
AndreiVolk said:
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
Click to expand...
Click to collapse
You were talking about the official builds... That's the official downloads from the official TWRP website (https://twrp.me). There's a world outside XDA as well...