Database Info

Can't mount sd card

Hi there I have a problem
My problem is that i've just root'ed my HTC Desire (I think?)
But my Desire won't boot right.. It only boots to recovery mode...
If i try to install an update.zip with clockwork it says can't read sd card
Pretty much anything i do on clockwork it says "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I have also tried adb but it says device not found
My computer registres my Desire when i plug it in but it doesn't recognize it..
What shall i do next?
Ps. I am running windows 7 x64
Sorry for any spelling errors i hope you understand and are able to help me

I had a similar problem. Try booting into clockworkmod recovery, connect your phone to your PC and select mount USB (or something like that) from the partitions menu. This should give you access to your SD card on your PC. Next, backup the contents of your SD card and then delete all partitions. I used gParted but i guess you can use disk manager in windows. One deleted, don't format the card or anything, just reboot the phone and hopefully you should boot up OK. Now you can format the SD card from within Android. Before you do all this is might be worth removing your SD card and seeing if you can boot up OK without it.

Thanks for reply
When I choose to "mount usb storage" nothing really happens it is not getting recoqnized
The phone won't boot without sd-card
Do you or anyone else know if you can sync your desire from recovery mode?

One step further
Okay i now got one step furter
My phone can now start up, but it still can't registre sd card
It just says sd-card removed
Any ideas

have you tried the "mount usb" option again? Although nothing appears to happen on the phone, you should be able to access the card from your PC. it worked for me in both Win7 and Ubuntu. Other than that I can't think of anything else apart from trying a different SD card.

I can't choose mount usb storage any more.. I can't get into clockwork
Now, when i press recovery I get into a black screen with at red triangle and i can choose from 3 or 4 things, inluding wipe and apply udate
I've allready tried a diffrent sdcard

Similar problem but extra issues
Searched for hours and been in a live chat a number of times and posted on another forum but can not find specific solution.
I wanted to install this http://forum.xda-developers.com/showthread.php?t=789830 HD rom so I partitioned my sdcard (successfully, to ext3 1.5gb, 33mb linux swap, rest fat32) and started wiping via ClockworkMod recovery.
That is when I ran into problems.
Now I can not mount my sdcard - "E:Can't mount /dev/blocl/mmcblk0 (or /dev/block/mmcblk0p1) (invalid argument) Error mounting SDCARD:!"
When I reboot, it just loops.
WinXP will detect my device via adb (when in recovery) but can't see the sdcard.
I had never used fastboot, so I am not sure if I am typing commands correctly.
Htc Desire 2.2 GSM * Uk 3 network * 8gb class2 sdcard * Bravo pvt1 ship S-off Alpharev * Clockwork 2.5.0.7 * HBOOT 0.93.0001 *
Was on Teppic's rom with init.d support http://forum.xda-developers.com/showthread.php?t=773997
Any help would be very much appriciated.
I hope I haven't missed an obvious or relavent thread.
EDIT
Tried sdcard from Nokia6500 but Desire won't mount that either.
When I go into fastboot and plug in my usb, I do get "FASTBOOT USB" come up, so why would cmd "fastboot devices" not detect my phone? In recovery, cmd "adb devices" it does detect it.

I don't mean to be a pest but i doubt any of us can live without our desire's
BUMP

I have the same problem when i make ext etc. for me helps putting card into another phone with android and format it
Sent from my HTC Desire using XDA App

I have no other android device but...
I have managed to get fastboot cmd's to recognise my device.
Just need to figure how to flash my phone but I dont really want to take any backwards steps in terms of flashing a recovery.
Would like to flash my last set-up if it is possible.
Wish me luck lol
EDIT
Sorted....ish
Long short cut short is:
sdcard reader, reformatted to all fat32 with Paragon hard disc manager 8.
copied rom zip to sd.
full wipe with clockwork recovery.
Then inserted sd and installed zip from sdcard.
booted.
smiled again, even though its a practically stock rom.

ok i just waited and it finally booted up normally and went under sdcard and erased all that data this removes the partitions

[Q] Emmc got write-protected or frozen

About a month ago my Xoom (MZ605, EOS 3.0) froze and I had to do a hard reset. After that the tablet became unusable due to the neverending stream of Closed Force dialogs. First I thought the fs and or partition table were buggered, but now I have discovered that whatever I do to the emmc, nothing changes at all: Fastboot flash, SBF flashing, fsck and gdisk in recovery (using adb shell). In all cases, the writing and flashing completes without any errors, but when checking for the results, nothing has changed at all.
Any idea on what might have caused this? Or even better: how to make to emmc writable again? If necessary I'm willing to open it up and mess with the hardware.
Thanks!

Have you tried locking and then re-unlocking the boot loader? Just a suggestion, not promising anything.
It will, normally, wipe your internal storage so make sure you backup any necessary data to a computer.
Sent from my SAMSUNG-SGH-I747 using xda premium

Hi d3athsd00r,
I tried that several times, but just be sure I tried it again. Unfortunately it didnt help Thanks for the suggestion anyway! If you or anyone else has any other ideas, please let me know. The personal data on the tablet isn't important btw (just music), so there's no problem if everything is lost.

Have you tried to format everything in cwm under the mounts menu? (Remove sdcard before doing so)
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2

I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.

ioish said:
I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.
Click to expand...
Click to collapse
I would say your recovery is faulty. Try an earlier version or a different kind
Sent from my Xoom

Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.

ioish said:
Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.
Click to expand...
Click to collapse
odd indeed....have u looked to see if any other devices from other makes have had a similar issue?
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2

I looked a lot on google, but didn't find anything relevant to my case. I even tried to find the datasheet of the chip to if there's a pin (ball) that controls the read-only, like a switch would. Unfortunately it doesn't seem to be publicly available on the internet.
The only topics I found to remotely relevant is:
http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Memory-In-Readonly-Cannot-Flash-EMMC/td-p/1030885
bu that doesn't have any relevant info.

Are you familiar with linux?
If you are, check out the first post on page 2 of this thread.
http://forum.xda-developers.com/showthread.php?t=1609825&page=2
Sent from my SGH-I747 using xda premium

Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.

ioish said:
Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.
Click to expand...
Click to collapse
Very odd indeed. I might have missed this but have you tried installing CWM (not TWRP as it only does the rm) and attempting to do a format from there?
Sent from my SGH-I747 using xda premium

I did try installing CWM using fastboot flash and also a newer version of TWRP and the command completes succesfully, no errors on the screen. When booting into recovery, the same TWRP is still there, as if I never flashed anything

Same problem with my Moto G. Nothing gets flashed. emmc is just write protected and I cannot mount anything

[Q] My phone suddenly says "Damaged USB storage"

So, here's the problem - I was just using my phone normally, when it froze - no big deal, recently it has been getting slower and I was just planning on factory resetting it after I back up everything. But, when it booted and went on the start screen, it says "Scanning USB storage for problems" or something like that and it says then "Damaged USB Storage -You may have to reformat it" and unmounts my SD card, so, I have no storage altogether. When I click on the notification it asks if I want to format USB storage. I just want to know if there's a way of retrieving some files, because in my phone FIle Manager there's nothing, and when I connect it to the PC (Windows XP), it doesn't dettect any stotage, if I do it through "USB Utilities" on my phone it shows two Removable Disks on my computer, which are empty, when I click on them it just says "insert disk into drive", and if I click "Turn on USB Storage" on my phone it just keeps on trying to connect, but can't.
I tried restarting it, taking the battery out, booting without an SD card, booting into safe mode, using adb to pull some files, searched the internet for a few hours but to no avail, found this "Tenoshare Android Data Recovery" but it needs root, which I'm not, so I tried rooting it with SuperOneClick - doesn't work, tried installing super user from the recovery menu from SD card, but it can't install it - I'm wondering if it's wortht it. So, now I don't know what to do - do I root my phone using the methods here (with odin and etc) and use that utility, do I just factory reset it (maybe try recovering files after I've reset it?), or is there any other available option to somehow recover the files? I'm on Android 4.0.4 unrooted with Baseband version I9103XXLQ3 - I had installed it a few years ago (my phone came with 2.3.6 and I just followed the instructions here on updating my firmware).
I'll be very grateful with any help, I just had a few more important files and the last time I backed up was in December, so any help is appreciated

[Q] Internal memory recovery with broken screen

Hello,
I have Samsung Galaxy Core Plus (SM-G350) with broken screen (totally black) and password set up.
I want to recover my internal card data, but any of my ideas wont work.
I have already installed CWM and tried to blindly mount /sdcard by USB, but I dont see any new drive on PC.
I wanted to root it, but any of methods I found wont work (maybe cause Im running in CWM? Yes, USB debugging is disabled).
I tried also 'adb pull', but I need to mount /sdcard (am I right?) where I get 'permission denied' error - in adb shell I cant perform any command except 'cd'.
Im thinking about flashing /data by Odin, but how to create the 'script' for it?
Anybody has any idea how can I do it?

Same Boat...
I've got a broken screen on Centura Galaxy. I managed to blindly ODIN CWM on it, and now get ADB in recovery, but debugging is off so I'm stuck with there. I've tried recovery screenshot tools to try to load rooted ROM, but had no luck. I know JUST enough to be dangerous, and not much more. Just need to get DCIM folder.

@xNombre
If this is still valid, you could try flashing TWRP onto the phone, where it should mount the SD Card automatically and it should connect to the PC automatically too. Search for TWRP (either 2.8 or 3) here on XDA

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.