Database Info

*SOLVED* can't mount /dev/block/mmcblk0 and "Image Not Found"

I tried searching for help, but can to a dead end. After I installed JF 1.5 and the phone rebooted, it just hangs on the G1 Tmobile boot screen.... I can restart it and load into recovery but get E: cant mount dev/block/.. I also tried the DREAIMG.NBH but when ever I try to load it (Power+Camera) I get "No Image Found!"... I dont know if it cant find the recovery_testkeys or if it was screwed up during the installation process... It does boot so im guessing no brick.
Any help is GREATLY appreciated
*EDIT*: SOLVED, I downloaded the DREAIMG-29.img, renamed the file with a .nbh extension, and bought a SD READER to MAC 4gig San Disk Card. IT ENDED UP BEING THE NEW CARD and READER THAT MADE IT POSSIBLE!
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip (Rename DREAIMG.NBH..
Hope this helps this pesky problem

maybe
It might be that it's not reading the sdcard right to read image to reflash. But also some people have been saying some apps are causing it not to go past the g1 screen seem the most common factor is desktop theme apps are doing this people have been able to remove these apps useing umbuntu to remove these apps and all goes back to normal.

Hmm.. umbuntu has never been a real good friend to me.. but yea the SD card was my last possible indication. I thought that after doing a factor reset under recovery deleted the apps...? Is there a way to just reflash to stock rc 33 or rcc 29? Im sort of new to the Android Dev scene... Could the Recover_Testkeys.img image be causing an issue also?
Thanks
Edit: Iv heard that the type of SD card might be an issue (Transend, San Disc, ect.)? ..... I dont know though.

deleted comment... accidental duplicate post

Try a wipe. I had the same thing happen to me only i did something dumb, but once i flashed it, it worked again.

It happened to me today, It stayed on the Android screen for about 30 minutes So I removed the battery and turned it on with home+power button,
did a wipe, and applied the update again.
I dunno if doing the wipe helped but it works now

By wipe you mean recovery then (Alt+W).. Iv done it about 10 times. I keep getting the "cant mount SDCARD" and "dev/block/mmcblk0" after attempting to install update.zip.
Any other thoughts..? thanx

please tell me you have adb set up. if so i can try to help you otherwise i can't do much for you

Tubaking182, To be honest, i dont know for sure if I did set up adb... Could you please explain what it is and if it is still possible to set it up? If you could help me, It would be GREATLY appreciated... im about to give up.... such a pain in the a**

Bump.. for help issues

they may have changed the vold.conf in order to support A2SD, but that would prevent the phone from recognizing SD cards that are not partitioned.

I was rooting my HTC Magic 32A and had the same problem when I choose [Flash zip from sdcard] at RA-hero-v1.6.2
The message was "cant mount /dev/block/mmcblk0"
Then I choose [Other > Move recovery.log to SD] at RA-hero-v1.6.2
And went back to choose [Flash zip from sdgard] and then it works.

G1: Cyanogen reboots randomly and sound stops when getting texts/calls

I have a couple problems that I've been having since rooting my phone and installing cyanogen. I'm currently using cyanogenmod 4.2.2 with recovery 1.4 on my t-mobile g1. Also, I have the CM updater.
1. When I am using my stock headset, the phone restarts automatically at random intervals. Also, when the headphones are plugged in when the phone initially starts, the phone will definitely restart shortly after the home screen finishes loading.
2. When I am listening to music through the stock headset (either through the base music app or pandora) and I receive a call or text message, I lose all sound functionality (including in-call sounds) When this happens I have to unplug my phone and restart it again to regain sound functionality.
Are these bugs with the following that others are experiencing that can't be avoided:
1. cyanogenmod or
2. root or
3. cyanogen recovery 1.4?
Am I the only one that has had these problems? Is there another ROM that anyone would recommend that would most likely rectify this?
Help!!!!

I have the same problem.
No idea how to fix it?
G1
CyanogenMod 4.2.2

I think I fixed my own problem
I flashed this new radio:
http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
Then I backed up my sd card, formatted it, and partitioned it into a main fat32 partition and a 500mb ex2 partition.
Then I wiped and re-flashed cyanogen 4.2.2 and it works!!!

Also, it took me a while to figure out how to partition my sd card. It seems there is no easy way to do this with windows vista. I had to use Ubuntu's partition manager called "gparted". Apparently this can be done without actually installing Ubuntu if you just boot from the CD, but my computer wouldn't read the sd card through Ubuntu until I installed ubuntu and downloaded the updates. Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!

anoyment
ajchandler said:
Also, it took me a while to figure out how to partition my sd card. It seems there is no easy way to do this with windows vista. I had to use Ubuntu's partition manager called "gparted". Apparently this can be done without actually installing Ubuntu if you just boot from the CD, but my computer wouldn't read the sd card through Ubuntu until I installed ubuntu and downloaded the updates. Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
Click to expand...
Click to collapse
Dude, take your HDD out of the computer, put it inside a USB enclosure and save your data, then just delete all partitions and install Windows again. Next time, you can just install Ubuntu from INSIDE Windows with "wubi.exe".
As for the sporadic resets, I am having the same problem. Only thing is: I had just flashed the 4.2.2 rom in the phone, wiped, and just then, being in the WC, I get a call, take the phone out of my pocket, it slips from my hand and drops right inside the can (yes, it had just been cleaned, Thank God), took it out fast enough, battery out. Couldn't find the screwdriver for it so I shook as much water as I could off, and let it dry in front of a full throttle fan for about 12 hrs.
It reset itself some times after that, but I don't know if the problem is the Rom, hope it is, (sorry). Next thing I know is, there's an update to ver. 4.2.5, so I updated, hasn't done it again yet, it's been 36hrs.
Hope I could help and anoy you some guys...

I have the same problem with my G1 (cyanogenMod-4.2.5 kernel 2.6.29.6-cm42 baseband 62.505.20.17H_2.22.19.26I), had to change from cyanogenMod-3.6.6 hoping it will fix the reboot problem, but it doesn't change
I reformat SD card (1 Gb) and repartitioned it, doesn't fix the problem. The difference is that is reboots now less frequently (with cyanogenMod-3.6.6 it started reboot suddenly and did it every 20min - 3 hrs, now 1-3 times a day).
Seems that it somehow related to WiFi connection, and may be email receiving process (may be free space problem? But as far as i can check there is free space available on the SD card).
If with cyanogenMod-3.6.6 i could assume that some new installed application caused it, then with 4.2.5 i didn't install anything, and it starts rebooting again recently.
Is there a way to write a log or something to see which app caused reboot? It's linux anyway, so should be smth to see the reason, right?

Updated to CM-4.2.7.1 and added a 4GB Class 6 TF
luk1 said:
I have the same problem with my G1 (cyanogenMod-4.2.5 kernel 2.6.29.6-cm42 baseband 62.505.20.17H_2.22.19.26I), had to change from cyanogenMod-3.6.6 hoping it will fix the reboot problem, but it doesn't change
I reformat SD card (1 Gb) and repartitioned it, doesn't fix the problem. The difference is that is reboots now less frequently (with cyanogenMod-3.6.6 it started reboot suddenly and did it every 20min - 3 hrs, now 1-3 times a day).
Seems that it somehow related to WiFi connection, and may be email receiving process (may be free space problem? But as far as i can check there is free space available on the SD card).
If with cyanogenMod-3.6.6 i could assume that some new installed application caused it, then with 4.2.5 i didn't install anything, and it starts rebooting again recently.
Is there a way to write a log or something to see which app caused reboot? It's linux anyway, so should be smth to see the reason, right?
Click to expand...
Click to collapse
LUKE, I AM YOUR FATHER, NOT...
Just kidding, just couldn't let a chance like this pass me by, sorry .
2 days ago I changed the 2GB TF (which was a class 1) with a 4GB TF, now a class 6. Wiped the phone and added an ext3 1GB partition.
Yesterday I updated the CYanogen Mod to ver 4.2.7.1. Haven't seen another reset since, but it could be that I haven't used the phone much other than for phone calls since the update. But altogether it seems pretty stable.
I just used the cm-updater and everything was done automatically.
If you don't already have it, download it from the market, check for new roms and download the one I said. Please let us know if it makes any difference for you.

ajchandler said:
Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
Click to expand...
Click to collapse
To reinstall the Vista MBR:
http://support.microsoft.com/kb/927392/en-us

[Q] Milestone XT720 has crash and black screen when install new applications

3 months ago to now, so I do not understand why does XT720 often crash and see black screen when install a new app (app >5Mb). I installed both in 3 ways: installed from the market, copy the app to memory card and install, install from computer with ADB. All that is hanging black screen, press the power key but the screen didn't open. And i have to remove the battery to reboot! I also tried a lot of Cook Rom also will get results like that.
Do the other android users have encountered this situation? And do you know the cause or how to fix it not? Hope for your help!
Regard!

I never had this problem maybe you should try hard reseting you phone.

spitcuba said:
I never had this problem maybe you should try hard reseting you phone.
Click to expand...
Click to collapse
Thanks for yours suggest! But how to hard reset the phone?

black screen maybe sdcard problems. try formating your sdcard..

ahhavmt said:
3 months ago to now, so I do not understand why does XT720 often crash and see black screen when install a new app (app >5Mb). I installed both in 3 ways: installed from the market, copy the app to memory card and install, install from computer with ADB. All that is hanging black screen, press the power key but the screen didn't open. And i have to remove the battery to reboot! I also tried a lot of Cook Rom also will get results like that.
Do the other android users have encountered this situation? And do you know the cause or how to fix it not? Hope for your help!
Regard!
Click to expand...
Click to collapse
I encountered this in other ROMS (Specifically using Khal's MIUI). I thought it was my SD card. But when i updated to CM6 I havent encountered this issue at all.
Btw, you can try booting with out the sdcard and see if that will get you to your home screen.

Noob_xt720 said:
black screen maybe sdcard problems. try formating your sdcard..
Click to expand...
Click to collapse
blessedhands said:
I encountered this in other ROMS (Specifically using Khal's MIUI). I thought it was my SD card. But when i updated to CM6 I havent encountered this issue at all.
Btw, you can try booting with out the sdcard and see if that will get you to your home screen.
Click to expand...
Click to collapse
Thanks for your suggest, i was try to format SDcard or flash to CM6. But it still happend

What about factory reset

Formatting won't solve your issue (for me it didn't). It is not software corruption of your card's filesystem. It is your kernel getting stuck writing large amount of data to the card, and can't drive it. You can observe it when installing large APK, or taking photo with max resolution, or record HD video. Sometimes overclocking/overvolting may help you, try that. The best solution is to get a class 10 SD card ... their speed matches up the data written and known to cause less lockup.

[Q] Need help with common problem with HTC Wildifre rooted

Hey guys, I rooted my phone from one the guides on this site.
HTC Wildfire
2.3.7
13.53.55.24H_3.35.19.25
Kernel 2.6.35.14-nFinity [email protected] #1
CM7.1.0.1-buzz
Since rooting it I've had the niggly problem of everytime I boot up my phone I get force closes for my launcher and sometimes a complete phone freeze causing me to remove my battery to undo it. At first I thought it was just ADW Launcher so I installed Zeam which seemed to stop the force closing (most of the time). The problem came back after a few months I noticed becoming more and more commonplace.
I notice on my bootloader the second .img cannot be found and I'm not sure what part that plays in this matter.
So I started a trial and error to see if I could locate the cause of the crashing. I found that when I removed my SD card my phone booted perfectly with no troubles so I formatted it thinking it must be a bad checksum only to have the problem return.
My SD card is a sandisk 2gig bog standard with the phone. I didn't partition an EXT onto it and I formatted it with the FAT system from my Windows XP sp3.
Please help, I love this phone too much lol
Also I can't get the TV off animation to work, if anyne has a zip file that works I would greatly appreciate it

[Q] Unable to locate internal sdcard error

Hello All,
I wanted to post this to the Android Development section but since I have fewer than 10 posts I am forbidden from doing so.
Intermittently I will notice some apps do not load images or act as they normally should, and upon opening Solid Explorer to do some investigation I receive an error message (Cannnot browse to "/mnt/sdcard". An unknown error occured.). I find I am unable to access the internal sdcard through Solid Explorer, and when navigating using Root Explorer it only displays an empty folder.
This seems to happen at least once a day, and restarting my phone usually fixes it at least for a few hours. Sometimes ending all applications through task manager & clearing RAM memory through RAM manager will allow me to normally browse my internal sdcard using Solid Explorer for about a minute or so, and then become unaccessable again. Phone reboots seem to be the only fix, albeit a temporary one that only lasts a few hours.
I am unable to save screenshots when this occurs, unable to save pictures, some apps do not function properly -- all which makes sense if the phone is really unable to access the internal sdcard. I have performed numerous wipes (full wipe, cache, dalvik) & reinstalled newer nightly SynergyROMs but I have been unable to fix the issue. Searching these forums has not brought me any relevant information which pertains to the same issue I am having.
I appreciate any help or insight you guys can provide, thanks for taking a look.
Quick Background:
32GB Samsung Galaxy S3 on Verizon network
No external microsd card
Unlocked & Rooted
Running SynergyROM Nightly (r73)
CWM-based Recovery v6.0.1.0

Why would you think to post this in Android Development? This is a question, and thus belongs in Q/A (where it is posted). Android Development is for people who actually developed something, like a ROM, Kernel, etc.
I don't know what kind of advice to give you though, besides try formatting in advanced options of CWM, a reprovision (*2767*3855# ) on stock (back up everything first, to somewhere other than internal SD as it will be wiped) or maybe a 32GB PIT, with a PIT being the least likely solution.

I second this question!!
Kenshingtx said:
Hello All,
I wanted to post this to the Android Development section but since I have fewer than 10 posts I am forbidden from doing so.
Intermittently I will notice some apps do not load images or act as they normally should, and upon opening Solid Explorer to do some investigation I receive an error message (Cannnot browse to "/mnt/sdcard". An unknown error occured.). I find I am unable to access the internal sdcard through Solid Explorer, and when navigating using Root Explorer it only displays an empty folder.
This seems to happen at least once a day, and restarting my phone usually fixes it at least for a few hours. Sometimes ending all applications through task manager & clearing RAM memory through RAM manager will allow me to normally browse my internal sdcard using Solid Explorer for about a minute or so, and then become unaccessable again. Phone reboots seem to be the only fix, albeit a temporary one that only lasts a few hours.
I am unable to save screenshots when this occurs, unable to save pictures, some apps do not function properly -- all which makes sense if the phone is really unable to access the internal sdcard. I have performed numerous wipes (full wipe, cache, dalvik) & reinstalled newer nightly SynergyROMs but I have been unable to fix the issue. Searching these forums has not brought me any relevant information which pertains to the same issue I am having.
I appreciate any help or insight you guys can provide, thanks for taking a look.
Quick Background:
32GB Samsung Galaxy S3 on Verizon network
No external microsd card
Unlocked & Rooted
Running SynergyROM Nightly (r73)
CWM-based Recovery v6.0.1.0
Click to expand...
Click to collapse
I logged in today because I am having the exact same problem. Same ROM as well, Synergy r73. I've tried formatting the SDCard, tried a complete reformat of the phone. But nothing seems to help.
Also, to clarify, it isn't restricted to the external SD card (which mounts to /mnt/etxSDcard folder). It's the entire /mnt directory that hangs. I'm able to go into options and mount and unmount the external card fine. But as soon as I try and access /mnt using any app (andExplorer, Wifi File Explorer, even a simple 'ls' in terminal) the phone hangs, stops responding to button presses, and eventually reboots itself.
Also, I've found my timing matches Kenshingtx's as well. If I reboot the phone, I can access external storage, and the entire /mnt folder for that matter, just fine, and it stays this way for about an hour or so.
Any further ideas are greatly appreciated.
btw, I think he mentioned posting the Android dev because there is a thread specifically dedicated to this ROM with numerous questions and answers in it. (Albeit hard to follow since it's over 800 pages) I already searched in there and found no mention of this issue.

The SD card problem sounds like something that used to happen with the old modems.
Go to about phone and check your baseband. If it doesn't end in G7 or HD then you have an older radio that had this issue.
Here's a link to where you can get what you need that explains everything better then I could.

MasterPoppy said:
The SD card problem sounds like something that used to happen with the old modems.
Go to about phone and check your baseband. If it doesn't end in G7 or HD then you have an older radio that had this issue.
Click to expand...
Click to collapse
My phone has the G7 modem in it.

Thanks for everyone's input so far. My baseband ends in F2 so I'll try updating my modem and see what that does (even though nerfage seems to be having the same problem with the G7 modem). And you're right, I wanted to post in the synergyROM development thread thinking the problem might've been specific to that ROM.
I'll also look into reprovisioning on stock rom per Zalithian's suggestion to wipe the internal sd card, and see if that helps.

@nerfage - I dunno what the problem is then, could be ROM specific. If you figure out what's wrong post how you fixed it here. You may also want to try flashing the HD rom. Might fix it, might not.
@Kenshingtx - Not sure if the wipe would help so make sure that's an absolutely final thing, googling around is always useful. Hopefully the flash thing does the trick though.

MasterPoppy said:
@nerfage - I dunno what the problem is then, could be ROM specific. If you figure out what's wrong post how you fixed it here. You may also want to try flashing the HD rom. Might fix it, might not.
@Kenshingtx - Not sure if the wipe would help so make sure that's an absolutely final thing, googling around is always useful. Hopefully the flash thing does the trick though.
Click to expand...
Click to collapse
Flashed the latest modem ending in HD, and tested my phone over the weekend. Still having the same issue where the internalsd becomes unavailable. Wondering if the hardware in our devices are faulty..?

nerfage said:
My phone has the G7 modem in it.
Click to expand...
Click to collapse
My phone appears to be fixed. I backed up all the files on my mnt/sdcard, performed full/cache/dalvik wipes, formatted internal memory through recovery, flashed the rom again (decided to try Beans ROM this past week) and I haven't had the same issue come back. It looks like the cause of the problem was something on my internalsd, try formatting it (after backing up any files you need) to see if it'll fix the problem for you too. Good luck.
Note: the fix does not appear to be related to the ROM, i was having the same issue on the Beans ROM as well until I formatted the internal memory