Database Users

How to create a update.zip???

Hi im interessted in. How can i flash a rom via the update.zip file??
I have a goldcard, so i can flash every update.zip i want.
Can i just rename the (for example) ''FroyoRider_FeeyoCM61_6.35_34_v2.1.zip'' to update.zip and flash via recovery?

Yes you can and if you've got a custom recovery you don't need the Goldcard to do it. Most recoveries though will recognize the .zip with any filename so you won't need to rename it.

.. yes i know the other method... but i have never found a method to restore the orginal recovery, so i want to keep it.
but the phone dont accept my goldcard or the file... the recovery said. the file isnt signed.

Ahh... good question :0)
You need to know a little about cryptography.
You sign things using cryptography. You can also encrypt things using cryptography. When encrypting, the content get changed to something only the intended receiver can read. When you sign things, the content can be read by everybody. You use the signing to verify that what you read has not been tampered with and actually is from you. So if someone "changes" anything in a signed file, cryptography will guaranty that you will discover that. If anybody else is imposing you, cryptography will show that he/she is fake. How does cryptography work then? This can be done using many methods, but here is what android uses (or a simplified version).
Cryptography is done using 2 distinct keys, public and private keys. Public key is what you "give" to everybody you want to communicate with. Private key is yours, and ONLY yours. If i sign an object with my private keys, then all can verify that this is object is from me by using my public key to check the signature. If you sign an object with the public key, then i can check using my private key, that the object is to me and only me.
So when HTC or who ever makes an update, they sign their software/updates with the private key. The device, here a magic, has the public key and can check the signature and verify that the update is from HTC and nobody else. It can also check if you have changed anything at all. If the update has been tampered with or is not from HTC, then the device will reject the software/update. Simple but effective.
Recovery:
The stock recovery will only accept signed updates by HTC. The custom recovery will accept signed updates, which are signed using google test key, which is freely available. (i'm not sure if it's google or somebody else, but you get the point). Clockwork recovery has an option to disable signature check to let you load any zip-file/update you want. The idea of signing the update.zip/rom.zip is to make sure that who ever made it, knows what he/she is doing. If you e.g. load a rom.zip which fails the signature check, then you know 1 of 2 things:
1) the person did not signed it
or
2) the file has been tampered with since it last was signed.
So if you want to load a file which fails the signature check, then you must re-sign it or disable signature check. But i will investigate WHY is the file failing before i re-sign it and load it.
The goldcard will not help here, since the only purpose it has is to allow you to flash an sapphire.zip which is NOT meant for your device id. It will not magically allow you to run code which is not signed.
Even in fastboot or ruu mode. The sapphire.zip is been checked for signature to make sure it's from HTC and has not been tampered with.
So, NO you cannot take FroyoRider_FeeyoCM61_6.35_34_v2.1.zip and rename it update.zip and try to load it using stock recovery. Unless you sign the files with HTC private keys, which make you a very powerful man and i would like you to contact me :0)
I hope i have shaded some light to your question!
ps: Some of the OLD guides will have you to rename the files like the "FroyoRider_FeeyoCM61_6.35_34_v2.1.zip" to "update.zip" and load it from custom recovery. That's because in the past custom recoveries did not have a "flash zip file" option which will let you choose any file ending with .zip!
That's is what DonJuan692006 is referring to.

Thanks a lot. This is an answer!

mumilover said:
The goldcard will not help here, since the only purpose it has is to allow you to flash an sapphire.zip which is NOT meant for your device id. It will not magically allow you to run code which is not signed.
Even in fastboot or ruu mode. The sapphire.zip is been checked for signature to make sure it's from HTC and has not been tampered with.
Click to expand...
Click to collapse
Let me ask you about the goldcard now: I have a HTC Magic here which currently has an incorrect SPL and radio combo due to a failed official update from HTC Brazil (SPL 1.76.0010 and Radio 3.22.20.17, SAPPHIRE PVT 32A SHIP S-ON H)
I've found in another thread in the xda-developers forums a SAPPIMG.ZIP built by Rogers Canada for their Magics. Looking inside the zip, the android-info.txt file says it's meant for a SAPP50000 model. But my Magic has the model ID SAPP60000... then, when I try to flash it to my phone (using Fastboot commander ), it rejects the file.
I've created a goldcard using another Magic (identical but working OK) that I have here. The messages I get when trying to flash the Rogers zip are these below:
###Calling fastboot with: flash zip C:\android\SAPPIMG_Sapphire_Rogers_WWE_3.54.631.3_R_Radio_63.18.55.06Q_6.35.16.19_release_144134_signed.zip###
sending 'zip' (110447 KB)... OKAY [ 19.522s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.576s
The signature error is due to the differences between the model ID of the file and my phone, or have my zip file been modified since signed by Rogers?
Thanks a lot!

yurifranzoni said:
(SPL 1.76.0010 and Radio 3.22.20.17, SAPPHIRE PVT 32A SHIP S-ON H)
###Calling fastboot with: flash zip C:\android\SAPPIMG_Sapphire_Rogers_WWE_3.54.631.3_R_Radio_63.18.55.06Q_6.35.16.19_release_144134_signed.zip###
sending 'zip' (110447 KB)... OKAY [ 19.522s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.576s
Click to expand...
Click to collapse
You need to rename it as sappimg.zip (not sappimg.zip.zip) and flash it from hboot mode. It's only there the goldcard will take effect...
But sadly, there is a BIG chance this will fail.
The spl has different partition layout which will make the flash of the radio fail!
What you have to do is to match the spl with the radio, then flash a new spl/radio combo.
In your situation, that's gona be hard... you have perfected spl! Plus any update will start with the radio which is likely to fail....
In other words, you kinda fu*ked.

mumilover said:
You need to rename it as sappimg.zip (not sappimg.zip.zip) and flash it from hboot mode. It's only there the goldcard will take effect...
But sadly, there is a BIG chance this will fail.
The spl has different partition layout which will make the flash of the radio fail!
What you have to do is to match the spl with the radio, then flash a new spl/radio combo.
In your situation, that's gona be hard... you have perfected spl! Plus any update will start with the radio which is likely to fail....
In other words, you kinda fu*ked.
Click to expand...
Click to collapse
mumilover, I've renamed it to sappimg.zip and this is the result:
###Calling fastboot with: flash zip C:\android\SAPPIMG.zip###
sending 'zip' (110447 KB)... OKAY [ 19.516s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.567s
I've tried flashing it through Fastboot commander (which is the same thing than typing the commands in the DOS prompt, right?). I expected that it would not work, because, well, I've tried nearly everything I found here in the forums
I'm still trying to find a RUU or HTC signed zip that contains the 1.33 SPL, so it would match the 3.22 radio. Does anyone know where to find something like this? Updating my radio do 6.35 is not an option...
I've reached this situation because of a ****ed brazilian official HTC update to Android 2.1. Before I tried to install it, my phone had CyanogenMod 6.1, with SPL 1.33 and radio 3.22. My mistake was to apply the update directly to the phone, without flashing the new SPL/Radio BEFORE.
During the update, it updated the SPL to the new 1.76 version, but when it starts to update the radio to version 6.35.xx, the phone screen becomes blank, then goes slowly white. I've tried that many and many times, still the same result.
I've tried applying the latest Rogers RUU (available for download in shipped-roms.com), which has similar SPL and Radio versions than the brazilian update, but no luck: even with the goldcard inserted, when it reaches the radio flash phase, the screen blanks again
Is there anything that could be done before sending my brick to service? They are replacing the logic board of every phone they receive in this situation - believe me, they have received many of them... I know a bunch of people that made the very same mistake as I did.
Thanks!!!

Again... as i wrote earlier, this has to done in hboot mode (volume - & power) with a goldcard.
You CANNOT do this with fastboot commands!
And yaa, i told you that you were screwed. Very bad combo which seriously messes with the your ability to fix it.

Right... my mistake, I forgot to mention that my brick does not boot in hboot mode anymore. It keeps stuck at the RUU USB screen, with the icon of the microchip and the red cross sign at the bottom.
Worse, it does not have the custom recovery anymore, so I'm not able to go there and do a "flash zip from sdcard".
Finally, if I try to do a "fastboot boot recovery.img", using any custom recovery image, what I get is a eternal "booting..." message, and the phone does not load the custom recovery image.
Any other ideas?
Thanks again!

GOOD NEWS!!
I've managed to FINALLY make it boot the system! I don't know why, but I tried the following and it restarted in CM 6.1 (the ROM installed before I tried to apply the official update):
- with the phone turned on, connected via USB and froze at the RUU USB screen, type the following in a command prompt:
fastboot oem boot
It will display a lot of data and then the PC screen will show FAILED (status read failed (Too many links))
- Then, I typed:
fastboot boot recovery-RA-sapphire-v1.7.0H.img
It told me "(waiting for device)". I left it there....
- Then, I fired up the Radio Switcher app and chose the "Shutdown device" option. My idea was to turn the brick off to try anything else...
BUT it took about 20 seconds and RESTARTED, then the CM logo shown up... and some seconds later it was RUNNING CM 6.1 again! Like it was before I tried to update!
I still can't reboot into recovery to flash the right SPL version, but that's a chance of success, isn't it? It still has the bad SPL/radio combo, but at least, it's starting!
How can I flash the right SPL into the phone WITHOUT restarting into fastboot or recovery? Is it possible?
Thanks!

ZTE Open constantly restarts

Hi:
I did root my phone, and I installed ClockwordMOD following the steps in this website:
pof [dot] eslack [dot] org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
This I did from 1.0.0B02 version can be downloaded from ZTE page. Later, I installed another ROM I downloaded from ZTE page, in this case, a ROM TME Spain.
With this version I started to have problems, so I tried to return to the previous version using the Recovery and could not. I was wrong.
Nor could re-root the phone, so I could not install CWM.
Fastboot not working, because when I was trying to make something out this error:
fastboot flash recovery recovery-clockwork-6.0.3.3-
roamer2.img
sending 'recovery' (5712 KB) ...
OKAY [0.487s]
writing 'recovery' ...
FAILED (status read failed (No such device))
finished. Total time: 5.824s
Unable to use fastboot or ADB, I had only the option of using the update.zip offering this site:
firefox [dot] ztems [dot] com
After updating correctly, restarting the phone everything seemed normal, but not passed the animated fox, and restarted again.
With version 1.1 installed FirefoxOS, the phone started to have problems.
Sometimes when unblocked the screen to put the code, pressing the numbers and did not write anything. I had to repeatedly press the power button for it to work.
The same was true at times when trying to access the applications. The touch did not work well at all or sometimes it was deemed.
Now when I try to update using any ROM from Recovery (which incidentally now says Android Recovery), I get the error:
E: failed to Verify whole-file signature
:crying:

elav said:
Hi:
E: failed to Verify whole-file signature
:crying:
Click to expand...
Click to collapse
Apply this update from your stock(android) recovery. It'll work!
update_signed.zip

LinuxHolic said:
Apply this update from your stock(android) recovery. It'll work!
Click to expand...
Click to collapse
Thanks. I try!!

[Q] Definitely [Bricked] Maybe

Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks

scari said:
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
Click to expand...
Click to collapse
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.

foxob said:
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
Click to expand...
Click to collapse
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you

scari said:
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
Click to expand...
Click to collapse
so this doesn't work? too bad. that has helped me save my zte open a few times.

foxob said:
so this doesn't work? too bad. that has helped me save my zte open a few times.
Click to expand...
Click to collapse
no, that method doesn't work definitely...
:crying:

are you able to get into fastboot?

hecatae said:
are you able to get into fastboot?
Click to expand...
Click to collapse
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).

scari said:
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
Click to expand...
Click to collapse
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.

Arrowblue said:
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Click to expand...
Click to collapse
when I flash the phone with windows this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
and when I try to flash with ADB under Mac Os this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
and I try to flash the original boot image and the modified one,
but without success...

Looking for HTC Desire 820n Stock MM ROM Single sim

Hello Guys. I looking for Looking for HTC Desire 820n Stock Marshmallow ROM. I downloaded one from this forum, but it doesn't work, dunno why. Could you help me?
A51_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.50512
OS-2.10.401.4
eMMC-boot 2048 OC
TWRP ver. 2.8
Already I using Tomal's Discovery v2.00
Thx for help.

Hello!
Here it is:
https://mega.nz/#!h1ghSaBA!gE3Sfsfcebdk0tyStLe5VFhYOfUia0gcvLkiV2zShRE
But i recommend you to do OTA update to Marshmallow
If you want to do that:
1) Download Stock Recovery: https://mega.nz/#!UkJRGKRB!nAPzWOobSYsVxTTrF5e0xtZVIL-5Mxh6nrVW84B-dVo
2) Download Lollipop RUU: https://mega.nz/#!F9QVgIZD!QopXqw1IPYhoo540nJn77vzJIanIanSeM6APMaoc1vc
3) Lock bootloader
4) Place Lollipop RUU to SD Card and rename file to 0PFJIMG.zip
5) Do OTA Update to Marshmallow
Cheers!

Ty so much man, I'll check this soon

Could you tell me two things: How to lock bootloader and how can I install stock recovery? Sorry for my knowledge ;__;

To install stock recovery:
1) Reboot to bootloader (Turn off phone, then press volume down and Power Button)
2)Click "Fastboot" (Just press Power Button)
3)Connect phone to PC
4)Install ADB 15 seconds installer (Google It! ?)
5)After instalation go to C:/ADB folder then press shift and right mouse Button then click "Open Command prompt)
6)Download stock recovery image (from #1 post)
7)Place it to C:/ADB folder
8)In command prompt type "Fastboot flash recovery (filename)"
To lock bootloader:
1)After installing stock recovery type In Command prompt: "Fastboot oem lock"
Cheers!

I've got sth like this after I typed a command in cmd:
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 7758080 is not a multiple of the block size 4096
sending sparse 'recovery' (14703 KB)...
error: write_sparse_skip_chunk: don't care size 7758080 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7758080 is not a multiple of the block size 4096
OKAY [ 1.694s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.704s

This is fixed ADB for this device: https://yadi.sk/d/v5Yp8iAtuHdQE
Download and replace all files In C:/ADB folder
And try again!

Thanks man for help! But this is something like hydra head- one problem solved, and we gain two new problems. Now rebooting phone to ROM is not available, stucked on bootloader. However, when I try to go into recovery i have this:http://obrazki.elektroda.pl/6530102200_1432399738.jpg

To enter stock recovery launch It then press Power and volume up Button
P.s are you from Poland?

Do you mean to click "Recovery" in bootloader and next hold vol up and power button? Doesnt working, still this same image ;/
Yes, I'm from Poland

Just keep pressing buttons randomly
######
Ja też jestem z Polski

Priv then
________
Masz piwo u mnie

HI, would you please give new links to the same files, these are dead already - my phone got bricked after system update tried. (it was rooted, but no more) - there is no OS now : ) it`s exactly the same model as the one metnioned above. It will be much appreciated, really!

Hello. Pleaze i née thé ruu for htc desire 820n. Thanks

Could someone throw again mega.co files as expired?

Hello!
MEGA has removed my files (don't know why)
Stock recovery: https://yadi.sk/d/v5Yp8iAtuHdQE
Lollipop RUU: https://yadi.sk/d/KYcWwUH4raUxm
Marshmallow RUU: https://yadi.sk/d/lWwMzPdNuHc3X
Cheers!

I started uploading 0PFJIMG.zip, after a while the phone is switched off and started flashing orange LED. The phone was connected to the computer. After disconnecting the phone can not start. Once reconnected to the computer is still flashing orange flashes. What should I do? Key combinations do not work

Fr4gMovi3 said:
To install stock recovery:
1) Reboot to bootloader (Turn off phone, then press volume down and Power Button)
2)Click "Fastboot" (Just press Power Button)
3)Connect phone to PC
4)Install ADB 15 seconds installer (Google It! ��)
5)After instalation go to C:/ADB folder then press shift and right mouse Button then click "Open Command prompt)
6)Download stock recovery image (from #1 post)
7)Place it to C:/ADB folder
8)In command prompt type "Fastboot flash recovery (filename)"
To lock bootloader:
1)After installing stock recovery type In Command prompt: "Fastboot oem lock"
Cheers!
Click to expand...
Click to collapse
my bootloader doesn't lock. how to lock?

domell98 said:
I started uploading 0PFJIMG.zip, after a while the phone is switched off and started flashing orange LED. The phone was connected to the computer. After disconnecting the phone can not start. Once reconnected to the computer is still flashing orange flashes. What should I do? Key combinations do not work
Click to expand...
Click to collapse
I don't know... But you should place this file in sd card... Try launch bootloader and flash TWRP recovery and then push file to SD Card....

HELP!!!!!
i need official stock rom of htc Desire 820n(single sim)...its urgent
A51_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
radio-01.01.010_U10305041_08.01.41222_2
OS-1.29.401.5
eMMC-boot 2048 MB oc

Need help with brick

I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it

Stimayk said:
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Click to expand...
Click to collapse
Try to flash with original miui ROM.

itmasen1 said:
Try to flash with original miui ROM.
Click to expand...
Click to collapse
I tried but no changes are applied

UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?

Stimayk said:
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Click to expand...
Click to collapse
in principle, there is a solution by going through EDL MODE . you have a chance to restore your phone,
do your research on the net about this method.