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
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.
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.
Hi, I keep seeing that some people brick their phones due to the changes in the process. Question, Due to some battery drainage I am getting, I am trying to do a phone reset.
I currently have TWRP installed and rooted the phone using the jccuando method. What is the best way to reset the phone to factory so I can re-root again and do what I need to do without bricking? Any advice would be much appreciated!
matteosaeed said:
Hi, I keep seeing that some people brick their phones due to the changes in the process. Question, Due to some battery drainage I am getting, I am trying to do a phone reset.
I currently have TWRP installed and rooted the phone using the jccuando method. What is the best way to reset the phone to factory so I can re-root again and do what I need to do without bricking? Any advice would be much appreciated!
Click to expand...
Click to collapse
Definitely boot to twrp via hardware keys or a boot to recovery app.. Do not do it from the settings menu. It will put you into twrp bootloop until you boot from the hard keys anyway. Just remember to flash supersu after you factory reset before you boot or you'll have to boot back into twrp again and flash it.
Swizzle82 said:
Definitely boot to twrp via hardware keys or a boot to recovery app.. Do not do it from the settings menu. It will put you into twrp bootloop until you boot from the hard keys anyway. Just remember to flash supersu after you factory reset before you boot or you'll have to boot back into twrp again and flash it.
Click to expand...
Click to collapse
Thank you so much. So I see I can get to twrp no problem. What to do inside twrp before I bootloop or do I need to reset factory before I get to twrp? Then what to do after I am in a bootloop ?
matteosaeed said:
Thank you so much. So I see I can get to twrp no problem. What to do inside twrp before I bootloop or do I need to reset factory before I get to twrp? Then what to do after I am in a bootloop ?
Click to expand...
Click to collapse
If you used the method I told you there should be no bootloop. Just got to the section wipe and slide the slider for a factory reset. Then afterwards press back and go to your external sd and flash supersu again then reboot it will reboot twice after you flash supersu so don't worry.
Swizzle82 said:
If you used the method I told you there should be no bootloop. Just got to the section wipe and slide the slider for a factory reset. Then afterwards press back and go to your external sd and flash supersu again then reboot it will reboot twice after you flash supersu so don't worry.
Click to expand...
Click to collapse
Thank you. I actuallt just got done. I did factory reset instead and booted up fine. I took your advice and flashed supersu after the factory reset and i am all good now. I wonder the difference between factory reset and the format data. I was a little scared to factory reset so it woud not erase the rom.
matteosaeed said:
Thank you. I actuallt just got done. I did factory reset instead and booted up fine. I took your advice and flashed supersu after the factory reset and i am all good now. I wonder the difference between factory reset and the format data. I was a little scared to factory reset so it woud not erase the rom.
Click to expand...
Click to collapse
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Swizzle82 said:
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Click to expand...
Click to collapse
Cool thank you. I didnt have a problem since i backed up my apps with titanium.
Swizzle82 said:
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Click to expand...
Click to collapse
Hi, did everything with no problem. I got another question and not sure if you have the answer. I was hoping to re-lock the bootloader again. Do you know of a way to do that and get the phone to boot up to the system? I am trying to avoid the bootloader reboot message after turning on the phone! Thank you for all your help!
matteosaeed said:
Hi, did everything with no problem. I got another question and not sure if you have the answer. I was hoping to re-lock the bootloader again. Do you know of a way to do that and get the phone to boot up to the system? I am trying to avoid the bootloader reboot message after turning on the phone! Thank you for all your help!
Click to expand...
Click to collapse
Do not relock unless you're pure stock no twrp or modded boot img. The annoying message will always be there.
Swizzle82 said:
Do not relock unless you're pure stock no twrp or modded boot img. The annoying message will always be there.
Click to expand...
Click to collapse
Cool. I tried to relock and unlock. No problem. I just want the stock recovery. Do you know if this is flash able yet ?
matteosaeed said:
Cool. I tried to relock and unlock. No problem. I just want the stock recovery. Do you know if this is flash able yet ?
Click to expand...
Click to collapse
There is a new thread about how to return to stock somewhere here in the forum..
Swizzle82 said:
There is a new thread about how to return to stock somewhere here in the forum..
Click to expand...
Click to collapse
Sweet. I have been looking at the forum and everything says tarp has to be installed and running . I'll keep looking. Thank you sir .
Absolutely do not re-lock your bootloader unless you are 100% stock. If you brick the phone with a locked bootloader, you are screwed.
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