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
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Controllerboy said:
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Click to expand...
Click to collapse
I would say the answer lies with issues between f2fs and SuperSU
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my SM-P600 using XDA-Developers Legacy app
And you flash the wrong SuperSU, the one needed is either v.2.79 or v.2.79-R3. try booting back to TWRP and clean Flash Lineage again and flash either one of the SuperSu I Mention before.
I have the same after install unofficial lineage 14.1 'decryption unsuccessful'
On TWRP 3.0.3-1 I go in 'wipe', then 'advanced wipe' and select 'Data', press 'Repair or Change File System' and then 'Change File System' to EXT4
That's work fine on my 2017G
For root
download.lineageos.org/extras
The arm64 zip
After install with TWRP go in deployment options and activated it!
Lineage is running with root
Thanks, everyone. That worked. I was quite worried for a while, I really don't want tot RMA the device a second time due tot me messing things up.
Where do I find the options in Twrp for deployment
jdg007 said:
Where do I find the options in Twrp for deployment
Click to expand...
Click to collapse
Twrp have no deployment option, what won't you to do.
joergwrage said:
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Click to expand...
Click to collapse
Probably it is caused by a known bug in the f2fs implementation in the kernel. Only @Unjustified Dev can solve it. Some people who already was using f2fs with TWRP 3.0.4 and LineageOS 13.1 are not having those issues and they were able to dirty flash the new LOS 14.1.
Updating to TWRP 3.0.3-1 is very recommended. TWRP 3.0.2 has some problems when flashing zips. SuperSU is one of them.
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
crazynitro said:
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
Click to expand...
Click to collapse
I have the same
Good day!
Our country just received the Oxygen OS 5.0.1 update.
How can I install it with an unlocked bootloader?
I was going to relock it but I found out that if I did, my data will be gone.
The only difference in the set-up of my phone from a stock OP5 is the unlocked bootloader.
Flash through stock recovery
Hitman478™ said:
Flash through stock recovery
Click to expand...
Click to collapse
I haven't done this kind of thing yet.
If I do this, will my data be wiped out or not?
What about using the OTA notification ?
quick05 said:
What about using the OTA notification ?
Click to expand...
Click to collapse
What do you mean?
I tried to update my phone using the normal way but after downloading and tried to install it, it failed because my bootloader is unlocked.
I just made a backup of data using codeworkx recovery. Copied the backup (Along with the files on userdata I wanted to keep) to my PC.
Wiped all and formatted data. Then installed Oreo and copied back the files and data backup from the pc to the phone and restored data with codeworkx recovery again.
Then flashed magisk 15.2 and rebooted.
Everything working fine now.
shriekyphantom said:
Good day!
Our country just received the Oxygen OS 5.0.1 update.
How can I install it with an unlocked bootloader?
I was going to relock it but I found out that if I did, my data will be gone.
The only difference in the set-up of my phone from a stock OP5 is the unlocked bootloader.
Click to expand...
Click to collapse
I managed to flash Nougat without locking my bootloader. But I also had to Format the Data partition to make it work. I used Titanium Backup to backup the data of the Apps and Myapplist to make a list of the apps. After installing Oreo I only needed to spent 1 hour to restoring the app data.
pleomaxell said:
I managed to flash Nougat without locking my bootloader. But I also had to Format the Data partition to make it work. I used Titanium Backup to backup the data of the Apps and Myapplist to make a list of the apps. After installing Oreo I only needed to spent 1 hour to restoring the app data.
Click to expand...
Click to collapse
Hello, I'm interested in the same thing.. I have oxygen osv4.5.x received notice for is 5.0.1 and want to install. I have an unlocked bootloader and am also rooted w/magisk. I want to keep my unlocked bootloader and root after upgrading. I also want to do a "clean" install.
Can anyone provide detail instructions, including best back up method of data and links to any files needed (twrp, magisk, etc) thanks
jmoricone said:
Hello, I'm interested in the same thing.. I have oxygen osv4.5.x received notice for is 5.0.1 and want to install. I have an unlocked bootloader and am also rooted w/magisk. I want to keep my unlocked bootloader and root after upgrading. I also want to do a "clean" install.
Can anyone provide detail instructions, including best back up method of data and links to any files needed (twrp, magisk, etc) thanks
Click to expand...
Click to collapse
This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
pleomaxell said:
This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Click to expand...
Click to collapse
Thank you... I like everything about my current build..should I wait to upgrade... Any other issues with Oreo?
jmoricone said:
Thank you... I like everything about my current build..should I wait to upgrade... Any other issues with Oreo?
Click to expand...
Click to collapse
I honestly dont see a big difference yet, but only had it for two days. Feels a bit snappier, my signal a bit stronger, and probably an improvement with battery life. I had issues upgrading but then again I flashed the wrong version of magisk. I think the most important thing is the latest android security update.
SysAdmNj said:
I honestly dont see a big difference yet, but only had it for two days. Feels a bit snappier, my signal a bit stronger, and probably an improvement with battery life. I had issues upgrading but then again I flashed the wrong version of magisk. I think the most important thing is the latest android security update.
Click to expand...
Click to collapse
Hey, thanks.. I will update later today. I see you provided which version of twrp (twrp-3.2.1-0-universal-codeworkx-cheeseburger.img). But what is the difference between the version you noted and the one I found (twrp-3.2.1-0-oreo-8.0-codeworkx-cheeseburger.img)
I want to make sure I have the correct version.
Thanks again
jmoricone said:
Hey, thanks.. I will update later today. I see you provided which version of twrp (twrp-3.2.1-0-universal-codeworkx-cheeseburger.img). But what is the difference between the version you noted and the one I found (twrp-3.2.1-0-oreo-8.0-codeworkx-cheeseburger.img)
I want to make sure I have the correct version.
Thanks again
Click to expand...
Click to collapse
You can ask that question on the TWRP thread. May be they can answer it correctly. I guessed that twrp-3.2.1-0-universal-codeworkx-cheeseburger.img was for both Nougat and Oreo and that is why I used it. So, if you want to be sure you should ask that on a TWRP thread.
pleomaxell said:
This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Click to expand...
Click to collapse
Hello, I was reviewing the process and just downloaded everything onto my computer and transferred onto my phone but have a few questions regarding some of the steps.
* Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP
** Can I update TWRP via the official app and is that version of TWRP okay to use over the "twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
* Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes' / This deleted my Internal Storage so I had to backup everything beforehand.
** How, what and where did you back up your data? Because later you mentioned "deleted my Internal Storage". I am guessing that because the OP5 does not have an external SD card everything is wiped and the new OS 5.0.1 needs to be saved onto a computer and then re-transferred back onto the phone. I am also guessing that the backup will need to be saved onto a computer as after wiping the phone it would also delete that file too, correct?
* Mounted the internal storage by using the Mount option from TWRP main menu.
** I am assuming that this option after the data wipe is self explanatory?
* I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
** This is what makes be believe all the files should be on a computer. How did you reboot and when you did, does it go directly / back to TWRP?
* Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots. / Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
** I am guessing here that once OS v8 is installed the TWRP img is no longer on the phone. I would need to transfer the TWRP back onto the phone then re-flash? Could I just install the TWRP official app and flash that way?
Thanks
jmoricone said:
Hello, I was reviewing the process and just downloaded everything onto my computer and transferred onto my phone but have a few questions regarding some of the steps.
* Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP
** Can I update TWRP via the official app and is that version of TWRP okay to use over the "twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
* Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes' / This deleted my Internal Storage so I had to backup everything beforehand.
** How, what and where did you back up your data? Because later you mentioned "deleted my Internal Storage". I am guessing that because the OP5 does not have an external SD card everything is wiped and the new OS 5.0.1 needs to be saved onto a computer and then re-transferred back onto the phone. I am also guessing that the backup will need to be saved onto a computer as after wiping the phone it would also delete that file too, correct?
* Mounted the internal storage by using the Mount option from TWRP main menu.
** I am assuming that this option after the data wipe is self explanatory?
* I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
** This is what makes be believe all the files should be on a computer. How did you reboot and when you did, does it go directly / back to TWRP?
* Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots. / Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
** I am guessing here that once OS v8 is installed the TWRP img is no longer on the phone. I would need to transfer the TWRP back onto the phone then re-flash? Could I just install the TWRP official app and flash that way?
Thanks
Click to expand...
Click to collapse
You have to flash TWRP by going to fastboot mode .
If you are rooted only then the TWRP app works
Aarju said:
You have to flash TWRP by going to fastboot mode .
If you are rooted only then the TWRP app works
Click to expand...
Click to collapse
Yes I am currently rooted. Once I flash the new OS will I still have root access to use the TWRP official app? Is that why after flashing new OS you need to flash TWRP via fastboot?
What about the backing up? I also have full titanium, thanks.
jmoricone said:
Yes I am currently rooted. Once I flash the new OS will I still have root access to use the TWRP official app? Is that why after flashing new OS you need to flash TWRP via fastboot?
What about the backing up? I also have full titanium, thanks.
Click to expand...
Click to collapse
After flashing the new rom you will be flashed stock recovery and you have to flash it through fastboot and flash magisk again.
Aarju said:
After flashing the new rom you will be flashed stock recovery and you have to flash it through fastboot and flash magisk again.
Click to expand...
Click to collapse
Hello, I followed the following instructions:
4. Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
6. Then used advanced wipe to wipe Cache and Dalvik.
7. Mounted the internal storage by using the Mount option from TWRP main menu.
8. I (also) was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
9. Copied the OnePlus full update and Magisk zip file.
I went to install the update w/in twrp and now I get an error message:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/oneplus5oxygen_23_OTA_028.....
What happened? Anyone please help...
jmoricone said:
Hello, I followed the following instructions:
4. Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
6. Then used advanced wipe to wipe Cache and Dalvik.
7. Mounted the internal storage by using the Mount option from TWRP main menu.
8. I (also) was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
9. Copied the OnePlus full update and Magisk zip file.
I went to install the update w/in twrp and now I get an error message:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/oneplus5oxygen_23_OTA_028.....
What happened? Anyone please help...
Click to expand...
Click to collapse
Wipe data and then copy the rom full zip flash it boot it to the starting screen then boot to recovery and then flash magisk ,you will see no errors.
Hello, I followed the following instructions:
4. Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
6. Then used advanced wipe to wipe Cache and Dalvik.
7. Mounted the internal storage by using the Mount option from TWRP main menu.
8. I (also) was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
9. Copied the OnePlus full update and Magisk zip file.
I went to install the update w/in twrp and now I get an error message:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/oneplus5oxygen_23_OTA_028.....
What happened? Anyone please help...
I received the following tip
"Wipe data and then copy the rom full zip flash it boot it to the starting screen then boot to recovery and then flash magisk ,you will see no errors."
But this makes no sense to me.
I have formatted my phone / wiped data / have the full rom & magisk on my "/sdcard" / went to install zip via TWRP, selected the rom and received the error message.
I decided to just go and upgrade via OTA and that failed. My phone has rebooted back to stock
what am i doing wrong?
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
hi, i have a sm-t510 with android 9, and im trying to install twrp but everytime i try i get some kind of wierd file corruption. all my files in sdcar are named with random numbers and letters and there is nothing in it. the tablet boot normaly, but i cant install anything or acces any of my normal file. is there anyway to fix that, or does anyone has a data back up i can use for that version XAC-T510XXU2ASK5. thank you.
cwarrow said:
hi, i have a sm-t510 with android 9, and im trying to install twrp but everytime i try i get some kind of wierd file corruption. all my files in sdcar are named with random numbers and letters and there is nothing in it. the tablet boot normaly, but i cant install anything or acces any of my normal file. is there anyway to fix that, or does anyone has a data back up i can use for that version XAC-T510XXU2ASK5. thank you.
Click to expand...
Click to collapse
Didn't read the instructions very carefully, now did you? The very FIRST thing you need to do when booting to TWRP is to FORMAT THE DATA PARTITION. Not wipe, but FORMAT. The data partition is encrypted and TWRP can't read it. That is why everything looks weird. Also, that is why you need to backup any pictures, downloads or anyting else you want to save because formating the partition will erase EVERYTHING and not just system stuff that wiping deletes.
lewmur said:
Didn't read the instructions very carefully, now did you? The very FIRST thing you need to do when booting to TWRP is to FORMAT THE DATA PARTITION. Not wipe, but FORMAT. The data partition is encrypted and TWRP can't read it. That is why everything looks weird. Also, that is why you need to backup any pictures, downloads or anyting else you want to save because formating the partition will erase EVERYTHING and not just system stuff that wiping deletes.
Click to expand...
Click to collapse
I have been rooting phones and tablet for the past 10 years its the first time it happens. Maybe its something new. Thanks for the info. But i already format the data and evwrything disapeared beside a file named twrp. And i cant reatore the data, cause i didnt have twrp to back them up. So if you have another sugestion, i am all ear
cwarrow said:
I have been rooting phones and tablet for the past 10 years its the first time it happens. Maybe its something new. Thanks for the info. But i already format the data and evwrything disapeared beside a file named twrp. And i cant reatore the data, cause i didnt have twrp to back them up. So if you have another sugestion, i am all ear
Click to expand...
Click to collapse
My post pointed out that formatting would erase everything and that you should backup prior to doing it. And there are several other methods of backing up data and apps besides TWRP. Yes, it leaves the data partition blank, but flashing a ROM and gapps will put the directories back. Of course, they will still be empty. If you used a Google Account, then that should have at least backed up your apps and some settings. When you setup a new ROM, it should let you restore them.
BTW, yes it was the first time it happened for most of us. Samsung keeps trying to improve "security" and adding encryption, by default, to the data partition is in all of their new tablets and phones.
lewmur said:
My post pointed out that formatting would erase everything and that you should backup prior to doing it. And there are several other methods of backing up data and apps besides TWRP. Yes, it leaves the data partition blank, but flashing a ROM and gapps will put the directories back. Of course, they will still be empty. If you used a Google Account, then that should have at least backed up your apps and some settings. When you setup a new ROM, it should let you restore them.
BTW, yes it was the first time it happened for most of us. Samsung keeps trying to improve "security" and adding encryption, by default, to the data partition is in all of their new tablets and phones.
Click to expand...
Click to collapse
my point is that i want to keep the stock rom, i was able to install a costum rom no problem after. but it doesnt work with the stock rom
cwarrow said:
my point is that i want to keep the stock rom, i was able to install a costum rom no problem after. but it doesnt work with the stock rom
Click to expand...
Click to collapse
You can't backup a stock ROM with TWRP because it can't handle the encryption. But you can use TWRP to root a stock ROM. In that case you just ignore the wierd internal data and put what you want to flash only on the external SD. IOW, if your reason for flashing TWRP is to use its backup function on a stock, don't bother, it won't work. But if your intent is to ROOT the stock ROM, then go ahead, but DON'T format data. Just put the files needed to root on the external SD and flash from there. You format the data partition in order to flash a custom ROM.
lewmur said:
You can't backup a stock ROM with TWRP because it can't handle the encryption. But you can use TWRP to root a stock ROM. In that case you just ignore the wierd internal data and put what you want to flash only on the external SD. IOW, if your reason for flashing TWRP is to use its backup function on a stock, don't bother, it won't work. But if your intent is to ROOT the stock ROM, then go ahead, but DON'T format data. Just put the files needed to root on the external SD and flash from there.
Click to expand...
Click to collapse
yeah but, i stil have the same problem though, i still cant use my tablette properly. i cant install new games and other app. but anyway i already rooted my stock firmware using magisk. but thanks anyway for the help
its just that i dont like the custom firware we have for it, and the stock firmware is slow af. but ill end up probably falshing a custom firmware anyway. have a good day.