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).
Hi I wanted to know how how can I flash roms from pc using adb or fastboot.
Please Help
Thanks in Advance
Few days ago, just seen this here..
It says custom roms can be flashed through fastboot mode. The command (which I'm not sure) will be
fastboot update customrom.zip
It needs alpharevx s-off. Pls check it and report if you are interested in that.
Sent from my HTC Wildfire using XDA App
Gonna Try it for sure
I Have Tried It But it gives the following error while trying to flash cm7
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
So Im pretty sure I nuked my nvram section by accident with a bad recursive rm /sigh (was trying to nuke a single directory and accidentally took out a lot more it seems)
can't boot into recovery but can fastboot but when I try to install an RUU .zip it fails with
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (status malformed (1 bytes))
finished. total time: -0.000s
Or
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in
depending on what image I try to flash
Running HBOOT 0.93 with s-off any suggestions for fix?
Oh and its a Telus desire that I don't believe is branded. One of the RUU's I am using is a Telus RUU
Have you tried flashing a new recovery first? That might allow you to toggle sig verification and then get a new ROM in.
You might need an alpharev custom hboot for that though, and I don't know how you'll get that if it doesn't boot
Im trying to flash RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip on my GSM HTC One M8.
I have root, S-off. when putting in command i get the following error...
C:\>fastboot flash zip Desktop/RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip
error: cannot open 'RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip'
any help would be great!
Thanks
Hi,
Have you checked the md5 checksum of the file you want to flash? Probably the file is broken..
Probably have a look into this thread here : http://forum.xda-developers.com/showthread.php?t=2708589
I am unable to flash the factory image for 5.1 for my lte tablet, I tried redownloading the factory image several times:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 846100724 bytes
error: update package missing system.img
Press any key to exit...
You can try to unpack the factory image, up to the point where you find eg. boot.img, system.img.
I guess that you know how to use ADB and FASTBOOT and already have everything you need inside your eg. Android folder.
1) copy the bootloader, boot.img , system.img inside your "Android folder" ( the folder which contains ADB, FASTBOOT )
2) flash the bootloader ( make sure to type in the right name )
3) flash boot.img , system.img
Restart the device and have fun :good:
So.... I manually flashed the 5.1 for my wifi Nexus 7 2013 and it the first boot is going on 15 minutes with the swirling color dots. I know the first boot I was told will be long... But 15 minutes or more? When should I start to think something is wrong?
Sent from my VS985 4G using XDA Free mobile app