Database Users

[Q] flashing ROM, lost SD card contents

This has been bugging me and I can't seem to find anything on here to explain it.
I have installed custom ROMs on my N7. Problem is most ROM instructions say to do a full wipe/factory reset. When I do that, the downloaded ROM that was sitting on the SDCard gets wiped out as well.
I then have to go back and search for info on how to reset/restore the N7 and start all over, because the recovery (both CWM and TeamWin) don't let me mount the SD card to copy the needed zip over.
How can I do the recommended data wipe without losing the sd card contents?
Failing that, what's easiest way to get the ROM zip back on the N7 when the recovery won't allow it?
Thanks

dont wipe data...
just do a 'factory reset' in custom recovery...then flash a rom

I use TWRP & don't wipe everything, just System & Factory (to delete installed apps).
This is after wiping Cache & Dalvik Cache.
Unless I'm missing something a data wipe will wipe everything except recovery.
I don't think we have the option to exempt the media folder like on other devices.
(you type faster than me PG)

I appreciate the suggestions, and I've done the factory wipe. It wiped out the /SDcard folder contents where the zips were.
How do I get zips back on the N7? tried ADB, tried sideload from TWRP, nothing works.
Having many more problems than the last time I did this.

jneg123 said:
I appreciate the suggestions, and I've done the factory wipe. It wiped out the /SDcard folder contents where the zips were.
How do I get zips back on the N7? tried ADB, tried sideload from TWRP, nothing works.
Having many more problems than the last time I did this.
Click to expand...
Click to collapse
factory reset in TWRP doesnt touch /data/media
are you sure you are on the most recent version of recovery?

updated to latest recovery version, that seemed to be my issue. sd card now untouched.

Pirateghost said:
factory reset in TWRP doesnt touch /data/media
Click to expand...
Click to collapse
Pirateghost speaks the truth.
The stock recovery however, wipes everything with it's "factory reset".
It's a little bit unfortunate that the identical terminology is used. No doubt new folks will occasionally get bit by assuming they are the same.
I haven't used cwm yet; not sure what it means by "factory reset" - or even if it uses that terminology.

[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?

[Q] Help! Memory Size Dropped Nexus 7

After rooting my Nexus 7 wifi 2012 tablet and trying several back ups and restores I started to notice the size of memory has gone from 13gig to 6gig.
I have done a factory reset from boot up recovery mode using TWRP. I also tried other options in TWRP wipe option, clearing internal cache, many other options to mention, not sure what most did, tinkering
I have also restored to a factory image using Nexus root toolkit option flash stock + unroot (forced flash mode) and restored from a downloaded image.
I thought restoring to factory image was suppose to put everythng back as it was! where has all the memory gone! 13gig before rooting and now 6 gig :crying:
EDIT
Well, I got the size to show back correctly with the factory image restored (13.36gb). I booted to recovery and selected "wipe data/factory reset" and also did the "wipe cache partition" just to be sure.
Why none of this work when I was doing the same from TWRP recovery mode rooted? I have to root again now, bet the same thing will happen and left with lower memory and no way to fix? time............................

Usually, it's TWRP I've always had partition formatting issues with it. Use the CWM recovery meant for your device instead.

RealPariah said:
Usually, it's TWRP I've always had partition formatting issues with it. Use the CWM recovery meant for your device instead.
Click to expand...
Click to collapse
RealPariah,
Thanks for the reply.
Have it sorted now. Turns out NRK buggy. Would not put nandroid backup to destination on hard drive. Not even with a reboot. Hence memory on Nexus tablet shrinking. I should have clocked on earlier. will check out CWM.
I was thinking of keeping NRK. Just read about CWM. Would it be o.k to download CWM from Googleplay and run it or would that interfere with NRK?

I've got the same issue. This weekend I just sideloaded 5.1.1 on mine (it's a 2012 model), and I'm looking at 6Gb only now (it's a 16GB N7).
I also have TWRP on it.
I used the Wugnet Nexus Root Toolkit for everything, which also supports CWM.. but why is that the one "meant" for the device? It's a custom recovery. Or is it more closely based on the stock recovery than TWRP is?
What's NRK?
I did a wipe on the cache partition already, so that clearly didn't work. I guess I could wipe data and start all over again.
PS. Using ES File explorer, I've found a number of what appears to be actual copies of my emulated sdcard data, not just symlinks:
1) /sdcard -symlink (to /storage/emulated/0 I think?)
2) /storage/emulated/0 (not a symlink)
3) /storage/emulated/legacy (not a symlink, but data is in there too.. a copy?)
4)/storage/sdcard0 (symlink)
5) /mnt/sdcard (symlink)
6) /data/media/0 (not a symlink, another copy?) Also, weirdly, the only directory I could change permissions on if I wanted to..
I'd have thought that would have been /Storage/emulated/0 .
I think /storage/emulated/0 is the main actual repository, and I get that there are symlinks, but /storage/emulated/legacy and /data/media/0 look like full on duplications to me.
Found the answer - I've got my space back.
1) Restore stock recovery,
2) boot into it and
3) do a factory reset from there.
http://www.wugfresh.com/faqs/incorrect-internal-storage-space/

I9505 doesn't boot anymore after removing "disabled" file xposed

Hello,
my s4 doesn't boot anymore and something weird happens all the time. I already tried delete system and caches, then flash rom (aosp) but this doesn't help.
I think my data partition is corrupted, but I don't want to wipe it as it contains all my stuff.
PS: the screenshot shows files that aren't there, I checked in the filemanager and they are there.
filesystem repair gives:
/sbin/fsck.f2fs /dev/block/mmcblk0p29 process ended with error 139
Even backup fails:
createTarFork() process ended with error 255

What if you use the xposed uninstaller zip?
If the zip doesn't help then I'm pretty sure the only solution is to wipe data.
Happened to me too several times, randomly, during reboots. Sometimes my data would get automatically wiped, and other times my phone wouldn't boot unless I wiped the data partition.
I believe it has something to do with F2FS, because, since I changed back to ext4, I haven't had this problem.

GDReaper said:
What if you use the xposed uninstaller zip?
If the zip doesn't help then I'm pretty sure the only solution is to wipe data.
Happened to me too several times, randomly, during reboots. Sometimes my data would get automatically wiped, and other times my phone wouldn't boot unless I wiped the data partition.
I believe it has something to do with F2FS, because, since I changed back to ext4, I haven't had this problem.
Click to expand...
Click to collapse
I flashed stock and then started over. Somehow my rom zip got corrupted and I got the same problem. So I redownloaded and flashed, everything is good now
Sent from my GT-I9505 using Tapatalk

Lineage stuck on boot loop on startup

Hi,
I have LineageOS 14.1 installed on my Moto G4 Plus. All of a sudden it rebooted and was stuck on the booting screen. I can get to TWRP. Things I tried that didn't help
wait 30 minutes
plug in phone to charger
clear cache
fully power off then on
If it comes down to it, I could flash a new ROM, but would like to save/backup the text messages/whatsapp messages.

@lightningglasses
Anything you installed/flashed before rebooting ?
try to dirty flash ROM and check if it boots or not.

____Mdd said:
@lightningglasses
Anything you installed/flashed before rebooting ?
Click to expand...
Click to collapse
nothing.an mp3 player app
try to dirty flash ROM and check if it boots or not.
Click to expand...
Click to collapse
will that loose the text messages etc?

lightningglasses said:
will that loose the text messages etc?
Click to expand...
Click to collapse
wiping "Data" deletes everything, dirty flashing does not not.
Just wipe delvik-Art and cache (*not data*), Then install ROM (plus gapps and root if you need), reboot, it will take around 10 minutes to re-generate delvik data, then it should boot..

____Mdd said:
wiping "Data" deletes everything, dirty flashing does not not.
Just wipe delvik-Art and cache (*not data*), Then install ROM (plus gapps and root if you need), reboot, it will take around 10 minutes to re-generate delvik data, then it should boot..
Click to expand...
Click to collapse
hmm didn't work, any other ideas?

lightningglasses said:
hmm didn't work, any other ideas?
Click to expand...
Click to collapse
I forgot to mention in previous post, did you wipe system? Try with that and install rom.
Reinstalling ROM heals damage made to /system partition and to boot, but not to /data.
so if still doesn't boot, that means damage happened to /data and you need to clean it, result in lost of data of apps (whatsapp and message you mentioned in your post.)
Still if you know what apps you installed last, delete it from /data/app/xyz-app (boot TWRP > advance > file manager)

____Mdd said:
I forgot to mention in previous post, did you wipe system? Try with that and install rom.
Reinstalling ROM heals damage made to /system partition and to boot, but not to /data.
so if still doesn't boot, that means damage happened to /data and you need to clean it, result in lost of data of apps (whatsapp and message you mentioned in your post.)
Still if you know what apps you installed last, delete it from /data/app/xyz-app (boot TWRP > advance > file manager)
Click to expand...
Click to collapse
It is still stuck in a boot loop after I
cleared cache, dalvic/art and system
used twrp's file manager to delete all recently installed apps from /data/app
flashed newest lineageos rom
clear davilink again
waited 15 minutes with phone plugged in
When should I wipe cache/dalvik/system? Before or after flashing rom?

lightningglasses said:
It is still stuck in a boot loop after I
cleared cache, dalvic/art and system
used twrp's file manager to delete all recently installed apps from /data/app
flashed newest lineageos rom
clear davilink again
waited 15 minutes with phone plugged in
When should I wipe cache/dalvik/system? Before or after flashing rom?
Click to expand...
Click to collapse
There is no other way to get your device back without losing data.
I have never used Titanium backup app but i know there is feature to restore data from TWRP backup, you can take backup of /data and restore backup of whatsapp.
I am still not sure about that feature, if you have time then i can test that feature, otherwise there is no way to keep data.
Edit: whatsapp makes chat backup every night at 2AM, if you haven't had any important chats after that, you can go for wipe.

If you can pay for titanium backup there might just be a way. I am not 100% sure but take a backup of the "data" partition(you can backup everything but data is most important) in twrp in internal storage only. Then clean flash everything. Then install titanium backup and buy the pro key. Then restore from twrp. If you find an option to restore only data then that's a better option. Downloading the app and restoring the data is better than restoring app and data. I'm not sure if it will work. But if nothing is working and your data is 100% vital you may wanna try this.
Another tip, don't restore blindly everything cuz bootloop may occur again