Database Users

Can't mount /dev/block/mmcblk0p1

I've managed to get into a right pickle with my Vodaphone Magic 32B
I originally flashed the SPL with Engineering SPL 1.33.2005. All was fine and I managed to use the Cyanogenmod without problems.
Last night I was trying to flash the evil hero rom, it kept failing (verification failed). After a few reboots to try reflashing my SPL now displays "Sapphire PVT 32B ENG S-ON H". It said S-OFF previously.
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.
Resolved
For some reason my phone has started working again. I booted it up today after leaving the battery out of it for a couple of days and "Sapphire PVT 32B ENG S-ON H" had changed to "Sapphire PVT 32B ENG S-OFF G"
I was just about to phone Vodafone as well!
Flashed back to cyanogen rom. Nice when things fix themselves!

I think I found what might be causing the problem. The command line in adb using "cat /proc/cmdline" gives the following.
board_sapphire.disable_uart3=1 board_sapphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=64 androidboot.baseband=2.22.19.26I androidboot.cid=VODAP001 androidboot.carrier=VODA-UK androidboot.keycaps=qwerty androidboot.mode=recovery_manual androidboot.serialno=<removed> androidboot.bootloader=1.33.2005 no_console_suspend=1 fbcon=rotate:1
I have tried changing the board_sapphire.disable_sdcard=1 to 0. using the fastboot -c option. Sometimes I can see the mmcblk0p1 block, but when I try and mount it just hangs.
Could someone please fastboot to cm recovery image and tell me what it says for when they do adb shell command "cat /proc/cmdline" ?

try fix_permissions already?

I did try the fix permissions option in the cm recovery rom. I tried pretty much every option to try and get it working!
I did not think fix_permissions did anything to the sdcard?
I have tried 5 difference SDcards now and formatted them in a variety of fat32/ext2/ext3/swap formats. None are detected.
When I use the fastboot -c option to enable the sdcards it sometimes detects the mmcblk0p1 block but freezes when trying to mount it.

I managed to get it to mount the scard but using the fastboot command
fastboot -c board_sapphire.disable_sdcard=0 boot cm-recovery-1.4.img
This does not work every time. But when I try and apply an update it freezes on "opening update package..."
I did manage to flash another SPL (1.33.2004). But it still has sdcard disabled in commandline..

I have exactly same problem after I flashed 32A radio and recovery on my mt3g. I cannot flash any rom, I can't boot the phone, I can't do anything without sd enabled. Only fastboot is able to access SD but does not allow me to flash anything including SAPPIMG.nbh.

I managed to got the phone back on stock rom...
Here's what I did and found out so far:
The fastboot option - fastboot -c board_sapphire.disable_sdcard=0 DOES NOT work on three versions of RA-Recovery image 1.2.0, 1.2.1, 1.2.2.
However, it DOES work on RA-Recovery v1.3.2 and I do too managed to flash SPL to engineer 2005 from SD card. But when I attempt to flash the radio in recovery mode, it will just freeze at opening update package... so I downloaded SAPPIMG.NBH, reverted my phone back to factory ROM. Note: I've tried to flash sappimg.nbh before I flash engineering SPL 2005,
Even though the phone is now back on stock radio, SPL and ROM, the sdcard is still disabled! In fact it is even worse, because on stock SPL, and ROM, I can't root at all without sdcard access. Anyone know how to enable it?

I have amon ra 1.5.1 recovery....
And I am trying to use switchrom option under console(altx). After typing in switchrom command I get an error.
I have an sd card mounting issue with the following message:
"mounting /dev/block/mmcblk0p1 on /sdcard failed"
Any idea why this may be? And if that file can be added to the sdcard??
-Thanks!

sirgreatness said:
I have amon ra 1.5.1 recovery....
And I am trying to use switchrom option under console(altx). After typing in switchrom command I get an error.
I have an sd card mounting issue with the following message:
"mounting /dev/block/mmcblk0p1 on /sdcard failed"
Any idea why this may be? And if that file can be added to the sdcard??
-Thanks!
Click to expand...
Click to collapse
+1 please!!!

I have exact the same problem as you guys.
You said that "fastboot -c board_sapphire.disable_sdcard=0" works (sometime). I've tried few Amon RA recoverys and booted repeatedly but without any success.
I still got E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
My SPL is 1.33.2010 with S-ON and i still can't flash it because of FAILED (remote: signature verify fail).
Could someone advice me?

htc hero gsm rooted modaco 3.0 amn ra 1.5.2
hi i have the same problem E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory), htc hero when turned on notification message REMOVED SD CARD, even though sdcard is inside, cant even sync, with pc, any help would be much appreciated

You need to change the mainboard to fix it. Otherwise, there's no known way to fix this problem.

This issue was killing me for about a month before I gave up and bought a new phone. This issue was on my Rogers 32a, and I knew that my SD had become unreadable via Recovery and ROM, because of a failure to follow proper instructions when upgrading the radio to from 3.22.20.17 to 6.35.07.20 in this thread:
http://forum.xda-developers.com/showthread.php?t=605239
I'm not sure where I went wrong, but I knew I made a mistake when flashing the images in fastboot. I decided that it would be best to start over, and go back to the Engineering SPL. At this point, my SD and bluetooth stopped working.
What I noticed was that my SD card could only be read in fastboot mode, and could even install sappimg.zip/nbh Engineering ROM with Recovery image on a gold card perfectly fine. However, like b1gwest, I was partially able to get the SD to work with the "enable.sdcard=0" override command. Because this would keep crashing, I wasn't able to do anything. In the end I flashed the stock Rogers RUU(Still no SD or Bluetooth)
I noticed that on the SD cards that I put in the phone, there would be large "qxdm_[time stamp].qm" log files being written to the SD cards anytime I tried accessing it in Recovery mode. And if I'm not mistaken, this is a fastboot option on the Hero or 1.76.x.x SPL's? ANYHOW, there was no way for me to fix this without access to the SD Card.
Until now. Lucky for me(maybe for some of you too), I kept my phone.
For ROGERS 32A, possibly for other providers... if you are willing to take the Perfected SPL hit to get your SD card running again, upgrade to the latest Rogers ROM(3.05.631.7).. This gives you 1.76.0010 SPL, and Radio 6.35.10.18.
This will not fix your SD(yet), so you need to go into fastboot mode and type the following
Code:
fastboot oem enableqxdm 0
This fixed my SD and Bluetooth. Results may vary, but hope this helps anyone having a similar problem.
I'm not responsible for bricking, yadda yadda yadda.. You know the risks already.

Finally
However, on SPL 1.33.0009 it's not working. I get:
Code:
fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
I think it's because of SPL. Do You know how to do it with this version of SPL?

You will need to upgrade to the new 1.76.xxxx SPL/6.35.xx.xx with your provider, which will also root your phone.
I would suggest you wait until a rooting option is available for the new SPL before you do this, though.

pyee0124, thank's for Your help.
I've upgraded spl and radio as You said (using htc 3.05). enableqdm 0 also worked.
ps. root and other roms aren't as important as fully working phone (with sd card ofcourse).

Same problem with G1.
I guess I'll pull my battery and wait a couple of days for now.
I can't run that fastboot command since I have a 32B Dream

Same issue
I have Vodafone AU 32B, same issue, have tried changing board_sapphire.disable_sdcard using -c option with no success.
Have also tried using different recovery roms upto v1.6.2 with no success.
Any ideas would be greatly appreciated.

I have the identical problem to the above post. Mt3g, tried different recovery Roms, can't access SD Card, get the same error no matter what I try. Anyone found a fix yet... ? My SPL says Security ON, which I'm sure was off before.
(Vodafone 32B AU also)

I had this problem too. I have just wierdly got around it by going to Apply sdcard:choose zip
I then chose the update.zip and bang everything installed perfectly when trying to install RAv1.1.0H 32A based ROM.
Very strange but at least I got it installed

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD

hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance

Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery

ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.

WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.

lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is

lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support

Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.

Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.

behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be

ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)

hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?

try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd

ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?

breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.

AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho

I am hanging at booting while trying to do this any ideas?

How to upgrade from rooted 1.5 to 2.2 on MT3G?

So...I'd really like to update to the 2.2 froyo mod but I get a script error when I'm trying. I can't even upgrade to cyanogen's 5.8 or whatever mod for some reason it gets stuck after installing on the boot up vodafone screen. I have a mytouch 3g 1.0 32b phone...do I need to update the radio or SPL in order to get any of these newer roms to work...how do I figure out which ones I need and what order should this be done in??

I have the exact same configuration (except I had 1.6 and had to downgrade to 1.5 first). I did not need to update the SPL or radio. Once I flashed 5.0.8, I got stuck at the boot screen. Then I wiped (on recovery screen Wipe --> All) and reflashed. This time, it worked like a charm. Which file are you using to flash?

anilo said:
I have the exact same configuration (except I had 1.6 and had to downgrade to 1.5 first). I did not need to update the SPL or radio. Once I flashed 5.0.8, I got stuck at the boot screen. Then I wiped (on recovery screen Wipe --> All) and reflashed. This time, it worked like a charm. Which file are you using to flash?
Click to expand...
Click to collapse
I don't remember off the top of my head...can you link me to the one you used? I had to do the same thing you did (downgrade from 1.6 to 1.5) so whatever you used should work for me...

Since I am a newb, the forum does not let me post URL's. I will send you a PM.

anilo said:
Since I am a newb, the forum does not let me post URL's. I will send you a PM.
Click to expand...
Click to collapse
I got your PM but I'm still having problems...I don't think have the right recovery thing installed (amonra or whatever?) because the only options I have when I reboot holding power + home are:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
nandroid v2.1.1 backup
nandroid 2.1.1 restore
I can't upgrade from zip files not named update.zip...and I can't even update the 5.0.8 file you linked me to even if I rename it to update.zip, it keeps giving me this error:
"e:cant mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (no such file or directory) e: cant mount sdcard:update.zip installation aborted."
I know when I had a G1 I was able to select a lot more options so my guess is I still need to change the amonrecovery? Do you know which one you're using or can you PM me a link to it?

Okay...so I found the recovery-RA-sapphire-v1.7.0G.img and am trying to upgrade it via the terminal by typing flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img and the first time I did this I didn't get a message or anything. I tried rebooting by holding down the power + the menu button but it just got stuck at the vodafone screen...
So I tried rebooting and going back into terminal emulator and doing it again, except now I get a long list of these errors:
mtd: read error at 0x00000000 (out of memory)
mtd: read error at 0x00020000 (out of memory)
and it just keeps going for like a page before it stops with different addresses...and now I can't get into a recovery at all....help!

colonelcack said:
Okay...so I found the recovery-RA-sapphire-v1.7.0G.img and am trying to upgrade it via the terminal by typing flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img and the first time I did this I didn't get a message or anything. I tried rebooting by holding down the power + the menu button but it just got stuck at the vodafone screen...
So I tried rebooting and going back into terminal emulator and doing it again, except now I get a long list of these errors:
mtd: read error at 0x00000000 (out of memory)
mtd: read error at 0x00020000 (out of memory)
and it just keeps going for like a page before it stops with different addresses...and now I can't get into a recovery at all....help!
Click to expand...
Click to collapse
install it via fastboot. that's a known issue with cm 5 and cm 6 roms.

Binary100100 said:
install it via fastboot. that's a known issue with cm 5 and cm 6 roms.
Click to expand...
Click to collapse
How do I actually install it onto my phone? I know the command to boot off an img file but whats the command to install it permanently so its always my recovery and I don't have to use fastboot every time?

colonelcack said:
How do I actually install it onto my phone? I know the command to boot off an img file but whats the command to install it permanently so its always my recovery and I don't have to use fastboot every time?
Click to expand...
Click to collapse
what the hell are you talking about???
Just fastboot flash recovery /computer/directory/recoveryfile.img
fastboot reboot

[Q] Cannot get into recovery mode after rooting by using super one click method

Hello all,
I have been using the super one click method to root my HTC Magic Saphhire 32A.
It works well so far albeit need to alter some SU files in the program. Running of terminal emulator with the command prompt SU confirmed that I have the superuser rights.
Now the problem is whenever I use ROM manager to reboot in recovery, the phone restart, HTC logo shows, then the next screen I see is a big asterisk and a phone image, after this I pressed Home + power, the screen manage to switch to Android system recovery utility, BUT with only 3 options:
1) Reboot system now
2) Apply sdcard:update.zip
3) Wipe data/factory reset
And in the end of the screen, there is one line highlighted in red: E: can’t open /cache/recovery/command
After the phone been rebooted, I switched off the phone. And Pressed vol - with power button, same issue happen too with the asterisk sign shows on the screen. After unrooting it, the phone recovery mode are back to normal with the 3 androids in skates appear on the screen.
Have anyone face the same problem? Any ways to sort this out? I am planning to back up my stock ROM, and wanted to try out some cyanogenmod ROM. I tried Googled and read lots of forum post but left without a solution. Any helps are appreciated! Cheers!
p/s: I am a noob in Android OS. XD

I have the legend and these is a process of booting the recovery from there as update.zip. have you tried renaming the ROM update.zip and flashing it from there?
Sent from my HTC Legend using XDA App

I fiddled with the ROm manger setting by choosing "delete recovery prior to flashing", and now it makes it worse.
I selected "reboot in recovery" in ROM manager and the phone reboot, but just stuck at the HTC start up screen.
I plugged in the phone while trying another recovery reboot, and it still stuck at the HTC screen, but with a red line on the top saying "fastboot USB". Gosh I think i am going no way with this...

E:Can’t open /cache/recovery/command
Same fault here mytouch 3g unlocked at&t 32b downgraded too cupcake and tried
getting E:Can’t open /cache/recovery/command

home and power button down still cant get you in recovery? you cant flash any other working rom?
32b myTouch 3g 2.2.1
Cyanogen Nightly 271
Hboot - 1.33.0006
Radio - 2.22.19.26i
Kernel - 2.6.35.9
ADW 1.3.3
ClockworkMod Recovery
Slideit keyboard

Did you flash custom recovery with ROM manager? Or you just rooted the phone with 1 click method?

Sorry for the late reply. I am just back from overseas business trips. I used Clockmod ROM Manager and did a backup, tried reboot in recovery, and the phone rebooted itself but stuck at the HTC logo now.
I can confirm that the phone is rooted with super user permission.
The reason being the phone didn't manage to get into recovery mode might be due to the missing recovery.img in the phone. Pushing the img file to phone through Clockmod didn't work apparently, so I tried command prompt from PC fastboot flash recovery c:\recoveryxyz.img. It failed too with an error remote failed.
I tried using the terminal emulator in the phone and tried pushing the recovery image again and it didn't happen too. Can some one please help? Cheers!

Download ROM manager and you have option that says install custom recovery it will install Clockwork, and you have flash alternative recovery it installs amon ra's recovery i prefer most

Will try it tonight and revert for the result. Cheers!

I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!

I don't know whether this info helps but here goes:
phone info:
sapphire pvt 32A ship s-on H
Hboot- 1.76.0007 (SAPP10000)
CPLD - 12
RADIO - 6.35.07.29
AUG 4 2009

callmeneotheone said:
I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!
Click to expand...
Click to collapse
OK here is the thing did you chose right model of your phone? HTC magic is 32A and mytouch and something else is for 32B you maybe flashed the wrong one?

Thanks WoblyGoblin for taking your time to help. Yes, I have selected the correct phone model. I chose HTC Magic.

Did you install the recovery?
Sent from my HTC Magic using XDA App

I am stuck in trying to install recovery img into the phone. can't boot in recovery mode, tried ROM manager and remote push of recovery img into the phone.
Please refer to the previous post for more info. Cheers!

Ok here is the solution for you use this guide but download this apk and this recovery.
If you dont have 1.5 android but 1.6 download Terminal emulator from market and when you start it type first:
su
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img

Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.

callmeneotheone said:
Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.
Click to expand...
Click to collapse
Did you try terminal emulator app?
And commands that i gave you?

yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!

callmeneotheone said:
yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!
Click to expand...
Click to collapse
Try this

HTC Desire HD won't boot after flash

Hello!
I have a big problem.
I might have bricked the device however the things what i can do are the following:
- Boot into recovery (clockworkmod)
- start a usb data connection with a computer (clockworkmod)
- input of the ADB commands through terminal running in the computer
What i did?
Flashed the memory with a Cyanogenmod 6.3 according to official guideline:
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
and took note and used most procedures from there actually:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Didn't do the engineering hboot.
Everything was working. I got cyanogenmod working.
Then after a while i tried to restore a backup which i had from original HTC configuration which was actually just before i did the cyanogenmod flash with clockworkmod.
So the backup was from the time i already unlocked the phone from locks and had root access.
So again the restore function worked and everything was back to normal.
How i managed to half brick the device?
Yesterday i wanted to put cyanogenmod back to my phone and then the s hit happened.
I admit that i didn't check whether the locks were off i just thought that these should have been off because backup soft was from time i had phone unlocked.
Anyway to cut the long story short - after flashing the memory with cyanogenmod with the help of rom manager the phone didn't boot anymore.
I tried all the options from clockworkmod flash and format and upgrade straight from sd card a new cyanogenmod but nothing worked. Again the white HTC screen and connection through a usb cable.
So probably i have the s-off and who knows what else.
I dont have a root access anymore as well because i already tried it through the terminal. It doesn't recognize the su command.
Question is, how can i put the cyanogenmod back on by only using clockworkmod recovery and working ADB connection through usb link?
Probably have to just get the locks off but the original instructions say i have to have terminal emulator running in phone but i only have clockworkmod recovery soft running at best.
S hit, again very long story, but hope someone can help me!
Cheers!

I had a similar problem yesterday, after flashing ClockwordkMod Recovery to version 3.0.0.5 (it said it had an update) and trying to reinstall CyanoGenmod 6.3 my phone would no longer boot, it got stuck in the white HTC Logo screen.
I'm not really an expert on this stuff, but I managed to "recover" my device by downgrading it again to 1.32.405.6 using this thread: http://forum.xda-developers.com/showthread.php?t=905003. First I had tried to recover a previously backed-up ROM, but that did not work.
I had to put the stock 1.32 PD98IMG.zip file on my SD card using ClockwordMod Recovery (since I could no longer boot), I'm not exactly sure which steps I took to do so, I have tried a lot of things yesterday before I got everything working again.
After this my phone could boot again and I was ready to play around again. I reinstalled CyanogenMod again using an older version of ClockwordMod Recovery. I'm not sure if this is related in any way, but my phone works smooth again..
Once again; I'm really not on expert on how all this stuffs works, I just hope that I can help you on the way with some ideas on how to fix your device.
So probably i have the s-off and who knows what else.
Click to expand...
Click to collapse
I figured out wether my device was S-OFF and/or Eng S-OFF by entering "adb reboot bootloader" from cmd. At the top of the page for me it states:
ACE PVT ENG S-OFF
I believe it stated only SHIP S-OFF when I had the problems you describe.

Thanks man for quick reply!
I definitely try the downgrading solution and i remember i too did the update for clockworkmod rom manager before the flash.
I'll report back tomorrow.
Cheers!

couldn't boot up any roms earlier after upgrading clockworkmod recovery to v3... downgraded to 2.5.1.3 and worked fine

Hi Guys, I have exactly the same problem. It would be really great if you provide me the step by step process to downgrade clockworkmod recovery.
Cheers,
Pav

I'd like to say to you guys that the downgrading solution worked
Didn't have to use any programs inside phone except clocworkmod recovery which was the only thing i had running.
Thank you user jvdminne!
The downgrading solution was in official cyanogenmod guidelines as well but forgot it anyway.
------------
Pavanka!
The downgrading solution from the link is pretty step by step actually.
But anyway, with my half-broken phone the lines didnt do the trick:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
I had to copy psneuter and misc_version to /tmp folder not into /data/local/tmp.
But anyhow, i already had # root access through computer. Probably from last half flashed system.
So only thing i basically had to do was to cd in windows cmd into folder where i had psneuter and misc_version and after that:
Code:
adb push misc_version /tmp
adb shell chmod 777 /tmp/misc_version
adb shell
in the shell (adb shell):
Code:
cd /tmp
./misc_version -s 1.31.405.6
And after that follow the instructions from previous link.
To get the ADB functions working just follow the guide here or from previous link where it had adb program included, but not sure whether it was working cause i had it from Android SDK package already set.
Hope you got some sense out of it.
Cheers!

Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...

maxa1577 said:
Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...
Click to expand...
Click to collapse
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required

ghostofcain said:
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required
Click to expand...
Click to collapse
phew cheers for that. First time flashing and I thought I killed me poor desire.