Alright so I've been looking everywhere - G1 Q&A, Help & Troubleshooting

and I can't find the shorter way of mounting your SD card in your console.
I know it's something like
mount something something enable
Anyone know it?

Never mind found it but it doesn't seem to work!
My phones ****ed.
Evrytime I type in ums_enable this comes out
/dev/block/mmcblk/
And nothing happens

why not mount the usb by the recovery menu and use adb instead.
adb shell is the same thing as console.

I've never used ADB :/

Okay now it everytime I click on apply and zip from SD i get
E: Can't mount /dev/block/mmcblk0 p1 (or dev/block/mmcblk0) (no such file or directory) E: Can't mount SDCARD:

Dunno the actual command, but Amon_RA's recovery has the option build in.

I would definitley get Amon Ra's Recovery on your phone.....
From there it has an option to toggle usb on or off (which will mount your sdcard so your pc can see it)
Also it can partition your sdcard.
IMO Amon Ra's Recovery should be part of your "rooting" process.

Related

[Solved] Can't flash ROM?

Hi, i try to flash Cyan's new rom v4.0.1, but i keep getting this error message in my recover console:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After trying unsuccesfully to flash the rom, my sdcard can no longer be seen in my phone and it became write-protected, unable to move files into the sdcard. Appreciate your help....
Edit: Yeah solved this menacing but simple problem which i found out is my sd card fault. Since i couldn't access sdparted in the recovery console, i had to use Ubuntu to partition my sd card again. Sighs... now i have to replace everything back into phone. Thanks anyways for those who gave advice.
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
you dont flash a rom in consol
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
david1171 said:
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
Click to expand...
Click to collapse
yes my sdcard is fat32(1st partition) and my 2nd partition is ext3 whilst the last is a linux-swap partition...
oshizzle1991 said:
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
Click to expand...
Click to collapse
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Scholesville said:
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Click to expand...
Click to collapse
Have you tried using the CM Updater?
Scholesville said:
yes my sdcard is fat32 and my 1st partition is ext3.
Click to expand...
Click to collapse
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again (alt w)
: run a filesystem check from the menu. If it tells you to run it manually,
drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
: flash
Enjoy!!
Hope this helps!!!
yourtravelboy said:
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
Hope this helps!!!
Click to expand...
Click to collapse
The problem is i can't even mount mount my 2nd partition, and everytime i write the command > # mount -o rw /dev/block/mmcblk0p2 /system/sd < , it justs says no such file or directory found.
I also can't go into parted in the recovery console so the now the problem is i can't even reformat my card. I'm going to try Ubuntu and reformat my card and partition it again. Sighs...
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
q2box said:
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
Click to expand...
Click to collapse
Yes, since i was not able to access parted in the recovery console, my only choice was to use Ubuntu: Partition Editor. When i diagnose my sdcard, i manage to format only my ext3 partition so my fat32 remain unchanged. You need to go download Ubuntu OS, then try to install or LiveCD the Ubuntu. There is a thread under android development which will guide you on how to do this...

Im a noob

Okay i'm sure ive become an annoyance in this section of the forum. I think i may have bricked my phone. This is what i did.
1. Unrooted myself and downgraded to RC29.
2. I formatted my sd card even though it already said fat32
3. Downloaded cyanogen recovery 1.4 image. And Hardspl and renamed it update.zip.
4. I connected to server 23 host in telnet and successfully typed in :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat cm-recovery-1.4.img > /system/recovery.img
5. The Hardspl part pretty much failed... i renamed it update.zip and downloaded it in recovery but once i hit reboot..it took me to recovery again and said : formatting cache:... and just stayed there. So i hit reboot again and it booted back to homescreen.
6. After this i figured i was rooted so i download cyanogen rom (http://forum.xda-developers.com/showthread.php?t=567610) and put it on my sd card.
7. I went to recovery and downloaded this zip file successfully.
My problem is: i can't get past the g1logo screen. I've tried reinstalling the rom and wiping data a couple times and it wont go past. Am i screwed?
okay nevermind this post i had to go to console and type in
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file to mount my sdcard so im goin back to RC29! may as well go to 1.6 til i can figure something out about rooting this is just ridiculous
kyram04 said:
okay nevermind this post i had to go to console and type in
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file to mount my sdcard so im goin back to RC29! may as well go to 1.6 til i can figure something out about rooting this is just ridiculous
Click to expand...
Click to collapse
anyway heres a website about how to root.....http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/

Can't apply ZIP updates. HELP! Wave invites for help.

OK.
So for the last week or two I've been trying to get myself fixed in this thread:
629469
You can read that for some background info. Seeing as this a new problem, I've posted a new thread.
I've pushed SuperD, signed-spl (danger) and ota-radio 2_22_19_26i to the phone.
But now I cant apply these updates. I choose "apply sdcard:choose zip"
and it says:
e:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid Argument)
E:Can't mount SDCARD:
HELP.
Wave invites for help (I'll try that one again)
I've run into the same problem but I got there a slightly different way.
I recently switched ROMs from kingklick's aosp 2.1 v1.5 to openeclair 1.5, and I wanted to switch back. I went to do the usual partition, wipe everything, apply update.zip and I got almost exactly the same error message that you got:
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(File not found)
E: can't mount SDCARD:
With my limited knowledge of Unix, I decided to jump into the console and dig around in the dev folder, I didn't see anything in /dev/block that was called mmcblk0, there were several files called "loopX", and also "mtdblkX".
It seems like my phone is acting as though I do not have an SD card at all. I've been testing out different things, I started the process over again by trying to partition the SD card and noticed it finished almost instantly. And now when I connect it to the computer and turn on the USB connection, my computer does not recognize it as a storage device. I then popped out the SD card and put it into the computer itself, it seems fine but there were some extra dm files that I did not expect to see. Not sure what those files are or how they got there.
I have the Death SPL, and the last ROM I used was KingKlick's AOSP 2.1 v1.5
Does anyone out there have any idea why this happened or how I can fix it?
Both of you, it sounds like your sd card is formatted wrong or corrupt. From amon-ra recovery you should try to wipe again, including the SD, and repair SD EXT. If that doen't work go back and use the "format SD" option.
One more thing, please take a few minutes and put together a signature on the forum with all your info, phone, spl, rom, sd setup, what you like for breakfast, all that stuff. Much easier to tell where to start.
Edit...if this should happen to accidentally work, please don't send any wave invites. I will probably never get rid of my 25.
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
dracoaffectus said:
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
Click to expand...
Click to collapse
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
I have the same problem wiht my G1 and am sending back my phone to HTC for this.
I have made a post here:
http://forum.xda-developers.com/showthread.php?p=5594269
All our phones have activated a memory debugging mode from from hboot. Modifying anything while booted to recovery or system doesn't affect anything because the trigger is happening from hboot.
You can still use fastboot while stuck in this mode. But your phone has no sd card access at the moment because it is locked by the hboot for writing debug logs.
I found that I was not able to flash in fastboot, as my hboot showed S-ON. However it was still possible to use fastboot boot.
Run cat /proc/cmdline
You will see that it says something like the following:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=1 smisize=64 androidboot.baseband=3.22.26.17 androidboot.cid=ROGER001 androidboot.carrier=Rogers androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT********** androidboot.bootloader=1.33.2005 no_console_suspend=1 con
sole=null
You could mount the cache partition to your sdcard directory for flashing files:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
I've had this problem for more than a week. I have tried changing SPL, unrooting, recompiling my boot.img, and appending kernel commands.
You can also force your recovery/system to mount the sdcard, but your phone will error out because both the hboot and system will try to write to the sdcard. There is a high chance of corrupting the sd card (correctable by reformatting) this way, but you can generate a gold card:
fastboot -c "board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0" boot recovery.img
The -c switch appends to the kernel cmdline at the end.
There is a working solution if you have SPL 1.76.x in your HBOOT. The command to disable memory debug logs is simply
fastboot oem enableqxdm 0
However I have never seen this SPL for the dream. 32B magic users who flashed this SPL with the accompanying radio ended with semi-bricks, with their SPLs showing 32A board. Attempts to downgrade back to 1.33.x have not worked. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=625604
I did theorize that we might have been able to upgrade our spl and radio to 1.76.x, run the enableqxdm command, and then downgrade back to 1.33.2010 using the test ruu. The 1.33.2010 works for the 32A magic, the 32B magic and the dream. This is one of the variants of the so called danger spl. If you have 1.33.2005 you already have a spl from the magic.
hiddengopher said:
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
Click to expand...
Click to collapse
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
dracoaffectus said:
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
Click to expand...
Click to collapse
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
also, you're going to want to go to "go to console" in recovery to do this
billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
dracoaffectus said:
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
Click to expand...
Click to collapse
I would say the sd card is dead. Try someone else's or a spare.
Picked up a 2GB microSD at the store for like $10 and got the same results right from the beginning.
So this means it's something wrong with my phone, and not the SD card.
Any suggestions?
....can I unroot?
I don't know if this matters, but I noticed some dm files on my sdcards after trying to startup my phone.
EDIT: I managed to UNroot my phone back to RC29 following the instructions on theunlockr.com. Now I have to contemplate if I'm ready to jump straight back into hacking again.
EDIT2: Ok, so now I'm back on the latest OpenEclair. The key to "fixing" it was to get a totally clean start by UNrooting my phone (http://bit.ly/5qbzIU thanks Unlockr.com). I wasn't able to do step 1 cause I was getting the same errors as before, so I skipped straight to loading the DreaIMG.nbh file, then continued to update to cupcake, load the latest radio, danger SPL, and openEclair, now my phone is working again. (p.s. already on Wave, so no need to send that invite Lachy95 )
Thanks
Its all fixed.
Used a different sd card, im stupid.
Thanks you thank you thank you
ill always remember

[Q] Please help format SD Card

Today my phone randomly rebooted when idle and didn't get past the talon loading screen when running Dlev 4.2 rom. it was working fine for 1.5 weeks or so on that rom and had made no changes other than activating voodoo lagfix yesterday. No matter what I did (Factory reset, clear cache...etc) it still wouldn't get past the talon loading screen so I reinstalled Dlev 4.2. Same problem, won't get past the kernel loading screen. So I flashed stock JL1 (rogers) with odin and my phone booted, but then had tonnes of fc's and eventually just reboot into 3e recovery and had a bunch of red errors (can't mount a bunch of stuff). It gave me the option to format sd card, so I chose that but it told me sd card was not found. I then thought to 1 click JF6, but after the at&t screen the phone just goes to black screen with lights on. I can get into 2e recovery mode still but no download mode with key combo's. I believe the sd card needs to be reformatted. I have a jig coming someday soon, ordered it 2 weeks ago, but I was wondering if there is anything I can try till it arrives to revive my phone. I tried adb commands from recovery but it doesn't detect my phone. My computer says installing drivers (CDC Abstract control Model (ACM)) but nevers finishes installing them. Thanks for you help.
I was able to get into download mode by typing adb reboot download when phone was booting. I flashed one of the speedmod kernels I had on my computer and I can boot into CWM Recovery now. I formatted sdcard and reflashed JL1 but still no boot. What else can I try???
Edit: I think my internal memory is damaged or something. When I boot into 3E recovery I get the following errors.
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media:Can't mount SDCARD:
Your storage not prepared yet, please use UI menu for format and reboot action.
E:copy_dbdata_media: format SDCARD:
Formatting SDCARD:...
E:Can't mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
Edit 2:
I have been doing research and have found out that I need to fix my partitions at /dev/block/mmcblk0p1. I pushed parted to my phone and used adb shell to run it following directions of a website, but when I try to make a new filesystem by typing parted /dev/block/mmcblk0p1 mlfs ext2 I get an error Error: /dev/block/mmcblk0p1: unrecognized disk lable. I don't know linux at all. Can anyone help please.

[Q] Unable to mount /sdcard in recovery

I have a 32 GB SIM unlocked version and I am unable to mount /sdcard in either TWRP, CWM, or CWM touch. It gives me the error "Error mounting /SDCARD" or something like that when I try. Any help?
got the same question :/
eltoffer said:
got the same question :/
Click to expand...
Click to collapse
I wasn't able to mount it, but I was able to transfer files to /sdcard using the adb push command. See if that works for you.

Categories

Resources