Hello,
Wondering what would happen if device get stolen? I've just started, especially since recovery is so easily accessible. Basically, anyone can enter, wipe data and everything left and put a new system... All that he needs is an microSD. Or in my case, I left all .zip files on mine, so that he can even chose whether he'd like more stock 5.1.1 or existenz.
Sometimes I don't know why I bother with a screen lock at all...
Anyone has any idea about preventing boot into recovery? Locking the recovery? Would disabled debugging and unknown sources fix the problem? Encryption?
Sorry if such subject already exists, couldn't find one.
Cheers!
Preventing recovery boot isnt something not known to be able to do however there is a "Theme" for Twrp that allows a password to be loaded up before accessing it
For your phone being turned on you can use Google device manager and enable required settings on your phones
Envious_Data said:
Preventing recovery boot isnt something known to be able to do however there is a "Theme" for Twrp that allows a password to be loaded up before accessing it
For your phone being turned on you can use Google device manager and enable required settings on your phones
Click to expand...
Click to collapse
OH. Didn't know about that. I'll have to try that one.
Sent from Xperia Z2
Luckily not from an iPhone = Yesterdays technology at tomorrows prices
I'll try that too. Found something for locking for 2.8.6.0, hopefully it will work for 2.8.7.0 too.
If all recoveries are locked and the android as well, would it be possible for someone to flash another recovery on top of existent ones?
dennnic93 said:
I'll try that too. Found something for locking for 2.8.6.0, hopefully it will work for 2.8.7.0 too.
If all recoveries are locked and the android as well, would it be possible for someone to flash another recovery on top of existent ones?
Click to expand...
Click to collapse
Depends on how you install
Flashable zips typically erase the partition where as images being flashed via command need to be wiped before installing
Related
I unlocked and rooted my AT&T HTC One with the stock AT&T 4.3 image, installed TWRP 2.6.3.3 and rebooted into recovery. Due to restrictions from my company, I am required to have the partition encrypted. When I boot into TWRP, I enter the same password I use to decrypt the phone when I boot it from off. However, TWRP fails to accept the password and will not let me access the file system.
I have also tried using flashing the recovery to CWM 6.0.4.3 and using that only to have the same issue.
Ideally, I would like to be able to flash patches to remove both the AT&T bloatware and the 'Dial 611' check for tethering.
I have tried a few proposed solutions from XDA to the issue but still cannot get around it. If any has had success in getting around it, can you please post steps of what you did here for the sake of clarity?
Thank you!
shockidelica said:
I unlocked and rooted my AT&T HTC One with the stock AT&T 4.3 image, installed TWRP 2.6.3.3 and rebooted into recovery. Due to restrictions from my company, I am required to have the partition encrypted. When I boot into TWRP, I enter the same password I use to decrypt the phone when I boot it from off. However, TWRP fails to accept the password and will not let me access the file system.
Click to expand...
Click to collapse
I have the same issues. Did you find a solution?
I did not. I eventually wound up doing a reset of all data the phone, applied the ROM image I wanted and added things back.
i only found this one: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/247
and then i changed the Password with cryptfs.
But it doesn't work for me......
I have the same issue here... =\
roux. said:
i only found this one: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/247
and then i changed the Password with cryptfs.
But it doesn't work for me......
Click to expand...
Click to collapse
I was just searching for the same issue, and I stumbled upon that thread as well. Except there's now an additional post from mid-February with more details:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/247#issuecomment-34895111
Looks like HTC doesn't use the same encryption scheme as stock Android, but rather uses some specific HTC algorithm, so TWRP doesn't support it because it would be too much work to do so. Dissapointing, but also understandable. I've only just encrypted my device (in order to be able to check my Exchange email for work), and I didn't think about the TWRP no longer being able to access my data partition or the internal sdcard... Reading through some of the more recent comments, though, it's still possible future releases of TWRP (2.7+) may resolve the issue, though I just tried the most recent release (2.7.0.0) with no luck.
I have the same issue. I tried the most recent TWRP as of this writing, 2.7.1.1, and it still doesn't decrypt on my HTC One.
I've had this issue on mine as well. Simply decrypt storage within settings. Reboot in TWRP, flash patch, re-encrypt. Pain in the a$$ but it works for me.
atrixboy said:
I've had this issue on mine as well. Simply decrypt storage within settings. Reboot in TWRP, flash patch, re-encrypt. Pain in the a$$ but it works for me.
Click to expand...
Click to collapse
How do you mean "simply decrypt storage within settings" ?
ObadUl024 said:
How do you mean "simply decrypt storage within settings" ?
Click to expand...
Click to collapse
Go into settings and disable encryption within the main android OS. Reboot into recovery. Flash whatever you need. Reboot back into OS. Re enable encryption. Pain but it worked.
Is there a way to dynamically load/use a custom recovery on an Andoid phone (generally, any phone) without actually having to overwrite the phone's stock recovery? For example, by booting to stock recovery, flashing a zip file that will start up CWM/TWRP so you can use it temporarily, but stock recovery is still there and when you reboot the phone it will still be there? Sort of like using a Linux live cd.
Because I figure someone will probably ask, I'm asking about this because I have a phone that I want to get into that is protected by a pattern lock. I haven't examined it yet, but I am strongly expecting:
- No root
- No custom recovery
- No ADB debugging enabled
I know I can bypass the pattern lock from CWM/TWRP (rm /data/system/gesture.key)...but I would prefer to not have to do an overwrite of the recovery partition if it can be avoided. And whether or not this ends up being needed for this phone, it will be good to know for future reference.
Gromlakh said:
Is there a way to dynamically load/use a custom recovery on an Andoid phone (generally, any phone) without actually having to overwrite the phone's stock recovery? For example, by booting to stock recovery, flashing a zip file that will start up CWM/TWRP so you can use it temporarily, but stock recovery is still there and when you reboot the phone it will still be there? Sort of like using a Linux live cd.
Because I figure someone will probably ask, I'm asking about this because I have a phone that I want to get into that is protected by a pattern lock. I haven't examined it yet, but I am strongly expecting:
- No root
- No custom recovery
- No ADB debugging enabled
I know I can bypass the pattern lock from CWM/TWRP (rm /data/system/gesture.key)...but I would prefer to not have to do an overwrite of the recovery partition if it can be avoided. And whether or not this ends up being needed for this phone, it will be good to know for future reference.
Click to expand...
Click to collapse
Only recoveries like that are along the lines of SafeStrap, but is device specific and you already have to be rooted and booted into the OS to install that one. So, for what you need, no.
es0tericcha0s said:
Only recoveries like that are along the lines of SafeStrap, but is device specific and you already have to be rooted and booted into the OS to install that one. So, for what you need, no.
Click to expand...
Click to collapse
Actually, after randomly stumbling across some articles tonight...it appears that you can. At least on some phones, some of the time, with "fastboot boot recovery.img."
http://forum.xda-developers.com/showthread.php?t=2597788
Ah. I didn't think of that because usually you have to unlock the bootloader to do that, which on most phones also wipe them, void the warranty, and often leave some kind of marker that would be obvious. But it depends on the phone still. And it's not uncommon for those things to be disabled on updates too. Also, Samsungs don't have fastboot at all, so that wouldn't be an option for any of them.
Hey guys so I've been killing myself just trying to find ways to get my newly rooted xperia z2 phone to boot into recovery mode.
Essentially I followed this guide to the bone and successfully rooted my phone --> http://forum.xda-developers.com/xperia-z2/development/stock-d6502-23-1-0-726-complete-guide-t3085893
The big problem is whatever I do, no matter the selection of recovery apps(quickboot, twrp manager, etc.) I install I can never get back into recovery mode, my phone turns off and goes into normal bootup, even when I try to do manual recovery mode the light indicator on top doesn't show up and the phone ends up starting normally.
I have factory resetted my phone a couple of times to have a fresh start each time I try something new but nothing seems to work.
On top of that SDFix and it's other variants does not work on my phone, so I can't install any apps on my micro sdcard. I'm really at a loss for what to do here(been at it for 3 days now) so I'm seeking help.
I'm not sure what information to give but I'll try to give as much details as I can about my situation, I'm really desperate to have recovery and my sd card working normally as I am currently very limited with the stuff I want to do on my phone. :crying::crying:
Info:
Model Number: D6503
Android Version: 5.0.2
Kernel Version: 3.4.0-perf-g72984dd [email protected] #1
Build Number: 23.1.A.0.726
SuperSU Installed
Phone is factory reset and rooted.
No other mods & apps installed aside from pre-installed apps and SuperSU
I would very much appreciate it if someone can help me with this problem, thank you!! :cyclops::laugh:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
saedted said:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
Click to expand...
Click to collapse
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
disenx34 said:
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
Click to expand...
Click to collapse
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
ptmaniac said:
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
Click to expand...
Click to collapse
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
disenx34 said:
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
Click to expand...
Click to collapse
On stock rom / kernel only nut's dual recovery will work. IT will also disable sony ric for you in the process. check here: http://forum.xda-developers.com/showthread.php?t=2261606
On custom kernel you have to choose a kernel with the recovery you want and flash that (don't forget to unlock BL before or you'll end up with softbrick). Recovery managers won't work as there is no recovery partition on your device...
install latest version of nuts recovery for z2 and install it after finish phone well reboot into recovery
Then dont update busybox it well break recovery
I've got two devices which I'm unable to encrypt now, a Moto G 2nd Gen Dual Sim and a Lenovo S8-50 tablet.
With both, when I start the encryption process it just reboots normally. I thought it might be because I had CWM recovery installed on my Moto G, so I flashed back the stock recovery but it still does the same. With the S8-50, I've never installed a custom recovery, just rooted it. I also changed the DPI in build.conf but I doubt that could prevent it encrypting but I wouldn't have expected rooting it to affect it either.
So it doesn't seem to be the recovery that's used for encrypting as I thought, or at least not only the recovery, so what else does it rely on?
bump. Anyone able to help? I really want to encrypt my devices.
doveman said:
bump. Anyone able to help? I really want to encrypt my devices.
Click to expand...
Click to collapse
doveman said:
I've got two devices which I'm unable to encrypt now, a Moto G 2nd Gen Dual Sim and a Lenovo S8-50 tablet.
With both, when I start the encryption process it just reboots normally. I thought it might be because I had CWM recovery installed on my Moto G, so I flashed back the stock recovery but it still does the same. With the S8-50, I've never installed a custom recovery, just rooted it. I also changed the DPI in build.conf but I doubt that could prevent it encrypting but I wouldn't have expected rooting it to affect it either.
So it doesn't seem to be the recovery that's used for encrypting as I thought, or at least not only the recovery, so what else does it rely on?
Click to expand...
Click to collapse
The encryption is carried out by encryptfs module in kernel. Rest inside /system itself, its just the code to interact with this module.
Jaskaranbir Singh said:
The encryption is carried out by encryptfs module in kernel. Rest inside /system itself, its just the code to interact with this module.
Click to expand...
Click to collapse
Thanks, that's useful to know but I've definitely found in the past that after installing a custom recovery it's not possible to encrypt and the device just reboots normally, so I assumed it must need to boot into the stock recovery to carry out the procedure. However, with the stock recovery restored to my Moto G it still doesn't work and I've never changed the recovery on the S8-50, so what else could be causing it reboot normally instead of running the encryption process?
Is it possible to run the process from ADB instead or will it still need to reboot to start the process even doing that and just result in the same normal reboot instead?
Bump. Anyone able to help me fix this problem on both devices?
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.