Related
So my phone got stuck at boot screen. Bell says I get full replacement, but I'm gonna lose all the data. I have the internal full of children opening gifts on Christmas.
Reading a million forums. Tried to learn enough to flash the firmware with odin. Tried flashing the stock JH2 back to phone. Phone boots to recovery and says problem mounting SD.
Can ADB be used to connect to phone in "Download mode" to Pull the media???
PLEASE PLEASE help?????
after odin is done the phone reboots to:
E:Can't mount /dev/block/mmcblk0p1
(no such file or derectory)
E:copy_dbdata_media: Can't mount SDCARD:\copy default media content failed
I'm still desperately trying to get my files. I've read about 1254 more threads. Found this one about flashing back to eclair...
http://forum.xda-developers.com/showthread.php?t=797302
So far I tried JH2, JL2, JM8 and still no luck. Anybody out there got any ideas?? links to help or compassionate remarks?
Phone no boot need remove files inside...is this really an impossibility??
Argh.... it never happens when the internal has useless data aye.
You tried flashing a firmware using all three files (PDA, modem, CSC) with repartition?
P.s. apologies if you have tried all this, just trying to establish a baseline
Sent from my GT-I9000 using XDA App
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Hoodmin said:
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
Repartition only erases the 2GB portion, ive done several repartitions and it never touched my personal files on the internal SD
Hoodmin said:
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
That won't work...the 'internal SD' is not a SD card in the traditional sense (standard, mini, micro) - it's a physical chip (IC) that's soldered on to the mainboard.
I haven't heard of anyone being able to pull data off a phone that's got the mmcblk0p1 failure. The best I've heard is of people repartitioning/formating the sd memory in order to get it working again - but of course, that would mean losing all data...sorry...
As what EarlZ said, repartition won't touch the part of the SD dedicated to user data. I've flashed via Odin countless of times and never once did my internal SD get wiped with a repartition so why not flash to something like JPU with repartition using 512 pit file?.
Edit: and reading the error seems to tell me it's a problem in the 2GB portion of the internal SD where the system and such get stored. So yes, do try a repartition. I guarantee you that your user data will be safe. The only time it would get wiped is if you actually choose to format that partition like how one does in Windows or through the settings. Odin flash won't do this most definitely.
If that fails...
Also take a look at this...
This guy seemed to have been lucky and got is supposed dead I9000m SGS working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
Well hot damn them are some good replies. I was brave enough to try re-partition and a few mod roms like in the thread mention as well as a few thread techniques I read. I must have read about 4622 threads by now. Still no luck for me I really really appreciate the help.
Thinkin I might just go wrap up the kids christmas presents tonight while they sleep and just make em open them all again hahaha.
In the mean time I'll just keep readin and keep tryin. Learned a lot at least.
So....
Original problem = boot cycle
-I flash back to JH2 and at least to phone gets to recovery mode and i see the mmcblk0p1 error. progress
-try flashing to the newer JL2 and it goes back to boot cycle
-try flashing back to JH2 to get recover mode again and still boot cycle
-read a million forums about trying mod roms and other techniques and still boot cycle
-get encouraged that re-partition will only affect OS side of SD card and try a million things again. Still boot cycle
-decide to go back to the JK4 that i started on and seems to be the root of all evil and then BAM recovery mode returns and this time it even recognized the device
-any attempt to connect with device either with kies or windows explorer causes PC crash
-phone even recognized by ADB I "think" this program could be used to try and "pull" media from the device but that's just a guess and I don't know how to use it
-the error now is not mmcblk0p1 instead: E:Can't/b mount /devlock/stl10 which could mean something or could be just the same and it leads me to this thread: http://forum.xda-developers.com/showthread.php?t=788850
-try flash techniques in the thread and back to boot cycle
-try going back to the JK4 so I have recovery mode again and still boot cycle. progress gone
I'm gonna flash this damn thing again and again until the damn copper lights on fire
Wow i Admire you man.Listen i dont know much about ADB but i think i saw a post of someone that literally pushed files in his internal card with it,and i clearly remember him saying he could browse through his phone although its card was burned.If so then a single copy would be possible.Since i cant help more,you better start reading on how to use it and find basic commands for it.
I wish you the best man!!!!
Have you tried this kernel: http://forum.xda-developers.com/showthread.php?t=901772
I seem to be able to get that running on my dead GT-i9000M. It has a file browser so maybe you can see if your pictures are even there/accessible. Also has a USB Mass Storage option but it didn't seem to work for me.
However, phone is still dead and needs to go in for repairs/replacement.
OK so now I'm f&*#ed
Tried JP1 method from this stupid page
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
and now I don't have download mode anymore.
somebody plz just shoot me
EDIT: Ok excuse this panic post. I still had connection to ADB and a simple "adb reboot download" command got me back.
Wow thank JDROM. This recovery mode really looks promising. I got the file manager working but I can't seem to find any directories with DCIM/ label or any media. Sure looks like this could help me somehow. Might only have half the SD mounted or something. I'll have to play around and read some more, but I gotta say this is the best progress I made in a while.
THanks SO much
Edit: Found in File manager to run partition manager and formating options show up. In here there is mounting options to /mnt/sdcard or /mnt/external_sd except when I try it returns the E:Can't mount /dev/block/mmcblk0p1 to /mnt/sdcard with parameters vfat(null) So hmmmm....
Edit: Also learned a bit more about ADB commands to possibly ""Adb pull /sdcard/DCIM"" if I ever get it mounted.
Well that's it for me. The quest is over. I admit defeat. Memories Lost. Game Over
That sucks man...i had a bunch of stuff on my phone that i lost when the internal died....mine took out the external sdcard i had in it too - so all my backups were destroyed as well!
Moral of story: Save important crap on something like dropbox!
Some dev should make a program that automatically syncs certain directories (like pictures, or backup folders) to dropbox. I'd donate for that.....
Hello,
With the issues I was having with the CM 10.1 nightlies, much as I would like to stay, I decided to install the Minimoto 1.7 ROM into the second ROM slot (created with Safestrap 3.05). First, let me say "wow!" I never thought I would see this much speed and available RAM on my Droid 3. Thank you very much, thingonaspring.
For the most part, everything is working great *except* access to both the sdcard (internal) and sdcard-ext (external) storage areas. I read many posts in the Minimoto thread and searched around but nobody else appears to have encountered this which I find rather odd.
After the initial install and after reboots, these areas were still not accessible. I finally ran the terminal emulator and found that, for some unknown reason, they were *not* mounted. I *did* find the internal storage (/dev/block/emstorage) mounted at /ss but not at /mnt/sdcard. I became root using "su" and did the following:
# mount /dev/block/emstorage /mnt/sdcard
# mount /dev/block/mmcblk0p1 /mnt/sdcard-ext
Now I can access them along with all of the files I previously had there. The included file manager, when started, presents buttons for "Internal Storage" and "SD", but it still complains that internal storage is not mounted. It will allow me to access the SD card, though.
Under Settings->Storage Settings, everything under "Internal storage" and "SD card" says "unavailable" and both the mount and format buttons are grayed out. Yet, under the "Windows Media Sync" heading, I *can* choose between internal and SD *and* it even shows the correct available/total space values.
Why were these not mounted to begin with? Is mounting them manually an acceptable solution? If it is, where do I put this information so that it occurs at boot like it should (there is no /etc/fstab on Android)? Did I perhaps do something wrong when installing this ROM, maybe because I used ROM slot 2 instead of 1 (which still contains the most current CM 10.1 nightly)?
I really want to get this resolved because, so far, everything else appears to work wonderfully. Even 3g access, which I still haven't gotten working with CM 10.1.
--John Gruenenfelder
I've been running Minimoto for months and both /sdcard and /sdcard-ext are mounted at bootup for me, always, just like stock.
So, I wish I could tell you why, but I cannot.
I guess what I would do is start over. Reboot into Safestrap, remove that second slot and recreate it. Flash the ROM and restart the phone. Do not wipe data/factory reset after flashing the ROM or you will be missing some files (basically, some files required by the customized initial setup application.)
It seems to be fixed! See below for (perhaps) how...
Okay, I gave this a try. Rather than wiping ROM-slot-2, I had enough free space to create slot-3 and I reinstalled Minimoto 1.7 there. Also, this time I downloaded the zip file on my PC and transferred it over rather than downloading it directly onto the phone. Using the UNIX "cmp" tool told me the two files were identical, but I still used the "new" one. It installed fine and I did *not* perform a data wipe.
Unfortunately, same issue. When the device starts I can see the "Preparing XXX storage" messages appear in the notification bar for both internal and SD storage. There are no error messages, but it also did not actually do anything. Then, using the terminal emulator, I gave a long read through the dmesg output. I am more familiar with the kernel messages one sees when booting Linux on a PC, but I still did not see anything unusual.
So, back into Safestrap recovery. This time I tried something different. First, I noticed that the Safestrap file manager *can* see both storage areas and in the locations where they ought to be. This is not new, actually, it has always been the case. Second, I uplugged the USB cable. I have been using it for charging (of course), but at present it was plugged into my laptop and not into the wall charger. Depending on how the mounting occurrs and the exact mount order, I thought this might interfere. Thirrd, and finally, I used the "Fix Permissions" button available in Safestrap on ROM-slot-2 where I had first intalled Minimoto.
After doing these two changes I rebooted the device back into ROM-slot-2. Surprise! I once again saw the "Preparing" messages in the status bar except this time it really worked. The two storage locations are available where they should be and I an access the data just fine. Even the "Storage properties" screen in Settings shows both as mounted with the correct available/total space values given.
Since a plain reboot did not work previously, I have to assume one of the two changes I made fixed the problem, though, since I did both at the same time, I cannot be sure which fixed it.
Now I can get back to enjoying the impressivee speed from Minimoto while I wait to see if (or perhaps when) either the 3g or HW keyboard ALT-key issues are fixed in CM 10.1. Of course, given how much slower CM 10.1 operates (by virtue of using *much* more RAM than Minimoto), I think I might find it very difficult to switch.
--John Gruenenfelder
If you've been trying to hoot while plugged into your laptop I can see it causing issues as when usb mass storage is active, the device can no longer see the sd cards. That is why we have a separate data partition for apps and app data. So if the computer is trying to mount them and denies the phone the ability to mount then I could see issues arising
Sent from my XT860 using xda premium
So I have installed several versions of this ROM since it began, however when I upgraded to 1-12-14, all went well except my internal SDcard will not be recognized. This means I can't use the camera or Titanium Backup, etc. However, I can see and use the external sd card w/o any issue. Upon every boot I get the icon saying that I need to format SDcard0, but it never completes, only soft reboots and the icon is gone until the next full reboot. I flashbooted boot.img twice after doing a FULL wipe. I have tried reinstalling 3 times doing FULL wipes every time, still get the same. When I boot into recovery and try to wipe SDcard, I get an error saying
can't mount /dev/block/mmcb1k0p36 (Invalid argument)
Error mounting /internal_sdcard/!
Skipping format
I have also just tried the new 1-15-14 build and get the same results. I have fastbooted the boot.img each time. Please help. I have installed many ROMs on this device before w/o ever an issue. What did I do wrong and how do I fix it? TIA!
Reboot recovery
Mount USB storage...
Plug phone into computer...
Let windows format corrupt partition...
Profit
Sent from my Vivid 4G using Tapatalk
Just putting another method which worked for me (one time issue and fix, so it's a crap-shoot). I don't have the luxury of connecting to a computer via usb for anything except charging.
-properly flash a sufficiently different ROM (I had kitkat, so I flashed ICS)
-start ROM up, check if fixed (mine was not)
IF NOT FIXED, CONTINUE
-mount the SD card in your recovery (mine is WCX recovery)
-reboot your phone into the ROM
This method worked for me. I saw in a different forum that when this happens it's usually because a file that describes the partitions gets corrupted and that because ICS and GB partition the SD cards and internal storage in a different way than Jellybean or Kitkat, that flashing a different ROM (if problem is on ICS/GB, then flash KK/JB, and vice versa) will force an overwrite of the file in question.
This is not as easy as rignfool's method, and once my charge port arrives in the post, I will abandon this method and use Windows to repair the partition like a sane person
Also, it seems like all my media on the internal storage has been wiped, but wutevr :/
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Yuskow said:
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Click to expand...
Click to collapse
If this is directed at me, this happened after I installed the March 17th or 18th nightly (put a new one on every once and a while). And to be completely fair, I had accidentally selected factory reset in hboot (thought it was highlighting recovery, boy was I pissed).
The problem (or so I've read) with installing another kitkat/jellybean ROM is that the SD card is mounted the same (/storage/sdcard0, and external SD is only /storage/sdcard1) as opposed to ICS/GB (I only remember that you access external SD through /sdcard/ext_sdcard or something to that extent). Only when the SD cards will be mounted at differing locations will the system re-write the files specifying mount points.
Hi all
For days I've been flashing all different kinds of things in hope to get my phone fixed, but I just can't find the answer.
So for those of you most kind enough to help, here's what's going on with my captivate (at&t)
I took it out of my pocket last week and the phone was frozen. Sometimes it happens... a quick pull out of the battery and re-insert fixes it in most cases... but not this time.
After restarting the phone was hanging on boot screen (CyanFox bootscreen).
I restarted... 15 minutes on that bootscreen still. I had no idea what was going on.
So I decided to reflash. It was a big decision, seeing as this ROM has been working absolutely fine for weeks, but I needed to get it working.
Soon after getting it into recovery, CWM was saying that it couldn't mount /sdcard
I tried even flashing using Odin to go back to stock following the guide here: http://forum.xda-developers.com/showthread.php?t=1300843 still not working.
Most of them ended up showing that little android loading bar for a second or two, but then get stuck in a boot loop.
I tried flashing many different kernels, and different recoveries, but everything all pointed towards: Unable to mount /sdcard
But alas, finally I found something that more or less works. I flashed the Initial Kernal for Cognition: http://forum.xda-developers.com/showthread.php?t=1127578
And I finally got back into a working device... or so I thought.
The phone is still unable to access the internal SDCARD. Just says 'unavailable'. I tried putting in an external 2GB sdcard, but that reads as Total Space: 00, and Available Space: 00
The external sdcard I know works, because my wife's samsung mini2 reads it just fine.
Multiple formats and it still can't be read.
I tried plugging in the device into my pc and select mass storage, but although the computer detects that the phone is plugged in (in device manager) the 2 drives for internal and external both remain hidden, and cannot be accessed.
I have absolutely no idea what to do next. I've used Odin and Heimdall, Repartitioned, and followed every stickied guide here, but I still can't find what to do.
I really appreciate any help anyone can give me on this.
Just for the record, ADB works just fine from my PC. I can send the commands to the device, but mounting the sdcard still proves impossible at this stage (no file exists).
Thanks again, I look forward to any advice anyone can spare.
flapsy said:
Hi all
For days I've been flashing all different kinds of things in hope to get my phone fixed, but I just can't find the answer.
So for those of you most kind enough to help, here's what's going on with my captivate (at&t)
I took it out of my pocket last week and the phone was frozen. Sometimes it happens... a quick pull out of the battery and re-insert fixes it in most cases... but not this time.
After restarting the phone was hanging on boot screen (CyanFox bootscreen).
I restarted... 15 minutes on that bootscreen still. I had no idea what was going on.
So I decided to reflash. It was a big decision, seeing as this ROM has been working absolutely fine for weeks, but I needed to get it working.
Soon after getting it into recovery, CWM was saying that it couldn't mount /sdcard
I tried even flashing using Odin to go back to stock following the guide here: http://forum.xda-developers.com/showthread.php?t=1300843 still not working.
Most of them ended up showing that little android loading bar for a second or two, but then get stuck in a boot loop.
I tried flashing many different kernels, and different recoveries, but everything all pointed towards: Unable to mount /sdcard
But alas, finally I found something that more or less works. I flashed the Initial Kernal for Cognition: http://forum.xda-developers.com/showthread.php?t=1127578
And I finally got back into a working device... or so I thought.
The phone is still unable to access the internal SDCARD. Just says 'unavailable'. I tried putting in an external 2GB sdcard, but that reads as Total Space: 00, and Available Space: 00
The external sdcard I know works, because my wife's samsung mini2 reads it just fine.
Multiple formats and it still can't be read.
I tried plugging in the device into my pc and select mass storage, but although the computer detects that the phone is plugged in (in device manager) the 2 drives for internal and external both remain hidden, and cannot be accessed.
I have absolutely no idea what to do next. I've used Odin and Heimdall, Repartitioned, and followed every stickied guide here, but I still can't find what to do.
I really appreciate any help anyone can give me on this.
Just for the record, ADB works just fine from my PC. I can send the commands to the device, but mounting the sdcard still proves impossible at this stage (no file exists).
Thanks again, I look forward to any advice anyone can spare.
Click to expand...
Click to collapse
i had the same problem a couple of weeks ago...
you internal sd card is dead...
you can do nothing about it for now...
if you want to confirm open your camera app and see if you can take any pictures...
if no, then follow the things as i say..
this requires you to do a partition of your external SD card and to that it should be formatted, so take the neccessary backups..
1) download this http://www.mediafire.com/download/sbjd049x4m36pb6/I897UCKI2_noBL_BoogsKernel.rar
2) after flashing this stock firmare with cwm, open up the recovery.
3)follow this guide http://forum.xda-developers.com/showthread.php?t=1447303
4)i couldn't get ICS to work..
5)so you can now use kitkat roms only on the captivate as we have the kernel for 4.4 only with swap sd
6)so after you follow the guide and boot into ICS, copy the rom.zip which you want to flash and the neat kernel swap sd, which can be found here http://www.mediafire.com/download/s34o69u39u66x8n/NeatKernel_v1.03-[02-08]-cma-swap-captivate.zip, be sure to thank the developer here http://forum.xda-developers.com/showthread.php?t=2548081
7)so flash the kitkat om which you want to use,and then flash the neat kernel after flashing the rom after that you can flash the gapps and reboot..
if you do everything like i said, your cappy will be up and working again..
Sir, you are a gentleman and a scholar
Although it didn't go exactly as planned step by step, with your instructions I finally managed to get it working on my 2GB external card.
Here was the process I did
1) Downloaded CM11, Gapps, Stock Kernal and the SwapSD kernal you linked
2) Flashed the stock kernal, the phone just went on a rebooting spree.. but after a few attempts I got it into recovery using the 3 finger combo
2) Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1447303 to partition the external SD card. (Since I have only a 2GB card, I partitioned 1GB for data, and 0MB for swap)
3) Done the classic wipe sys/ cache/ data
4) (Here is where things changed a bit for me, as I couldn't boot into ICS either. And no other rom would work at this point) I installed the new SwapSD kernal to get a newer version of CWM by mounting USB storage via CWM and copying the files to there.
5) The device rebooted a couple of times during install, but it automatically went straight back into the newer CWM.
6) Installed CM11, let that finished and installed Gapps straight after.
7) Rebooted and the phone is now reading my external sd card as its internal storage, which is fantastic
Although with it's limited storage and broken internal storage, it still needs replacing, but at least I now have a device from which I can still run a few apps on regardless.
So thank you again dude
*edit* just need to figure out why the adb drivers decided to not work anymore.
Sometimes I hate having windows 8...
So, after MONTHS of trying to fix my red 600 dollar paperweight, I feel it is time to give up and make a post here. I have tried everything from using RUUs, factory resets, restoring from backups, ADB sideloads, etc. and have had absolutely zero success. So here's the story!
A couple months ago, I installed MultiROM on my HTC One M7WLS in an attempt to get Ubuntu Touch to work on it. The install of MultiROM went smoothly and after a reboot, my phone was working normal. Naturally, once my phone was reconfigured I created a backup in the MultiROM TWRP (v2.8.0) to ensure I didn't lose my current state (or so I thought). After the install, I went to install a secondary rom on the phone on another partition. After the second ROM installation completed, I rebooted my phone, only to be stuck in a boot loop. From here, I went to recovery once again and deleted the new partition, and restored my previous one when I had it working. After this is when everything started going bonkers. Upon rebooting my phone, I discovered I no longer had a working radio (it completely disappeared; nothing even shows in settings for Baseband version) and I no longer had internal storage!!! I can access my phone's internal storage through File Manager, but I am unable to install apps, take pictures, or even watch videos on Facebook because it tells me I do not have internal storage, and that I need to insert an SD card. I have tried several things in an attempt to get my phone back to working condition, but I am still stuck with a copy of Cyanogenmod with no radio or internal storage.
Honestly, I have no clue what to do from here so I hope someone has insight on how to do this. I have tried uninstalling the MultiROM addon, but it does not allow me to since I can't put the ZIP file on my phone, or sideload it in since ADB says there is no phone connected. ANY AND EVERY BIT OF INPUT IS APPRECIATED!
So today I managed to restore my recovery to vanilla TWRP 2.8.1.0, and also managed to flash a ROM to the device. Sadly, in the OS I still have no internal storage or baseband, and I have not been able to find ANYWHERE how to restore JUST the baseband for this phone. Also, I have not been able to find how to fix the problems I am having with the internal storage. Once again, any and all input is appreciated
halodub said:
So today I managed to restore my recovery to vanilla TWRP 2.8.1.0, and also managed to flash a ROM to the device. Sadly, in the OS I still have no internal storage or baseband, and I have not been able to find ANYWHERE how to restore JUST the baseband for this phone. Also, I have not been able to find how to fix the problems I am having with the internal storage. Once again, any and all input is appreciated
Click to expand...
Click to collapse
Go into TWRP and choose wipe / Format Data / type yes
when it's done you will have a blank device but the sdcard should be back.
get adb working on your phone with post 2 / faq 2 here
http://forum.xda-developers.com/showthread.php?t=2541082
when you get adb devices to work from TWRP
go to advanced / sideload
then on your pc - adb sideload rom.zip
be sure the rom is in the same folder as adb
If you still have problems here's the Sprint RUU
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856