Database Info

How to flash back to original RC29? I've flash back my recovery and boot image

How to flash back to signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip?
I've flashed my mtd1 and mtd2 which I backed up before I apply the modified recovery.img.
But when I do the reboot and update, It said:
"E: No signature (376 files)"
"E: Verification failed"
It seems I dont get my images flashed correctly, be I'm sure the boot image was flashed..

fluke.l said:
How to flash back to signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip?
I've flashed my mtd1 and mtd2 which I backed up before I apply the modified recovery.img.
But when I do the reboot and update, It said:
"E: No signature (376 files)"
"E: Verification failed"
It seems I dont get my images flashed correctly, be I'm sure the boot image was flashed..
Click to expand...
Click to collapse
I'm assuming you have the modified recovery.img installed. Run SignApk.jar on the signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip. Rename it to update.zip and put it on the sdcard (taking care to unmount the usb mass storage before unplugging). Boot into recovery menu (Home+Red) and Alt+S to flash. When it's done press Home+Back as prompted. That should do it.

Isn't the official RC29 update.zip signed with google's private key?
How could I sign it?
I'm just recovered to the offcial boot.img and recovery.img, which were backed up by myself from mtd1 and mtd2.

The way signing works with java archives is rather than encrypting the files themselves, the signing process simply adds a list of filehashes encrypted with the priv key. Resigning simply overwrites this list with your own (in this case the test private keys).
If you want to install with the original stock ota update then flash the original recovery.img (you can extract it from the stock ota update).

jashsu said:
The way signing works with java archives is rather than encrypting the files themselves, the signing process simply adds a list of filehashes encrypted with the priv key. Resigning simply overwrites this list with your own (in this case the test private keys).
If you want to install with the original stock ota update then flash the original recovery.img (you can extract it from the stock ota update).
Click to expand...
Click to collapse
Thanks. I got it.
I'll do this soon.
I've failed with log into google account many times with the unofficial update package.
Everytime when I finished log in, the com.google.setupwizard throws exception.

Right I have the modified RC30 and the modded recovery & boot image.
I'm going to return my G1 for a new one but before i do, i need to flash it back so it can install the OTA updates. (Phone keep shutting off when i close my screen) I want to make sure what I'm going to do is correct so i don't brick my phone.
Download the RC29 patch and extract the recovery & boot img.
Flash the images into the phone.
Is this correct ?
Thanks for the help

You don't need to reflash recovery or boot. Use SignApk.jar on the official RC29 or RC30 and put it in the root of memcard. Reboot and flash. Should be official. You have to sign it with test keys or the modified recovery will reject it.

jashsu said:
You don't need to reflash recovery or boot. Use SignApk.jar on the official RC29 or RC30 and put it in the root of memcard. Reboot and flash. Should be official. You have to sign it with test keys or the modified recovery will reject it.
Click to expand...
Click to collapse
Alright thanks a lot.

Signature error for ADP1

I am now on JF1.3 on my ADP1. I tried to flash this 'leaked' image:-
http://andblogs.net/2009/01/new-adp1-images-leaked/
I renamed the file as update.zip and reboot with Power+Home. Then did the ALT+W and ALT+S.
The Flashing failed because of errors in Signature(5 files). I tried the following to remedy:-
1) Reformatted the card
2) Renamed the Update.zip to 'Update'
Even after these I am keeping on getting the Signature errors. Please help solve this issue. Thanks.
* I tried to install Cupcake and it works. Though returned to jf1.3 because of the radio issues.

vinodis said:
I am now on JF1.3 on my ADP1. I tried to flash this 'leaked' image:-
http://andblogs.net/2009/01/new-adp1-images-leaked/
I renamed the file as update.zip and reboot with Power+Home. Then did the ALT+W and ALT+S.
The Flashing failed because of errors in Signature(5 files). I tried the following to remedy:-
1) Reformatted the card
2) Renamed the Update.zip to 'Update'
Even after these I am keeping on getting the Signature errors. Please help solve this issue. Thanks.
* I tried to install Cupcake and it works. Though returned to jf1.3 because of the radio issues.
Click to expand...
Click to collapse
You have to use fastboot as this is not an update.zip.
You can either flash each img or you can try out the full system update...
Code:
fastboot update update.zip
I have *not* tried this approach yet but it is documented so I assume it works?
Also, you will notice that there is no misc partition; you can ignore that error and flash the rest (skip splash1/splash2 if you already have custom splash screens).
Added nice-ities:
-The ability to skip signing-in to your google account
-System updater
-...it's new?

Thank you !. Fastboot worked.

Problems re-flashing recovery

Happy Easter to everybody!
Since a couple of days (when I tried several times to install WLegend 0.3), when I go to recovery and try to wipe dalvik-cache, i get an error message saying
Code:
run "wipe dalvik" via adb
I would like to overcome the problem reflashing the rav 1.5.2 on my magic, but when I try to do it via adb, the following message appears:
Code:
mtd: read error at 0x00020000 (Out of memory)
Can someone help me re-flashing the recovery?
Many thanks!!!

no one who wants to help me?

i've read somewhere that that error message that you get is bug in recovery and although it said that it didn't erased dalvik, it did.
so actually...you can flash your new rom without reflashing recovery or what so ever...

ya its a bug in the 1.5.2 recovery, upgrade to the latest 1.6 something
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk

digitaljeff said:
ya its a bug in the 1.5.2 recovery, upgrade to the latest 1.6 something
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
The strange thing is that it started not immediatly, but after some correct wipes

Here is what I obtain trying to re-flah the recovery...
Code:
Microsoft Windows [Versione 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Tutti i diritti riservati.
D:\sdk\tools>
D:\sdk\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ # flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
header is the same, not flashing recovery
/ #
D:\sdk\tools>fastboot devices
HT95PKF06370 fastboot
D:\sdk\tools>fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\sdk\tools>
The first time I flashed the custom recovery, all this sh!t didn't appeared!

I used flashrec and it worked like a charm. Anyway, why are you trying fo flash an old version of the recovery? Use the latest for your Magic (I'm guessing it's a 32A, since you're using the H recovery image), but be sure to verify the md5 checksum before.

A nice thing I did to quickly get my RA image back was save it to my SD, rename it to "recovery-backup", open up flashrec, and click "restore backup". That will flash your Amun RI, because the flashrec recognizes it as teh backup image because that what it saves the original image as.

keinengel said:
I used flashrec and it worked like a charm. Anyway, why are you trying fo flash an old version of the recovery? Use the latest for your Magic (I'm guessing it's a 32A, since you're using the H recovery image), but be sure to verify the md5 checksum before.
Click to expand...
Click to collapse
I'm trying to understand if the errors I get are due to the fact that I re-flash the same recovery or to some other problems...
knny1491 said:
A nice thing I did to quickly get my RA image back was save it to my SD, rename it to "recovery-backup", open up flashrec, and click "restore backup". That will flash your Amun RI, because the flashrec recognizes it as teh backup image because that what it saves the original image as.
Click to expand...
Click to collapse
Thanks, I'll try flashrec

/ # flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
header is the same, not flashing recovery
/ #
Click to expand...
Click to collapse
Means that you already have the recovery that you are trying to flash...
D:\sdk\tools>fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
Means you dont have an engineering SPL.
P.S i suggest you use ROM manager from the market, it can flash a nice Clockwork recovery or amon_ra 1.6.2

Which MAgic do you have? a new 32a with 3.5mm headphone jack?
Also your erros just mean
1. Your flashing an older recovery then you have (or same)
2. your SPL is not "unlocked"
If you have a new mytouch 1.2 or fender you must use 1.6.2H
Also, you can do all this in terminal or buy putting the recovery ont he sd card and using adb shell.
But get a new recovery, your main problem is your using the one with taht exact known problem which is why it was updated.

Thank you all for the responses!
@ eyegor: if I understand, it is not possible to flash the same recovery (eg 1.5.2 on 1.5.2), am I right?
I don't need an engineering SPL in order to flash new roms, right?
@ crypysmoker: I have a standard 32A magic (no 3.5mm jack)

It is but not from terminal.
No, you do not.

I did the update to 1.6.2, now it's all ok! no errors updating, no errors wiping...
Thank you all for the support!

[Q] How To Modify default.prop?

Hello Everyone,
Thank you in advance for any help on this item.
I have an HTC Sensation phone which is already S-off and has CWM in it.
It also has "su" previleges in it and I was able to modify CID too.
The ROM inside it is stock ROM.
I have been reading and following several guides on how to modify default.prop for other devices. And from what I gather I have to do the following :
1. Unpack boot.img.
2. Modify default.prop.
3. And repack boot.img.
The problem here is that I tried all sorts of things only to end up failing in the "repacking" stage.
I want to modify default.prop to be able to set adb daemon (adbd) to have root previleges and eventually be able to "inject" into HTC sensation my own custom-made versions of framework.jar and other files.
Is modifying default.prop possible?
Is the method I am using correct?
Is it possible to have my own customized framework.jar inside the HTC Sensation?
I hope you guys can point me to some sites and links which can help me in what I intend to do.
Thank you all very much.

Use dsixda kitchen.

Hello Sebastian,
Thanks for your response.
I also tried to use the dsixda kitchen.
What I did was :
1. Downloaded a backup of my phone using ClockworkMod Recovery.
2. I took the boot.img file from the backup generated.
3. Unpacked boot.img using the kitchen.
4. And then repacked it using the kitchen again.
5. I then flashed the generated boot.img into the phone.
6. The phone went into a forever loop in the start up screen.
Did I do it right?
I am rechecking the notes on the kitchen again though. I might have missed something.
Thanks again.

Upload your boot.img, I'll check it. Do you use fastboot.exe to flash boot?

Hello Again,
Thanks once again for the support Sebastian.
"Upload your boot.img, I'll check it. Do you use fastboot.exe to flash boot?"
I use fastboot.exe first and then try to use the ClockworkMod Recovery Advanced option to update the "boot" only part.
I am attaching here my dsixda-kitchen generated boot.img.
This boot .img was generated with the following steps :
1. Unpack htc stock rom boot.img generated by CWM nandroid backup.
2. No changes were made in the ramdisk nor in the kernel part.
3. Repack the ramdisk and kernel using dsixda kitchen.
4. Used fastboot.exe to flash the boot part. "fastboot flash boot boot.img"
5. Wiped the cache partition of the phone.
6. Wiped the /data/dalvik-cache directory.
7. Restarted phone in normal mode.
8. Phone hanged up in startup image.
Many thanks again and more power.

Error on OTA [EMUI 3.1 6.1.1]

Hello,
I am trying to update my H60-L12 from 6.1.1 to 6.1.16 (and then beyond) using OTA.
I have my phone rooted and with custom recovery. I know I have to unroot and restore stock recovery to get the OTA updates. Yesterday I learnt also that to get 6.1.16 I have to use TAPVPN to connect to the internet via Singapore (thanks to @bcostea for the hint).
Now I find that my phone downloads the update and when it tries to install there is an error in the process at the 6%.
I learnt that the update process logs its progress in the file /splash2/recovery_log
There I find this:
Code:
UI percent:5%.
file "/system/framework/com.google.widevine.software.drm.jar" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/framework/com.google.widevine.software.drm.jar", "6189c99c76c84310f35b967e768440088e140f78", "7b4afc644b4d388fe159120f434f769a635a8c5e")
str1:/system/framework/com.google.widevine.software.drm.jar, str2:6189c99c76c84310f35b967e768440088e140f78
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=231: err_no = 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=233: push binary errno 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=238: assert info: assert_filename:/system/framework/com.google.widevine.software.drm.jar
E:assert failed: apply_patch_check(E:
It seems that my com.google.widevine.software.drm.jar is not the one expected by the process.
That makes some sense, as after I installed the full stock rom, I was not able to apply the pa_gapps (some error related to not being possible to install them in a system that did not had a previous version installed to avoid conflicts) (more details on this are available if anybody has a hint or is willing to trobuleshoot it).
Thing is that I applied open_gapps, which are working just fine, but seem to have a different com.google.widevine.software.drm.jar version.
Till 6.1.1, I was able to replace the com.google.widevine.software.drm.jar file in my phone with one from the system.img of the Stock ROM, and then the update was working.
With 6.1.1 I have not been able to find the right file (one with a SHA-1 hash of 7b4afc644b4d388fe159120f434f769a635a8c5e, seems to be necessary).
I have 3 files with hashes:
6189c99c76c84310f35b967e768440088e140f78
654d36de1c8e9e84979a67e897f36dc17a6f7565
bb6bfd30b3d6d03ecf9531e37bcdb0b5a8123e11
They come from stock, from pa_gapps and from open_gapps, but none of them work.
I put them in the \system\framework folder, but the update still fails with the same error.
Can anyone give me a hint? I am going to try by deleting the file, as I have seen that in the log there is one that is not found and the process does not complain that much.
Maybe someone has the right file in this phone and can send it to me. That would be great!!
Thanks in advance!

Well, it seems I managed to make it work.
Instructions below are without warranty. You know that. It's your phone, if you break it, it's your fault. Not mine. You acknowledge that.
Here is how I did it (if you don't know how to execute any of the steps, just google. Instructions have been provided a million times on how to boot in recovery, how to flash an image or how to do a full backup from custom recovery...):
1. I downloaded the full image of the release I had in my phone (I.e. 6.1.1)
2. Using Huawey Upgrade Extractor I extracted system.img and recovery.img
3. I restarted into custom recovery (TWRP) and took a full backup of my phone to the SD. I then removed the SD.
4. I restarted in fastboot mode and using fastboot.exe I flashed recovery.img and system.img (in my case that did not remove anything from my phone, but as I said before, I took a backup beforehand, just in case).
5. I rebooted the phone. Everything was working just fine.
6. I used TAPVPN app to connect through Singapore, so I could get the update to 6.1.16.
7. The update downloaded and installed as expected.
8. Then I used again TAPVPN to get 6.2.1.
9. Same result: download and installation as expected.
10. Then I rooted again and installed custom recovery by using Honor Multi-Tool.
I hope this helps.