Hey everyone.
I'm one of the lucky few that had internal sd wiped during the process of upgrading from NB4 to NE6.
Yes, totally my fault, as I should have backed up my internal. But I didn't.
To compound it, my nandroid backed up to internal rather than external sd (DOHHH).
Needless to say, I haven't written over the wiped internal, and I know there's a way to recover the deleted files (and nandroid)-- I just haven't done it on the Note 3 yet.
There are multiple guides out there on recovering internal storage by using cygwin, creating a raw image of the internal, mounting it as a drive, and using software like recuva. This is the guide I'm loosely following, however, our data block is in a different location. I believe 25, from what I can tell. This is the guide I'm using right now.
My Desperate Questions
Has anyone been able to recover their wiped internal storage on the Note 3, specifically?
Is our data partition at dev/block/mmcblk0p25 ?
Does anyone recommend any other methods of doing this?
Any help totally appreciated.
Where I am now:
I've been running Recuva for the past 4 hours which apparently doesn't recognize a drive connected through MTP. I tried something tricky and it appears to be running. But, given the status it reports (pretty much nothing), it could just be scanning my computer.
Concurrently, I'm trying the guide I linked up there. I have root, and busybox installed (to system/bin), but adb keeps disconnecting when I get to the "adb forward tcp:5555 tcp:5555" step, and device keeps going offline.
You can't access the media through MTP. MTP is sort of like FTP -- files are transferred from one system to another and presented by the receiver as if they were local. You could work with the media if you install a modified kernel and used UMS.
The first thing you should do is copy the media image to a removable SD card so you can use a desktop computer, and also to make a backup. With the image on a micro-SD card you could then continue to use your phone while you recover the data. I'm new to Linux but I think 'dd' from a device will copy everything, not just listed files. Put a 32GB micro SD in the slot and try this and see what it looks like:
dd if=/dev/block/mmcblk... of=/dev/block/mmcblk1
Note that I did not include the full path to the internal SD -- I don't happen to have that handy while I'm in this reply editor on my device.
Frank
ADDED:
Partition 25:
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk1
Frank
---------- Post added at 02:04 AM ---------- Previous post was at 01:29 AM ----------
Don't forward anything in ADB, just go straight to the file system:
adb shell
Frank
Frank Westlake said:
ADDED:
Partition 25:
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk1
Frank
---------- Post added at 02:04 AM ---------- Previous post was at 01:29 AM ----------
Don't forward anything in ADB, just go straight to the file system:
adb shell
Click to expand...
Click to collapse
Thanks so much for your response. With a little digging (a lot of digging) I confirmed it was partition 25, but found no reference to it in my device.
I grabbed an app called DiskDigger where the data partition is identified under:
/dev/block/platform/msm_sdcc.1/by-name/userdata
I'm using cygwin right now to copy that partition to a userdata.raw file (on my computer) which I can hopefully mount using VHD, and then use Recuva to salvage the data. I'll find out in a couple hours if that worked. And if not, I'll definitely go grab a bigger SD card and follow your recommendation.
Question. Once copying the full partition to the SD card, what would you use to extract the data and restore it to the internal SD?
I have not lost anything important enough to go to the trouble of disk-digging, so I have no experience with it.
Frank
---------- Post added at 03:53 AM ---------- Previous post was at 03:29 AM ----------
I just took a quick look at the guide you referred to and using that procedure you will need to forward a port to ADB. I don't know why that procedure, maybe it's necessary for cgwyn.
Also in that thread is a comment that the procedure won't work on devices which can't use UMS. The Note 3 can't use UMS unless you've installed one of the kernels which enable it.
Frank
Related
Quick question but I flashed DT onto Synergy RLS1 w/ GM and I checked my internal memory before and after but it didn't change. Did it flash successfully? Any way for me to check? I thought it was supposed to move dalvik-cache to the internal memory therefore taking up internal memory space. I did it via the Synergy updater if that helps, thanks in advance.
Download a2sdgui from the market place and run it The program will give all the info you need on a2sd in a graphical inface it will also allow you to make changes
So i downloaded it and it closes on me, saying:
Could not start because of one of these reasons
1. Device is not rooted (it definitely is)
2. A2SD scripts could not be found.
3. No ext partition found.
I do have god mode and I did upgrade ext2 to ext3, could this affect the program?
I believe this is due to god mode. When you flash the zip file in recovery, it installs everything to /system as it's supposed to. When you boot into Synergy w/GM, that yaffs2 gets mounted as /system0, and a different ext2 partition is mounted to /system.
From adb shell or teminal app, run the following command: find / -name *a2sd*
If you only get results in /system0, then you have the same problem I currently have. I'll let you know if I fix it.
---------- Post added at 08:57 AM ---------- Previous post was at 08:50 AM ----------
Here is a version that has the required mount commands for god mode in the installation script.
http://forum.xda-developers.com/showpost.php?p=16138710&postcount=9885
Smidley said:
I believe this is due to god mode. When you flash the zip file in recovery, it installs everything to /system as it's supposed to. When you boot into Synergy w/GM, that yaffs2 gets mounted as /system0, and a different ext2 partition is mounted to /system.
From adb shell or teminal app, run the following command: find / -name *a2sd*
If you only get results in /system0, then you have the same problem I currently have. I'll let you know if I fix it.
---------- Post added at 08:57 AM ---------- Previous post was at 08:50 AM ----------
Here is a version that has the required mount commands for god mode in the installation script.
http://forum.xda-developers.com/showpost.php?p=16138710&postcount=9885
Click to expand...
Click to collapse
Im not on it right now but if i remember right you dont need any more internal memory anyway, theres plenty. I think mine was like three hundred something.
I flash mine in GM just fine. If u want more internal after flashing dta2sd u have to go into terminal and type su enter then cachesd enter I believe.
Sent from my nike hating evo!
Was ( and still am) curious why Google choose MTP over MassStorage. The other member (http://forum.xda-developers.com/showthread.php?t=1023153) did some tests with interesting results. Can confirm that got similar results for MTP's favour ( transfered same video,music,pdf files to GN and HTC Sensation).
I don't think that was the only reason for Googles decision.
Also find out one very annoying experience with MTP : you can't edit file on phone memory. It has to be transfered to PC, modified and put back to phone...
aspot72 said:
Was ( and still am) curious why Google choose MTP over MassStorage. The other member (http://forum.xda-developers.com/showthread.php?t=1023153) did some tests with interesting results. Can confirm that got similar results for MTP's favour ( transfered same video,music,pdf files to GN and HTC Sensation).
I don't think that was the only reason for Googles decision.
Also find out one very annoying experience with MTP : you can't edit file on phone memory. It has to be transfered to PC, modified and put back to phone...
Click to expand...
Click to collapse
It allows them to lump all of the internal storage together since MTP doesn't require the partition be unmounted with the phone.
Many people have phones that were partitioned poorly (N1, Vibrant, etc...) and after you install some apps you get an error that you've filled up your space (even though your phone still has 10GB free).
They hacked around it by doing Apps2SD, but even then, it wasn't perfect.
This new method allows them to utilize the full 16/32GB of storage however you want without any additional requirements from the user.
For most people that just want to copy their pictures off the phone, MTP is a lot smoother. It 'just works' and let's them get by with their day.
Unfortunately, the new way isn't perfect. I use Ubuntu for example and am having a hell of a time getting it to work. I eventually just gave up and installed a Samba File server instead.
Does anyone else have problems with folders not appearing or with errors when transferring files, or is it because I'm using a Mac and Android File Transfer software?
@tjhart85, you can get mtp working but you just need to compile the latest libmtp from source, libmtp that's included in the ubuntu repos is an older version.
i think I'm the minority here in that I actually like MTP.
The fact that I can unplug the phone, and it's ready to go is worth it. I hated the media scanning tool from gingerbread and before. Now the phone is ready to go when I unplug.
It lets the entire phone be one partition, so there are no annoying issues with multiple partitions for system, apps, etc.. It also lets the phone be used while its connected and transferring to/from the device. Also, no more mounting/unmounting and waiting for the device to be available.
It overall just removes headaches associated with files not being able to be accessed properly because they're on a different partition or on the SDcard (such as no widget support from apps installed on SDcard).
I also don't get the big deal over MTP and actually prefer it. I have a mac and haven't run into any problems. The file transferring didn't seem any slower and if anything seemed faster so I don't really get why everyone seemed to freak out when it was originally revealed.
Sent from my Galaxy Nexus using xda premium
This explains it - from the horse's mouth itself.
http://www.androidpolice.com/2011/1...behind-galaxy-nexus-lack-of-usb-mass-storage/
wolfman87 said:
This explains it - from the horse's mouth itself.
http://www.androidpolice.com/2011/1...behind-galaxy-nexus-lack-of-usb-mass-storage/
Click to expand...
Click to collapse
Great read. Thanks. I don't know why they're so against file managers, though.
tjhart85 said:
Unfortunately, the new way isn't perfect. I use Ubuntu for example and am having a hell of a time getting it to work. I eventually just gave up and installed a Samba File server instead.
Click to expand...
Click to collapse
I haven't tried this, but it does look promising:
http://collectskin.com/adbfs/
It sure sounds better than setting up a samba server, and since it's based on adb it can be made to run over wifi (although I'm not sure that is recommended).
---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------
Buddy Revell said:
Does anyone else have problems with folders not appearing or with errors when transferring files, or is it because I'm using a Mac and Android File Transfer software?
Click to expand...
Click to collapse
It seems not all folders are appearing over MTP.
For instance my TitaniumBackup folder stored in /sdcard does not show at all and I'm not sure why. It might be because the folder contains no files the phone can work with? I honestly have no idea.
This was on Windows. Not Linux or Mac. So it seems to be a MTP-issue, not a platform-issue.
I had to adb shell in, create a tar of that and then adb pull it out to get it.
So yeah. MTP has its flaws. Hence me working on a workaround:
http://forum.xda-developers.com/showthread.php?t=1423392
---------- Post added at 09:36 AM ---------- Previous post was at 09:34 AM ----------
aspot72 said:
Also find out one very annoying experience with MTP : you can't edit file on phone memory. It has to be transfered to PC, modified and put back to phone...
Click to expand...
Click to collapse
If I were to nitpick I would have to say that technically speaking that was always true, but yeah, now you actually have to manage that transfer manually and that sucks.
But you can use the memory on the phone while transferring from pc!
jamontoast1291 said:
I also don't get the big deal over MTP and actually prefer it. I have a mac and haven't run into any problems. The file transferring didn't seem any slower and if anything seemed faster ...
Click to expand...
Click to collapse
can I ask what exactly happens when you plug into a MAC? Eg, do you have to launch ATP, does it appear in Finder, does it launch iPhoto automatically? I'm just trying to get a picture & short of taking my MAC into town ... has anyone YT'd this?
Sent via phone - nuff said
MTP also solves the 4GB file size limit. With USB mass storage all phones have FAT32 for their data partition in order to be compatible with most computer, but that means 4GB file limit.
With MTP the file system isn't visible for the computer, so the phones will use a good filesystem like EXT4 also for the data partition.
Gents,
Good day all. I hope you are fine and doing well.
Reference to the above mentioned subject, kindly note that I have a rooted GSM Galaxy Nexus and I keep flashing custom ROMs.
As everyone does, I backup all of my apps & their data using Titanium Backup before flashing another ROM, and the restore them once I finish flashing the new ROM.
I had a strange problem which occurs only when flashing any 4.2.1 based ROM, the problem that Titanium Backup tells me that there is no backup files!
I have tried to access the internal storage using many file managers but I cannot find the partition which contains Titanium backup files and my stored files. I have connected the USB cable to PC and was not able to find them as well!
But when I reboot in Recovery, I can find them while searching for the Zip File (Install Zip From SD Card).
I have returned back to a 4.1 based ROM and was able to access them.
The problem happens only when I flash a 4.2.1 based ROM, and with different ROMs.
I have tried to use "Fix Permissions", but it did not solve the problem,
would you help please?
Root ur phone after the 4.2.1 update and use root explore or free es explore to access under data/media/.. The 4.2 update sets sdcard @ data/media/0/
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 09:36 AM ---------- Previous post was at 09:28 AM ----------
But.. If ur bootloader is locked then u cant root, if ur unlock ur bootloard it formats ur sdcard.. So what i would do is
go back to 4.1
Backup ur sdcard to pc
Do a factory reset from stock recovery
Update to 4.2
Restore sdcard from pc
Sent from my Galaxy Nexus using Tapatalk 2
QUOTE=LiquidXed;36910504]Root ur phone after the 4.2.1 update and use root explore or free es explore to access under data/media/.. The 4.2 update sets sdcard @ data/media/0/
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 09:36 AM ---------- Previous post was at 09:28 AM ----------
But.. If ur bootloader is locked then u cant root, if ur unlock ur bootloard it formats ur sdcard.. So what i would do is
go back to 4.1
Backup ur sdcard to pc
Do a factory reset from stock recovery
Update to 4.2
Restore sdcard from pc
Sent from my Galaxy Nexus using Tapatalk 2[/QUOTE]
Thanks for your reply.
I have rooted the phone again and still cannot access that area.
kindly advise
Boot into recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
danger-rat said:
Boot into recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
Hello,
I have tried this but got the following on the shell:
ata/media # chown -R media_rw.media_rw *
/sbin/sh: ata/media: not found
would you advise please?
Dear Guys,
While I was on 4.2.1 ROM, I have created a file called 123456.txt .
I have flashed a 4.1 ROM (where I am able to browse all of my files without a problem) and searched for the file I was created ( 123456.txt) and found it under the path sdcard/0
Kindly advise
Sent from my Galaxy Nexus using xda app-developers app
whyomax said:
Hello,
I have tried this but got the following on the shell:
ata/media # chown -R media_rw.media_rw *
/sbin/sh: ata/media: not found
would you advise please?
Click to expand...
Click to collapse
Should be data/media, not ata/media
---------- Post added at 12:05 PM ---------- Previous post was at 12:03 PM ----------
whyomax said:
Dear Guys,
While I was on 4.2.1 ROM, I have created a file called 123456.txt .
I have flashed a 4.1 ROM (where I am able to browse all of my files without a problem) and searched for the file I was created ( 123456.txt) and found it under the path sdcard/0
Kindly advise
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That sounds about right - not sure what your question is?
Hello danger-rat,
When I was on 4.1, all files were stored in /sdcard directly.
When I flash 4.2 ROM, I cannot access /sdcard. All file managers starts from sdcard/0. ٍo I cannot restore my backups and access my stored files.
This is my main problem.
Do we have another solutions for this problem? I have searched for it many times and most of the developers says that this new storage criteria is for the Multi-User support.
In the other hand, I am using "Android commander" as adb shell. would you recommend another adb shell so I can try to write the above code again?
Thanks,
Search for sdcard jb 4.2
Sent from my i9250
Here's the brief version, before you do a search...
It appears that Google has updated the file system to be more flexible - there's a lot more variation in storage these days, with SD cards, OTG mounts, internal storage, etc, and then there's multiple user interfaces to add to the mix. I can't say I like the new structure, but I guess it is what it is...
Anyway, you will likely have several folders, such as /sdcard/0, /sdcard/legacy, /sdcard/emulated, etc. They are all symlinks from other storage locations. If you use an updated recovery, or a root file explorer, you should be able to see and use everything. I know I can...
Just takes a bit of getting used to, and a bit of patience...
Thank you guys..
Hi All,
Phone Model - Galaxy Nexus i9250
Android Version - 4.3
Build Number - JWR66Y
I accidentally deleted few of the photographs from the gallery day before yesterday, I wanted to restore the photos and I googled around and found some some softwares which are capable of doing that
My phone is not rooted so I don't have SuperUser permissions
Wondershare Dr. Fone for android - It is able to detect my phone but it says "SU" permissions needs to be granted
I have a file recovery software installed on PC so I can use it get the data recovered from phone, but my Galaxy Nexus is being detected by the PC as "Portable Media Player" instead of a USB storage device. So any way I can make my phone be detected as USB storage device by my PC
Any help ?
I do not believe you can connect Gnex as mass storage device, I believe some have tried but I recall it always ending in failure (search xda for galaxy nexus mass storage, or tuna mass storage or something like that for more details or to see if anyone was ever able to get that working)
rooting is fairly easy though if you need su(superuser aka root permission) and I believe there are ways to do that without having to wipe the device fully.
I will try to help you find that method of rooting if you need it and would like to try so that you can attempt using an application that requires su(but even then it might not be able to fully recover everything you hope for. But could for sure be worth the try )
Let me know if you need help finding the info
---------- Post added at 07:24 AM ---------- Previous post was at 07:15 AM ----------
I did just find something else on this.
Someone mentioned that they used nexus root toolkit to make a full backup of device(which can also be done using adb I believe) and you don't need root perms to do that.
They then scanned that with recovery program and got back most of what they had deleted.
Problem arises if you have been using device a LOT since deleting the files and the deleted blocks have started to get overwritten. (I might suggest making the full backup, placing that onto a USB drive or sdcard, that way you can just scan that drive with program and hopefully get results you are looking for since THAT can be mounted as mass storage device)
Hey guys. I'm very familiar with android and it's processes but I have stumbled onto something that I cannot solve... My Internal SD Card has somehow made it self write-protected.... even to my PC! I can't save anything to my internal SD card at all. All camera apps, with the exception of the stock samsung camera set to ext-sd store mode works. If the other camera apps don't have that option, I can't use it. I can't download anything from the web (it will automatically say download unsuccessful and even ODIN can't touch it (I tried to ODIN back to stock NK3... and it partially worked... except that I still have all my downloaded apps installed)
Here's what happened.
The problem started when I was on DomPop v0.1.3 (5.0.2) It started with me not being able to take a screenshot, which I fixed.
Then I flashed PAC-Man RLS 3 (12312014) and that's when I noticed that I can't save any downloads to my internal SD card.
So I recovered to my saved rooted stock NB1... Still no avail and this is where I found out that my 3rd party cameras don't save anymore.
I've done everything from flashng a new ROM, flashing a new recovery, ODINing back to stock... nothing seems to work! And I'm slowly starting to lose space on my ext-sd soo any help would be appreciated by this chic. Thanks in Advance
PS
As of the time I wrote this, I have ODINed 3x now... still, every time I reboot, I still have my downloaded apps... it's as if my /data partition is write protected from ODIN too!
This happened to my SM-N900T when I installed a custom Recovery which contained the wrong '/sepolicy_version' for my device. The Recovery developer fixed the file but I had to format '/data' after installing it to get files with the correct policy.
Frank
---------- Post added at 01:16 PM ---------- Previous post was at 12:59 PM ----------
In your root directory, '/se_policy' should look like this, but notice that this is Android 4.3:
VE=SEPF_SM-N900T_4.3_0002
HS=7708d6f9dfc68813c4dddb915812c67b
HA=7136aebc8fc8205ec9adde19ca84e501
HP=0ef457e4c9cbf00b9100f4872e3f7d50
HF=852e176fdcb7a45fc1617bd4e93c2bf9
HM=7bd39dbe5813e94be374bee74d87bf0c
If it shows the wrong device then you can probably fix it by flashing the correct TWRP. And you will probably have to format '/data'.
Frank
Frank Westlake said:
This happened to my SM-N900T when I installed a custom Recovery which contained the wrong '/sepolicy_version' for my device. The Recovery developer fixed the file but I had to format '/data' after installing it to get files with the correct policy.
Frank
---------- Post added at 01:16 PM ---------- Previous post was at 12:59 PM ----------
In your root directory, '/se_policy' should look like this, but notice that this is Android 4.3:
VE=SEPF_SM-N900T_4.3_0002
HS=7708d6f9dfc68813c4dddb915812c67b
HA=7136aebc8fc8205ec9adde19ca84e501
HP=0ef457e4c9cbf00b9100f4872e3f7d50
HF=852e176fdcb7a45fc1617bd4e93c2bf9
HM=7bd39dbe5813e94be374bee74d87bf0c
If it shows the wrong device then you can probably fix it by flashing the correct TWRP. And you will probably have to format '/data'.
Frank
Click to expand...
Click to collapse
Huh... I now I remember... I was on TWRP when the problems started... I'm on Philz now and I still have it. Would this fix the write protected internal SD card issue too?
Try this ---> http://forum.xda-developers.com/showthread.php?t=2684384
meoshe said:
Try this ---> http://forum.xda-developers.com/showthread.php?t=2684384
Click to expand...
Click to collapse
That looks like the same problem and a much simpler solution, but make sure you have a good policy file first.
Frank
---------- Post added at 01:37 AM ---------- Previous post was at 01:26 AM ----------
Up above I use two filenames, '/sepolicy_version' is the correct name of the file. In my case TWRP had the wrong '/sepolicy_version' until the developer fixed it. I still recommend installing the most recent TWRP to get all the right files -- make sure it's the right version (4.3 or 4.4) -- then run restorecon. Then after the fix, return to Philz if you want.
Frank
Did your phone die @deBricker or did this solve the problem? Other people might be waiting with the same problem.
Frank
No. Had to go in recovery and wipe my internal memory (lost everything since I was stupid enough not to make an updated backup... my last one was a month ago) after that, it's been smooth sailing.
I didn't even see that post until today.