Database Users

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.

Anyone have any idea?
Thanks

Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck

CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?

You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes

I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.

Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.

patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.

bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.

utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.

monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.

you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)

Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.

Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/

Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.

I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?

[HOW-TO USE TWRP] Make.A.NaNDroiD BacK-Up and Restore on J700t1 (Metro PCS)

Team RejectZ
How to Nandroid Back up and Restore as well as flash zips with TWRP on the Galaxy J700t1 (Metro PCS variant)
Hello , TimmetaL6669 here from Team Rejectz... It feels so good to be back.. So we have been having this little problem with the TWRP when it comes to doing a back up or flash anything because of, "system can't mount -data , failed" "system can't mount external sd card " .. or something along those lines... So after playing with it for awhile I finally figured out what the problem is... We are used to the old file system before Marshmallow... Before Marshmallow and before SE Linux Enforced the system would write directly to data or the sd card by mounting it directly... but with the new security the system writes through the system.. not by mounting thus avoiding potential malware attacks... so if the system can write to itself... so can we... This fix is more simple than I originally thought... there is no need to mount data unless you are flashing a ROM in which case we can use odin....or TWRP... you just have to know from where...So without further adue,
Pre-Requisites:
You must be Rooted usisng Mese2050's ported TWRP recovery and flashing SU binaries or by using Paco's Method.
You must have a micro SD card with at least 4 GB on it for your zips and backups
WARNINGS: DO NOT WIPE DATA OR CASHE OR DALVIK CASHE FOR ANY REASON YOU WILL END UP IN A BOOT LOOP OR AT THE RESTORE SCREEN
There isn't any reason to change cashe or data unless you are doing a full ROM change ..... Odin does this anyway when you odin so unless you just made an entire ROM with kernel and recovery included with STOCK cashe then DON'T WIPE CASHE OR DATA on marshmallow.. New security.. They did away with us messing with DATA or CASHE.... No need anyway for a back up or restore or to flash zips.... a good updater script for zips for marshmallow will mount the System anyway.
To Nandroid Back UP:
1. Boot into TWRP and click BACK UP. You're gonna need to switch your storage.... Switch your storage to Micro SDCard STORAGE .. because thats where we are going to be making our backup to..Then Swipe to Back up. Wait for your backup to be complete
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To Nandroid RESTORE:
Boot into TWRP. Click RESTORE. This time though we have been running into the "can't mount storage/ can't mount data" issue ...So..... Instead of switching to your Micro SDCard storage, STAY IN INTERNAL STORAGE. click "go up a level". Click external SD. Find your back up and swipe to Restore.
To Flash zip Files
Again just like with the restore option we are going to stay in the internal storage and click "go up a level" click external sd card and find the zip file you want to flash from your sd card. Click install Image
Thats it. Click thanks if I helped you, Feel free to ask questions if you get stuck. Make sure that you are completely rooted first with SU and Busybox binaries in /system/bin , /system/xbin and root/sbin before you try to use TWRP. Before attempting a back up, or to use TWRP make sure you follow the instructions carefully in Mese2050's TWRP thread.
" Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery]."
Also ensure that you have "unknown sources" checked in Settings/Security tab. and also in "Developer Options" you wanna have USB debugging and OEM unlock checked too.

This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app

needmuchohelp said:
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.. hut keep a copy of the su zip file on your sd card anyway just in case

needmuchohelp said:
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.. hut keep a copy of the su zip file on your sd card anyway just in case

Yeah, i do. My sd files look almost exact to bottom screenshot
Sent from my SM-J700T1 using XDA-Developers mobile app
---------- Post added 10-08-2016 at 12:04 AM ---------- Previous post was 09-08-2016 at 11:59 PM ----------
I think I had done this prior to reading this post, but I did smart install of busybox at same time, when I restarted it wasn't reading sd properly and I formatted thinking it would solve issue. Lost data on sd and still didn't fix issue. Did full clean install, normal busy box, everything golden now
Sent from my SM-J700T1 using XDA-Developers mobile app

I am a little confused. I have the SM J700T. I thought I was following Messi2050's instructions. Here's where I am so far. I have a 32gb micro sd card which I did not have installed when I setup Kies3. Kies3 was installed in the PC to install the phone drivers. Correct? I saw the drivers install when I connected the phone having Odin3 running at the same time. After the drivers installed the phone connected to Odin. Then I launched Odin 3 in order to flash a kernel which turned out to be incompatible with the J700T and got the "Kernel is not Seandroid Enforcing" error. I found a recovery image which was supposed to take me back to stock, and it seemed to work in that I could then install the Messi2050 kernel "odin-permissive-kernel-j700t-t1". The install went ok. Then I flashed the TWRP "odintwrp-3.0.2-0-j700t" which seemed to go ok, but when I disconnected the phone from the PC and rebooted into TWRP I was seeing the Enforcing error on the screen until TWRP fully booted. Anyway, I put the Micro SD card in with the SuperSU zip on it and used TWRP to install "UPDATE-SuperSU-v2.46.zip" , which kinda hung on the install until I sorta cancelled it and immediately the install finished. I rebooted and checked for root with Root Checker and after a while I got a successful report. So then I tried to do a backup of the phone as explained above in this thread.. I selected the MicroSD card to back up to and selected all the selectable partitions, but ended up with lots of can't mount data errors. Eventually I selected only system to backup and it succeeded. So now when I boot up the phone I am still seeing the Enforcing error on the initial black boot screen, but it boots normally and I have been able to use rooted tools and apps. I do not have Busybox installed yet as I believe I have to start over to clear the Enforcing error. I also did not follow Messi2050's instruction to MTP the SU file onto the phone while I am in TWRP. (Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.) I assume that means you have to have the phone connected to the PC. So how do I fully clear the Enforcing error? Here, in this thread, it says, "WARNINGS: DO NOT WIPE DATA OR CASHE OR DALVIK CASHE FOR ANY REASON YOU WILL END UP IN A BOOT LOOP OR AT THE RESTORE SCREEN ", so there must be something I am missing when Messi2050 says, "-if you want internal storage or data to work in TWRP: Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone! Go to [Reboot] -> [Recovery]. So somewhere in here I need to get oriented correctly. I think I have to reset the phone but I tried a factory reset but it didn't clear the Enforcing error. I would appreciate a considered response from the members who know what to do!! Thanks

@bromerrill
Messi2050's directions for format data would be from the beginning as in right after you flash kernel and twrp and before you backup using this threads method for backup.
After a backup/restore using this method in this thread, do not wipe anything.
-sent from this device using this app....

OriginalShinken1 said:
@bromerrill
Messi2050's directions for format data would be from the beginning as in right after you flash kernel and twrp and before you backup using this threads method for backup. After a backup/restore using this method in this thread, do not wipe anything.
So, first you use Odin to flash Messi2050's kernel, which, when you reboot gives the Enforcing warning message; then you Odin the TWRP, and then EXACTLY what do you wipe and why and how??
Does this or another step resolve the inability to do a backup of data and the other partitions? I followed the instructions in this thread, but it didn't work.
Perhaps it has to do with the first wipe? Perhaps you could explain why these errors are happening; something to do with the Marshmallo file system? How to resolve it?
Click to expand...
Click to collapse

@bromerrill
Click format data. Type yes (you'll see)
Make sure you have supersu zip on sd card just in case. Then go back to "install" and flash supersu.
Sorry pics are turned.
-sent from this device using this app....

Well it seems we still do not have a handle on this rooting process. After following the instructions and getting root twice, each time upon a reboot after a while the phone gets soft bricked. Getting the Custom binary blocked by FRP error. It could be related to turning off the developer options subsequent to getting root. If that is the case those who know need to advise those who don't not to turn off developer options! As far as this thread is concerned I don't see a clear explanation of the backup / restore procedure. There has to be something you do before using TWRP to do a backup, otherwise you get errors that you can't back up the data, etc. I appreciate the skewed pictures but that doesn't explain anything because there is no procedure explained. I wrote, "then EXACTLY what do you wipe and why and how??" which is not yet answered. How hard is it to do a step by step so all the users can get a clear understanding of the procedure??

Samsung galaxy tab a 10.1 cant mount data

Had this fixed on my first one . Had to return it and I cant find how i fixed it. Rooted. TWRP gives error message cant mount data. I cant backup or restore. Can someone point me to the fix, please?

Please note any instructions contained within this post are to be followed AT YOUR OWN RISK. I am not responsible for data loss, device failure, or any other form of damages resultant from the below post.
Final Edit: Method below tested and working on my SM-T580. Please read entire post before making any device modifications.
The reason you cannot mount /data is because TWRP does not support Samsung encryption, and your /data partition is encrypted by default. To fix this, you must disable encryption and FORMAT (not just wipe) your /data partition. You will lose all data on your device by doing this.
To disable encryption you must flash this ZIP file by ashyx via TWRP. I will update this post momentarily with the link.
Edit: Procedure that worked for me is as follows: [YOU MUST HAVE A ROM FILE TO REINSTALL]
-oem unlock and flash twrp
-format data
-wipe cache, dalvik, system, and data
-back out to main menu and reboot recovery
-flash your rom of choice back onto the device, I personally am using Fenix v2 found on XDA
-flash ashyx zip *not sure if this is actually necessary but it couldnt hurt, I flashed this file at this time
-reboot system
-then reboot to recovery to flash xposed, sd patch, etc
-you will see that twrp successfully mounts /data
Good luck!

REtails said:
Please note any instructions contained within this post are to be followed AT YOUR OWN RISK. I am not responsible for data loss, device failure, or any other form of damages resultant from the below post.
The reason you cannot mount /data is because TWRP does not support Samsung encryption, and your /data partition is encrypted by default. To fix this, you must disable encryption and then FORMAT (not wipe) your /data partition. You will lose all data on your device by doing this.
To disable encryption you must flash this ZIP file by ashyx via TWRP. I will update this post momentarily with the link.
Edit: There you go, so to recap: backup important data, reboot to recovery, flash zip, reboot to recovery, format data, reboot to system.
Click to expand...
Click to collapse
NO joy. See my post in stock ROM above (below now I guess...)

tennessee_titan said:
NO joy. See my post in stock ROM above (below now I guess...)
Click to expand...
Click to collapse
What? Not sure what you meant but it seems there is more to it than this. For some reason my device is forcing encryption across all sorts of wipes and such so I am currently trying to figure this out as well, will update if/when I figure it out
Edit: got it, updating post and sending you a PM

Stuck on 'To start android, enter your password'

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

SM-T580 Android 7 : /data encrypted, can't flash no-dm-verity

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.