How can I access the /data/ partition?
I was using the touchpad, installed some apps like teamviewer/unified remote/xbmc from the market, and all was going well and then for no reason the tablet froze, CM9 just stopped responding. So I rebooted it (holding the home button and power button was the only way to get it to do anything) but it's stuck at the Cyanogenmod boot animation. It's been on that animation for 5-10 minutes, so I rebooted again, went into clockworkmod and reflashed the latest nightly and gapps. I then rebooted, android booted up, said it was upgrading/optimizing 77 something apps, then it said it was starting the apps, and then it froze at that point, wouldn't proceed. I then reboot and am stuck at the boot animation again. My best guess is that one of the apps I installed is hosing it. I plugged the usb cable in and normally during the boot animation of my phone I can adb logcat but I can't seem to adb detect this device during boot animation. Windows see's it as a MTP device but no filesystem comes up in my computer. So adb logcat and adb shell so I can get into /data/app to wipe out the last few apps I installed won't work, but on my phone I can also adb shell in from CWM. So I rebooted into CWM but when I connect the cable to the laptop it still doesn't see it as an Android ADB device. No adb shell. Not like my phone at all.
So back to my original question, short of wiping /data from CWM, is there anyway for me to get at /data/app to delete some files? I'm curious what's causing this.
You can do an and pull from clockwork mod or have you tried mounting it on the computer from the clockwork mod options?
I've mounted before in clockwork but only sdcard, so that i can put a zip on it to flash. Can you also usb mount the /data partition?
Sent from my SGH-I777 using XDA
If you can reboot into WebOS, I know a way you can mount it and grab what you need.
Boot into WebOS, and connect your tablet to your PC. Then start up Novaterm (C:\Program Files\Palm, Inc\terminal\novaterm.bat). Connect to your tablet.
From there, you'll be at a root prompt. This is good. Type the following commands:
- mount /dev/mapper/store-media /media/card
- mount /dev/mapper/store-cm--data /media/hdd
- cd /media/hdd
- mkdir /media/card/cmdata (this will make a backup folder for you)
From there, you can use basic linux commands to copy files from your data partition to your media card. The ones you should need (forgive me listing the extra commands, even if you know them):
- ls (LS) will give you a directory listing
- cp -r <Folder> /media/card/cmdata (this will backup whatever folder you wanna backup to the cmdata on your card)
- rm -r <folder> (this will remove whatever folder you wanna remove)
- rm <filename> (this will remove whatever file you wanna remove)
I just tested this method, and it allows you to back up whatever you want, as long as you can get into your /data partition. You can do whatever you need to do. Just be careful you don't remove something you don't have to.
Hope this helps you, mate. If so, hit Thanks, if not, drop me a PM and we'll discuss other options.
glitchsys said:
I've mounted before in clockwork but only sdcard, so that i can put a zip on it to flash. Can you also usb mount the /data partition?
Click to expand...
Click to collapse
Yes, you can, but you can only read it from a Linux PC. A Windows system will not be able to access the partition, because it is an ext3 filesystem.
You can also use the "USB mode" used to install CM, but it will run into the same problem. Without Linux, you will not be able to access files.
I would clear the cache, that usually seems to solve these kind of issues. (Of course it could also mess it up further...)
Related
My SGS shows the boot up screen/noise, then just sits on a black screen and vibrates occasionally
I'm able to press the 3-buttons and boot up into ClockworkMod Recovery, however nothing seems to fix it. I've tried applying update.zip, wiping cache, factory reset, loading the restore-update.zip, and "restore" to the only checkpoint, but nothing works.
I screwed up when installing a theme, these were the first part of the directions:
1. adb shell
2. su (grant su rights on your phone when asked)
3. mount -o rw,remount /dev/block/mtdblock3 /system
3. rm system/framework/twframework-res.apk
4. rm system/framework/framework-res.apk
5. rm system/app/settings.apk (if no file is found try Settings.apk ... no ide if it matters tho)
Click to expand...
Click to collapse
I got this far, then realized that the files I needed to replace those with were on the internal SD, but IN A ZIP. So I couldn't use them. RMing the old ones meant nothing worked anymore.
Now my phone is in debug mode, can't seem to get su access (although I can use adb to a limited extent), and I can't get it to work
Any help for me?
I have3 the same problem Have you found out how to fix it?
Looks like your going to have to use odin to reflash ive had this many atime from unsuccesful modding and always worked.
I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
wolffboy212 said:
I was trying to fix my NC and install the 1.0.1 firmware. So I tried to format everything back to factory setting so I went into clockwork mod recovery and thought formatting the system partitions would restore me back to factory settings. Well I formatted "boot" and now it will not boot.
tl;dr I formatted boot, is it bricked?
help?
Click to expand...
Click to collapse
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Do "Method one: Eight interrupted Boots" and post what happens afterwards
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Geezer Squid said:
As I understand it, it is not bricked. You need to go read both the Nookie Froyo thread and the Clockwork Thread in the Nook Color Development Subforum. There is a way to put Nookie Froyo on an sdcard. You then boot with that and there's a way to put stuff back on the NC.
Do you have a Clockwork backup?
If you can boot back into Clockwork, there are some copies of other folks nandroid backup available. You can then put that on your sdcard and restore it.
I don't have the exact answer for you, but I'm sure it can be fixed.
Click to expand...
Click to collapse
Paul22000 said:
Do "Method one: Eight interrupted Boots" and post what happens afterwards
Click to expand...
Click to collapse
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
wolffboy212 said:
When I press the power button nothing happens. I.E. screen stays black. Would your guy's ideas work if you can boot at all?
Click to expand...
Click to collapse
I had the same thing happen. I tried plugging it into my Macbook, but nothing happened. I plugged into my Windows PC, and it came back to life.
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Syco54645 said:
A nookie froyo SD card would work fine. Restore from there manually. Next time make a nandroid and do not delete things that you do not know...
Click to expand...
Click to collapse
i have a nandroid back up and i cant get into recovery mode.
Because you deleted boot. Use a nookie froyo SD card and put the contents of boot back manually.
wolffboy212 said:
i have a nandroid back up and i cant get into recovery mode.
Click to expand...
Click to collapse
Which button combo are you trying to use to boot into recovery mode? If you haven't already, make sure you're using the three-button method.
Sent from my Nooted friend...
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
It is not three buttons. Only need home and power.
wolffboy212 said:
I have gotten it to boot to froyo on my sd card.
Now I need help restoring the boot partition from there.
Thank you very much with the support so far
Click to expand...
Click to collapse
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Syco54645 said:
I am not certain what to do exactly as I have never used nookie froyo. Generally you are going to want to do
modified /system/boot
mount -t vfat /dev/block/mmcblk0p1
then put the files back in there from in nookie froyo.
Someone else may have the exact way. Sorry I cannot be of more help but that will mount boot when in stock. Of course you will have to mount system as RW as well.
Click to expand...
Click to collapse
Bare with me I know very basic unix and linux commands but I do have the brain capacity to figure things out (not boot partitions).
I was on the command line and I couldn't get into the nook color stuff just the nookie froyo stuff on the sdcard.
suggestions?
Please read CW recovery thread. All answers are in there!
Really, please take time to browse through existing threads before posting questions which have already been answered several times.
Anyway, considering the number of people asking, here goes:
Note: You can do all this from the Nook, without the need of ADB, except for the fact that you will need gapps on nookie in order to install terminal and root explorer (although you could install those apps by directly installing APK's), see http://nookdevs.com/NookColor:_Nookie_Froyo_Tips, Third-party app support
Please read entire thread before attempting anything!
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
OR,
If you're able to access ADB (available when booting CW recovery and mounting /system and /SDcard, format from android required on SD to work here), CREDIT GOES TO Duloz, try this:
adb push uRecRam.bak /sdcard/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /sdcard/uRecRam.bak > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Click to expand...
Click to collapse
Note: Don't worry about errors concerning unmount.
If you're not back in business, post your questions, being very clear about what worked and what didn't.
Thank you.
Sent from my HTC Desire using XDA App
Back from Clockwork Recovery to Virgin (Factory) Recovery ... works like a charm!
samuelhalff said:
Please read CW recovery thread.
- Boot into nookie with market installed.
- Install terminal emulator.
- Install root explorer
- Create a new folder at root (/), for example "boottmp" => "/boottmp"
- Launch terminal emulator
- type: "su"
- type: "mount /dev/block/mmcblk0p1 /boottmp"
- type: "echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt" (this will force reset on next boot, as if you did 8 failed boots)
- open browser
- Download boot.zip from here: http://forum.xda-developers.com/showpost.php?p=10470539&postcount=268
- copy zip content to "/boottmp", by replacing existing files
- shutdown
- remove sdcard
- power up, you should see installation process after splash screen. Wait for it to finish, and it will reboot.
- power off
- Next you need to reset to factory settings:
- Boot while using power button and N button. Should boot to menu allowing reset. Proceed with reset.
Boot and be happy.
Click to expand...
Click to collapse
Works perfectly, thanks! I actually used adb instead of root explorer to do the copy and mount (etc.) commands, and did a manual 8-times power start interruption, but essentially the same. This made my poor "sound-failing" Nook a virgin again so I can swap it out at the store today. Crossing fingers that they will provide quick and easy exchange service (and let me test the sound on the replacement before I leave the store!)... Then, back to Autonooking (and even back to Clockwork Recovery...) again; now that I know how to go back and forth.
Owe you (or y'all) a beer!
Hello...i've search4ed and searched and no answer pertains to my problem that I can find. I followed this guide to get CM7.2 loaded on my 16gb sandisk sd card: http://forum.xda-developers.com/showthread.php?t=1000957 The gapps I'm using the CM7 download link. The CM7.2 rom is the newest one available on the download link
Everything loaded smooth and works great except when I get to the part of installing gapps, I reboot into recovery mode (blue penguin with scrolling writing) and everytime it cannot find gapps installer so it ignores it!! I don't know what else to do here.. I've verified the hash using md5sum and it matches... I have my gapps.zip file located on the ROOT of my sd card /sdcard/gapps.zip. I've also tried putting gapps in /sdcard/boot. I've also tried changing the name to gapps-update.zip, update-gapps.zip, gapps-gd....etc.zip, etc etc etc. No matter what or where I put the file it isn't found.
When I boot the NC i can get to a boot menu from there, i've tried all combinations of booting (internal, sd, normal, etc etc). I've tried installing through boot manager and that doesnt work. It reboots to recovery mode and still doesn't find the file. I've flashed clockwork in boot manager and that didn't help anything.
I'm not sure what I just did, but i rebooted and now I have a "burrito manager" icon. I tried installing through that and no go. Don't know what else to do.
I DO have wifi setup/connected.
*EDIT... not sure if it matters, but I do seem to have an issue. I'm connected to wifi but NTP isn't updating my clock settings. It is setup in settings to auto update the date/time using network settings and it doesn't update. Could this be an issue with getting market to show up if the time is wrong??
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
DizzyDen said:
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
Click to expand...
Click to collapse
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
ballgum said:
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
Click to expand...
Click to collapse
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
leapinlar said:
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
Click to expand...
Click to collapse
That worked! thank you very much...
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I canĀ“t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
Hi gurus,
I currently have TWRP, rooted, stock android, encrypted, and a lot of apps and data on the phone. I'm looking for a way to decrypt the phone and bring me back to the same state that I left it.
I think this is process, correct me if I missed anything.
1. Put the phone in Airplane mode, so nothing changes during this process
2. Reboot into recovery
3. TWRP backup
4. adb pull /data/media <PCDirectory>
5. Do the decryption steps, flash TWRP, re-root
6. adb push <PCDirectory> /data/media (don't do this)
6. Use Android MTP and Windows to copy the files from back to Nexus 6.
7. TWRP restore backup from setup #3.
8. Reboot phone and I should be back to where I was except now decypted
9. Turn off airplane mode
----- ANSWER: I took the dive, and everything works. -------
Here's what I did. (I used a mix of adb, fastboot, and NRT)
1. Put the phone in Airplane mode, so nothing changes during this process
2. adb reboot recovery
3. TWRP full nandroid backup
4. adb pull /data/media <PCDirectory> (while still in recovery)
5. adb reboot bootloader
6. fastboot flash boot boot_noforceencrypt.img (flash the no-encrypt boot image)
7. fastboot format userdata (wipes the device)
8. Reboot and enable USB Debugging
9. Use NRT to root and flash TWRP
10. Reboot into recovery
11. TWRP nandroid restore (Make sure to uncheck boot, as I made a mistake the first time. If the "old" boot image gets restored, the phone will re-encrypt itself on startup)
12. Reboot and enable USB Debugging
13. Copy any missing files from the <PCDirectory> back to the Nexus 6 using MTP.
Good luck, now I have a much faster phone! There is probably a way to do this all in NRT or the command prompt, but I had NRT setup already and didn't have to re-download any additional files.
My situation is identical to yorus so I'll be curious if we get a good answer.
No. Don't use Adb to push to data/media. You'll screw up the permissions to the /decade folders. Use MTP in android (not recovery) to do the transfer back.
when I do the transfer back in MTP, I assume there will be some files that will already exist on the device? Should I overwrite or skip?
ertw96 said:
when I do the transfer back in MTP, I assume there will be some files that will already exist on the device? Should I overwrite or skip?
Click to expand...
Click to collapse
Merge if you can, otherwise overwrite
This is exactly what I've been wanting to try.
ertw96 said:
Hi gurus,
I currently have TWRP, rooted, stock android, encrypted, and a lot of apps and data on the phone. I'm looking for a way to decrypt the phone and bring me back to the same state that I left it.
I think this is process, correct me if I missed anything.
1. Put the phone in Airplane mode, so nothing changes during this process
2. Reboot into recovery
3. TWRP backup
4. adb pull /data/media <PCDirectory>
5. Do the decryption steps, flash TWRP, re-root
6. adb push <PCDirectory> /data/media (don't do this)
6. Use Android MTP and Windows to copy the files from back to Nexus 6.
7. TWRP restore backup from setup #3.
8. Reboot phone and I should be back to where I was except now decypted
9. Turn off airplane mode
----- ANSWER: I took the dive, and everything works. -------
Here's what I did. (I used a mix of adb, fastboot, and NRT)
1. Put the phone in Airplane mode, so nothing changes during this process
2. adb reboot recovery
3. TWRP full nandroid backup
4. adb pull /data/media <PCDirectory> (while still in recovery)
5. adb reboot bootloader
6. fastboot flash boot boot_noforceencrypt.img (flash the no-encrypt boot image)
7. fastboot format userdata (wipes the device)
8. Reboot and enable USB Debugging
9. Use NRT to root and flash TWRP
10. Reboot into recovery
11. TWRP nandroid restore (Make sure to uncheck boot, as I made a mistake the first time. If the "old" boot image gets restored, the phone will re-encrypt itself on startup)
12. Reboot and enable USB Debugging
13. Copy any missing files from the <PCDirectory> back to the Nexus 6 using MTP.
Good luck, now I have a much faster phone! There is probably a way to do this all in NRT or the command prompt, but I had NRT setup already and didn't have to re-download any additional files.
Click to expand...
Click to collapse
Now if I can just get ADB to work on my windows 8 computer.
lalew25 said:
Now if I can just get ADB to work on my windows 8 computer.
Click to expand...
Click to collapse
I did this on a Windows 8.1 computer. So it should work on Windows 8. I did have some trouble installing the drivers orginally and found that the Nexus Root Toolkit does it best.
It allows you to delete all your previous drivers, and any other drivers that Windows attempts to install. Then it installs the correct USB drivers for the Nexus 6, and you're ready to rock and roll. Enable USB debugging and you it should be able to detect your device.
I'll give that a try, thanks.
I think I already have the nexus toolkit. Is it a big speed difference when you take off the encryption? Does it effect battery life at all?
lalew25 said:
I think I already have the nexus toolkit. Is it a big speed difference when you take off the encryption? Does it effect battery life at all?
Click to expand...
Click to collapse
Yes to both, in certain operations... A little bit.
Yes definitely. I had a Nexus 5 before running Lollipop, and I play 2 racing games, Real Racing 3 and GT 2 Racing, both of which run perfectly fine on my Nexus 5. On the Nexus 6, during game play it was fine, but switching apps and loading times during the game took forever, slower than my Nexus 5.
After Decrypt, but games fly, and general operations feel a lot snappier too. Sorry, don't have any benchmarks, but decrypting does speed up the phone quite a bit.
If you've used up more than half of your storage, will a nandroid backup even work? I need to get that backup onto my PC, but don't think I have room to backup my phone on phone....
Help?
No context issues. Ownership should be media_rw.media_rw for /data/media and everything within. /data/media and /data/media/0 should be 770. umask inside should be 002. Not sure if setting this will allow adb push to honor it. Otherwise, resetting the perms can be done in batch.
Anyway, no need to boot back into Android. After formatting /data in TWRP, it does need to be rebooted though to remount /data. And for some reason, rebooting straight into the recovery seems to cause it to then reboot to OS. Instead, reboot to bootloader from TWRP and then go to recovery from there. Some directories might need to be created (I think /data/media is there but /data/media/0 doesn't. As well, /sdcard in twrp will currently point at /data/media instead of /data/media/0)
Code:
cd /data
mkdir media
chmod 770 media
cd media
mkdir 0
chmod 770 0
push the contents of /data/media/0 back with adb
Code:
chown -R media_rw.media_rw /data/media
cd /data/media/0
find . -type d -exec chmod 775 {} \;
find . -type f -exec chmod 664 {} \;
nvm