Develop Bugs

[Q] Cannot flash ROMs | write_raw_image

Hello. I'm new to all this. I've searched several forums for an answer to my issue, but unfortunately I haven't been able to get to a final resolution.
What's wrong?
When I boot into ClockworkMod (2.5.0.7) Recovery, I get the below:
E:Can't find MISC:
E:Can't mount cache:recovery/command
E:Can't find MISC:
E:Can't mount cache:recovery/log
E:Can't find MISC:
Click to expand...
Click to collapse
When I try to backup the current ROM, I get this:
Backing up boot...
Error while dumping boot image!
E:Can't mount cache:recovery/log
E:Can't find MISC:
Click to expand...
Click to collapse
When I try to flash LeeDr0iD 2.3d, I get:
-Writing boot.img
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/LeeDr0iD.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
So I thought this might be because the .zip file is corrupted or something, so I went on and downloaded and flashed the latest CyanogenMod (checked the MD5 to make sure), but it gave me the same error.
What I did to my device?
I rooted using the unrevoked method. It was pretty straight forward, just installed the Android USB drivers and ran the reflash_package.exe... At the end I checked the root access by adb shell, then su, and I got the ever-so-famous #. I noticed there was an "update.zip" in the root of the SDcard after rooting the phone, but I didn't run it.
What I gathered from my search
When I was searching I read about SPrecovery, I'm guessing it's another recovery...thingi, other than CMrecovery, but I never found a .zip file for it [maybe someone can point me to it].
I also read something about a file PC36IMG.zip, and that people have fixed this error I'm getting using that file. From what I gathered, I think that file was used in the HBOOT downgrading process (from 0.8 to 0.7-something). I downloaded this file but I didn't copy it to my SDcard because I read something I'm not supposed to "apply" it when I enter HBOOT on my phone.
I have yet to use AlphaRex 1.8 to S-OFF the NAND security, but I currently don't have a blank CD to burn the alpharev image. [Question: can I just run the "fastboot flash hboot bravo_alphaspl.img" command on Windows 7, without having to boot into the Linux livecd? I already downloaded and installed the Android SDK tools =/].
My device information
HTC Desire GSM. Froyo (Android 2.2) out of the box, now running software: 2.29.405.5
And this is what appears in HBOOT:
Bravo PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Click to expand...
Click to collapse
PS: I wouldn't blame you if you hit the back button on your browser after being shocked by this long post...wait, you wouldn't be reading this if you already navigated away from the thread...ah well =/.

As you have a PVT4 Desire you need to use AmonRa instead of CWM, read the PVT4 thread in General

Use amon-ra recovery. I had the same error as you on my pv4 desire.
Sent from my HTC Desire using Tapatalk

Ok, so I'm trying to flash the Amon-Ra recovery but I get the below error:
sending 'recovery' (3936 KB)... OKAY [ 0.938s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.404s
Click to expand...
Click to collapse
I'm guessing this is because I do not have S-OFF yet (and I can't get S-OFF right now since I do not have a blank CD to burn the Linux livecd). So, I can just unroot the device, then root it again but point unrevoked to the Amon-Ra recovery instead of the CMrecovery, right?
Question about unrooting: Download the official RUU. Connect the phone to HTC Sync. Run the official RUU. That's it?
EDIT: Do I have to unroot then root again? Or is it possible to just run unrevoked on the already-rooted device but point it to the Amon-Ra recovery instead?

You need to be rooted to S-OFF, just run unrEVOked again and choose a custom recovery

EddyOS, thank you, and you as well drSTRIFE. I finally flashed my first custom ROM.
To whom it may concern, 'what did I do':
I tried running unrevoked but I kept getting the "Error: failed to get root. Is your firmware too new?", so I factory reset the device and gave it another try. Successfully flashed Amon-Ra. I tried flashing CyanogenMod and it was flashed successfully, but the splash screen kept looping. I only wiped the cache before, so now I wiped ALL userdata, and reflashed CyanogenMod. Now it works. Unfortunately though, I did not backup my original ROM, but I have the official RUU, so I guess that's enough if something goes wrong.

Error in Recovery and Flashing! Help!

Ok, I’m a new Desire user and rooted the phone using unrevoked 3.32, I went into ClorkworkMod 2.5.0.7 and this is the error:
E:Can’t find MISC:
E:Can’t mount CACHE:recovery/command
E:Can’t find MISC:
E:Can’t mount CACHE:recovery/log
E:Can’t find MISC:
I followed the steps, and I don’t know what I did wrong. I can’t flash a new ROM (Oxygen 2.1.2). Here’s the error:
Installing update…
assert failed: write_raw_image("/tmp/boot.img"."boot")
E:error in /sdcard/update-oxygen-2.1.2-signed.zip
(Status 7)
Installation aborted
Can anyone guide me?

Flash another recovery in fastboot (if you're s-offed) or with unrevoked if you're s-on

I tried but it does not work with the flash process fails AmonRa finish
root its clockwork ..
Bravo PVT4 SHIP s-on
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27

same problem with my Desire.
I found the recovery-RA-desire-v2.0.1 here work for my desire
flash it using Unrevoked 3.21 here with the custom image option, just point it to the recovery-RA-desire-v2.0.1.img and rerun the root.
then you can flash new rom with no error (status 7)

Unrevoked usually flashes clockworkmod recovery 2.x.x.x. This version 2 does not work with pvt4 versions of the desire:
http://www.roms-au.com/installation/rooting/pvt4-issues/
Flashing amonra recovery will solve your problem. If you really want clockwork mod, you should download clockwork since version 3 oder even 4:
http://forum.xda-developers.com/showthread.php?t=1112658&highlight=recovery

Cant flash Rom with recovery or fastboot

Hey
unlocked bootloader, s-off and latest cwm touch recovery. Tried to flash a Sense 5 Rom but I get this error in recovery:
E: Error in /*path*/*rom.name*.zip
(Status 1)
Installation aborted.
Help pls, thx for any reply.

Solution
Used another sd card and tried it 2 times, now its working

[Q] wildfire s cant install roms (status 0)

hi i have a wildfire s
specs:
android 2.3.5 (newest official update)
t-mobile germany rom (cid: t-mob101)
unlocked with htcdev
s-on
hboot-1.09.009
teamwin recovery v2.2.2.0
phone is rooted, flashing root.zip worked
tried to install 3 different roms with 2 different recoverys and it says:
-- Install /sdcard/pa_marvel-4.5...
Finding update package...
Installing Update
E:Error in /sdcard/pa_marvel-4.5....
(status 0)
* verifying filesystems...
* verifying partition sizes...
Error flashing zip '/sdcard/pa_m....
can anyone help me please?
do i have to be s-off to flash roms?

JustW0LF said:
E:Error in /sdcard/pa_marvel-4.5....
(status 0)
* verifying filesystems...
* verifying partition sizes...
Error flashing zip '/sdcard/pa_m....
do i have to be s-off to flash roms?
Click to expand...
Click to collapse
No. You do not have to be S-OFF to Flash ROMS.
I would suggest you to do the following and see if it works.
1. Try flashing any of the following recoveries and then try flashing a new ROM.
a. ClockworkMod Recovery 5.0.2.8
b. TeamWin Recovery Project 2.7.1.0
c. ClockworkMod Recovery 6.0.5.3
d. CWM Advanced Edition PhilZ Touch
2. Backup sdcard data. Format the sdcard and try again.

Generally "status 0 error" occurred during the flash with wrong ROM/kernel or device. So check you device model number again. And make sure you are using right recovery for your device.
Sent from HTC Desire 616

[Q&A] Semi bricked Desire

Hey Folks!
After the dead of my desire (7 buzzes / vibrates -> indicates a broken soc/motherboard) and the new rising (got a motherboard of a desire with a broken screen) the old lady worked again!
I got the s/n and system from the one with the broken screen - this is normal because it's stored on the mainboard. It was a CM v7 as I remember.
Here as a list of things I did and where I stuck now:
flashed an up-to-date recovery TWRP -> worked
tried to install a new rom with a new hboot which -> didn't worked out
Since here I only can access the recovery
All attempts to flash something (via recovery or fastboot) -> doesn't work
also tried to use revolutionary (even it's already unlooked and s-off) -> but the app stucks
I could only flash the boot logo via fastboot the rest results in different errors like:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?

Here is an other error message i get when running this fastboot command
Code:
fastboot getvar all
getvar:all FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm realy appreciate any help!
BTW: I'm not a robot!

Des!re said:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Click to expand...
Click to collapse
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.

eddiehk6 said:
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
Click to expand...
Click to collapse
Thanks for your reply. Some things I forgot to mention in the thread above.
I successfully rooted, s-off, and flashed a new hboot & rom to my old desire.... all before she died. I remembered I needed some tries for the hboot... but it worked out fine in the end.
I also need to say that I tried (with the new/repaired one) different clients (hardware and os, win & linux) and different cables. Just to be sure.
I also went sure that fastboot is working (fastboot devices) and there always was my serial -> so it's good for sure
I read something about that the Alpharev hboot (with the repaired phone there was also the bootsplash with 'alpha-rev s-off / why so serious?' before I flashed it away to the stock 'htc') is somehow write-protected itself which can cause issues???
I tried to flash the "Alpha Jelly (250/5/182) hboot" to be able to install CarbonRom 1.0 (4.4.4) by spezi77 (http://forum.xda-developers.com/showthread.php?t=2658853). But I didn't succeeded at all.
eddiehk6 said:
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
Click to expand...
Click to collapse
I think I flashed the recovery via fastboot, it just worked once. When I tried to flash CWM it didn't worked anymore.
eddiehk6 said:
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
Click to expand...
Click to collapse
I did checked the md5sum's and I tested a couple of Roms (more than 3)
eddiehk6 said:
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
Click to expand...
Click to collapse
My old devices was a PVT4 and the repaired one is a PVT1 - there should be no difference for the hboot i guess?
eddiehk6 said:
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
Click to expand...
Click to collapse
This I should have done straight after I repaired the hardware and I was able to boot in CM7.... To late for now but if I have a working state I definitely do this!! :good:
eddiehk6 said:
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
Click to expand...
Click to collapse
I don't have a booting system yet so I need to postpone this. To be able to do the pb99img.zip method i formatted the whole sd-card with one partition as fat32. But when I have (hopefully) soon a working system I need to partion it correctly - easy!
eddiehk6 said:
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
Click to expand...
Click to collapse
I'm the resarcher! I'm going down to reasearch - I will report!
Thanks for your help so far!

I'm the resarcher! I'm going down to reasearch - I will report!
Click to expand...
Click to collapse
I went down to research!
I tried to flash hboot 'Bravo Stock' by Alpharev.
Code:
fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)...
OKAY [ 0.104s]
writing 'hboot'...
OKAY [ 0.160s]
finished. total time: 0.264s
looks good for me!
the bootscreen changed from
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
to
Code:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
so first and third line changed!
And because it's so nice to flash hboot i also flashed AlphaRev Jelly successfully!!
I try flash a rom now :fingers-crossed:

After I successfully flashed my hboot (twice!)....
I'm not able to wipe or install stuff....
Team Win Recovery Project v2.7.1.0
WIPE -> Factory Reset (Wipe Data, Cache and Dalvik)
Code:
Factory Reset Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
E:Unable to recreate and-sec folder.
Updating partition details...
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup.
Full SELinux support is present.
E:Unabke to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Updatting partition details...
E:Unable to mount storage.
### FAILED ###
Team Win Recovery Project v2.7.1.0
Install -> ZIP
Code:
Zip Install Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not create file for updater extract in '/tmp/updater'
Error flashing zip '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'
Updatting partition details...
### FAILED ###
Maybe there is something "broken" with the filesystem?
As always I appreciate any help

Did a 'clear userdata' in the boot menu and then a wipe via TWRP.
Now it was successful but with this errors in the console:
Code:
Factory Reset Complete
Successful
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Wiping Android Secure
Formatting SD-Ext using make_ext4fs function.
Updating partition details...
But I wonder where are these errors from
Installing a rom still doesn't work. I think the problem is this line:
Code:
E:Could not create file for updater extract in '/tmp/updater'

There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
You have to do the following steps to flash any files :
- boot into recovery mode
- choose 'Advanced'
- choose 'Terminal Command'
- You're now on the '/' (root of the file system). Choose 'Select'
- Type : 'mkdir tmp' without quotes, then Hit the enter key of your keyboard.
- Return to the main screen (Go back 3 times)
- Choose 'Install' and select the file.
Click to expand...
Click to collapse
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046

Des!re said:
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Click to expand...
Click to collapse
I've personally never used TWRP on the Desire.
I recommend trying with 4EXT Recovery, never had any issues with it.
If you can successfully flash an hboot, you should be able to flash the recovery.img using the same method.