Related
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).
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
Hey there.
I am S-ON and trying to find a way of updating the firmware to 2.22xxx on my M8 with CID HTC_032.
Anyone?
EDIT:
I found this guide http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 and the firmware zip has my phone's modelid and cidnum.
However, after renaming the file 0P6BIMG.zip, placing it on the ext_sd and rebooting to bootloader, the hboot checks the zip and after that I get an error in red font: Press <POWER> to reboot.
Anyone?
EDIT2:
nevermind. I found this guide http://forum.xda-developers.com/showthread.php?t=2735235 and following step 6 with the zip file provided there I managed to upgrade my firmware.
Hello,
i have single sim d820 (europe)
Code:
***************************
Software status: Modified
A51_UL PVT SHIP S-ON
hboot-3.19.0.0000
radio-01.01.010_U10305041_08.01.50512
os-2.10.401.2
***************************
Before i messed it up it was unlocked and rooted and S-ON, then i wanted to install OTA and i flashed firmware.zip extracted from OTA zip file (bad idea). Now i'm unable to get my phone working...
What i can do:
-enter bootloader
-fastboot commands
-enter recovery
What I've tried and didn't work:
-flash stock recovery, lock, flash RUUk44.zip via fastboot (signature verify fail)
-flash stock recovery, lock, flash lollipop OTA (signature verify fail)
-flash TWRP, restore k44 backup (bootloop after reboot from recovery)
The question is, if I would somehow obtain firmware from k44 stock, is it possible to downgrade on S-ON using "fastboot flash zip" and then restore backup or flash RUU?
I cannot find magical RUU.exe for this model there are only zip files...
Guys maybe someone can dump kitkat firmware i would be grateful...
I appreciate any idea, please help me solve it
Look here: http://www.easy-firmware.com/index.php?a=browse&b=category&id=725
The first zip ist the europa version kk 4.4. for 51 ul.
Rename it as OPFJIMG.zip and put it on your external sd car. boot into bootloader and let it run. I hope it works for you!
By the way, is it possible for you to upload and share your complete OTA zip? Would be wonderfull.
Oel said:
The first zip ist the europa version kk 4.4. for 51 ul.
Rename it as OPFJIMG.zip and put it on your external sd car. boot into bootloader and let it run. I hope it works for you!
By the way, is it possible for you to upload and share your complete OTA zip? Would be wonderfull.
Click to expand...
Click to collapse
Zip method does not work for me neither from fastboot nor from sdcard. In fastboot i get "signature verify fail", via sdcard it says sth like "fail due to large image failed".
I'm now downloading exe file from your link.
edit: RUU.exe from link above failed - stuck at 4%(checking header or sth like that)
I will upload OTA zip this night.
Maybe i don't understand something, but i wonder why RUU zip doesn't contain firmware.zip like OTA update package.. ?
Good luck and thank you for the upload bro!
cr3h said:
I will upload OTA zip this night.
Click to expand...
Click to collapse
Do you have the OTA uploaded ?
Today it was possible for me to install the orange version spain from the ruu.zip what i mentioned to you!
I was following this tut:
"You can extract the ROM.zip from any RUU to install via ZIP
Start the RUU and once at the first main screen click Start>Run and type
%temp%
now, find the newest folder and in there will be a ZIP file called Rom.zip - copy this to your desktop and rename it to OPFJIMG.zip Now copy this to your SD card and start the phone in HBOOT (turn it on whilst holding volume down). It will find the file and start the update. Just follow the instructions...
It will wipe your phone, though"
Than with the zip on the sdcard i started fastboot and adb on my computer, i entered the command "fastboot oem lock", the message "Unlocked" and Security Warning" appeared, than i pressed the On/Off button, it changed to bottloadermodus, and voila, it was eating the zip!
Only this zip was good enough, the other zips was not running, not the europe version and not the english orange version. But with the spanish version ist was ok. But only with the extracted Rom.zip. When i started the Ruu.zip it stops the update Process after some %. But the Rom.zip from the same ruu works without bad messages.
Now i have a clean firmware on y desire 820n 51 ul.
The languages in this version are: Deutsch, English, Español, Francais, Portugues.
Oel said:
Do you have the OTA uploaded ?
Today it was possible for me to install the orange version spain from the ruu.zip what i mentioned to you!
I was following this tut:
"You can extract the ROM.zip from any RUU to install via ZIP
Start the RUU and once at the first main screen click Start>Run and type
%temp%
now, find the newest folder and in there will be a ZIP file called Rom.zip - copy this to your desktop and rename it to OPFJIMG.zip Now copy this to your SD card and start the phone in HBOOT (turn it on whilst holding volume down). It will find the file and start the update. Just follow the instructions...
It will wipe your phone, though"
Than with the zip on the sdcard i started fastboot and adb on my computer, i entered the command "fastboot oem lock", the message "Unlocked" and Security Warning" appeared, than i pressed the On/Off button, it changed to bottloadermodus, and voila, it was eating the zip!
Only this zip was good enough, the other zips was not running, not the europe version and not the english orange version. But with the spanish version ist was ok. But only with the extracted Rom.zip. When i started the Ruu.zip it stops the update Process after some %. But the Rom.zip from the same ruu works without bad messages.
Now i have a clean firmware on y desire 820n 51 ul.
The languages in this version are: Deutsch, English, Español, Francais, Portugues.
Click to expand...
Click to collapse
Here is link to uploaded OTA: http://forum.xda-developers.com/des...ta-d820n-single-sim-a51ull50-europe2-t3226897
I'm getting this error, after hboot detects 0PFJIMG.zip: Device halted due to Large Image update fail, and my bootloader is relocked.
Did you flash this onto OS-2.10.401.2??
It looks like i have to wait for lollipop RUU and/or for S-OFF possibility.... am I correct?
Maybe i can try flash separate partition dumps from FW 1.29 (radio, rcdata, etc...)?
cr3h said:
It looks like i have to wait for lollipop RUU and/or for S-OFF possibility.... am I correct?
Maybe i can try flash separate partition dumps from FW 1.29 (radio, rcdata, etc...)?
Click to expand...
Click to collapse
S-OFF would solve the problem, because you can flash (upgrade and downgrade) than every os-version for the desire 820.
Of cource, you can try to flash dumps from 1.29 if this was your original firmware. Maybe it works.
Oel said:
S-OFF would solve the problem, because you can flash (upgrade and downgrade) than every os-version for the desire 820.
Of cource, you can try to flash dumps from 1.29 if this was your original firmware. Maybe it works.
Click to expand...
Click to collapse
If i only have these dumps... :crying:
cr3h said:
Hello,
i have single sim d820 (europe)
Code:
***************************
Software status: Modified
A51_UL PVT SHIP S-ON
hboot-3.19.0.0000
radio-01.01.010_U10305041_08.01.50512
os-2.10.401.2
***************************
Before i messed it up it was unlocked and rooted and S-ON, then i wanted to install OTA and i flashed firmware.zip extracted from OTA zip file (bad idea). Now i'm unable to get my phone working...
What i can do:
-enter bootloader
-fastboot commands
-enter recovery
What I've tried and didn't work:
-flash stock recovery, lock, flash RUUk44.zip via fastboot (signature verify fail)
-flash stock recovery, lock, flash lollipop OTA (signature verify fail)
-flash TWRP, restore k44 backup (bootloop after reboot from recovery)
The question is, if I would somehow obtain firmware from k44 stock, is it possible to downgrade on S-ON using "fastboot flash zip" and then restore backup or flash RUU?
I cannot find magical RUU.exe for this model there are only zip files...
Guys maybe someone can dump kitkat firmware i would be grateful...
I appreciate any idea, please help me solve it
Click to expand...
Click to collapse
Hello. Did you managed to fix your phone? I have exactly the same problem as you. I don't know how to fix it ;d
Hello. Did you managed to fix your phone? I have exactly the same problem as you. I don't know how to fix it ;d
Click to expand...
Click to collapse
No, i did not.
I think there are 2 maybe 3 options:
- Wait for s-off (or pay for it now), then downgrade
- Wait for lollipop RUU for our current firmware
- Try to flash twrp backup of someone's lollipop - but im not sure if twrp works on llpop already, does it?
- Maybe try to flash firmware partitions separately, dumped from someone's d820n, but i don't know if it's even possible to reflash device that way. This can also be a last step to totally brick
I made s-off and cid-11111111 also flash with ( RUU_A51_UL_K44_DESIRE_SENSE60_Orange_ES_1.28.75.2_Radio_01.01.010_U10305041_08.01.41222_2_release_421565_signed 0
this ruu.Flash successful but still hang on logo and restart.
hello, can you share the Orange_es .zip file?
cr3h said:
Hello,
i have single sim d820 (europe)
Code:
***************************
Software status: Modified
A51_UL PVT SHIP S-ON
hboot-3.19.0.0000
radio-01.01.010_U10305041_08.01.50512
os-2.10.401.2
***************************
Before i messed it up it was unlocked and rooted and S-ON, then i wanted to install OTA and i flashed firmware.zip extracted from OTA zip file (bad idea). Now i'm unable to get my phone working...
What i can do:
-enter bootloader
-fastboot commands
-enter recovery
What I've tried and didn't work:
-flash stock recovery, lock, flash RUUk44.zip via fastboot (signature verify fail)
-flash stock recovery, lock, flash lollipop OTA (signature verify fail)
-flash TWRP, restore k44 backup (bootloop after reboot from recovery)
The question is, if I would somehow obtain firmware from k44 stock, is it possible to downgrade on S-ON using "fastboot flash zip" and then restore backup or flash RUU?
I cannot find magical RUU.exe for this model there are only zip files...
Guys maybe someone can dump kitkat firmware i would be grateful...
I appreciate any idea, please help me solve it
Click to expand...
Click to collapse
http://forum.xda-developers.com/des...hip-s-hboot-3-19-0-0000-t3508017#post69879100
So i am s-offed with superCID
a couple of days ago, i flashed the developer edition RUU and relocked my bootloader.. so no my device was complete stock, no root and a relocked bootloader
After that i checked and MM update was available, downloaded, installed and during installation, at around 25%, this error occured (detailed below)
reflashed RUU, ran all the play store updates, created an adb backup and then downloaded the update, and once again it happened. I can reflash the ruu and restore the adb backup, but can anyone tell me why does this error occur and how do i avoid it?
Here is the error description:
Stock recovery opens up
installing update
M60QCT.01.002.018
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: device or resource busy
verifying current system
"/system/app/KidMode-google/KidMode-google.apk" has unexpected contents.
E:Error in /data/data/com.android.providers.downloads/app_fota/OTA_m8_ul_m60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4-4.17.1540.9_release_460124.zip
(Status 7)
Installation aborted.
OTA failed! please power off the device to keep it in this state and file a bug report!
P.S: During update, the firmware flash was successful, the error occured while system was being updated
Why do you relocked bootloader ? Not needed when you have a S-Off device.
Which RUU ? Is it a RUU zip and not RUU exe ? If it is RUU zip then you may have a non-stock KidMode-google.apk in the zip. I read many people have same problem with one particular decrypted RUU zip which is not officially from HTC.
Try with official 4.17.1540.9 RUU exe download from HTC - http://www.htc.com/us/support/rom-downloads.html
ckpv5 said:
Why do you relocked bootloader ? Not needed when you have a S-Off device.
Which RUU ? Is it a RUU zip and not RUU exe ? If it is RUU zip then you may have a non-stock KidMode-google.apk in the zip. I read many people have same problem with one particular decrypted RUU zip which is not officially from HTC.
Try with official 4.17.1540.9 RUU exe download from HTC - http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
i just relocked for no reason.. and yes it was an ruu zip so that seems to be a problem.. i will try the ruu exe
thanks a lot
Edit: yes my RUU zip is the decrypted one so pretty sure that is the problem