On a2017u b35, flashed supersu zip 2.82 in two without problem,but when I run supersu, it says root undetected. How to fix this? Thanks
Try magisk 14.3 instead :3
Try SuperSU 2.79 and see if that works.
ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
marcdw said:
Try SuperSU 2.79 and see if that works.
ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
Click to expand...
Click to collapse
Tried 2.79 it is the same.
J0nhy said:
Try magisk 14.3 instead :3
Click to expand...
Click to collapse
I tried 15.3 and 16 before, install is OK, running is also OK, I but magisk cannot retain the root request after reboot, i.e. it still prompt the root request pop-up when app runs.
xdataibai said:
On a2017u b35, flashed supersu zip 2.82 in two without problem,but when I run supersu, it says root undetected. How to fix this? Thanks
Click to expand...
Click to collapse
I had the same issue with raystef66"s B35 7.1.1.][stock] SL!M¹ DF!NR. I eventually just went with Magisk.
patio54 said:
I had the same issue with raystef66"s B35 7.1.1.][stock] SL!M¹ DF!NR. I eventually just went with Magisk.
Click to expand...
Click to collapse
Which version magisk? I tried 15.3 and 16,both have the issue that not remember the root request after reboot,i.e. it will prompt again when app runs
xdataibai said:
Which version magisk? I tried 15.3 and 16,both have the issue that not remember the root request after reboot,i.e. it will prompt again when app runs
Click to expand...
Click to collapse
15.3 , I couldn't pass safteynet with 16. I did have to reflash the Magisk zip occasionally to re-root. Don't know why.
You might want to check in TWRP to see if the data and other partitions are formatted as ext4. Myself and a couple of others had a similar problem on Project New World and finally figured out that Magisk didn't like the partitions formatted as F2FS. Once formatted to EXT4 everything ran fine.
robertbarber said:
You might want to check in TWRP to see if the data and other partitions are formatted as ext4. Myself and a couple of others had a similar problem on Project New World and finally figured out that Magisk didn't like the partitions formatted as F2FS. Once formatted to EXT4 everything ran fine.
Click to expand...
Click to collapse
I will check it out, if it is f2fs and I format it as ext4, can I restore twrp back,will restore put the format back? Which partitions should I check beside data? Thanks
robertbarber said:
You might want to check in TWRP to see if the data and other partitions are formatted as ext4. Myself and a couple of others had a similar problem on Project New World and finally figured out that Magisk didn't like the partitions formatted as F2FS. Once formatted to EXT4 everything ran fine.
Click to expand...
Click to collapse
How do I check it? In twrp, didn't see the partition format shown in any options. Thanks
Its been a while and I am not on the Axon anymore but I checked all the partitions that I could, Some will not allow you to change them like cache and one or two others but the rest should be able to show you how they are formatted. As for restoring files I think it will restore it to whatever file system you had before because that's what it was saved as but I am not 100% sure on that. Someone may know more about that than I do. For how to go about checking the partitions to see how they are formatted this YouTube video should be able to give you a guide as to what to do. TWRP may have updated since it was made but it should be able to work for you. You just want to format it as EXT4 if its formatted as F2FS https://www.youtube.com/watch?v=8AbU_2z07Vg
I've never had an issue with F2FS data partition and Magisk/SuperSU. TWRP can format /data,/cache, and /system as F2FS. You just have to look a bit harder, it's in the repair/change filesystem options.
Thanks, it turns out that /data is f2fs,others are ext4. I format data to ext4. Then magisk can retain setting changes now, even though still cannot remember root request after reboot. And adaway works now. Thanks.
Thanks, it turns out that /data is f2fs,others are ext4. I format data to ext4. Then magisk can retain setting changes now, even though still cannot remember root request after reboot. And adaway works now. Thanks.
Related
Hi, thanks for all the information here.
Thanks to the guides, I was able to downgrade, backup TA, upgrade, build personal kernel, install twrp, working android pay.... everything is good. But:
I have tested out some modules for Magisk, two I wanted to use boot me in a boot loop/stuck on boot.
I can fix this using TWRP, I just use mount_magisk stored in my download on internal storage.
Then I disable the 'bad' module, by typing in the terminal: /magisk/<module folder>/disable
BUT!
This only works because my data is decrypted.
I want to encrypt my data.
It is true we still don't have a TWRP that supports our encryption?
If I encrypt, is there anyway to disable a bad magisk module?
I think magisk is stored in the boot, correct? So it is not in data, so it does not matter if data is encrypted or not?
I hope someone can clear up some of my worries.
Thanks
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
Ok, so if I wanted to recover my system, I could just reflash boot (my kernel)?
I would have to install magisk again but that is ok.
But would I even be able to install magisk if my data is encrypted?
I think v12 can be installed if no access to /data, but v13 not?
Thanks
ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
I don't have an encrypted partition. Could anybody with encrypted partition try it?
voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
Yes it does say that, but it is talking about fw version 34.1.A.1.198 - which is marshmallow right?
From what I understand TWRP was fine with XC's encryption in marshmallow, but with nougat it doesn't work.
So I think (that version of) TWRP will not work. (but I have not tested myself, but I read a post somewhere saying it didn't)
Hi everyone,
Just got my new G6, after much pain I managed to unlock the bootloader, install TWRP (v3.2.1.0) and to root it with SuperSU (stable release 2.82).
For now I'll keep the stock rom but I wanted to make a backup in case something went wrong with other tweaking I might do and I couldn't because TWRP couldn't "mount /system (device or resource busy)".
So I went into the mount menu and tried checking system but it just won't. I can mount it as read only but I can't mount it as writable.
If it's of any importance, I couldn't get magisk to install to root the phone and had to use SuperSU instead.
I could do the backup while mounting system as read only but I feel like it might be an issue in the future (for custom roms or even restoring the backup maybe ?) if I can't fix this issue.
So does anyone how to get TWRP to mount system as writable ? Thank you
Elvenstar said:
Hi everyone,
Just got my new G6, after much pain I managed to unlock the bootloader, install TWRP (v3.2.1.0) and to root it with SuperSU (stable release 2.82).
For now I'll keep the stock rom but I wanted to make a backup in case something went wrong with other tweaking I might do and I couldn't because TWRP couldn't "mount /system (device or resource busy)".
So I went into the mount menu and tried checking system but it just won't. I can mount it as read only but I can't mount it as writable.
If it's of any importance, I couldn't get magisk to install to root the phone and had to use SuperSU instead.
I could do the backup while mounting system as read only but I feel like it might be an issue in the future (for custom roms or even restoring the backup maybe ?) if I can't fix this issue.
So does anyone how to get TWRP to mount system as writable ? Thank you
Click to expand...
Click to collapse
Have you formatted data trough the dedicated option in TWRP? Format, not wipe, where you have to put "yes".
Anyway you can try with Melina's TWRP which solves many problems of the official one: https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Killua96 said:
Have you formatted data trough the dedicated option in TWRP? Format, not wipe, where you have to put "yes".
Anyway you can try with Melina's TWRP which solves many problems of the official one: https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Click to expand...
Click to collapse
I did try it once after the magisk install failed and I assumed it was because of that issue but I haven't tried yet with superSU correctly installed. Should I immediately try the backup after formatting or boot the phone once before ?
The issue I have with Melina's TWRP is that it's not compatible with fulmics and if I were to install any custom rom I think it would be that one (to keep stock camera mostly)
Elvenstar said:
I did try it once after the magisk install failed and I assumed it was because of that issue but I haven't tried yet with superSU correctly installed. Should I immediately try the backup after formatting or boot the phone once before ?
The issue I have with Melina's TWRP is that it's not compatible with fulmics and if I were to install any custom rom I think it would be that one (to keep stock camera mostly)
Click to expand...
Click to collapse
Format data, reboot recovery, and try to install magisk or mount system.
For Melina's TWRP it has NO problems with Fulmics, Zefie said that "officially" is not compatible because two users said that they have problems with that TWRP only with fulmics, i can assure you that with last version of both Melina's TWRP and Fulmics i never had problems like those two users, anyway you can try to use Melina's TWRP and if you have any problems just flash back the official twrp.
Killua96 said:
Format data, reboot recovery, and try to install magisk or mount system.
For Melina's TWRP it has NO problems with Fulmics, Zefie said that "officially" is not compatible because two users said that they have problems with that TWRP only with fulmics, i can assure you that with last version of both Melina's TWRP and Fulmics i never had problems like those two users, anyway you can try to use Melina's TWRP and if you have any problems just flash back the official twrp.
Click to expand...
Click to collapse
Alright so it's been a rough ride.
I formatted data, reboot TWRP and then indeed I was able to mount system as writable.
I then did my backup, which said it was successful and the only error it showed then was "unable to unmount /system"
I flashed magisk and rebooted into the normal system and the phone of course was back to factory settings and asked me my google account. Except that when I tried logging in it always showed me an error along the lines of "google play services keeps crashing". (making it impossible to get through the installation part of the system)
I'm not sure why that happened. I had frozen some apps but that shouldn't have been saved since I formatted data right ? and the phone was working perfectly fine before that.
But anyway I didn't really know what to do at that point so I just jumped the gun and downloaded and flashed fulmics.
It worked fine but only with supersu. For some reason magisk just doesn't want to get installed at all.
The rom itself worked fine but I had no root access by choosing magisk in the aroma installer so I wiped again and installed it again with supersu which works.
I also flashed xposed which is also working as intended.
So I'm all set for now I think.
Maybe when I need to wipe again I'll figure out why magisk doesn't work but for now I'm satisfied.
In any case, thank you for your help
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
It was released a few days ago, just go with custom or wait for working solution
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
No-verity didn't work for me but remove encryption.zip did.
this didn't work for me, it resulted in a bootloop
ric69 said:
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
Click to expand...
Click to collapse
fre78 said:
this didn't work for me, it resulted in a bootloop
Click to expand...
Click to collapse
Sorry for you. check Mount system or data or enable MTP. Internal storage was probably still at 0
I rebooted more than 10times it's ok here
zainbfaisal said:
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
Click to expand...
Click to collapse
sir may i ask how come ur able to have twrp .
how dd u install twrp on android 8.0 UK firmware?
thanks for help
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
OREO stock keeps encrypting DATA partition
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
NewbieFTW said:
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
Click to expand...
Click to collapse
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
skydivider said:
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
Click to expand...
Click to collapse
Magisk removes the encryption disabler .zip for some reason.
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
zainbfaisal said:
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
Click to expand...
Click to collapse
I'm sorry then, I don't know what to say. It worked for me.
I needed reinstal magisk after boot for root, but worked for me...
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
When this happend to me, i hit format data and typed yes, when i mount on TWRP i can see my storage again
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
miguelan.ruiz said:
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
Click to expand...
Click to collapse
Samsung Pay will, at the moment, probably never work again because it trips Knox.
For Samsung Health the fix is still the same: install a build.prop editor and change the value of RO.Config.Tima from 1 to 0.
not for me
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
doesn't work for me
Apparently there are 2 kind of users here.
One part did manage to install stock Oreo (BTU? other CSC?) , with root (magisk? superSu?) and a working TWRP (3.2.1?) which is not read-only on our beloved S7 Edge (SM-G935F)
The other part did not manage to setup this particular config.
It would be nice to have a detailed step-by-step guide from scratch by someone who managed to do it, so we can reproduce it.
I tried creating a system backup through TWRP just now for the first time ever. Throughout the process, it gave me multiple messages saying "unable to mount data" and the same for some other folders, and when the backup supposedly finished, it just said failed.
Is there anything I can try without actually wiping either of the partitions? This obviously because I'm trying to create a backup so I can wipe afterwards.
cyborgium said:
I tried creating a system backup through TWRP just now for the first time ever. Throughout the process, it gave me multiple messages saying "unable to mount data" and the same for some other folders, and when the backup supposedly finished, it just said failed.
Is there anything I can try without actually wiping either of the partitions? This obviously because I'm trying to create a backup so I can wipe afterwards.
Click to expand...
Click to collapse
In twrp main menu screen select ' Mount ' menu and make sure mount data is ticked then go back and try backing up again.
spawnlives said:
In twrp main menu screen select ' Mount ' menu and make sure mount data is ticked then go back and try backing up again.
Click to expand...
Click to collapse
Thanks for your reply, it doesn't actually let me tick that box. Nothing happens when I tick it. It also says that the data partition is 0mb. Any idea what that might mean?
cyborgium said:
Thanks for your reply, it doesn't actually let me tick that box. Nothing happens when I tick it. It also says that the data partition is 0mb. Any idea what that might mean?
Click to expand...
Click to collapse
Which version of twrp are you using
Latest is 3.2.3.0 which should fix the data issue ( it"s a known issue).
spawnlives said:
Which version of twrp are you using
Latest is 3.2.3.0 which should fix the data issue ( it"s a known issue).
Click to expand...
Click to collapse
That's the TWRP version that I've got installed.
I just reinstalled both stock firmware and reflashed TWRP but the exact same issue persists. At first I was able to mount data though, I could flash zips such as Magisk etc. But after having set everything up again on my phone, I couldn't mount data anymore.
cyborgium said:
That's the TWRP version that I've got installed.
I just reinstalled both stock firmware and reflashed TWRP but the exact same issue persists. At first I was able to mount data though, I could flash zips such as Magisk etc. But after having set everything up again on my phone, I couldn't mount data anymore.
Click to expand...
Click to collapse
Not sure on your steps to install twrp
Have you tried going into twrp in wipe menu and format data
spawnlives said:
Not sure on your steps to install twrp
Have you tried going into twrp in wipe menu and format data
Click to expand...
Click to collapse
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
cyborgium said:
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
Click to expand...
Click to collapse
Sounds like your device is still encrypted
Did you flash the no Verity encrypt zip file
Also I said to format data not wipe.
In the mount menu these are the options I have enabled.
spawnlives said:
Sounds like your device is still encrypted
Did you flash the no Verity encrypt zip file
Also I said to format data not wipe.
In the mount menu these are the options I have enabled.
Click to expand...
Click to collapse
You're right, I formatted data, not wipe.
I did flash the no verity zip, does the order in which I flash Magisk, no-verity and RMM state unlock matter?
cyborgium said:
You're right, I formatted data, not wipe.
I did flash the no verity zip, does the order in which I flash Magisk, no-verity and RMM state unlock matter?
Click to expand...
Click to collapse
The instructions I followed to install twrp
Flash twrp (which you have done)
Format data
When finished reboot back into twrp(use twrp reboot menu option)
Flash no-verity zip via twrp ( have to make sure you have it on internal storage or SD card)
Then flash everything else
Not sure if you need RMM state unlock if your bootloader(OEM) is already unlocked in developer options though.
spawnlives said:
The instructions I followed to install twrp
Flash twrp (which you have done)
Format data
When finished reboot back into twrp(use twrp reboot menu option)
Flash no-verity zip via twrp ( have to make sure you have it on internal storage or SD card)
Then flash everything else
Not sure if you need RMM state unlock if your bootloader(OEM) is already unlocked in developer options though.
Click to expand...
Click to collapse
I've just done everything you stated above, still the same issue, can't mount /data.
Really don't understand what it is that im doing wrong or if I'm even doing anything wrong..
Thanks for your help anyway though, appreciate it.
cyborgium said:
I've just done everything you stated above, still the same issue, can't mount /data.
Really don't understand what it is that im doing wrong or if I'm even doing anything wrong..
Thanks for your help anyway though, appreciate it.
Click to expand...
Click to collapse
Just as matter of curiosity I use FX file explorer (root) in the menu filesystem it should tell you what format your data partition is mine or ext4. I have read that some people through twrp have changed it to something like ext3 and then back to ext4
Also this is the thread I used to install my twrp
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
This thread may also help you out
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
spawnlives said:
Just as matter of curiosity I use FX file explorer (root) in the menu filesystem it should tell you what format your data partition is mine or ext4. I have read that some people through twrp have changed it to something like ext3 and then back to ext4
Also this is the thread I used to install my twrp
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
This thread may also help you out
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
Click to expand...
Click to collapse
I think that second thread you linked may have done the trick.
At first it didn't seem to help, but when I tried it again after reflashing everything, I am now able to mount /data.
I'm still in the dark as to why this happened and hasn't happened to anyone else other than the person who created that file, but either way, thank you very much for your help.
cyborgium said:
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
Click to expand...
Click to collapse
Try the modded twrp from nx thread
After doing the Tmo to international conversion, I downloaded a new rom and appropriate files. They show in ES File Explorer, but I am unable to locate them in TWRP. Anyone have this issue, I have to be missing something. Thanks in advance.
just put them in downloads and go there in twrp
Downloads folder literally doesn't exist in TWRP for me.
The whole file system looks different at / in TWRP than in ES explorer.
You need to mount sdcard/storage in TWRP
I have tried with no success. Under mount it won't even allow me to click the option to mount sd card. When I click sd card in the list I get a slew of folders with random character names (ie- ggDjkk7hFJJgGvV)
I have noticed in my oos system settings my phone shows encrypted. Could this be why? Is there a way to turn off encryption that I'm not seeing, if this is the cause?
Floridaplur said:
I have tried with no success. Under mount it won't even allow me to click the option to mount sd card. When I click sd card in the list I get a slew of folders with random character names (ie- ggDjkk7hFJJgGvV)
Click to expand...
Click to collapse
That means it's still encrypted. What version of TWRP are you using? My guess is you are using the wrong TWRP. You can try booting back into OOS and removing your PIN / Password / fingerprints.
Otherwise you may have to boot back into OOS, backup your data, and format the data partition. Reboot to recovery again, then transfer whatever you need to TWRP, flash, and it will re-encrypt on the next boot. Again though, make sure you have the correct TWRP first before you go through all this trouble.
I am using bluespark TWRP that was in the guide to Tmo intl conversion.
Floridaplur said:
I am using bluespark TWRP that was in the guide to Tmo intl conversion.
Click to expand...
Click to collapse
have u tried the other twrp builds that may be more up to date?
Floridaplur said:
I am using bluespark TWRP that was in the guide to Tmo intl conversion.
Click to expand...
Click to collapse
Yes, that one will give you the issue. The encryption did not seem to be working in it.
You should use the latest version of this recovery to resolve your issue: [RECOVERY][3.3.0-2][fajita]Official/Unofficial TWRP recovery for OnePlus 6T (Stable)
So after updating to twrp 3.2.2, I was successfully able to clean install havok and have everything working. What I have noticed though, is that after booting into the rom, it is encrypted again.
The first go I realized I had the wrong gapps, so I downloaded the correct one, and rebooted to recovery. At this point it was encrypted and I couldn't see downloads again. I decided to do a data and cache wipe and installed everything via adb sideload and it went perfectly. I guess this phone just wants me to only load roms when I have my laptop with me. Either way, I'm up and running. I miss how easy things we're back in the HTC Evo days.