Hi,
I've a weird issue with my SD card. I've done a backup using RA but since i rebooted, my android does not recognise the sd.
I've plugged my sd into my laptop and i do see all files but nothing when i insert it into my android.
When i'm in recovery mode, i've got this log:
lun0: unable to open backing file: /dev/block/mmcblk0 in "dmesg"
I do not understand how my sdcard could be broken ?
Thanks
Ced
Up Up Up....
Any idea where this log comes from. Is this an hardware issue on the phone.
I've swapped my old microsd card by a new one but same result so i'm leading to a potential SD card problem.
Any body has an explanation for this log "lun0: unable to open backing file: /dev/block/mmcblk0" ?????
Thanks
I have a similar problem tried a new rom, wiped, flashed, rebooted then it had sdcard mount problems thought it was the rom so i wiped and then tried to flash with no luck it says
build: RA-sapphire-v1.5.2H
E:Can't mount /dev/block/mmcblk0p1 (or dev/block/mmblk0)
(No such file or directory)
E:Can't mount SDCARD
Boots RA-sapphire-v1.5.2H and fastboot just fine
maybe similar problem? is the phone bricked?
SAPPHIRE PVT 32A
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Really need some help here i'm stuck
Can anyone help? i'm totally stock
up up
I've looked a little bit more:
So when i boot using the recovery-RA image version 1.2.3h or the lastest recovery-RA-saphire.1.5.2.H, i cannot see my sdcard
connecting via adb i can see that in /dev/block/ there is no device mmcblk0
In dmesg, i see the qualcomm MSM SDCC controller.
Question:
- What are the conditions to see this mmcblk0 ?
- Is there a way to turn on debug under the recovery-saphire image to track down the issue and mmc events ?
Thanks
Ced
SDCard not being read by phone due to phone entering memory debugging mode
To run this fix, you should have .qxdm files on your sd card in the fat32 root directory generated by the phone. These are memory debug files generated by the phone, as your phone has entered a memory debugging state. If you do not see those files on your sd card this fix does not apply to you.
Depending on your problem you may need to change your SPL.
Note that your fastboot might be S-ON, so you wouldn't be able to flash from recovery.
Case 1) HBOOT version 1.76.x.x (you have a 32A Magic or Hero)
In this case your fix is simple. Get your phone in fastboot mode, and run the following command. There are many guides on how to perform fastboot, which I am not repeating here:
fastboot oem enableqxdm 0
Case 2) Your HBOOT says 1.33.x.x or something else
First make sure you have radio 2.22.19.26I. If you don't, make sure you have the appropriate recovery. You can use the recovery flash_image command to flash one.
After this, downgrade your ROM to HSPL, then back to whatever SPL you were using: http://forum.xda-developers.com/showthread.php?t=455860
When I did this for my G1/Dream I also made sure I was on radio 2.22.19.26I with the correct recovery before downgrading to the HSPL. You might not need this radio to work with this SPL, but better safe than sorry.
* * *
These are possible solutions. If this doesn't work something else is wrong.
I only have seen case 1 for the hero. The other cases might work for other phone models, but the cases I have presented should be sufficient.
And post to Q&A instead of dev next time
xaueious > do you have a link to a proper guide for that?
Related
OOOOPs i seem to have done something wrong
i installed a fj build from here:
http://forum.xda-developers.com/showthread.php?t=490598&page=2
to get the numbers in UK instead of US format
and now the phone does not load /
I had jf rc9 root and bootloader have tried a wipe and reload with no luck.
Please help !??!
reinstall a different JF build you should be fine, unless you had your apps moved to your SD card and then you need to push the modifued mountd.conf and init.rc and make sure that /system/sd exists
how do you get access to sd card with usb without turning phone on? as cannot get popup on my computer to install a new build ?
i can load system recovery and bootloader screen with usb cable attached but cannot access on pc? - sorry probably an obvious solution have missed - mount / unmount facility
i can see removable disk in my computer but when i try to open states:
please insert a disk into drive E:
but is coming up that a mass storage device is connected
tubaking182 is a star.
prob sorted. opened sd with another phone.. got new build and installed it again.
done ! *phew*
Hi everyone, looking for a little guidance.
Phone: Android G1 (Rogers Canada Dream) running Cyanogen 4.2.15.1, been running fine since 4.2.6.1
Removed SD card while it was on and it rebooted... when it restarted it showed no applications and said the SD card was inaccessible and required a format. After rebooting a few times with no success I bit the bullet and formatted it... all apps are gone except for the ones that are on that image for Cyanogen. I have no market app to download new apps and when I plug it into my PC and mount it I don't see it show up as a drive like it did so I have no way to get the apps back on.
Has anyone had this happen before? Phone still works but I need to get it back to a state where I can get access to the SD and install the market... Any suggestions appreciated!!
There is a thread on the HERO section of Modaco site called "no adb, no sd". I think the 1st post on the last page MIGHT help. There are adb commands you can run to see if the phone has randomly stopped accessing the SD. Worth a shot.
PM me if you have trouble finding the thread n I'll have a look when I'm at my laptop.
Sent from my HTC Hero using XDA App
I misunderstood I think.
So it is now showing an sd present? Have you tried formatting in a pc?
Tried reboot without the sd in, then insert once fully booted again?
Sent from my HTC Hero using XDA App
I remove the SD Card, formatted it in my PC put it back in the phone and I can store pics and vids on it and access them but cant see or access it from the PC when in the phone. I also have no file browser so I cant install any apps or even access the market icon is gone).
D RoiD said:
Hi there! I had posted on the forum with the G1 issue where my SD card seemed to have died.
http://forum.xda-developers.com/showthread.php?t=738105
I have since removed the SD card and reformatted it, I can store pics and vids and replay them so the card is fine. I tried letting it boot up then adding the SD card when booted, that caused it to reboot, same issue...
Not having access to the card, I cant install any apps or browse the SD to install from there... really sucks
I'd be willing to blow it away and restart too and install CyanogenMod-5.0.8 but I need some guidance.
Click to expand...
Click to collapse
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
ddotpatel said:
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
Click to expand...
Click to collapse
Pics taken DO save to me SD. I Can access them from a PC is I remove the SD and put it in the PC. Not when I plug the phone in via USB then tell it to mount.
I just did a low level format, same issue.
UPDATE: Just tried the Android System Recovery and Toggle USB-MS and it shows on my laptop now! Going to try the recovery backup now.
aha,... so its just a mounting issue, not that the hardware has turned itself off.
Once when using an older ROM (maybe Villain 10?) we had this same issue, not able to mount SD,... going into Settings --> Connect to PC --> and turning off Notify/ask me solved the problem.
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
D RoiD said:
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
Click to expand...
Click to collapse
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
akapoor said:
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
Click to expand...
Click to collapse
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
D RoiD said:
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
Click to expand...
Click to collapse
If your contacts are saved in the phone's memory, then yes. Any settings, apps, configurations that are stored on the phone will all be gone.
A wipe pretty much gives you the factory settings. (As if you just bought the phone) So you'll have to re-signin into your Google Account and let the Contacts Sync, etc..
EDIT: Depending on what you are flashing (flashing and wiping are two different things), you may not even need to wipe.
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
D RoiD said:
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
Click to expand...
Click to collapse
Try this:
-Confirm the Image-
1) Make sure you have the full image you are going to flash. (Compare MD5 Hashes and/or just redownload the image)
2) Make sure the image you are flashing is the in the ROOT directory of your SDCard. In other words, it shouldn't be in any folder.
-Flash the Image-
1) When in Recovery, choose to flash an image.
2) Depending on what recovery you have, you may have to select/find the Image you want to flash.
3) Flash the image
-Wipe (Depends)-
1) If you are coming from a different ROM base (ie anything -> cyan), you'll want to wipe.
2) After the phone successfully flashes the image, wipe the phone.
Reboot.
Let me know how it goes.
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
D RoiD said:
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
Click to expand...
Click to collapse
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
akapoor said:
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
Click to expand...
Click to collapse
The SD card reader in my phone? It has to work if I can read an write to it ( tested photos and videos) and in recovery I was able to make a backup.
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
D RoiD said:
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
Click to expand...
Click to collapse
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
akapoor said:
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
Click to expand...
Click to collapse
Ok I did a wipe and now I see the SD when mounted on the PC with the phone on.
I have my market icon back so I can reinstall my crap.
I'll leave it as is for a bit but appreciate everyones input!!!
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
Hi
I want to install the ICS ruu. But first I need to upgrade my hboot since I'm still on 6.98.xxxx. It's s-off by revolutionary.
So I tried to upgrade the hboot with this guide: http://forum.xda-developers.com/showthread.php?t=1858508&page=2
It didn't work.... Steps a and b work, then typing the commands in b1 wasn't possible to typs the "su", I already had this ~# after the second command. I read that this happend with others too.
The back up command (c) also worked, but then the problem comes. flashing the new hboot with the given command (d) did not work. I always get the error:
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd: can't open '/sdcard/hboot.img': No such file or directory
I'm sure the hboot.img is on the sdcard, I checked it several times
What am I doing wrong?
1- Check if there is the backup.img file on the SD card? Just to make sure your SD card is OK
2- Make sure your hboot.img file is valid, i.e it is not corrupt while downloading, hidden attribute was not set, etc...
1. you're right, the backup.img does not exist either. What's the problem with my sd card? I never had problems with it so far.
2. I think the file is ok, it's not hidden. I downloaded it from two different places (the mentioned guide, and another guide to install eng hboot)
what can I do to make the sd card work properly?
Try with another sd card
BTW, what is your current "software number"? What is your phone's region?
Sent from my HTC Desire S using Tapatalk 2
I'm running Endymion V3.5. What do you mean with phone's region exactly?
ok, I'll try with a different sd card in the evening. But I think it's strange that the card should be broken, it always works..
I have read a similar thread yesterday (I don't remember which one it was). The guys simply unmount and remount the sdcard using adb and... VoilĂ .
Thanks. I was looking for a similar problem but did not find anything. I'm going to try this too.
Thank you guys. Now I managed to upgrade the hboot. I really just had to mount the sd card again and then it worked.
No I go on an try to install the PG88IMG.zip
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.