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

MAGIC - 32A - S-ON (Signature Verification ON) & Memory Card not accepted now

I am getting similar problems as this user
http://forum.xda-developers.com/showthread.php?t=664124
But in my case i am having my radio and spl is correct.
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
Radio: 3.22.20.17
Click to expand...
Click to collapse
I have access to fastboot and recovery so far
I have tried many firmwares in this radio as well as 6.xx radio new one. Had no problems so far. I was running a ROM on this radio itself. Then i wished to switch back to cyanogen latest. So i wiped and tried flashing the following
1/ flashed first - defaged firmware
2/ updated cyanogen 15.1 over it
3/ flashed the port of 32A
After this on booting, phone was stuck @ htc boot screen. So i again came back to recovery, and tried flashing again. This time it said a signature fail on defaged firmware file as well as other files in it.
Tried few times and still same issue.
Tried formatting sd card mounting on phone - recovery usb. but then after that it is no more detecting. I tried partitioning fat32, ext2-512mb, swap 32mb, manually through paragon and put again, still memory card not detecting. I get similar errors
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
Click to expand...
Click to collapse
Just to know if it is a recovery issue, tried updating recovery in fastboot mode.
I get a similar error as below
INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
This is when i noticed, the S-ON on top, my phone signature verification was off, that is before all this my fastboot said
SAPPHIRE PVT 32A ENG S-OFF H
Click to expand...
Click to collapse
I dont know how it went from S-OFF to S-ON. And that is the reason why fastboot was not accepting anything
Then to update recovery i did adb push to /sdcard and then flashed from there. And then i got my recovery updated to 1.6.2. This confirms somewhere phone is able to write to memory card through adb, but i cannot use recovery to flash from it. memory card has no prob neither phone hardware
Still no use, memory card is not detected + cannot flash files.
My current scenario
-- my radio and spl is correct, i have recovery lates 1.6.2
-- phone has no rom now
-- i can access fastboot and recovery
-- my signatures - S-ON so cannot use fastboot to flash anything
-- memory card not detecting, tried 1-2 memory cards. All detecting on pc

didnt you forgot to flash samming.img? BEcause without that, it wont turn off. Try flash again, use a gold card if doesnt work. Download from here:
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
hope it helps

I did not forget to flash that, it was not something i wanted. My phone was a completely rooted phone with everything running perfect. I was just reinstalling cyanogen from start.
Regarding goldcard, I couldnot find my sdcard CID, so could not create it.

create a new one. Create gold card from the recovery option. You can coonect your SD card to your computer with the phone in recovery mode, there is a MS Connect menu, select that one. you can get the CID and do the process again.
If i were you i would run HTC update from a SPL edition wich would be able to root and do all over again for safe keeping.

how to create gold card from recovery ? my memory card is anyway not mounting on recovery now
regarding getting cid, on memory card reader i couldnot get cid, maybe my card reader is not worth providing such info
thirdly, i have tried updating using original ruu, it fails in the stage of update where it says rebooting into bootloader.
I tried the same in fastboot mode, normal mode and recovery. Nothing works, except 1 change that in fastboot mode, it turns the phone to stuck at the fastboot screen and i have to pull out battery.
Any other options ?

before starting the phone, you press Power+Home, and you'll have the custom recovery option right?
There is a option called: "USB MS-Toggle" activate it , From that option you can get a CID without any problem and recover everything

have you tried a G1 method?
http://www.krishnendu.com/my-g1-android/rooting-my-google-g1-htc-dream-t-mobile-uk-edition_137.html

jgcaap said:
before starting the phone, you press Power+Home, and you'll have the custom recovery option right?
There is a option called: "USB MS-Toggle" activate it , From that option you can get a CID without any problem and recover everything
Click to expand...
Click to collapse
I dont know whether its my english that u r nt following or you dint read my post carefully. i had mentioned in my posts that it is not mounting my memory card. In recovery when i do that i get an error
Can't mount /dev/block/mmcblk0
.......................

oh sorry . My english sometimes tricks me. the issue you are passing, there is sure a way out. Could you describe the exacly process you used for installing CM please?

jgcaap said:
oh sorry . My english sometimes tricks me. the issue you are passing, there is sure a way out. Could you describe the exacly process you used for installing CM please?
Click to expand...
Click to collapse
Just as we do any flashing. put to sd card and flashed through recovery in this order(PLZ READ MY FIRST POST COMPLETELY)
1. defaged firmware
2. cyanogen latest update over it (without rebooting)
3. 32A port

what did you had before as radio ? Hboot? Etc
Have you tried to download a oficially signed from HTC Hboot and in fastboot flashing it ?

try the following to see if works.
1)Link your Phone to your computer, run it in fastboot mode.
2)Run a HTC update (choose anyone)
3)Click next until the update confirmation part.
4) run %temp% and you'll find Rom.zip and rom1.zip , copy to a folder and unzipit. Close the update app.
5) collect the following files:
userdata.img
system*.img
Splashe*.nb0
recovery.img
radio.img
hboot*.nb0
boot.img
(The ons with * are the version of the following update you are applying)
6) Zip to a samppimg.zip, put on the SD card and enter in HBoot mode (Volume down+power)
PS: i dont know if works, and it might become worst but try at your own risk. Never passed throught that situation. Last optiion read: http://forum.xda-developers.com/showthread.php?t=655097 and follow the JTAG Hack option. I Dont know any other way.

please post here exacly what you have done:
http://forum.xda-developers.com/showthread.php?p=6243163#post6243163
Lets hope to try to see what we can do.

[Solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb

Hi all!
I have a big problem...
My Hero wan't boot so I go in the Recovery Console.
But if i want to restore a Backup this message appears:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
E: Can't mount SDCARD:
I tried several SDCARDs... same message.
I've wiped all several times. Reformat the SDCARD...
Access via ADB brings:
error: device not found
Fastboot mode is possible... but
fastboot boot cm-hero-recovery.img
in the konsole brings: "downloading 'boot.img'... FAILED (remote: not allow)"...
What can i do?

This might help?.....
http://forum.xda-developers.com/showthread.php?t=681583
then go to .....
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/

Thanks for the links...
I could re-flash the T-Mobile ROM (2.73.111.26)... The Hero starts and now it works with Android 1.5 ...
I have access to the SDCARD ... but the USB Connectivity doesn't work...
No ADB and no storage Device in Windows...
"fastboot oem eraseconfig" doesn't work... think about the false HBOOT (HBOOT-1.76.0007)...
flashrec also doesn't work... there comes "Flash FAILED: could not run command"
Any ideas?

Had exactly the same.
Forget about the rom, it doesn't matter (i.e. flash whatever you like).
You already got your SD card support back, for the rest you need to update the SPL (search for an unlocked version for your hero, double-check because it can _really_ brick your device if this fails). After that fastboot oem eraseconfig works and your usb is back to normal.
Did that yesterday, worked like a charm and actually makes sense (unlike other suggestions like "reflash N times", "unplug and replug usb or change the cable" and "send in for service"). Your USB is fine (as seen in fastboot), it's just not working after your kernel booted -> Due to messed up configuration parameters in the flash area. Basically the kernel commandline, if you will..

Wich version of SPL I do you flash?
How do you flash it? Like...
fastboot oem rebootRUU
fastboot flash zip SPL_image.zip
in the fastboot konsole?
RecoveryConsole is not useable to me... My Hero is not rooted anymore... And it seems to be very difficult to get root again :-/

What do you mean by?
Swerner1975 said:
I have access to the SDCARD ... but the USB Connectivity doesn't work...
Click to expand...
Click to collapse
According to BTDAGs guide, flashing 2.73.61.5 should enable you to use flashrec to do the custom recovery again.

[solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Thanks for your help. I have solved the problems...
- first I flashed the T-Mobile D ROM like described in the Link (extract rom.zip and flash)
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
- then I have detected, that flashrec does'nt work on the ROM
- then I created a GOLD Card
- with this I flashed in the OEM fastboot Mode (described here) the HTC Update ROM (_HTC_Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe)
- then flashrec was working and I was able to flash a Recovery Image
- in the Recovery Console I flashed the unlocked Modaco SPL (from here)
- now it was possible to erase the config, which locked the USB after Kernel Boot (fastboot oem eraseconfig)
- after that I restored the last Nandroid Backup...
- Now I'm happy

Re: NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Excellent news.
-------------------------------------
Sent via the XDA Tapatalk App

[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?

[Q] ADB - HBOOT or FASTBOOT (USB) / HBOOT Version .85

I know this may be hopeless, but I thought I would exhaust all efforts before accepting defeat. I have the MT4G and I have rooted it as well as S-Off. I loaded a ROM on it was working great (Beast V 4) and then it just froze while watching a movie. I had to pull the battery to get it to reboot. It rebooted to the loading screen (Animated Green Droid) and just sat there for 15 min or so. Pulled the batter and it would just stop at the MT4G splash screen. So I booted into HBoot and have:
Glacier PVT ENG S-OFF
HBOOT 0.85.2007 (PD1510000)
MI CROP-0429
RADIO-26.03.02.26_M
eMMc-boot
When loading Recovery I get:
Clockworkmod Recovery v3.0.2.4
E: Cant Mount /cache/recovery/command
E: Cant Mount /cache/recovery/log
E: Cant Open /cache/recovery/log
E: Cant Mount cache/recovery/last_log
E: Cant Open cache/recovery/last_log
I am able to:
Wipe data/factory reset
Resulting in Date wipe complete and then comes back with same errors seen above
Wipe Cache Partition
Resulting in Cache Wipe Complete and then comes back with same error.
Wipe Dalvik Cache
Resulting in nothing. and then comes back with same error
I then tried the PD15IMG.Zip on the root of the SD Card
Result:
[1] BOOTLOADER - Fail-PU
Leaving the rest blank
Update Fail!
So it seems bricked I know. I have bee reading for hours it seems and here are the questions I pose.
1. I read somewhere if the HBOOT is .86 there is nothing I can do, but it mentioned in the thread if I had .85 there was hope, but the person had .86 so the person involved was done. Plus it was different phone. I am wondering since I have .85 is there something else I can do?
2. Another thread I read the person has used ADB and -w to wipe everything off the device. However everything I can find tells me you cant use ADB in FASTBOOT or HBOOT. Is this true? Or can I? I have loaded different drivers to where device manager will see the device as ADB Device but when I run "ADB Devices" It sees nothing. Therefore cannot run -w on it. However this person somehow did then ran the PD15IMG.Zip and it fixed it. Any ideas on how this could be accomplished?
Any help would be appreciated. I am a novice at this, but I do have SDK loaded. I downloaded the HTC Drivers for the device, but it doesnt recognize my device (assuming since I cant get a full boot) and also drivers that will load the phone as an ADB device just cant see it (I know getting repetitive)
One other thing everything I have seen for screen shots is it shows the Fail-PU for each item. Mine however just stops at BOOTLOADER and then tells me update fail and to just press power to reboot.
Couple things I failed to mention
Phone is Rooted and Obviously S-Off (seen above) - Using the Visionary 11 and Gfree process (Not through SDK, but Terminal Emulator and Astro File)

1. You can try to manually flash recovery and ROM using "fastboot flash recovery recovery.img" and "fastboot flash system system.img" commands. The recovery image can be downloaded from Development forum, the stock ROM system image needs to be extracted from PD15IMG. The flash will fail, though - so don't get your hopes high.
2. You can't use ADB in bootloader, you need the phone to boot the kernel and run the ADBD (ADB daemon) to be able to access ADB.
I'm sorry to disappoint you, but Fail-PU means dead eMMC chip, and there's no way around it, no matter which bootloader you have. The only hope is when you have cache failures in recovery, but don't have Fail-PU (and in this case, engineering bootloader helps). Fail-PU is one-way ticket.