Hi, i'm trying to flash by using fastboot with command prompt. I can't flash anything by useing the recovery option in hboot because it keeps taking me back to the hboot menu.
Right. I extracted the rom.zip from the RUU Rom "testruu" which went okay, it has all the images, includeing the recovery image to get it working again. but when i type in "fastboot -p (serial number) update rom.zip" which the rom.zip is located in the sdk tools folder. it comes up with the error
"Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in "MS-DOS symbols.........."
Any ideas? i tried flashing other rom's but they don't contain the "android-info.txt" within the image zip package.....
Please help because my phone is 100% dead with no recovery working and stuck at the htc logo screen.
so no one knows how to flash in fastboot? well great.
Enter fastboot then plug Desire to your computer and run official RRU (*.exe file)
That should help
Cheers
I want to flash userdata.img, system.img, recovery.img, boot.img files via ADB to my Desire in order to unroot my 2.1, then make it able to upgrade to 2.2 via OTA.
I am using rooted HK 2.1 ROM, have downloaded Asia WWE 2.1 RUU and extracted those .img files.
How can I disable the signature checking? I've got below errors when I tried to flash the img file to my Desire.
C:\r5>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... INFOsignature che
FAILED (remote: signature verify fail)
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
txitxi2004 said:
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
Click to expand...
Click to collapse
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
scott4 said:
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
Click to expand...
Click to collapse
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
i've tried flashing the original recovery.img to Desire, still can't solve the signature check problem. I also have tried doing below:
push flash_image and mtd0.img (what should be the CID of HK 2.1 official rom?) to Desire through ADB, the execute like: flash_image misc mtd0.img
however the upgrade still couldn't pass the signature check... sigh..
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
kekojan said:
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
Click to expand...
Click to collapse
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
eh.. delete me
Update to previous post. I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing (clockwork) was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
Click to expand...
Click to collapse
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
Click to expand...
Click to collapse
The corresponding part of the recovery log below.
- Installing: SDCARD:images_new.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:images_new.zip
Opening update package...
I:Update file path: /sdcard/images_new.zip
Installing update...
I:Trying update-binary.
I:Trying update-script.
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
I like the theory, but you would probably have to fool the RRU so that it thinks your img files have the same checksums as the original img files. I've never heard of anyone being able to repack and flash an RRU file.
kekojan said:
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
Click to expand...
Click to collapse
I think something is wrong with your update-script.
Btw, forget about your system.img, you can't use it .. you have to work with the contents of the system directory instead
ieftm said:
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
Click to expand...
Click to collapse
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
Bootloaders are either ship or eng.
The latter ignores secuflag and allows extended fastboot commands.
So bootloader or s-off are two separate things.
S-off is mainly for unsigned flashing and nand writelocks.
scott4 said:
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
Click to expand...
Click to collapse
only on cdma desire.
For gsm desire you will need to wait for our s-off/eng hboot 0.93 release.
This is a patched hboot to ignore security, and allow extended fastboot commands.
So essentially S-OFF and eng.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
Flashing the misc partition allows you to bypass (fake, really) version checks with an RUU flash, nothing more. It doesn't affect root nor does it have anything to do with signature checking (which is currently impossible to disable on the GSM Desire).
Hey all. Real noob question, and sorry if I didn't find this thread (searched before posting)...
I just used the offical HTC rooting method and want to try out the ICS with HW Accel. ( http://forum.xda-developers.com/showthread.php?t=1411461&page=1 ) from SVN. I downloaded the svn branch, exctracted it, zipped the contents to update.zip and try to run fastboot update /path/to/update.zip and get the following error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any help would be greatly appreciated. Thanks.
I had to restore back to stock and I do not use windows. I was looking for threads but all of them needed windows. So, I am making a tutorial on how to go back to stock on Win/Mac/Linux.
Note - I used my netbook which runs arch linux to complete these steps. I have not tried any other os but it should work.
Requirements On all systems -
Usb drivers (HTC sync provides them on windows. They are preinstalled on linux/mac)
Fastboot
RUU for your device
On linux/mac you need wine. Get wine from your distro on linux and for mac you need to build it manually. Afaik there a few programmes to provide prebuilt wine on mac.
If you don't have wine, get the rom.zip for your RUU from someone here or a windows machine.
Acknowledgementsckpv5 for his tutorial (http://forum.xda-developers.com/showthread.php?t=1705484)
mirGantrophy for his tutorial on how to do it on linux (http://forum.xda-developers.com/showthread.php?t=1974272) Check his thread for pics and screenies.
eLukas for teaching me how to extract rom.zip (http://forum.xda-developers.com/showthread.php?t=1729898)
CafeKampuchia for his tutorial (http://forum.xda-developers.com/showthread.php?t=1706070)
Some other forum(forgot its name) for telling me about a command (fastboot oem rebootRUU)
Let's start
Download the ruu for your device from ruu.androidfiles.org (gsm one v = primoU, cdma = primoC and dual sim = primoDS)
Extract the rom.zip
Linux - Use elukas' script
Mac - get the rom.zip from somewhere. Sorry.
Windows - Run the ruu. Search for temporary folder and copy the rom.zip to somewhere safe.
Extract the rom.zip. We need to flash recovery and kernel(boot_signed.img) from this folder.
Reboot phone to bootloader. Connect it to your system. Make sure fastboot detects the phone.
For recovery
Code:
sudo fastboot flash recovery recovery_signed.img
For kernel
Code:
sudo fastboot flash boot boot_signed.img
Code:
sudo fastboot erase cache
Now we flash the Ruu
Code:
sudo fastboot oem rebootRUU
You may get an error related to hboot. Flash the zip again.
I hope it works for you. If you're on windows, you don't need to type sudo before fastboot.
This worked well, did it in litterally 4 minutes :good:
Is there anything I should add to it?
Umm getting the Ruu was a bit confusing, but i figured it out. Primo....
Thanks, I'll add that the gsm version is primou ,cdma is primoc and primods is dual sim.
arnavk007 said:
Is there anything I should add to it?
Click to expand...
Click to collapse
where do i get mac zip?
vialsofliquid said:
where do i get mac zip?
Click to expand...
Click to collapse
The zip varies from device to device, so you need to download the RUU for your device and then extract the rom.zip from it.
Hi.. thank you for the guide..
actually I am still collecting information in case I need to flash back the stock rom,
but the thing that I want to ask is, do you know where I can get the stock kernel?
Is it also extracted from the windows ruu?
thanks in advance for your reply
-Rif- said:
Hi.. thank you for the guide..
actually I am still collecting information in case I need to flash back the stock rom,
but the thing that I want to ask is, do you know where I can get the stock kernel?
Is it also extracted from the windows ruu?
thanks in advance for your reply
Click to expand...
Click to collapse
Yeah, the RUU contains everything you need. Follow the guide and you'll be fine.
arnavk007 said:
Is there anything I should add to it?
Click to expand...
Click to collapse
I get this is old but, after
fastboot oem rebootRUU
You should
fastboot flash zip rom.zip
Thanks for posting this guide
Good work.
!#quote my post if you want to get my attention more quickly
HTC One S 1.5Ghz Soft Bricked to!
Hey! I have a similar problem to with my HTC One S. I tried the above mentioned but it always get stuck in ''Sending'' When I try to flash recovery or RUU.zip file
Edit: It's not stuck in sending anymore but I get this error:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
I'm thinking that this RUU.zip isn't a zip file I can install via fastboot. And is a SD-card zip file. Which is a problem due to that I can't mount the SD card. And this is the only RUU matching my cellphone and there's no .exe files I found for it
HTC-One-User said:
Hey! I have a similar problem to with my HTC One S. I tried the above mentioned but it always get stuck in ''Sending'' When I try to flash recovery or RUU.zip file
Edit: It's not stuck in sending anymore but I get this error:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
I'm thinking that this RUU.zip isn't a zip file I can install via fastboot. And is a SD-card zip file. Which is a problem due to that I can't mount the SD card. And this is the only RUU matching my cellphone and there's no .exe files I found for it
Click to expand...
Click to collapse
I gave up on RUU files all together and tried different ROMs til I found one that worked. Also managed to fix the SD card error with this guide: http://forum.xda-developers.com/showthread.php?t=2086156
Hi, I'm trying to install cm10.1-RC5 from Arch Linux. I've wiped and factory reset and flashed the boot.img. I don't have s-off.
When I try to install the .zip in ClockworkMod 5.8.4.0 I get errors indicating that my bootloader isn't a compatible version. For example:
assert failed: getprop("ro.bootloader") == "1.31.0000"
E:Error in /sdcard/cm-10.1.0-RC5-endeavoru.zip
(Status 7)
Installation aborted.
I gather that this means my hboot or firmware needs an update. I've found this thread which seems relevant:
http://forum.xda-developers.com/showthread.php?t=2241419
I ran "fastboot oem readcid" and got this:
...
(bootloader) DEBUG: cid: VODAP021
OKAY [ 4.075s]
finished. total time: 4.075s
So I guess this means I need Vodaphone specific firmware? Where can I access this?
Or am I on the wrong track?
Post the result of fastboot getvar version-main..
This is a cmd fastboot command (windows)... No idea what's the command for Linux.. Might be something similar..
This way we can make sure which firmware you have...
-Sent from my IceCold One X!
vin4yak said:
Post the result of fastboot getvar version-main..
This is a cmd fastboot command (windows)... No idea what's the command for Linux.. Might be something similar..
This way we can make sure which firmware you have...
-Sent from my IceCold One X!
Click to expand...
Click to collapse
Thanks for the quick reply, here's the output:
version-main: 1.29.862.11
finished. total time: 4.069s
I've located this thread:
http://forum.xda-developers.com/showthread.php?t=1957376&highlight=upgrade+firmware+linux
This pointed me to .zip containing hboot 1.36.
I tried following these instructions:
http://sadevil.org/blog/2012/12/23/manually-flashing-an-ota-update/
Unfortunately the directories the tutorial references are different to the one in my .zip.
Now there are 2 ways you can upgrade your device's hboot
1: Returning to stock with a ruu and then updating to jellybean hboot with ota update.
2. Flashing the firmware zip and then installing a custom rom.
For running a ruu you will need access to a windows pc since it's an exe file : http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260561-signedexe/
If you want to upgrade your firmware by flashing... Here's the firmware upgrade for your cid : http://goo.gl/yAa0G
Download the firmware and rename it to firmware.zip and then put it in the fastboot folder..
Steps:
1. Relock bootloader : fastboot oem lock
2. Reboot to ruu : fastboot oem rebootRUU
It will take you to a black htc screen... Wait for a few seconds for the screen to settle down and then flash the firmware :
Fastboot flash zip firmware.zip
You might need to flash the firmware twice if you get an error the first time! Its quite normal! After successfully flashing the firmware, you need to unlock the Bootloader, flash a custom recovery and then flash the custom rom!
PS: Again, the commands are for fastboot cmd (windows).. Linux might be a little different..
-Sent from my IceCold One X!
vin4yak said:
Now there are 2 ways you can upgrade your device's hboot
1: Returning to stock with a ruu and then updating to jellybean hboot with ota update.
2. Flashing the firmware zip and then installing a custom rom.
For running a ruu you will need access to a windows pc since it's an exe file : http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260561-signedexe/
If you want to upgrade your firmware by flashing... Here's the firmware upgrade for your cid : http://goo.gl/yAa0G
Download the firmware and rename it to firmware.zip and then put it in the fastboot folder..
Steps:
1. Relock bootloader : fastboot oem lock
2. Reboot to ruu : fastboot oem rebootRUU
It will take you to a black htc screen... Wait for a few seconds for the screen to settle down and then flash the firmware :
Fastboot flash zip firmware.zip
You might need to flash the firmware twice if you get an error the first time! Its quite normal! After successfully flashing the firmware, you need to unlock the Bootloader, flash a custom recovery and then flash the custom rom!
PS: Again, the commands are for fastboot cmd (windows).. Linux might be a little different..
-Sent from my IceCold One X!
Click to expand...
Click to collapse
Golden gold you are sir/madam! Got CM10.1 running like a beast!
Thankyou kindly.
That's Great! Enjoy cm10! :good:
-Sent from my IceCold One X!
firmware for htc_38 for hboot update
I have HTC One X, currently i m at hboot 1.72 and CWR 6.0.4.7. I want to update my hboot for that i need firmware for my device whose CID is htc_38. I have already gone through xda page of "collection of firmware" to search for my device's firmware but i didnt get it there. plzzzzzzz help me out here.
abhinav625 said:
I have HTC One X, currently i m at hboot 1.72 and CWR 6.0.4.7. I want to update my hboot for that i need firmware for my device whose CID is htc_38. I have already gone through xda page of "collection of firmware" to search for my device's firmware but i didnt get it there. plzzzzzzz help me out here.
Click to expand...
Click to collapse
You are with the latest firmware!!!!