First off thanks for all the wonderfull help. I finally managed to flash jf1.51 and get the phone running again. Kinda hard 2 do without a sdcard and when fastboot didnt work!!!!!
Now that the phone is running again I STILL have no sdcard slot!! The phone just says...
Removed SD card
The SD has been removed. Insert a new SD card to increase your device
No one has had this problem....
********Original********
We will start with what happened up till that point.
I originally was using haykuro hero with apps2sd (Original Tmobile 1gb sdcard) It worked but slow and crashing on just about everything.
Did the multiple speedups / optimizations for hero.
Switched too Superheros beta v1 hero rom. (No problems other than slow/app crashing)
Ordered a new Transcend 4gb class 6 sdcard.
Waited until I received the new card before switching too Superheros beta v2.
Setup the partitions on the new 4gb just like I had done with the 1gb (and the 1gb had no problems except 4 being slow)
Updated to superheros beta v2 rom. Everything went fine, had like 9mb free (I used the full Rom) After the phone was setup and rom was booted. Used the app2sd app built into the rom. Moved the apps/cache 2 sdcard. Rebooted phone and had a bootloop (kept replaying the htc boot animation)
So remembering reading when hero first came out. I assumed that some of the files for hero did not transfer too the sdcard (Remember when people had problems with app_s.zip)
So I go into the bootloader mode (home + power) to reflash the rom and receive this error (Now during this time I still have the 4gb in)
Installing from sdcard...
Finding update package...
E:Can't mount /dev/black/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
--------------------------------
I have tried 4 different sdcards with 3 different sdcard readers and every one of them has this error. I have tried wiping but didnt change anything.
It is like the phone cannot see any sdcard anymore. I can adb but I dont know anything that could help.
Thanks
-Matt
**Edit**
Have tried partitioning to only fat16 and fat32 on sdcards.
Have tried fastboot with dreaimg.nbh and still does not detect sdcard.
Have tried putting app_s.zip into ext2 partition.
Have tried Downloading different roms and rom types.
Have tried "mount /sdcard" *error mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory*
Have tried Pushing app and app_s to /data from update.zip
Have tried copying app and app_s to /mmcblk0p2 from a linux os "Phone will not detect either partitions" (/mmcblk0p1 is fat32. /mmcblk0p2 is ext2)
Have tried editing mountd.conf and init.rc
Everytime I try and apply update.zip I get these weird files on the sdcard. (http://www.pcxpressrepair.com/android/qxdm_20080904_032341_1.dm , http://www.pcxpressrepair.com/android/qxdm_20080904_032607_1.dm There are just 2 that I uploaded.
Also here is a Logcat of when the phone is trying to boot (bootloop)
http://www.pcxpressrepair.com/android/logcat1.txt
During bootloop here are the mounts
--------------------------------------------
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 76.7M 13.3M 85% /system
/dev/block/mtdblock5 89.8M 14.7M 75.1M 16% /data
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
I have had similar problems but it was because of a bad download. Or I disconnected the phone to quickly from the USB before selecting remove.
Wrong forum. Mods, lock this thread pronto!
Also I received a letter from tmobile saying that they are going to drop me because of roaming too much. I would be nice to get this worthless phone running again. I have until July 7th 2 switch carriers. Because my G1 is basically a paperweight now I was thinking of getting the HTC lancaster with AT&T but it will not be on the market in time.
By the way the phone is acting and no one else having this problem. I am lead 2 believe that this is a hardware issue with the G1. But, every time I try and flash the rom I get that weird file on my fat32 partition. So I would assume that the phone can still write to the sdcard, even though it cannot mount it. So don’t know if it is hardware or not. But, tonight I will disassemble the phone. (Because I’m not getting 2 much help here)
Also if apps2sd or cache failed when the rom was running for a moment what would be a way to restore it back (If the phone worked and no apps2sd is still fine 4 me!). Every time I try and link back 2 the phone it cannot find the directories that are on the sdcard (obvious cuz the sdcard is not mounted) I had this problem before but, the sdcard was mountable so there was no problem.
Would there be a configuration file that I can pull, modify, and then push back with the app2sd/cache info on it. I am moments away from pushing the entire update.zip 2 the phone. I am running out of options on what 2 do or how 2 fix.
-Matt
phone wont even turn on now.
Will it blend? Post results.
As soon as I get a blender
Same Prob
I'm having the exact same problem, has anyone found a solution yet?
Same issue here! Reformatted, wiped the works and nothing. And I have searched everywhere and like you it seems hardly anyone has this same issue. If I can't get it resolved soon I am getting the phone replaced.
I have got the same problem on my vodafone HTC Magic. Can boot to spl, fastboot to recovery rom but cannot mount SD Cards. Anyone found a solution?
Related
So today i rooted my phone installed JF1.41, i partitioned my sd card IN MY G1, since i have a mac and for some reason it wont partition the card right. Then i did the apps2sd deal... Then i wanted to use a theme, well that screwed everything, and it wouldnt get back to normal or even start again. So completely formatted my card, which now has NO PARTITIONS(i guess just 1), and i think the phone is trying to read files on a partition that dont exist now, and NOTHING is working. Anyone on here that can help? I am rather smart with this stuff, but really am going to need someone to help me. I need my phone tomorrow.
Thanks.
How did you reformat your sdcard? Did you check in parted to see that you in fact only had 1 partition again? I suggest you flash a new updated ROM like Cyanogen 4.2.5. That has apps2sd script built into the rom. It will do it automatically so you don't have to mess with all that.
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
illthinking said:
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
Click to expand...
Click to collapse
you're going to need a second partition for apps2sd to work. I suggest you do that first before you flash a rom, or else you will just have to end up reflashing.
Ok Downloaded Cyanogen4.2.5
This is the problem i keep having when i try to apply the update it say
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
So i think it has to do with the fact it wants to read /dev/block...etc from the partition of the sdcard that is now non existent
problem is i have a mac and cant properly fromat the 2nd partition (ext2)
unless you know of a way
the way i first did it was using some code i got off of here to have the phone do it itself... now that i cant start the phone i cant do the partition
what recovery do you have? I suggest you put this one on your phone.
http://forum.xda-developers.com/showthread.php?t=566669
It partitions your sd card for you.
Also for Cyanogen, you need to flash the htc OTA update one, then flash his update for those to work.
ok...
so i found some plugins for the new Snow Leopard OS for mac called MacFuse 2.0 along with its counterpart fuse-ext2 and i partitioned my card
you might want to upgrade to ext3. it's faster than ext2 and runs smoother
just tried to flash the recovery found here
http://forum.xda-developers.com/showthread.php?t=566669
with no avail and tried to start the phone(power+camera) and said no image
heres what it said for the recovery
/ # mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on / system/modules failed: No such file or directory
mount: mounting /system/xbin.cramfs on /system/xbin failed: No such file or directory
I mean, what i want to know is how to build the file format back on my sd card so itll work, or build it so it will look on my actual phone... People put up the code to have it switch where it reads things from, there MUST be a way to switch it back manually as well
Use fastboot and write the recovery image
here's a link to fastboot
http://developer.htc.com/adp.html
then when thats running plug in your G1 and turn on holding Power and camera when the screen turns on you might have to press back to enable FB but once its enabled type in terminal
Code:
cd *where ever your recovery image is*
fastboot flash recovery *recoveryname*.img
reboot
can someone hook up a quick step by step on how to hook my phone up fastbooted? I have a mac and i can get the phone to say fastboot, but im lost after that... If you want to reroute me to a different thread, please verify that it REALLY has the info before posting it.
i have been trying to find the name of the device and im getting
/dev/tty.Bluetooth-Modem as the device name, but a Permission Denied thing... now i cant just go click something in the phone menus, since i cant get the phone to start, so is there a way to get permissions through the Terminal application?
that error you get when you type mount -a is normal continue as instructed:
flash_image recovery /(whatever your recovery image is called)
if you have adb you could try parted /dev/block/mmcblk0 and type print to see your parttitions.
so i can get it to say it flashes the recovery, but still not starting
so when i try to do any updates it says SDCARD wont mount
any input?
Looks like im going to go for a broken record, until SOMEONE can help me figure my phone out... I need to get it running, and i know someone can figure it out
Can't mount /dev/block/mmcblk0p1
I've managed to get into a right pickle with my Dream 32B
Now when I try and update from SD it gives me an error message saying
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I can still fastboot to a recovery rom and use adb but I cannot flash any roms to get the phone up and running.
I have tried 2 different SD cards and reformatted them both. Both of them worked fine before yesterday.
I have tried "adb shell mount /sdcard" and this gives the same error
Any suggestions would be much appreciated.
can someone help me or no
I got this exact same message. After a few days of troubleshooting, I concluded it was a broken SD card slot. Sent it in for repair to HTC, and it was fixed.
got the same problem when i was rooting my phone...
to cut it short it's 95% SD card format error, you need to reformat your SD card from recovery mode as in Amon-ra 1.7 or something...
that actually solved my problem
isaacwaller said:
I got this exact same message. After a few days of troubleshooting, I concluded it was a broken SD card slot. Sent it in for repair to HTC, and it was fixed.
Click to expand...
Click to collapse
I've HTC desire running RUU. Rooted with unrevoked. S-off. HBOOT 0.93. No USB Brick. Phone working fine. SDcard disappeared when restoring nand-backup. Tried unbricking, etc. No use.
Going to send it to HTC.
I need your help - Jacob - or danne_jo - or anyone else in the know...
I've been using Wildpuzzle since day one but have always failed to get apps2sd working. Due to my sdcard never getting an ext4 partition. Why - I havent the faintest clue?
I cleared all data + cache - and also formatted sd-ext on the 3rd try. Installed Wildpuzzle 8.0.6. from formatted no ext sd - Restarted. Changed sd-card to another formatted FAT32 no ext sd. Ran Rom Manager to Partition SD - tried EXT 512 / Swap 0 - and another try EXT 512 / Swap 64...both turning up the same result: On restart - Htc splash screen comes up - followed by the bootanimation looping again and again - and only thing that helps is my removing the battery - and going into recovery - clearing all once again. And Reflashing Wildpuzzle...which then works normally. But noway to get Apps2SD and thus OC kernel working.
My Touch Screen is ATMEL, if that makes any difference...
HELP?
Posted the same error yesterday and somebody told me that
you have to flash 0001 agin after partition SD Card
Click to expand...
Click to collapse
but after a long period of flashing and trying to get it work again I lost my mood, because I couldn't get it to work as easy as you. After the boot loop I ejected the battery and wiped it again, cleaned all caches, but when trying to get wildpuzzle again on the phone he told me that there is an error in line 15 with the restriction.
and everytime I tried to restore my old backup ( 2 different versions ) he told me always that the MD5 doesn't match. So after long trying and many different versions I got it again to work with an UK Recovery Backup and from that I got it back to my old version.
maybe I will try it today again and flash it after the partition and maybe it work. Would be nice if you could try it, because as I red in your post, it is easier for you to get back to old custom room.
would save me a lot of time and nerves
I did that. No luck w that either.. same result as before...
Sent from my HTC Wildfire using XDA App
I used this hardware mod on all 50 of the tablets with great success. Just be careful to not remove any of the other little chips, I used heat to loosen the glue.
http://forum.xda-developers.com/showthread.php?t=1877585
Good luck
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Reference Material:
Fix for the P1000 - This is exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1711150
Fix for the Atrix 4G - Again, exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1766939
Another Example
http://forum.xda-developers.com/showthread.php?t=1463756&highlight=ics
Re-partition steps:
http://forum.xda-developers.com/showthread.php?t=845708 <- this did not work
Heimdall Suite re-partition with known good pit file <- This did not work
I'm on the exact same place, attempting the exact same, currently I was trying to edit vold.fstab as well as init.rc but it seems you have a better grasp of this.
I use a Sprint sph-p100, a CDMA version just like yours and as far as I know fully compatible with anything (save modem but I only use wi-fi).
I've tried your first link with a GB rom and failed (didn't pass first Samsung logo), but I will keep trying and post back anything I achieve.
If you indeed make a kernel or image that makes them boot please share it with us and I will GLADLY test it out.
I'm also aware that an easy solution is to open up the hardware and remove the internal SD Card (the kernel will assume the external is mmcblk0 instantly) but I dislike doing butchery and maybe breaking my device.
Chris... much progress has been made on this... first off. I am dumping the Gingerbread Verizon images for the CyanogenMod 9 Rc1 for P1c. I am currently following the kernel rebuild instructions from the device developer "cdesai" is working on. Those instructions are here:
http://forum.xda-developers.com/showpost.php?p=20162940&postcount=3
with repo setup here:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
With the instructions on how to build just the kernel I will modify the initramfs.list among other files to get the required results. What I will need to help you is do the exact same thing, just with the initramfs.list for your P100 device ??
Are you willing to use CyanogenMod 9? I have pretty much abandon Gingerbread unless someone can hook me up with a known working P1c Gingerbread git.
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
ChrisCTX said:
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
Click to expand...
Click to collapse
Mine is detected too. But fails when you try and fdisk is. I have several devices with the same results. If you want try to fdisk /dev/block/mmcblk0
Tell me if that eventually shows up as a 32mb disk with an empty partition
The correct commands are
adb shell
su
fdisk /dev/block/mmcblk0
p
q
Don't have a rooted rom on it now (can't really install anything besides flashing), but I tried it minus "su" and it didn't do anything at all.
Update the status. I have made the changes to support booting from the SDCard. For the first time I can mount the /data directory via the recovery. There is an install sequence that I haven't yet mastered. Will be in touch
Sounds great Jim, thanks for all the effort so far
I am waiting for the release of this. My tab internal SD crapped out also.
please help
im on the same boat if in need to take of the internal storage let me know i will do it just tell me some directions
Same issue
JimRich said:
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Hey guys I am having the same issues (as far as i can tell) with my Verizon Samsung Galaxy Tab SCH-i800. so the first issue is i tried to install a stock rom to fix a corrupted cache partition. now it tries to boot US Cellular. As of this moment the error i get when i put the device in recovery mode:
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
I am wondering if i can just create a new partition on a new SD card? i bought this device on ebay a couple weeks ago and i don't want to continue attempting sketchy leads for fear of hard bricking it. All help is greatly appreciated. I really don't want to give up on this thing because i feel like the soultion is out there... I am very good with performing commands via command prompt if that is nessasary, also i have access to an Ubuntu 12.4 computer if that would make things easier? Please help?
***Also as far as i know this is equipped with android Froyo and the issue developed after the previous user attempted to update. Please email me a reply or reply to my post.
Thanks,
-Andy
I switched to a hardware modification. This worked great!
http://forum.xda-developers.com/showthread.php?t=1877585
Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:
Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...