I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Gaby_64 said:
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Click to expand...
Click to collapse
Does TWRP print anything about "successfully decrypting /data with default password" in the console when it starts?
Go WIPE > ADVANCED WIPE > check the box next to "Data" > REPAIR OR CHANGE FILE SYSTEM. What does it say the file system of /data is?
Edit: Did you format /data before or after the issue happened? Never mind, you have to have formated /data afterwords if you were trying different ROMs.
ext4
i dont see the console
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
troy5890 said:
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
Click to expand...
Click to collapse
i tried as both f2fs(performance is worth it) and ext4
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Doc Ames said:
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Click to expand...
Click to collapse
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
troy5890 said:
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
Click to expand...
Click to collapse
May I ask, why are you using that version of TWRP?
Choose an username... said:
May I ask, why are you using that version of TWRP?
Click to expand...
Click to collapse
It's the only version that will boot up successfully when flashed through fastboot.
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
It's the only version that will boot up successfully when flashed through fastboot.
Click to expand...
Click to collapse
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Choose an username... said:
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Click to expand...
Click to collapse
I tried but it ended up not flashing successfully
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
I tried but it ended up not flashing successfully
Click to expand...
Click to collapse
all hail axon7tool then :v
Choose an username... said:
all hail axon7tool then :v
Click to expand...
Click to collapse
Looks like I'll give that a try, thank you
Sent from my ZTE A2017U using XDA-Developers Legacy app
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
Hello everyone heres a guide on how i formated my le pro 3 720 64gb from ext4. please know that this will delete all of your data will be delete i strongly recommand doing a twrp or tatanium backup before hand! allso if this somehow ****s up i will not be hold responsible. i am simply showing you all how i did this to get my result. now with all the formalitys in place lets talk about what exactly the steps are after you backed up everything you want to keep download your feverite rom. the one i am ussing is turbos aokp destroyer ver2, download it unto your pc, allso make sure you have twro custom recovery that support the f2fs.
here is the one i ussed. https://drive.google.com/file/d/0B9ZMWt4u_wSDVkp3UlMxS1liMUE/view
after you have made sure your twrp support it and you backed up everything you need. boot into twrp, wipe/advanced wipe/check data/repair or change file system/chenge file system/ f2fs do the same for data and for cache. then connect you phone via the usb cable to a pc with minimal adb put the rom you decided to install on your le pro 3 into the minimal adb folder and call it something easy like Kitty. i do this all the time xD
then open a cammend windows as admin and type the fallowing code.
adb push push kitty.zip /sdcard
this will start your rom being moved from the pc unto your sdcard on your phone. and i allso belive its the safest way to do it dont qote me on that tho.
then you just install your kitty rom and you should be good to go. NOTE in my case with the destroyer 2 aokp from my good freind turbo i dont think the /system supports f2fs as it reformats it into the ext4 on installation, but data and cache will reamain f2fs at all times. and it does seem quite abit faster regardless. thanks everyone for reading and im sorry if this is done in a extreme noob fashion i hope you all will be able to understand whats going on and all. peace out and be sure to let me know how it turns out for you
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
venezolano69 said:
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
Click to expand...
Click to collapse
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
DrTorretz1 said:
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
Click to expand...
Click to collapse
OK thanx for the guide
venezolano69 said:
OK thanx for the guide
Click to expand...
Click to collapse
Your welcome hope it helps!
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
FYI, at the very least you can format your cache partition to F2FS without losing any data.
slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
villarleg said:
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
Click to expand...
Click to collapse
Wow thanks village! I'm happy you enjoyed the guide also thanks for letting me know about the system I will put it up there!
venezolano69 said:
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
Click to expand...
Click to collapse
Does it come up with a error or something? I'm not sure mine did it fine
slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
Yeah I suppose so. It works really well regardless
DrTorretz1 said:
Does it come up with a error or something? I'm not sure mine did it fine
Click to expand...
Click to collapse
Something like "not possible to mount"
venezolano69 said:
Something like "not possible to mount"
Click to expand...
Click to collapse
That sounds really strange. I'm sorry I can't assist further. Data should be the most important one annyways
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Enamak said:
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Click to expand...
Click to collapse
Do you have an otg?
venezolano69 said:
Do you have an otg?
Click to expand...
Click to collapse
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Enamak said:
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Click to expand...
Click to collapse
Otg is very good stuff, when you wipe everything you put Rom insidie the otg and you can flash everything you want
I have another problem.. I formated /cache /data (no problems, errors). After that I flashed "TURBO2012's China / US EUI 23s V8" (no problems, errors).
But DiskInfo from the playstore is showing me ext4 in /cache and /data ?
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
cherryduck said:
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
Click to expand...
Click to collapse
Same here. I tried it a few days ago with the latest Lineage nightly and started formatting all partitions with F2FS with the same outcome: stuck on bootscreen.
Gradually I returned my partitions to ext4 and only after I returned everything to 'normal' I got past the boot screen. Not even "cache" worked with F2FS.
About after 6 months, I decided to change ROMs on my Moto X. Just like before, I booted into recovery, made a nandroid backup, and tried to wipe cache, ART and Data. But when I try to wipe the data partition, the recovery freezes, my phone starts vibrating and goes into a bootloop. Neither the new ROM will boot, nor will the Nandroid boot. Is there a way to wipe data partition using ADB, as ADB still works.
Also if it helps, I'm using the adopted storage format for my SD Card(i.e. where the SD Card is formatted as internal storage)
Thank you! Don't have a device rn, so any help is appreciated!
I experienced the exact same thing. Was unable to wipe or re-install back up. My data was in the f2fs format so I changed it to ext4 and was able to wipe and finally install a new ROM. Currently using TWRP 3.1.1.0. Not sure if this helps you but that's what I had to do to get it to function.
Sent from my XT1575 using Tapatalk
Use "format data" first, then go to advanced wipe. It will erase all internal memory.
What rom/kernel was the last? Twrp version? @kkricardokaka95
---------- Post added at 09:43 PM ---------- Previous post was at 09:41 PM ----------
lilcdroid said:
I experienced the exact same thing. Was unable to wipe or re-install back up. My data was in the f2fs format so I changed it to ext4 and was able to wipe and finally install a new ROM. Currently using TWRP 3.1.1.0. Not sure if this helps you but that's what I had to do to get it to function.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
What rom/kernel it happened?
I had it with RRemix + handbag kernel 2.0.
At the time I was running Viper OS with handbag 2.0. I went back to CR Droid with stock kernel for now. I haven't had a chance to mess with things since to verify its fixed.
Sent from my XT1575 using Tapatalk
lilcdroid said:
I experienced the exact same thing. Was unable to wipe or re-install back up. My data was in the f2fs format so I changed it to ext4 and was able to wipe and finally install a new ROM. Currently using TWRP 3.1.1.0. Not sure if this helps you but that's what I had to do to get it to function.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I used 4 different variants of TWRP but to no avail. I think my data was also in the f2fs format, I don't remember. Will keep it in mind next time something goes wrong! I used a Flash to Stock tool and I'm sitting at 5.0.0. Used fastboot to flash TWRP, will flash some other ROM and check what's wrong.
I was on Ground Zero ROM(Validus) with Handbag kernel.
dzidexx said:
Use "format data" first, then go to advanced wipe. It will erase all internal memory.
What rom/kernel was the last? Twrp version? @kkricardokaka95
---------- Post added at 09:43 PM ---------- Previous post was at 09:41 PM ----------
What rom/kernel it happened?
I had it with RRemix + handbag kernel 2.0.
Click to expand...
Click to collapse
Format Data wasn't working. Recovery hung and rebooted resulting in a bootloop
kkricardokaka95 said:
Format Data wasn't working. Recovery hung and rebooted resulting in a bootloop
Click to expand...
Click to collapse
Try the suggestion from post #2.
(Twrp - advanced wipe - format/repair file system)
It is most definitely the handbag kernel. I'm back on stock CRdroid kernel (completely fresh install of ROM) and have wiped format, backed up, restored all without any problems on TWRP 3.1.1.0. I even put my file system back to f2fs for data.
Sent from my XT1575 using Tapatalk
You'll have to go back to stock then flash twrp and then recover your backup.
Happened to me when I used handbag with los14. 1 and aicp
So I just bought this Tablet and I wanted to Root it, but I immediately noticed that in trying to flash anything, this verification thing gotme stuck in a bootloop. I looked further into it, and I need to patch dm-verity out, however, the latest .zip I tried is for Android 6 it seems, as when I tried to flash it and then let TWRP make modifications, it still got stuck in the Verification Error bootloop.
Now I flashed the original system to it again through Download Mode, and that fixed the bootloop. However, I then went into Odin, flashed TWRP, went into TWRP, tried to do as it said in the guide where it says I need to "Wipe Data", but when I try to do that it says "Failed to mount '/data' (Invalid Argument)". So what now? And does anyone here have a dm-verity patch for this tablet that supports Android 7? Thanks
yanniclord said:
However, I then went into Odin, flashed TWRP, went into TWRP, tried to do as it said in the guide where it says I need to "Wipe Data", but when I try to do that it says "Failed to mount '/data' (Invalid Argument)". So what now? And does anyone here have a dm-verity patch for this tablet that supports Android 7? Thanks
Click to expand...
Click to collapse
Which guide?
ashyx said:
Which guide?
Click to expand...
Click to collapse
This one
https://forum.xda-developers.com/ga...ab-tablets-t3552509/post70924135#post70924135
Oh, I recognize your name, didn't you also make the no-dm-verity script?
yanniclord said:
This one
https://forum.xda-developers.com/ga...ab-tablets-t3552509/post70924135#post70924135
Oh, I recognize your name, didn't you also make the no-dm-verity script?
Click to expand...
Click to collapse
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
ashyx said:
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
Click to expand...
Click to collapse
These instructions are a tad simpler.
To disable forced encryption, disable dmverity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using the FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
ashyx said:
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
These instructions are a tad simpler.
]To disable forced encryption, disable dmverity and mount internal storage:[/B]
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Click to expand...
Click to collapse
Hmm alright, I actually tried that before but it worked this time after I reinstalled the Stock Firmware multiple times and did multiple resets as well, thanks
So do you have a no-dm-verity.zip for Android 7 for me? Or does the one from the thread work?
Oh and, I want to flash Magisk, so shall I flash Magisk first and then no-dm-verity? I am pretty sure that is correct assumed of me.
EDIT: Thanks for the no-dm-verity zip, will try it and I will also try Magisk Thanks for all the help, has been a while with Samseong devices for me :/
EDIT 2: As far as I remember, doesn't Magisk disable dm-verity to begin with when it flashes itself?
yanniclord said:
EDIT: Thanks for the no-dm-verity zip, will try it and I will also try Magisk Thanks for all the help, has been a while with Samseong devices for me :/
Click to expand...
Click to collapse
Will work on Android 7 too.
If you flash Magisk you shouldn't need the patch.
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