OK so this is totally self inflicted. At some point I was dinking around in the settings and the device asked me if I wanted to set a pin at startup. I went along with it and did that thinking it was a good idea. What it seems to have done (besides the startup pin) is encrypted the phone. Now technically everything works I can just enter my pin to boot to ROM or TWRP. But I want to remove the encryption and for the life of me I cannot find how to do that.
Any help would be GREATLY appreciated.
Here are notes on my situation:
-yes i searched the internets and XDA and mostly found stuff about the Nexus and OnePlus devices
-under security settings it just says "encrypted" there is no option to decrypt
-i have tried wiping and even formatting to different formats on data and system partitions
-tried different roms as well
-this is a Axon 7 U device
-running TWRP 3.1.1-0
-ROMs RR and Dark Rom
-obviously boot loader unlocked
Thank You
DarkQuark said:
OK so this is totally self inflicted. At some point I was dinking around in the settings and the device asked me if I wanted to set a pin at startup. I went along with it and did that thinking it was a good idea. What it seems to have done (besides the startup pin) is encrypted the phone. Now technically everything works I can just enter my pin to boot to ROM or TWRP. But I want to remove the encryption and for the life of me I cannot find how to do that.
Any help would be GREATLY appreciated.
Here are notes on my situation:
-yes i searched the internets and XDA and mostly found stuff about the Nexus and OnePlus devices
-under security settings it just says "encrypted" there is no option to decrypt
-i have tried wiping and even formatting to different formats on data and system partitions
-tried different roms as well
-this is a Axon 7 U device
-running TWRP 3.1.1-0
-ROMs RR and Dark Rom
-obviously boot loader unlocked
Thank You
Click to expand...
Click to collapse
Remove your PIN and then add it back but this time when it asks you if you want the startup pin choose no thanks.
Startup pin IS encryption.
bkores said:
Remove your PIN and then add it back but this time when it asks you if you want the startup pin choose no thanks.
Startup pin IS encryption.
Click to expand...
Click to collapse
I had tried that earlier and it did not work. What did work was doing doing a format data in twrp. I think mine was just stuck.
DarkQuark said:
I had tried that earlier and it did not work. What did work was doing doing a format data in twrp. I think mine was just stuck.
Click to expand...
Click to collapse
i believe that's the only way to decrypt the phone. You can have your phone encrypted without jt asking for a pin or pattern and startup, and it happens every damn time you forget to flash supersu or magisk on first boot. If you flash another ROM later you'll have to format data, or it will fail if it is encrypted.
If your phone has TWRP I suggest that you go to it and format data, then install supersu/magisk via sideload or an sd card or otg without rebooting.
Related
I'm on 4.2.2, unlocked and rooted. Decided to encrypt tablet the other day and have had issues since. I can get past the encryption PIN without issue, but 90% of the time I'm locked out of the lock screen PIN, with a message of wrong PIN.
I want to do a factory reset, but when I do manage to get into the device (sometimes entering no PIN works), when I get to the confirmation to factory wipe it refuses my PIN. I also cannot change my PIN because it refuses to accept my PIN. Yes, I'm certain I'm using the correct PIN.
Can't do a factory reset because Clockworkmod can't mount the SD card due to the encryption. Should I uninstall Clockworkmod and try that? I just don't want to end up bricking or totally locking myself out if there is another route I should take.
You could try flashing stock and then format /data and /userdata using fastboot
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
You could try flashing stock and then format /data and /userdata using fastboot
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Thanks. Should I be able to do that even though the SD card is encrypted? I have done a fair amount of Googling around, but have not found a lot of information about encrypted devices and issues.
-----------------------
I ended up formatting all storage partitions, and wiping cache, then took about 2 hours to get ADB working correctly, but was finally able to sideload a new image.
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
GMX1PT said:
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
Click to expand...
Click to collapse
On man I'm in totally the same situation with you! I tried that dualboot too and stuck in boot screen, so i flashed the original rom zip and managed to boot well but the fingerprint isn't working any more......:crying:waiting for solutions
Okay, now that I woke up I will try to do a data wipe, I'll tell you about it, please do tell me if you find something
I'm also unable to activate wifi
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
ab7casper said:
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
Click to expand...
Click to collapse
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
GMX1PT said:
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
Click to expand...
Click to collapse
It's not, it was just a user having that issue on a Nexus 6P. Reset should fix. Set it up without a lock on it, then you should be able to set up fingerprints for each rom.
Thinking about. It, that sounds like a lot of hassle if you just want to try out different roms quickly.
GMX1PT said:
I'm also unable to activate wifi
Click to expand...
Click to collapse
I did not do this dual boot but I ran into WiFi not activating (endless searching for a WiFi access point), but I was able to fix it. Your probably uninterested in how I got into the situation but I fixed it with a previous nandroid backup done with one of the earlier versions of TWRP. Here are the steps that recovered WiFi:
Using TWRP, advance wipe Dalvik & Cache
Restore from a nandroid backup (OOS v4.5.2 in this case) ONLY system & /System
Reboot into the system and ignore TWRP's no OS warning
Using TWRP, advance wipe Dalvik & Cache
Reboot back into TWRP recovery and flash the Full v4.5.5 OTA file (~1.6GB) AND flash root (e.g. SuperSU)
Clear Dalvik&Cache and reboot into the system
After I did that everything return back to normal including the WiFI issue. The fingerprint scanner is working normally and I never lost any data what so ever.
Hello, so i was running @xXx 9.1 and i decided to update to 9.2. So I simply dirty flashed (which should normally work) and rebooted. However I was stuck on the booting logo for ages to I bootted back to TWRP to try and reflash, however when I got to TWRP, everything was encrypted (sdcard/ was full of nonsense which looks like encrypted files). However it didn't ask for my password as it usually did and I can't find a single way to manually decrypt. Does anyone know what I can do to not loose ALL my data?! I backup via Titanium Backup as I usually do incase of a data problem but my entire internal storage is not accessible.
Hope someone can help!
just flash stable oos5 firmware+modem, phone should boot and able to decrypt.
Im_Mattgame said:
Hello, so i was running @xXx 9.1 and i decided to update to 9.2. So I simply dirty flashed (which should normally work) and rebooted. However I was stuck on the booting logo for ages to I bootted back to TWRP to try and reflash, however when I got to TWRP, everything was encrypted (sdcard/ was full of nonsense which looks like encrypted files). However it didn't ask for my password as it usually did and I can't find a single way to manually decrypt. Does anyone know what I can do to not loose ALL my data?! I backup via Titanium Backup as I usually do incase of a data problem but my entire internal storage is not accessible.
Hope someone can help!
Click to expand...
Click to collapse
same problem any answer?
Suraxit said:
same problem any answer?
Click to expand...
Click to collapse
What version of TWRP are you running. This is an old thread.
Could someone help me fix my OnePlus5?
Simply from one day to the other the Touch screen stopped working, I can not select any option, being possible only by physical button.
I can not enter Recovery Mode because when I first connected the device I have already entered a password, so I can not type the password because the touch does not work.
I do not know what else to do!!!
I have the OTG cable from OnePlus and even putting Mouse or Keyboard, both do not work.
Would anyone have other suggestions?
Follow the compressed video showing the recovery mode locked by password, touch does not work.
And photo from FastBoot Mode Screen.
Any updates on how you fixed this or what the problem was?
I had to RMA, motherboard was replaced.
I have the same problem
My screen stoped working and the recovery mode is protected with password like the video sent, i live in Brazil and here i dont have the RMA option, can someone help me?
_-^SORCERER^-_ said:
Could someone help me fix my OnePlus5?
Simply from one day to the other the Touch screen stopped working, I can not select any option, being possible only by physical button.
I can not enter Recovery Mode because when I first connected the device I have already entered a password, so I can not type the password because the touch does not work.
I do not know what else to do!!!
I have the OTG cable from OnePlus and even putting Mouse or Keyboard, both do not work.
Would anyone have other suggestions?
Click to expand...
Click to collapse
i was facing this and fixed it.
just use unbrick tool
after the phone boot up and touchscreens still doesn't work, just do a reboot
Tks @Apayah, Will try this procedure, and return with status.
@Apayah, theoretically OnePlus 5 returned works, I will wait a few days to see if the problem continues.
Thank you so much.
edujmjr said:
My screen stoped working and the recovery mode is protected with password like the video sent, i live in Brazil and here i dont have the RMA option, can someone help me?[/QUOTE @edujmjr I used the unbrick process and now works.
Try this process.
Enviado de meu ONEPLUS A5000 usando Tapatalk
Click to expand...
Click to collapse
_-^SORCERER^-_ said:
@Apayah, theoretically OnePlus 5 returned works, I will wait a few days to see if the problem continues.
Thank you so much.
Click to expand...
Click to collapse
Np, all good now?
Apayah said:
Np, all good now?
Click to expand...
Click to collapse
At this moments, yes, I will wait more days.
Thanks for your support in this problem.
_-^SORCERER^-_ said:
At this moments, yes, I will wait more days.
Thanks for your support in this problem.
Click to expand...
Click to collapse
no problem
Apayah said:
i was facing this and fixed it.
just use unbrick tool
after the phone boot up and touchscreens still doesn't work, just do a reboot
Click to expand...
Click to collapse
I'm facing the same issue . My phone was working perfectly fine one minute and then the next, the screen stopped responding including the two capacitive buttons. I rebooted it thinking it mgiht fix it, but now i"m stuck on the lockscreen.
Could you point me to the unbrick tool? Is it this one:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Does it do a factory reset or would it fix the unresponsive touchscreen issue without any loss of data?
CoCoGirl886 said:
I'm facing the same issue . My phone was working perfectly fine one minute and then the next, the screen stopped responding including the two capacitive buttons. I rebooted it thinking it mgiht fix it, but now i"m stuck on the lockscreen.
Could you point me to the unbrick tool? Is it this one:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Does it do a factory reset or would it fix the unresponsive touchscreen issue without any loss of data?
Click to expand...
Click to collapse
your bootloader unlocked ?, if you're on twrp, then do a back up via mtp.
yes i was use that one, well i was do factory data reset and still touchscreen was didn't work, i was still on twrp so i backing up all my data before i mess with it.
I've also had this issue already had the MB replaced but I had my new MB lost touch for about 5min today so i'll see if it gets worse like it did last time.
Apayah said:
your bootloader unlocked ?, if you're on twrp, then do a back up via mtp.
yes i was use that one, well i was do factory data reset and still touchscreen was didn't work, i was still on twrp so i backing up all my data before i mess with it.
Click to expand...
Click to collapse
I got an usb-c to OTG cable and was able to use the mouse in trwp. I followed a guide online to get past the lockscreen by deleting the lockscreen key files. After I did that, my screen just magically started working again. But now when I boot into the phone, it swipes to unlock but I can't access anything. It looks like it may be encrypted or something? I tried to set a new password to a pin/pattern but it won't save.
When I boot into trwp, it asks me to enter a password but I never had one? I tried using "default_password" and also using the numbers to represent the pattern but still doesn't work. Any idea how I can access my files or get my phone to boot up fully? I'm trying to avoid a factory reset, :crying:
CoCoGirl886 said:
I got an usb-c to OTG cable and was able to use the mouse in trwp. I followed a guide online to get past the lockscreen by deleting the lockscreen key files. After I did that, my screen just magically started working again. But now when I boot into the phone, it swipes to unlock but I can't access anything. It looks like it may be encrypted or something? I tried to set a new password to a pin/pattern but it won't save.
When I boot into trwp, it asks me to enter a password but I never had one? I tried using "default_password" and also using the numbers to represent the pattern but still doesn't work. Any idea how I can access my files or get my phone to boot up fully? I'm trying to avoid a factory reset, :crying:
Click to expand...
Click to collapse
Ahh i never facing like that, try using multirom twrp ? At least at this moment you need to backup you're data.
You mean lockscreen thingy on data/system? There's a 3 files i guess and if you delete that, yes you can pass your screen.
I have no idea if twrp asked for a password, before this happened you're decrypted or encrypted? Password on twrp only for encrypted i think
Apayah said:
Ahh i never facing like that, try using multirom twrp ? At least at this moment you need to backup you're data.
You mean lockscreen thingy on data/system? There's a 3 files i guess and if you delete that, yes you can pass your screen.
I have no idea if twrp asked for a password, before this happened you're decrypted or encrypted? Password on twrp only for encrypted i think
Click to expand...
Click to collapse
I deleted the 5 files in data/system and passed the lockscreen. But it doesn't let me see any information . I think I was probably encrypted since I don't believe I decrypted anything. I can't backup my data in twrp because without entering the password my files have a lot of folders that look like "WDAbwwoefdFZZfde." Before I deleted the keys, twrp asks me to enter my password which is a pattern, same one as when i start my phone. After I deleted the lockscreen keys, trwp asks me to type a password from letters or numbers.
Do you think if I were to dirty flash my rom again without wiping, that it will recreate the lock keys and decrypt my data? Without having to use multirom twrp?
CoCoGirl886 said:
I deleted the 5 files in data/system and passed the lockscreen. But it doesn't let me see any information . I think I was probably encrypted since I don't believe I decrypted anything. I can't backup my data in twrp because without entering the password my files have a lot of folders that look like "WDAbwwoefdFZZfde." Before I deleted the keys, twrp asks me to enter my password which is a pattern, same one as when i start my phone. After I deleted the lockscreen keys, trwp asks me to type a password from letters or numbers.
Do you think if I were to dirty flash my rom again without wiping, that it will recreate the lock keys and decrypt my data? Without having to use multirom twrp?
Click to expand...
Click to collapse
Right seems encrypted problems, did you try multirom twrp yet? Should be on GZR xda thread
My OnePlus 5 stop Work again.
Enviado do meu iPhone usando Tapatalk
I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.
Flapjack said:
I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.
Click to expand...
Click to collapse
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?
Choose an username... said:
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
Click to expand...
Click to collapse
I don't remember exactly... nothing I haven't frozen on their phones before.
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?
Click to expand...
Click to collapse
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?
Flapjack said:
I don't remember exactly... nothing I haven't frozen on their phones before.
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?
Click to expand...
Click to collapse
well, if you wiped and installed everything again it should work...
Something must have been wrong with the ROM itself. I don't get it, since it worked fine the first install. I installed AOSP instead and it booted right up. I'm going to take a full backup, freeze the things I normally freeze, then see what happens.
I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.
beokabatukaba said:
I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.
Click to expand...
Click to collapse
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot
Choose an username... said:
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot
Click to expand...
Click to collapse
You misunderstand. I could only boot RR once, and if I accidentally encrypted the device during setup or afterward, the next time I tried to restart, it would be stuck on the boot screen. All subsequent reinstalls also got stuck on the boot animation since I wasn't removing encryption even if I wiped data, system, cache, etc. Moving to AEX allowed me to boot with encryption, and it was at that point that I realized my mistake. That sounds precisely like what is happening to flapjack, except that the cause may or may not be the same since he got through multiple boots the first time and presumably had already setup a pin/password on one of the first boots.
Immediately after the pin is setup should be when it asks if you want to require the pin on startup (aka if you want to encrypt), so if he opted to do that after setting everything up rather than on the very first boot, he may have exactly the same issue I had.