Develop Bugs

Trying to use ADB to flash_image on Desire Z

Hey, I've been following Cyanogen mods guide about flash_image to flash PSFmod onto my phone. I can use ADB to push files to my SD card and stuff, but when I follow this:
Code:
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
But I get this error:
Code:
error scanning partitions
Does anyone know how to fix it?

You get that error from which of those commands ?

From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?

Beegee7730 said:
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Click to expand...
Click to collapse
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?

Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App

I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?

steviewevie said:
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Click to expand...
Click to collapse
I got it from the Cyanogen Mod Wiki, should I look for a different version?
theXeffect said:
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would but the recovery I'm flashing isn't supported by Rom Manager.
steviewevie said:
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
Click to expand...
Click to collapse
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.

Beegee7730 said:
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Click to expand...
Click to collapse
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Wait a sec.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Tried few days ago with a kernel,but don`t works too.
You mean I need the eng hboot,then it should work,right?
Otherwise fastboot don`t work.

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>

Beegee7730 said:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
You haven't got S-OFF. You need S-OFF to flash a custom recovery.

I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.

Beegee7730 said:
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Click to expand...
Click to collapse
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.

steviewevie said:
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
Click to expand...
Click to collapse
SHIP.
I assume I need to reflash it with the engineering one?

Beegee7730 said:
SHIP.
I assume I need to reflash it with the engineering one?
Click to expand...
Click to collapse
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?

Beegee7730 said:
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Click to expand...
Click to collapse
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.

steviewevie said:
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
Click to expand...
Click to collapse
Ah, managed to flash it.
Will test and report back when done.
EDIT:
It works!
Thanks alot!

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
I think too,the same with my HTC Hero.
Fastboot wont work without engineering bootloader/hboot!
So the same at Desire Z.

E:Cant mount /cache/recovery/command

Have been getting this error of late after i run unrevoked, then when i go to recovery to flash rom i get this error...is there any solution to this, or is there a new version of unrevoked to solve this porblem? Im using unrevoked v3.32.
Thank you.

Phone details? recovery version? Which Rom?

davebugyi said:
Phone details? recovery version? Which Rom?
Click to expand...
Click to collapse
Unfortunately i gave the phone back to a friend who need help, so cant provide any info

Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.

lowkey1979 said:
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
Click to expand...
Click to collapse
Do you have a pvt4-desire? If, you have to flash amonra-recovery, because cwm is incompatible with pvt4-desires.

or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF

ghalalb said:
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
Click to expand...
Click to collapse
Can you tell me how to flash recovery with fastboot?

You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/

MatDrOiD said:
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
Click to expand...
Click to collapse
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?

andrew21 said:
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
Click to expand...
Click to collapse
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189

hi mates,
to flash recovery with fastboot need to be s-off.
the command are really simple.
boot in hboot, select fastboot (shoul see fastbbot usb on the phone screen)
open a command line
Code:
fastboot flash recovery c:/wheretefileis/yourecovery.img

MatDrOiD said:
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
Sir,
I tried this method but i get a "flash_image: not found". It seems like i don't have the flash_image command on my phone. I've looked everywhere to find a way to get that command and i found this - http://www.villainrom.co.uk/forum/s...)
finished. total time: 1.094s
Thank you sir

chage a sd card for try!

zk7513153 said:
chage a sd card for try!
Click to expand...
Click to collapse
Already did change the sdcard sir.
On another note, whenever i tried remounting the /system for RW access to copy flash_image, free space drops to Zero Kb. To isolate, i tried remounting to just Read access, free space remained the same. Anything I'm missing here, or do I really have to S-OFF my phone before I can make changes on my /system ?
Thank you very much.

nonofficialcover said:
I also tried flashing via ADB and I get this:
C:\fastboot flash recovery c:\recovery-RA-desire-v2.0.1.img
sending 'recovery' (3936 KB)...
OKAY [ 0.687s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.094s
Thank you sir
Click to expand...
Click to collapse
For this part I think you need to disable signature verification in recovery.

I was able to solve my problem after I did S-OFF.

trouble rooting and running CM9

After a bunch of trouble yesterday I was able to setup Revolutionary and root my phone with tacoroot, or at least I think I rooted it. Then I found CM9 that people were posting in these forums. I loaded the CM9 and the google apps market thing into the sdcard with adb and installed it. Then I restarted my phone and it couldn't make it past the CM9 welcome screen.
Then this morning I was reading online and I found something that suggested that I need to update the radio so I pushed PG32IMG.zip with adb and now it seems to be locked in a boot cycle with HBOOT. When I get into the bootloader it tires to update the radio but when I try to just load my phone it gets stuck at the CM9 welcome animation.
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0722
eMMC-boot
Any ideas would be great. Thanks in advance.
Edit: Could this problem come from me not installing super user access? The tutorials I followed didn't have something that said to do it and it wasn't a step in the process. I think there is probably access because I have S-Off; however, I did buy this phone used and the previous owner could have rooted it and then reverted it back to Sense.

Plug in the phone and turn it on normally, when it gets to the boot animation use the command "adb shell rm /mnt/sdcard/PG32IMG.zip" then try redownloading and flashing the radio and flashing cm9, you don't need to worry about root, cm9 is already rooted.
Sent from my Incredible 2 using Tapatalk 2

prototype7 said:
Plug in the phone and turn it on normally, when it gets to the boot animation use the command "adb shell rm /mnt/sdcard/PG32IMG.zip" then try redownloading and flashing the radio and flashing cm9, you don't need to worry about root, cm9 is already rooted.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
It says "rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied"
C:\>adb shell rm /mnt/sdcard/PG32IMG.zip
rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied
C:\>adb shell
[email protected]:/ $ rm /mnt/sdcard/PG32IMG.zip
rm /mnt/sdcard/PG32IMG.zip
rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied
255|[email protected]:/ $ su
su
Permission denied
1|[email protected]:/ $ Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)
at dalvik.system.NativeStart.main(Native Method)
rm /mnt/sdcard/PG32IMG.zip
rm /mnt/sdcard/PG32IMG.zip
rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied
Click to expand...
Click to collapse

benj123 said:
It says "rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied"
Click to expand...
Click to collapse
Try this:
Code:
adb shell
su
rm /mnt/sdcard/PG32IMG.zip
Sent from my Incredible 2 using Tapatalk 2
---------- Post added at 02:35 PM ---------- Previous post was at 02:31 PM ----------
Just saw your edit, while it's bootlooping type "adb reboot recovery" then try reflashing cm9, make sure you wipe everything.
Sent from my Incredible 2 using Tapatalk 2

prototype7 said:
Just saw your edit, while it's bootlooping type "adb reboot recovery" then try reflashing cm9, make sure you wipe everything.
Click to expand...
Click to collapse
Should I wipe the SD card? When I was trying to flash I had been wiping the cache partition and the Dalvik cache. I never wiped the battery status.
Edit: Sorry I should have added that I've already tried installing CM9 a couple of times with various versions and they all seem to get stuck at the loading animation. Yesterday I downgraded from 2.3.4 to 2.3.3 and then rooted it. Then I tried to install CM9. Do I need to wipe the OS partition prior to installing?
Edit2: Do you mean I should do a "wipe data/factory reset" to wipe all the user data? I hadn't been doing that before when I had been trying to install CM9

benj123 said:
Should I wipe the SD card? When I was trying to flash I had been wiping the cache partition and the Dalvik cache. I never wiped the battery status.
Edit: Sorry I should have added that I've already tried installing CM9 a couple of times with various versions and they all seem to get stuck at the loading animation. Yesterday I downgraded from 2.3.4 to 2.3.3 and then rooted it. Then I tried to install CM9. Do I need to wipe the OS partition prior to installing?
Click to expand...
Click to collapse
What version are you installing?
Sent from my Incredible 2 using Tapatalk 2

prototype7 said:
What version are you installing?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to install an unofficial CM9. Whatever ones I found in the forums. A lot of the links to downloads from a few months ago don't work anymore so I've had to scavenge around to find some.
I have cm-9-20120712-UNOFFICIAL-vivow.zip and cm-9-20120816-UNOFFICIAL-vivow.zip

I fixed it. I feel like an idiot. My problem was that I just didn't wipe the user data. I must have missed that step in the tutorials and thought that clearing it was part of the install.
Thanks!

benj123 said:
I fixed it. I feel like an idiot. My problem was that I just didn't wipe the user data. I must have missed that step in the tutorials and thought that clearing it was part of the install.
Thanks!
Click to expand...
Click to collapse
Did that fix the bootloop? I'm having a boot loop issue after following this guide. I'm S-OFF, but i get an error when I try to flash the radio in fastboot. "fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip"
I get the msg: FAILED (remote not allowed)
EDIT 1: weird. i kept getting bootloops after OS would load. I tried to flash the Radio and got the error below:
C:\miniadb_inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.312s]
writing 'zip'... FAILED (remote: not allowed)
In recovery, I wiped the data (factory reset) and cache. Then it boot fine. I turned off fast boot and turned on usb debugging (not needed for fastboot usb) and I still get the failure above. Any ideas why I can't flash the Radio.
Also, do I really need to flash the radio as the OP stated? I've currently got:
HBOOT-6.13.1002
RADIO-1.09.01.0622
EDIT 2: I just rebooted and I'm back in a bootloop. As soon as the OS loads, it reboots.
EDIT 3: I got it working. I just needed to follow scotty's guide and flash from the oem rebootRUU state.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)
fastboot reboot-bootloader (make sure your baseband changed)
fastboot reboot

Sorry man I have no clue. I just got my first android yesterday so I'm very new to this whole rooting thing. If go into the bootloader then my phone still tries to update the radio. I'm just going to manually delete the file one of these days on my computer when the sdcard is out of the phone

agapedisciple said:
Did that fix the bootloop? I'm having a boot loop issue after following this guide. I'm S-OFF, but i get an error when I try to flash the radio in fastboot. "fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip"
I get the msg: FAILED (remote not allowed)
EDIT 1: weird. i kept getting bootloops after OS would load. I tried to flash the Radio and got the error below:
C:\miniadb_inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.312s]
writing 'zip'... FAILED (remote: not allowed)
In recovery, I wiped the data (factory reset) and cache. Then it boot fine. I turned off fast boot and turned on usb debugging (not needed for fastboot usb) and I still get the failure above. Any ideas why I can't flash the Radio.
Also, do I really need to flash the radio as the OP stated? I've currently got:
HBOOT-6.13.1002
RADIO-1.09.01.0622
EDIT 2: I just rebooted and I'm back in a bootloop. As soon as the OS loads, it reboots.
Click to expand...
Click to collapse
You need to rename the file to just PG32IMG.zip and install it from hboot.
Sent from my Incredible 2 using xda app-developers app

Baloeb said:
You need to rename the file to just PG32IMG.zip and install it from hboot.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I finally got it working the other night. I guess my EDIT 3 didn't work then, so i just added it again. I try to flash everything via USB instead of sdcard now, b/c I get more reliable results and I don't have to keep swapping the sdcard. :good:

[Q] galaxy nexus stuck on boot loop screen animation.

I update, my ROM from cyanogenmod ROM 10.1 m1 to 10.1 m2 ROM and know my galaxy nexus is stuck on boot loop animation! I tried, tacking out the battery and then turning it back on no luck in also tried the ( volume button and power button method) and still no luck with that. Is,there a way I could fix it?

wipe data and reflash rom.

Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse

Never, mind i got it working know!

mrcoleminer said:
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse

Zepius said:
mrcoleminer said:
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse

Chamaeleon said:
Zepius said:
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse

Soulaysahmi said:
Chamaeleon said:
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
I was using the ClockworkMod (I don't remember exactly the version number but I updated recently and it was the touch screen one). I'll try to re-install also the recovery with the very last version (6.0.4.7). Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse

Chamaeleon said:
Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
have you tried adb sideload?

Soulaysahmi said:
have you tried adb sideload?
Click to expand...
Click to collapse
Just tried.
On the terminal after the command
adb sideload cm-11-20141115-SNAPSHOT-M12-maguro.zip
it tells me "error: closed"
I also tried to reinstall the Clockwork via bootloader but didn't change the situation (still not able to do a complete factory reset)

you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?

Soulaysahmi said:
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Click to expand...
Click to collapse
You are right, I didn't click "install zip from sideload" before. Now I tried in this way and, effectively, it worked: I managed to send and install the zip apparently without any problem but than after rebooting I'm still not able to turn on the phone completely. Again the same problem. I re-tried to do wipe data/factory reset both from the recovery and using adb but didn't managed to finish the process...
It seems I tried all the options since now.... but my nexus is still unusable...

did you try getting back to stock rom using any guide on this forum?

Soulaysahmi said:
did you try getting back to stock rom using any guide on this forum?
Click to expand...
Click to collapse
I tried but still with the same result. I'll try to follow the guide I found here

I mean through methods other than recovery, through fastboot mode or odin mode.

Soulaysahmi said:
I mean through methods other than recovery, through fastboot mode or odin mode.
Click to expand...
Click to collapse
I tried to Restore Galaxy Nexus to Stock (as described here) with the proper google image but in the last passage I get:
$ fastboot -w update image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMELC03
Baseband Version.....: xxx
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
FAILED
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'
I put all I need in one folder and I decided to update the bootloader at the PRIMEMD04 version but apparently I didn't managed because doing again the procedure I was getting the same error
ps: I'm using linux so I don't have odin

when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?

Soulaysahmi said:
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Click to expand...
Click to collapse
Yes I have BOOTLOADER VERSION - PRIMELC03
With fastboot I tried to install the PRIMELC04 bootloader
$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.969s]
finished. total time: 8.278s
$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But than, after the reboot, on the screen it's still written BOOTLOADER VERSION - PRIMELC03
I think this is the main problem now... if it's not updated the bootloader I can not reinstall the rom probably...

you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img

Soulaysahmi said:
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Tried as you suggested to install the PRIMELC04 bootloader flashing each image.
Apparently is not possible also in this way. After rebooting on the screen is still written BOOTLOADER VERSION - PRIMELC03.
So I tried to install a stable cyanogenmod 10.2.1 (which should work with the bootloader 03).
I used adb sideload and after the "installing updates" message, everything stopped with the message "fixing fs_size in crypto footer". After more than 30 min I rebooted and the situation was the same as before.

[Q] HTC Desire HD not working after flashing 4ext

My DHD will not boot up. I can put it into recovery mode, but am not able to navigate the menu with my volume buttons or select options with the power button.
This occurred after an (apparently failed) attempt to flash the 4ext recovery.img onto my phone.
My phone has an unlocked bootloader, S-ON, and not rooted, if that helps.
I appreciate any help with my issue in either successfully flashing the recovery.img or getting my phone to work in any way. Thanks!

Switch5050 said:
My DHD will not boot up. I can put it into recovery mode, but am not able to navigate the menu with my volume buttons or select options with the power button.
This occurred after an (apparently failed) attempt to flash the 4ext recovery.img onto my phone.
My phone has an unlocked bootloader, S-ON, and not rooted, if that helps.
I appreciate any help with my issue in either successfully flashing the recovery.img or getting my phone to work in any way. Thanks!
Click to expand...
Click to collapse
try reflashing another recovery?TWRP or CWM from the official site?
use this command
fastboot flash recovery recovery.img (rename your img to recovery.img )

Steam. said:
try reflashing another recovery?TWRP or CWM from the official site?
use this command
fastboot flash recovery recovery.img (rename your img to recovery.img )
Click to expand...
Click to collapse
sending 'recovery' (6116 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 4.849s
This is the error I get. realize that my phone is stuck in HBOOT because I cannot navigate to Fastboot. Thanks for the reply.

Switch5050 said:
sending 'recovery' (6116 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 4.849s
This is the error I get. realize that my phone is stuck in HBOOT because I cannot navigate to Fastboot. Thanks for the reply.
Click to expand...
Click to collapse
probably the misc partition is fked, or the chip's gone bad.I'd try reflashing HBOOT by putting it manually via the sdcard, naming it PD98IMG.zip and putting the sdcard back.I'd wait out on another opinion though.

Steam. said:
probably the misc partition is fked, or the chip's gone bad.I'd try reflashing HBOOT by putting it manually via the sdcard, naming it PD98IMG.zip and putting the sdcard back.I'd wait out on another opinion though.
Click to expand...
Click to collapse
In case I don't get another option, could you instruct me on how to transfer the file to the sdcard? Sorry, not very knowledgable on this type of thing.

Switch5050 said:
In case I don't get another option, could you instruct me on how to transfer the file to the sdcard? Sorry, not very knowledgable on this type of thing.
Click to expand...
Click to collapse
Remove it from the phone, insert it into a cardreader of some sort, transfer it to the sdcard renaming it to PD98IMG.zip,putting the file in the root of the sdcard, no folders, putting the card back into the phone, booting to Hboot, pressing the power button just once to start the procedure.If you can't press any of the buttons in HBOOT too, then your phone is effed.
again, don't try this before someone else gives an opinion on this matter.

Steam. said:
Remove it from the phone, insert it into a cardreader of some sort, transfer it to the sdcard renaming it to PD98IMG.zip,putting the file in the root of the sdcard, no folders, putting the card back into the phone, booting to Hboot, pressing the power button just once to start the procedure.If you can't press any of the buttons in HBOOT too, then your phone is effed.
again, don't try this before someone else gives an opinion on this matter.
Click to expand...
Click to collapse
Cannot navigate HBOOT. My phone is apparently effed.

Switch5050 said:
Cannot navigate HBOOT. My phone is apparently effed.
Click to expand...
Click to collapse
Have you tried Glevitan's tool to flash CWM recovery? You can find it here:
http://forum.xda-developers.com/showthread.php?t=2133336
Or actually, these are the steps his tool do for flashing the recovery (use adb.exe and fastboot.exe, and change the location of CWM image):
echo Rebooting into fastboot usb
echo.
adb reboot-bootloader
adb kill-server
sleep 10
set recovery=tools\recovery\recovery-clockwork-touch-5.8.1.5-ace.img
fastboot flash recovery %recovery%
fastboot reboot​

Matth59 said:
Have you tried Glevitan's tool to flash CWM recovery? You can find it here:
http://forum.xda-developers.com/showthread.php?t=2133336
Or actually, these are the steps his tool do for flashing the recovery (use adb.exe and fastboot.exe, and change the location of CWM image):
echo Rebooting into fastboot usb
echo.
adb reboot-bootloader
adb kill-server
sleep 10
set recovery=tools\recovery\recovery-clockwork-touch-5.8.1.5-ace.img
fastboot flash recovery %recovery%
fastboot reboot​
Click to expand...
Click to collapse
that is if he can get to adb working at all, he's in hboot and he can't navigate, so no go

Switch5050 said:
sending 'recovery' (6116 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 4.849s
This is the error I get. realize that my phone is stuck in HBOOT because I cannot navigate to Fastboot. Thanks for the reply.
Click to expand...
Click to collapse
Take The sdcard out And reboot in hboot. Then try navigating To fastboot