Hi.
I have rooted my Galaxy note GT N7000 & installed a "XXLT4 240 Dpi v2.2 Multi-lang, Stable Aroma Installer" Rom.
All worked perfectly & also working now.
But after complete installation, I have stupidly formatted the internal storage on MAC in "MS DOS Fat" mode.
And now,
1. After starting my phone, I am getting the message "USB storage damaged".
I've tried formatting internal storage (/sdcard) from CWM recovery but it says "can't mount sdcard"
2. I've also tried connecting it to MAC again but the phone cannot go into mass storage mode as well. Same happens in Windows.
Now what can I do? I don't bother about any data in the internal storage. Just want the working usb storage. ASAP!!!!
Please Help Please!!!!! :crying:
Related
I followed this simple steps
http://www.addictivetips.com/mobile...based-custom-rom-on-t-mobile-samsung-vibrant/
and installed cyanogen mod on my samsung vibrant.
The problem i am facing is that its not detecting my internal 14GB memory.
When i go into clockwork recovery mod, there i am able to mount my memory
and its visible in my pc.
How to make it usable in phone?
i tried with different cyanogenmod rom's from stable to nightly build.
Nothing make the sdcard (internal memory) detect after phone starts.
One thing is its not cracked because i am able to access it from recovery when i mount the usb storage using clockworkmod, it displays the contents in computer.
I am confused why this is happening
is there anything that i should try ?
why is it available while i mount usb storage from clockwordmod? :x
I got the solution.. check the post if you have similar problem
http://forum.xda-developers.com/showthread.php?t=1633355
Hi,
I was trying to format my internal storage after connecting it to my pc. However the format got interrupted and now the phone does not read the internal storage at all??
What can I do? Can't figure anything out... Also tried to format internal storage using recovery but am unable to do so.
PLEASE HELP ME.....PLEASE............
Okay well- I have solved it out... just putting it in case somebody else goes through this too..
I went to recovery and with usb connected, I tried to mount the internal storage. And then windows connected to it asking me to format again since the drive cannot be used.
I formated and it went correctly this time and bang..problem fixed
Hi,
I'm new to all of this, so please excuse me if I'm posting in the wrong place!
Despite knowing how to preserve and backup my data, I accidentally deleted an album on my samsung GT-I9300 internal memory with a number of files that weren't backed up. I immediately stopped using my device so that nothing was writing to the storage, meaning that my files should still be there as just the pointers will have been removed.
In desparation I have now learned the following:
1. UMS - No longer an option, just MPT on the device.
2. No UMS - means that I can't use windows recovery software that is out there as the internal memory isn't recognised as a mass storage device.
3. So I rooted my device in order to try out undelete, DiskDigger and the pro version of Hexamob recovery.
Surprisingly, this went well (I am not experienced). I used the droidviews tutorial CF-Root-SGS3-V6.4.zip and odin. (Thank you droidviews).
4. Now I was able to try out Undelete (no good for the internal ext4 memory, has to be fat). Disk Digger and Hexamob have found some of my jpeg and mp4 files, however not all of them despite me turning the phone off.
5. Next step, I installed the android terminal emulator so that I could try this:
su
setprop persist.sys.usb.config mass_storage
reboot
However, I get the error: "Connected as an installer". Although I can now see the internal and SD card memory on my PC, I can't access them.
6. I know easy UMS from xda developer will only mount the external memory as UMS, not the internal.
So finally, my question is!!
Does anyone know a way to mount the internal memory as UMS please? Or a way to get around this "Connected as an Installer" issue that Samsung have on the device? I really want to try this method so that I can try out some of the PC recovery tools and see if they find any more deleted data before I start using my device again.
My device details now that it's rooted:
Model: GT-I9300
Android: 4.1.1
Kernal Version 3.031-368423 [email protected]#1
Baseband Version I9300XXDLID
Many Thanks!
i havent seen any successful story when it comes to recovery of data from internal sd
bala_gamer said:
i havent seen any successful story when it comes to recovery of data from internal sd
Click to expand...
Click to collapse
Thank you for taking the time to reply.
Hello,
Last week I decided to update my old rooted 4.1.2 for a brand new 4.4.4 ROM you can see in the thread: http://forum.xda-developers.com/gal...29-9-2014-official-stock-rom-testing-t2890734
It went quite well, I used PhilZ 6.48.4 to install the zip file. For not very rational reasons I wanted to do it a second time to make it "perfect"; I did go on PhilZ to wipe all my data like the other time, I verified if "mount USB storage" worked before doing so, it did as in ADB my phone was detected....problem is after formating my phone storage on Philz, strangely I can't connect my phone to my PC anymore. It just says on my computer (Windows 8.1) "USB device got a problem", ADB doesn't detect it anymore, same for ODIN, smells bad lol.
So I wondered if you can use an external SD Card on Philz, in order to put the ROM zip file on this external SD Card and bring back my phone from the dead with it??
I precise that my phone isn't Hard Bricked, I can't start it anymore coz I formatted all, but I can still access to a fully working PhilZ Touch interface...aside that my dumb PC won't recognize my phone again
Thank you for you future help
In Philz when you mount USB storage from "Mounts and Storage" it mounts your external SD.
Great so there is a way out of this! I'll try it out by buying a micro SD card
Please someone help me. I flashed the OOS 3.1.1 community build through twrp. Now I formatted my samsung 32 gb sd card as internal memory in adoptive storage, but when I try to migrate data it says "not enough storage space".
tomriddle25 said:
Please someone help me. I flashed the OOS 3.1.1 community build through twrp. Now I formatted my samsung 32 gb sd card as internal memory in adoptive storage, but when I try to migrate data it says "not enough storage space".
Click to expand...
Click to collapse
Try moving individual apps
Is this the same ota that oneplus is sending to our devices?
Wait, so you defined the SD card as internal memory, and you're trying to migrate the data from internal to sd?
I have the exact same problem. I installed OxygenOS 3 and have the latest OTA update.
I enabled the adoptable storage (can't post links yet) but I can't see my sd card on my pc, when the phone is connected. It shows up in my phone without any problems.
I tried to reformat my SD into portable storage than into internal again but I always receive the "not enough storage message" whenever I try to migrate data.
Quoting from this thread on the Oneplus Forums: https://forums.oneplus.net/threads/use-sd-card-as-internal-storage-cant-also-with-6-0.460967/
this appears to be the answer.
1. activate USB Debugging on Developer Options
2. download adb tools here and put it in one folder.
3. plug your phone to pc via USB
4. now open windows explorer and "shift + right click" at adb folder, then sellect "open command window here"
5. type "adb shell sm set-force-adoptable true" (without quote) and then press enter
6. unplug your phone and go to setting>storage&usb>SD Card
7. click 3 dot on top right corner>setting>format as internal
All credit for this response goes to: https://forums.oneplus.net/members/alfred-albert.860990/
Yeap, those were my exact steps. Actually my SD working is working pretty good in the phone, with all the new apps being correctly installed into it.
Deep down, what is really upsetting me, is that I can't see the SD card on my Windows Explorer when I connect the phone to my PC (and yes, I tried it on different computers as well). I really like to use it as a portable storage device
Before OxygenOS 3 I was using CyanogenMod and this was working as expected.
Do you have a clue what could be going on?