I somehow got my filesystem encrypted when I flashed TWRP and rooted. When I try to boot into TWRP, I have to enter a password to be able to see anything or do any modifications. What happened?
I didnt have this problem on my Axon but googled.
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
I have no idea if this will help you or not but it will wipe data so your phone will be factory reset. Do at your own risk.
Twerkules said:
I somehow got my filesystem encrypted when I flashed TWRP and rooted. When I try to boot into TWRP, I have to enter a password to be able to see anything or do any modifications. What happened?
Click to expand...
Click to collapse
bhint15 said:
I didnt have this problem on my Axon but googled.
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
I have no idea if this will help you or not but it will wipe data so your phone will be factory reset. Do at your own risk.
Click to expand...
Click to collapse
This is from the Thread @bhint15 posted ,
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
and the reason why ask for password is cuz Axon 7 Data/Storage is Automatically encrypted out of the box, that's why you don't or not going to find any sort of encryption data setting under Settings and That's the reason a lot of users here have issues trying to get back to stock or something similar.....
This may give you some insight.
https://youtu.be/y0fHGJY-vFE
For me it's the Axon 7. I like the bigger res screen, the upcoming daydream compatibility and superior audio and non-Apple like OS.
The Honor 8 dies seem to have a better camera, but I can live with that. Plus I have an LG G5 for when I want photos.
You just have to decide witch Frasier is more important to you.
RojasTKD said:
This may give you some insight.
https://youtu.be/y0fHGJY-vFE
For me it's the Axon 7. I like the bigger res screen, the upcoming daydream compatibility and superior audio and non-Apple like OS.
The Honor 8 dies seem to have a better camera, but I can live with that. Plus I have an LG G5 for when I want photos.
You just have to decide witch Frasier is more important to you.
Click to expand...
Click to collapse
Wrong Thread mate LoL,
DrakenFX said:
Wrong Thread mate LoL,
Click to expand...
Click to collapse
What the neck how did u end up here....
Disregard ?
DrakenFX said:
This is from the Thread @bhint15 posted ,
and the reason why ask for password is cuz Axon 7 Data/Storage is Automatically encrypted out of the box, that's why you don't or not going to find any sort of encryption data setting under Settings and That's the reason a lot of users here have issues trying to get back to stock or something similar.....
Click to expand...
Click to collapse
Alright, I managed to be able to write to /system temporarily by formatting the Data partition in TWRP, then rebooting back into TWRP. However, after rebooting into OS and setting up my phone, I rebooted into TWRP and was faced with the encryption password prompt again! Does the filesystem just re-encrypt itself when you start the OS, or am I doing something wrong?
Twerkules said:
Alright, I managed to be able to write to /system temporarily by formatting the Data partition in TWRP, then rebooting back into TWRP. However, after rebooting into OS and setting up my phone, I rebooted into TWRP and was faced with the encryption password prompt again! Does the filesystem just re-encrypt itself when you start the OS, or am I doing something wrong?
Click to expand...
Click to collapse
I gave up for now. I tried for 4 days to fix this. In the end I have 30 days to return the phone. Hopefully someone will figure out a work around for this issue. I really like using twrp. I have not read a comment on here of anyone being able to boot into system then back into twrp with out having to enter a password to decrypt. I hope someone out there can do it and they figure out a way to fix it for the rest of us..
HonestOtter said:
I gave up for now. I tried for 4 days to fix this. In the end I have 30 days to return the phone. Hopefully someone will figure out a work around for this issue. I really like using twrp. I have not read a comment on here of anyone being able to boot into system then back into twrp with out having to enter a password to decrypt. I hope someone out there can do it and they figure out a way to fix it for the rest of us..
Click to expand...
Click to collapse
When does twrp prompt for password? I just booted into TWRP and it didn't prompt me. Then I simply booted back into the rom. Never prompted for a password.
runderekrun said:
When does twrp prompt for password? I just booted into TWRP and it didn't prompt me. Then I simply booted back into the rom. Never prompted for a password.
Click to expand...
Click to collapse
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Twerkules said:
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Click to expand...
Click to collapse
Which bootloader unlock did you do? I wonder, why would this not happen to me but happen to you? I am willing to test anything that needs to be tested.
You cannot fix that. Like DrakenFX said, the partition encrypts itself in the OS. You cannot disable/bypass this!
XblackdemonX said:
You cannot fix that. Like DrakenFX said, the partition encrypts itself in the OS. You cannot disable/bypass this!
Click to expand...
Click to collapse
Auto-encrypted can be disabled but that's way, way out of my league, need to rebuild boot. Img with that feature disabled.
There are two different scenarios that will be in play here. Is the bootloader unlocked or not. If the bootloader is unlocked then boot.img can be patched with the zip from idlekernle that disables the dm-verity and fstab. You cannot do this if your BL is locked, because it will modify the signed boot.img that that provides root, and will not boot anymore.
After it's patched, the system will not encrypt after /data wipe and TWRP will access it without problem. The downside is no encryption.
For the BL locked crowed, the /data has to be reformatted after flashing new rooted boot.img. This image also enforces encryption so one way to solve this would be for @tenfar to provide us with signed boot.img that set encryption of as well as. Otherwise the TWRP will need a password to decrypt /data if it can't use the default_password. In this case you should be able to enter the same pin you have setup for lock screen to decrypt the main encryption key.
The system re-encrypts itself on every system start after factory reset or /data format because of the forceencrypt flag in fstab, so the pin will be needed as long as that's the case. While TWRP should be able to try to decrypt with "default_password" in case you have not setup any on lockscreen, this sometimes fails, so having a pin on lockscreen usually helps. The cause is most likely that /cryptkey is altered somehow and TWRP can't use it. Wiping /data and rebooting should generate an fresh /cryptkey. I have been able to just flash modded recovery while still on stock boot and backup the /data with no key.
/system should not be encrypted ever since it would make block level OTA impossible to do. Why TWRP is not mounting it or seeing it 0b is a separate question.
Twerkules said:
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Click to expand...
Click to collapse
That would be dreamy. I have no issues waiting, fingers crossed.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
peramikic said:
There are two different scenarios that will be in play here. Is the bootloader unlocked or not. If the bootloader is unlocked then boot.img can be patched with the zip from idlekernle that disables the dm-verity and fstab. You cannot do this if your BL is locked, because it will modify the signed boot.img that that provides root, and will not boot anymore.
After it's patched, the system will not encrypt after /data wipe and TWRP will access it without problem. The downside is no encryption.
For the BL locked crowed, the /data has to be reformatted after flashing new rooted boot.img. This image also enforces encryption so one way to solve this would be for @tenfar to provide us with signed boot.img that set encryption of as well as. Otherwise the TWRP will need a password to decrypt /data if it can't use the default_password. In this case you should be able to enter the same pin you have setup for lock screen to decrypt the main encryption key.
The system re-encrypts itself on every system start after factory reset or /data format because of the forceencrypt flag in fstab, so the pin will be needed as long as that's the case. While TWRP should be able to try to decrypt with "default_password" in case you have not setup any on lockscreen, this sometimes fails, so having a pin on lockscreen usually helps. The cause is most likely that /cryptkey is altered somehow and TWRP can't use it. Wiping /data and rebooting should generate an fresh /cryptkey. I have been able to just flash modded recovery while still on stock boot and backup the /data with no key.
/system should not be encrypted ever since it would make block level OTA impossible to do. Why TWRP is not mounting it or seeing it 0b is a separate question.
Click to expand...
Click to collapse
Well i have formatted my data maybe 30 times with all sorts of different recoveries and boot images. My original boot image is long gone so hopefully that isn't the key. I also don't use a lock screen, I guess I could if it unlocks the data, but I certainly wouldn't want to keep using a lock screen. Anyways I am done with the phone for now, will revisit it when someone fixes posts they had the decrypt PW issue and fixed it.
HonestOtter said:
That would be dreamy. I have no issues waiting, fingers crossed.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
Well i have formatted my data maybe 30 times with all sorts of different recoveries and boot images. My original boot image is long gone so hopefully that isn't the key. I also don't use a lock screen, I guess I could if it unlocks the data, but I certainly wouldn't want to keep using a lock screen. Anyways I am done with the phone for now, will revisit it when someone fixes posts they had the decrypt PW issue and fixed it.
Click to expand...
Click to collapse
See if you can set the pin, go into TWRP and us it. If it works, go back to OS and remove lockscreen, set to none and then go back to TWRP and see if it still asks for one. Did you run TWRP in read only mode or did you swipe to mount as RW?
peramikic said:
See if you can set the pin, go into TWRP and us it. If it works, go back to OS and remove lockscreen, set to none and then go back to TWRP and see if it still asks for one. Did you run TWRP in read only mode or did you swipe to mount as RW?
Click to expand...
Click to collapse
I assume you mean the lock screen pin? I set a lock screen pin of 1234, but "password failed, please try again". So that didn't work. Is there a different pin for the encryption?
***update
That sucked. I don't use a lock screen but after I tried the pin it won't let be go back to none for the lock screen. I was just starting to use this phone to, now its back to the old phone because I can't use a phone with a lock screen . So sad. Hopefully someone figures out a solution to all this security crap.
I'm having the same issue on B27. Do a factory Reset, then a Format, and after it boots to the OS, the data is encrypted again. I'd be somewhat ok with it but I'm not clear on how to install things like Xposed if the drive is encrypted? I assumed ADB SIDELOAD... but not through encryption.
If the answer is "I don't know" -- then can someone help me restore to stock B27. I have a locked bootloader.
zigzampow said:
I'm having the same issue on B27. Do a factory Reset, then a Format, and after it boots to the OS, the data is encrypted again. I'd be somewhat ok with it but I'm not clear on how to install things like Xposed if the drive is encrypted? I assumed ADB SIDELOAD... but not through encryption.
If the answer is "I don't know" -- then can someone help me restore to stock B27. I have a locked bootloader.
Click to expand...
Click to collapse
Xposed should install just fine if you're getting the message in TWRP. Id you're getting the encryption message after the phone is booted and can't access the phone, then you need to format data, then install Xposed so you can use the phone.
Some zips like SuperSU zip will not be able to be installed when the partition is encrypted. Xposed zip should install just fine
mmamedov said:
Xposed should install just fine if you're getting the message in TWRP. Id you're getting the encryption message after the phone is booted and can't access the phone, then you need to format data, then install Xposed so you can use the phone.
Some zips like SuperSU zip will not be able to be installed when the partition is encrypted. Xposed zip should install just fine
Click to expand...
Click to collapse
But if TWRP cannot access the encrypted data, how can one select and flash the TWRP flashable zip that accompanies the Xposed APK? Is the only solution to sideload? I see the option in TWRP but I am not familiar with how to do it.
Related
I've been reading something that interested me.
https://www.reddit.com/r/MotoX/comments/2kx2lv/how_do_you_encrypt_a_rooted_moto_x/
Specifically.
I had the same issue today. Booted into safe mode, then I was able to encrypt.
Press power button to get power off popup menu. Press and hold power off. You will get another popup offering to reboot in safe mode.
Safe mode worked. This uncomplicates my process of rooting, unrooting, encrypting, and having issues rerooting after encryption. This is also a crazy easy single step process for an issue that has given me months of headaches.
You shall be the first person ever that I have given gold to.
Thank you so much!
Click to expand...
Click to collapse
I enter my password in the encryption settings menu and hit the Encrypt button
Click to expand...
Click to collapse
How would encryption effect flashing a new rom?
What are your guys thoughts on encryptimg a unlocked and rooted phone?
I do not want to enable it yet till it is comfirmed its ok.
Thanks.
Um I haven't had a problem and I've encrypted the software many times as I have installed many rooms and I always encrypt after setting everything up post root so it should just work without issue. Maybe they just weren't being patient and it can take a bit of time
timde9 said:
Um I haven't had a problem and I've encrypted the software many times as I have installed many rooms and I always encrypt after setting everything up post root so it should just work without issue. Maybe they just weren't being patient and it can take a bit of time
Click to expand...
Click to collapse
What about unencrypting? To say to flash a new kernel or rom?
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
timde9 said:
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
Click to expand...
Click to collapse
Ohh. Cool. I'll have to learn adb.
@timde9
I've got twrp installed.
To get to recovrry mode, do I go into recovery mode in twrp and then the recovery button in twrp to install packages m zips from adb?
to install packages via adb is pretty simple really you just open twrp go to advanced menu and open "adb sideload" from there. Then connect your device to your computer install adb and sideload an app with this syntax
"adb sideload ***.zip"
That is radical. Ty for this.
Encryption went like a breeze.
took no more than 20 min. I feel safe now.
timde9 said:
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
Click to expand...
Click to collapse
Just found out after encrypting twrp fails to mount data to backup. I might restore without encryption. That way I have access to backups on my phone too.
So I am having a problem restoring a backup. Since I cannot decrypt, to get rid of data from being locked down, do I flash with a rom? I am stuck.
Ok I have to do a factory reset. But not sure if this exists and works through twrp. Or if I have to do a factory reset some otherway.
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Hitti2 said:
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Click to expand...
Click to collapse
Is this ok to do? I don't want mess anything up.
Hitti2 said:
Is this ok to do? I don't want mess anything up.
Click to expand...
Click to collapse
That will erase all your data including files, apps, etc. Anything installed to /system should be untouched.
asuhoops8628 said:
That will erase all your data including files, apps, etc. Anything installed to /system should be untouched.
Click to expand...
Click to collapse
Thanks for confirming this. Exactly what I need when time comes to decrypt "wipe" I will use this.
I wasn't sure if it would delete the partition or wipe, this is why I asked.
Ty.
Hitti2 said:
Thanks for confirming this. Exactly what I need when time comes to decrypt "wipe" I will use this.
I wasn't sure if it would delete the partition or wipe, this is why I asked.
Ty.
Click to expand...
Click to collapse
Upon reading this again, just to be safe, you might want to start with just a fastboot erase. I think format does the same thing, but I have never used it.
Since you would be specifying the partition with both commands, I do not think you are in risk of completely blowing up your user partition if you choose to use fastboot format, but once again, I have always just used fastboot erase.
Hitti2 said:
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Click to expand...
Click to collapse
So I went to use this. I got an error.
Code:
Formatting is not supported for filesystem with type 'raw'
So now, that I am guessing, since twrp can now decrypt, I should just be able to go into twrp and do a full wipe and reinstall of the trupurexmm 2.5 And encryption should be gone?
Hitti2 said:
So I went to use this. I got an error.
Code:
Formatting is not supported for filesystem with type 'raw'
So now, that I am guessing, since twrp can now decrypt, I should just be able to go into twrp and do a full wipe and reinstall of the trupurexmm 2.5 And encryption should be gone?
Click to expand...
Click to collapse
Nope. Encryption is still enabled. I flashed trupurexmm 2.5 following
5. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Click to expand...
Click to collapse
I'm having an issue encrypting. Encryption will not start on my rooted moto x. I factory reset and encrypted, but could not get root working. Flashed everything via adb sideload in twrp but root refueses to work. Any ideas
Sent from my XT1575 using Tapatalk
I can't decrypt to mount with twrp. This worked for months prior to today after I updated to version 3.0.0.0. Now I cannot get in to flash anything. I have no password on boot or password at all and I have tried "default_password". No luck. Any suggestions?
SOLVED: Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
i dont know if this helps for you, but:
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
kaufikauf said:
i dont know if this helps for you, but:
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
Click to expand...
Click to collapse
Yea I saw that as I was searching for possible solutions. I was really hoping to wiping data
ryman222 said:
Yea I saw that as I was searching for possible solutions. I was really hoping to wiping data
Click to expand...
Click to collapse
just to get it exactly:
you just updatet TWRP? Nothing else?
How did you updatet?
kaufikauf said:
just to get it exactly:
you just updatet TWRP? Nothing else?
How did you updatet?
Click to expand...
Click to collapse
Correct, fastboot flash recovery recovery.img
ryman222 said:
Correct, fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Im really not sure about this,
but it could be that you have to install SuperSu and then it works
Can you boot your phone normally?
kaufikauf said:
Im really not sure about this,
but it could be that you have to install SuperSu and then it works
Can you boot your phone normally?
Click to expand...
Click to collapse
Yea boots fine runs like it always did. I might just completely wipe and see what happens.
I would try to install the new SuperSu first, if this doesnt work you can wipe later.
By the way it would be great if you post your results here, seems to be problem for older versions too.
kaufikauf said:
I would try to install the new SuperSu first, if this doesnt work you can wipe later.
By the way it would be great if you post your results here, seems to be problem for older versions too.
Click to expand...
Click to collapse
Installed, no luck.
Wiping now will report back...
EDIT: It did need to be formatted and reset.
When making a backup with twrp, what folder should be backed up? Boot, system, system IMG, vendor, vender IMG, data, cache? I need a back so I can restore current setup if I don't like this "Android N" beta update.
Before installing Android N, everything worked normally. Now it wants a password every time. Tried everything. I want to get my backup, but if I wipe data, it wipes the backup. If i transerf the backup to the phone after wiping (still in twrp), I am stuck on the Google logo. LOL
Edit: Now flashed twrp 3.0.0-1, looks fine. Copying backup to the phone.
ryman222 said:
I can't decrypt to mount with twrp. This worked for months prior to today after I updated to version 3.0.0.0. Now I cannot get in to flash anything. I have no password on boot or password at all and I have tried "default_password". No luck. Any suggestions?
SOLVED: Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
ryman222 said:
I can't decrypt to mount with twrp. This worked for months prior to today after I updated to version 3.0.0.0. Now I cannot get in to flash anything. I have no password on boot or password at all and I have tried "default_password". No luck. Any suggestions?
SOLVED: Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
The only way to save your data is to change the default password instance to an actual password and then flash TWRP
CitySlicka said:
When making a backup with twrp, what folder should be backed up? Boot, system, system IMG, vendor, vender IMG, data, cache? I need a back so I can restore current setup if I don't like this "Android N" beta update.
Click to expand...
Click to collapse
Only,
-Boot
-System
-Data
I do also cache recovery efs but not needed.
*Don't ever restore system image or vendor image.*
Works like a charm!
dontbeweakvato said:
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
The only way to save your data is to change the default password instance to an actual password and then flash TWRP
Click to expand...
Click to collapse
Thanks a ton @dontbeweakvato. This worked flawlessly, also posted your text in some other forums where people are still looking for answers You saved my data, thanks
didnt work for me
This is the only way works for my Nexus 6P.
https://www.youtube.com/watch?v=zpYVDJgusLo
will this wipe my rom
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
kickenwing13 said:
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
Click to expand...
Click to collapse
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
murphyjasonc said:
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
Click to expand...
Click to collapse
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
kickenwing13 said:
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
Click to expand...
Click to collapse
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
murphyjasonc said:
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
Click to expand...
Click to collapse
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
found something on a N6 thread that says wipe user data and it should work .
kickenwing13 said:
found something on a N6 thread that says wipe user data and it should work .
Click to expand...
Click to collapse
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
Are you by chance trying to restore a backup on your RMA?
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
I had a similar problem with TWRP 3.0.3-0 when I tried to restore a backup. It asked for a password, which has never happened before. I couldn't access my backup or any of my data or boot up. I had to restore stock. Clearing user data did nothing.
murphyjasonc said:
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
Are you by chance trying to restore a backup on your RMA?
Click to expand...
Click to collapse
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
kickenwing13 said:
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
Click to expand...
Click to collapse
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
martinomac said:
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
Click to expand...
Click to collapse
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
CyberpodS2 said:
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
Click to expand...
Click to collapse
Thanks for confirming, I wasn't aware that there's a difference between Format Data and Wipe Data. After formatting data, I should be able to sideload the ROM, gapps, etc back via TWRP right?
I always try to keep an emergency folder on the PC with the minimum needed to copy back to the phone through recovery. In my case I keep a copy of pure nexus, dynamic gapps, supersu and elementalx. That combination never fails to boot and I know it well enough to get back in business in short order if it all went to hell. Do what's best for you.
Sent from my Nexus 6 using XDA-Developers Legacy app
For some reason I cannot decrypt when booting TWRP. On a normal boot, I get the prompt to enter my PIN, I enter my PIN, and it boots. In TWRP it says "failure to decrypt."
I'm using 3.2.1-7 of TWRP, which worked before, but now it's unable to decrypt my internal data.
Halp?
Edit: I guess when I get home I'll install an older version of TWRP and see if that helps, but I am otherwise sunk.
TPMJB said:
For some reason I cannot decrypt when booting TWRP. On a normal boot, I get the prompt to enter my PIN, I enter my PIN, and it boots. In TWRP it says "failure to decrypt."
I'm using 3.2.1-7 of TWRP, which worked before, but now it's unable to decrypt my internal data.
Halp?
Edit: I guess when I get home I'll install an older version of TWRP and see if that helps, but I am otherwise sunk.
Click to expand...
Click to collapse
First thoughts : Backup internal and format data.
Perhaps try https://androidfilehost.com/?fid=818222786056030640 but that's only for lockscreen but you'll never know
edit : or try like another twrp3.2.1.0 (but will result in repair data too) or 3.2.1.6
raystef66 said:
First thoughts : Backup internal and format data.
Perhaps try https://androidfilehost.com/?fid=818222786056030640 but that's only for lockscreen but you'll never know
edit : or try like another twrp3.2.1.0 (but will result in repair data too) or 3.2.1.6
Click to expand...
Click to collapse
I mean, I know I'll be able to backup all my data since I can access it on a normal boot. Just very weird/annoying. I'm going to try flashing an older version of TWRP and seeing if it works.
...Maybe I should backup my data first
Did you ever find a solution to decrypting in TWRP? Currently having same issue with LOS15.1 and TWRP3.2.3.0.
I wasnt able to get mine to work, so I just backed up all my data and reformated, if you lost root you can still sideload magisk, dunno why but you can
hey guys, i really need your help urgently.
i just finished setting up my OP8Pro to my needs and then i restored wifi networks from my Titanium Backup from Android 8, i booted and it won't boot anymore.
i get a FATAL EXCEPTION IN SYSTEM PROCESS: WifiHandlerThread...
so now i need to reset these settings via stock recovery and i already modified my recovery to enable ADB but i can't access /data
anyone has a hint for me how to access /data and where to find the wifi config on Android 11?
it's not stored in /data/misc/wifi anymore :/
thanks a lot in advance!
You can reset WiFi within WiFi settings in settings.
But I would probably just clear data on the app you restored either in settings/apps or simply via titanium.
If it still fails then boot to recovery and wipe system.
Your storage will remain unaffected.
You could also try safe mode, power off and hold vol up and down as soon as you see the bootloader warning
Fyi I wouldn't bother restoring WiFi passwords like that, there's other ways of doing it.
Google can back these up for you for example, there are apps which can do it like swift (I think can do it)
dladz said:
You can reset WiFi within WiFi settings in settings.
But I would probably just clear data on the app you restored either in settings/apps or simply via titanium.
If it still fails then boot to recovery and wipe system.
Your storage will remain unaffected.
You could also try safe mode, power off and hold vol up and down as soon as you see the bootloader warning
Fyi I wouldn't bother restoring WiFi passwords like that, there's other ways of doing it.
Google can back these up for you for example, there are apps which can do it like swift (I think can do it)
Click to expand...
Click to collapse
thanks for your answer but unfortunately i can't boot anymore and i can't decrypt /data anymore even after reflashing stock recovery.
what's the best way to flash via fastboot to preserve data?
thank you!
eis0r said:
thanks for your answer but unfortunately i can't boot anymore and i can't decrypt /data anymore even after reflashing stock recovery.
what's the best way to flash via fastboot to preserve data?
thank you!
Click to expand...
Click to collapse
You'd have to grab one of the fastboot ROMs then flash.
Why can't you open recovery? Isn't your pin / password being accepted?
If it's not and fastboot installation can't be done then honestly I'd just MSM your current firmware..it's easier than fastboot tbh.
You'd need to bootloader unlock after but this is going to wipe everything anyway.
dladz said:
You'd have to grab one of the fastboot ROMs then flash.
Why can't you open recovery? Isn't your pin / password being accepted?
If it's not and fastboot installation can't be done then honestly I'd just MSM your current firmware..it's easier than fastboot tbh.
You'd need to bootloader unlock after but this is going to wipe everything anyway.
Click to expand...
Click to collapse
my bootloader is already unlocked and i was rooted on 11.0.0... i can boot into fastboot and recovery but i'm not prompted my unlock pattern.
this was working before testing adb integrated recovery and restoring stock recovery...
eis0r said:
my bootloader is already unlocked and i was rooted on 11.0.0... i can boot into fastboot and recovery but i'm not prompted my unlock pattern.
this was working before testing adb integrated recovery and restoring stock recovery...
Click to expand...
Click to collapse
I don't get you mate??
I'm saying that if you use the MSM tool it will lock your bootloader so you'll need to unlock it again.
In regards to your recovery if you can get to it then choose English, then wipe, then system, then wipe system.
That will get you back like I said in my previous post.
If it's not asking for your pin/password (there is no pattern)
Then you're fine
I've not used that recovery but I don't see a point in using it
dladz said:
I don't get you mate??
I'm saying that if you use the MSM tool it will lock your bootloader so you'll need to unlock it again.
In regards to your recovery if you can get to it then choose English, then wipe, then system, then wipe system.
That will get you back like I said in my previous post.
If it's not asking for your pin/password (there is no pattern)
Then you're fine
I've not used that recovery but I don't see a point in using it
Click to expand...
Click to collapse
sorry i haven't used MSM yet so i didn't know it'll relock the bootloader but i'm more familiar with fastboot flashing so i'd like to stick with that also because i read of problems with the fingerprint reader when relocking the bootloader.
i thought i could delete reset the faulty wifi config via adb by using the adb-enabled stock recovery but i wasn't able to mount /data with it since it's encrypted and it's not asking for my pattern to decrypt it.
neither the stock recovery is asking for it now...
i don't want to lose my data hence i'm looking for a way to get it back running without completely reinstalling.
do you think it could work by only flashing system partition via fastboot?
thanks man!
eis0r said:
sorry i haven't used MSM yet so i didn't know it'll relock the bootloader but i'm more familiar with fastboot flashing so i'd like to stick with that also because i read of problems with the fingerprint reader when relocking the bootloader.
i thought i could delete reset the faulty wifi config via adb by using the adb-enabled stock recovery but i wasn't able to mount /data with it since it's encrypted and it's not asking for my pattern to decrypt it.
neither the stock recovery is asking for it now...
i don't want to lose my data hence i'm looking for a way to get it back running without completely reinstalling.
do you think it could work by only flashing system partition via fastboot?
thanks man!
Click to expand...
Click to collapse
Use the thanks button buddy
I think you've certainly got a shot at it and what's the worst that can happen?
Did you actually try to wipe system in recovery? That would be my way to go.
MSM is extremely easy but I understand not wanting to lose storage.
That being said if you're correct about decryption then it won't matter anyway
dladz said:
Use the thanks button buddy
I think you've certainly got a shot at it and what's the worst that can happen?
Did you actually try to wipe system in recovery? That would be my way to go.
MSM is extremely easy but I understand not wanting to lose storage.
That being said if you're correct about decryption then it won't matter anyway
Click to expand...
Click to collapse
well after trying lots of different things i ended up wiping system settings in stock recovery. atleast i didn't lose storage.
thanks a lot for your help tho!
eis0r said:
well after trying lots of different things i ended up wiping system settings in stock recovery. atleast i didn't lose storage.
thanks a lot for your help tho!
Click to expand...
Click to collapse
You're very welcome mate, I've done the same a few times..it's not that much of a loss really, a lot of apps pick up where they left off and if you do have titanium then your back ups are retained.
Glad you're sorted.
PS: this would have had the same effect that installing system would have had, only this time you get a clean slate