Encryption unlocked & rooted? - X Style (Pure) Q&A, Help & Troubleshooting

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

Related

TWRP hangs on booting to recovery

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.

Just got RMA, can't disable force encryption

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

[HELP!] TWRP createTarFork() error 255 when backing up data

I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Pro4TLZZ said:
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Click to expand...
Click to collapse
What was corrupt? How did you fix it?
keeganjk said:
What was corrupt? How did you fix it?
Click to expand...
Click to collapse
Something in the partition, so I didn't restore that
Pro4TLZZ said:
Something in the partition, so I didn't restore that
Click to expand...
Click to collapse
Which partition? I just wiped my device and reinstalled FreedomOS.
keeganjk said:
Which partition? I just wiped my device and reinstalled FreedomOS.
Click to expand...
Click to collapse
Userdata partition
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
OK.
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
keeganjk said:
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
Click to expand...
Click to collapse
I'm sorry I can't help you more
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
What's the difference between TWRP and bluspark TWRP?
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
I can't restore; I deleted all my backups in an attempt to free up space.
I think I found the solution!
1. Go to Wipe in TWRP, swipe to factory reset
2. Download:
OnePlus Recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
OxygenOS: http://oxygenos.oneplus.net.s3.amaz...3_OTA_015_all_1708252353_e6d7756780064352.zip
3. Rename recovery image as recovery.img, boot phone into fastboot, plug into computer, run these commands on the computer:
fastboot devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
4. Open recovery on phone
5. Select Forgot Password, will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select Install over ADB or Install Over USB or something similar and plug phone into computer.
7. Run 'adb sideload oxygen-os-filename' without quotes on computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probobaly isn't, so don't shut it off or unplus USB.
9. Download Bluspark TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=26601&task=get
9. Reboot into fastboot, plug into computer and run these commands on the computer:
fastboot devices
fastboot flash recovery bluspark-twrp-filename-location.img
fastboot boot bluspark-twrp-filename-location.img
10. Success (hopefully)
Oh. Wait. Now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
the solution to this was to boot to your previous rom that u have made nandroid backup with and then setting up the same password/pin in settings > security. When you then boot into twrp it will ask you for the pin/password to decrypt your data partition and then you can flash the nandroid backup(you have to have the same password there). here it is obvious that you are trying to flash data partition that uses different encryption password (in case of stock rom there is non) and this obviously wont happen.
maybe another solution would be to connect externally usb and unmounting data partition and then restoring from usb...
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Need4Sneed said:
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Click to expand...
Click to collapse
For me flashing normal oxygenos with magisk 16 and formatting data and trying to make it boot with the new flash and then rebooting into recovery and restoring made it work. I guess it has to do with the right filesystem having to be made first.
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.

Can't create a backup through TWRP.

I tried creating a system backup through TWRP just now for the first time ever. Throughout the process, it gave me multiple messages saying "unable to mount data" and the same for some other folders, and when the backup supposedly finished, it just said failed.
Is there anything I can try without actually wiping either of the partitions? This obviously because I'm trying to create a backup so I can wipe afterwards.
cyborgium said:
I tried creating a system backup through TWRP just now for the first time ever. Throughout the process, it gave me multiple messages saying "unable to mount data" and the same for some other folders, and when the backup supposedly finished, it just said failed.
Is there anything I can try without actually wiping either of the partitions? This obviously because I'm trying to create a backup so I can wipe afterwards.
Click to expand...
Click to collapse
In twrp main menu screen select ' Mount ' menu and make sure mount data is ticked then go back and try backing up again.
spawnlives said:
In twrp main menu screen select ' Mount ' menu and make sure mount data is ticked then go back and try backing up again.
Click to expand...
Click to collapse
Thanks for your reply, it doesn't actually let me tick that box. Nothing happens when I tick it. It also says that the data partition is 0mb. Any idea what that might mean?
cyborgium said:
Thanks for your reply, it doesn't actually let me tick that box. Nothing happens when I tick it. It also says that the data partition is 0mb. Any idea what that might mean?
Click to expand...
Click to collapse
Which version of twrp are you using
Latest is 3.2.3.0 which should fix the data issue ( it"s a known issue).
spawnlives said:
Which version of twrp are you using
Latest is 3.2.3.0 which should fix the data issue ( it"s a known issue).
Click to expand...
Click to collapse
That's the TWRP version that I've got installed.
I just reinstalled both stock firmware and reflashed TWRP but the exact same issue persists. At first I was able to mount data though, I could flash zips such as Magisk etc. But after having set everything up again on my phone, I couldn't mount data anymore.
cyborgium said:
That's the TWRP version that I've got installed.
I just reinstalled both stock firmware and reflashed TWRP but the exact same issue persists. At first I was able to mount data though, I could flash zips such as Magisk etc. But after having set everything up again on my phone, I couldn't mount data anymore.
Click to expand...
Click to collapse
Not sure on your steps to install twrp
Have you tried going into twrp in wipe menu and format data
spawnlives said:
Not sure on your steps to install twrp
Have you tried going into twrp in wipe menu and format data
Click to expand...
Click to collapse
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
cyborgium said:
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
Click to expand...
Click to collapse
Sounds like your device is still encrypted
Did you flash the no Verity encrypt zip file
Also I said to format data not wipe.
In the mount menu these are the options I have enabled.
spawnlives said:
Sounds like your device is still encrypted
Did you flash the no Verity encrypt zip file
Also I said to format data not wipe.
In the mount menu these are the options I have enabled.
Click to expand...
Click to collapse
You're right, I formatted data, not wipe.
I did flash the no verity zip, does the order in which I flash Magisk, no-verity and RMM state unlock matter?
cyborgium said:
You're right, I formatted data, not wipe.
I did flash the no verity zip, does the order in which I flash Magisk, no-verity and RMM state unlock matter?
Click to expand...
Click to collapse
The instructions I followed to install twrp
Flash twrp (which you have done)
Format data
When finished reboot back into twrp(use twrp reboot menu option)
Flash no-verity zip via twrp ( have to make sure you have it on internal storage or SD card)
Then flash everything else
Not sure if you need RMM state unlock if your bootloader(OEM) is already unlocked in developer options though.
spawnlives said:
The instructions I followed to install twrp
Flash twrp (which you have done)
Format data
When finished reboot back into twrp(use twrp reboot menu option)
Flash no-verity zip via twrp ( have to make sure you have it on internal storage or SD card)
Then flash everything else
Not sure if you need RMM state unlock if your bootloader(OEM) is already unlocked in developer options though.
Click to expand...
Click to collapse
I've just done everything you stated above, still the same issue, can't mount /data.
Really don't understand what it is that im doing wrong or if I'm even doing anything wrong..
Thanks for your help anyway though, appreciate it.
cyborgium said:
I've just done everything you stated above, still the same issue, can't mount /data.
Really don't understand what it is that im doing wrong or if I'm even doing anything wrong..
Thanks for your help anyway though, appreciate it.
Click to expand...
Click to collapse
Just as matter of curiosity I use FX file explorer (root) in the menu filesystem it should tell you what format your data partition is mine or ext4. I have read that some people through twrp have changed it to something like ext3 and then back to ext4
Also this is the thread I used to install my twrp
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
This thread may also help you out
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
spawnlives said:
Just as matter of curiosity I use FX file explorer (root) in the menu filesystem it should tell you what format your data partition is mine or ext4. I have read that some people through twrp have changed it to something like ext3 and then back to ext4
Also this is the thread I used to install my twrp
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
This thread may also help you out
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
Click to expand...
Click to collapse
I think that second thread you linked may have done the trick.
At first it didn't seem to help, but when I tried it again after reflashing everything, I am now able to mount /data.
I'm still in the dark as to why this happened and hasn't happened to anyone else other than the person who created that file, but either way, thank you very much for your help.
cyborgium said:
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
Click to expand...
Click to collapse
Try the modded twrp from nx thread

HELP with resetting wifi config on V11.0.0.IN11BA

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

Categories

Resources