Extract HDMI update from 1.47.651.1? - EVO 4G Android Development

Calkulin, or anyone else, is it possible to extract the HDMI update from the 1.47.651.1 OTA and apply it to 1.32.651.6? (deodexed of course)

bump. Was thinking it would be in settings.apk, or settingsprovider or htcsettings or something of the sort. Any ideas? Would be awesome to get this HDMI settings/update into our older firmware versions.

Related

Patching OTA_Supersonic_1.32.651.6.zip to PC36IMG.zip

Goal: Load the OTA_Supersonic_1.32.651.6-1.32.651.1_release.zip over the userdebug RUU PC36IMG.zip. Completely HTC stock updated package.
Background:
I'm sure some people will disagree with me. I really want a completely stock approach to staying on the userdebug RUU (official leak) with the official OTA update to .6 software and .05 radio. I'd rather not have to patch in custom ROMs but have a completely stock and updated system with userdebug root access in normal android mode and root access plus /system write access in recovery. Any and all help is appreciated! I'm still new to HTC's flashing/update process!
Current Method:
Flash Toast's PC36IMG.zip
Boots into normal android mode with software 1.32.651.1 and radio .04
HTC Software Update does not detect any available update.
I've patched the build.prop (attached at bottom) to state release-keys instead of test-keys.
reboot recovery - load toast's custom recovery
adb push c:\build.prop /sdcard/build.prop
adb shell
cp /sdcard/build.prop /system/build.prop
Rebooted into normal android mode. This allowed the HTC Software Update to detect the OTA .zip.
It downloads and then verification of the downloaded OTA .zip fails.
Patched with otacerts.zip from stock 1.32.651.1 and verification of OTA .zip passes.
reboot recovery - load toast's custom recovery
adb push c:\otacerts.zip /sdcard/otacerts.zip
adb shell
cp /sdcard/otacerts.zip /etc/security/otacerts.zip
Reboot into normal android mode, run HTC Software Update, downloads and verification passes.
Select apply OTA .zip Now and it reboots. After it reboots and starts to apply the OTA .zip, it doesn't finish and reboots back to normal android mode w/o applying the OTA .zip.
I've gone through the OTA .zip file update-script and the first two commands check the build.prop for two values, which I've double checked exist in the build.prop I patched and applied.
Not sure what else is holding it back from applying the OTA .zip? As far as I can tell, it should be a release build, not a test build. What have I missed?
Thanks for any help!!
Files to Download:
Toast's PC36IMG.zip
OTA_Supersonic_1.32.651.6-1.32.651.1_release.zip
Patched build.prop
Patch otacerts.zip
I'm confused. What will this get you that you don't get from Toast Root > Flash Flipz' 1.32.651.6 and radio?
jmglidden said:
I'm confused. What will this get you that you don't get from Toast Root > Flash Flipz' 1.32.651.6 and radio?
Click to expand...
Click to collapse
OTA contains a total of 56 files which are all system patch files, radio and recovery updates, while flipz ROM 1.31.651.6 contains 978 files with a separate radio update.zip and does not update the recovery with the one from the OTA.
no offense to any of the developers. flipz 1.31.651.6 copies over the whole system directory (978 files) while the OTA only patches 56 specific system files which need to be patched leaving the rest of the system untouched including permissions.
the OTA also updates the radio and recovery while patching the 56 system files all in one clean boot using the stock recovery.
there shouldn't be any issues with 4G or any other system component when using the OTA which might arise from a mass replacement of the /system.
joeykrim said:
OTA contains a total of 56 files which are all system patch files, radio and recovery updates, while flipz ROM 1.31.651.6 contains 978 files with a separate radio update.zip and does not update the recovery with the one from the OTA.
no offense to any of the developers. flipz 1.31.651.6 copies over the whole system directory (978 files) while the OTA only patches 56 specific system files which need to be patched leaving the rest of the system untouched including permissions.
the OTA also updates the radio and recovery while patching the 56 system files all in one clean boot using the stock recovery.
there shouldn't be any issues with 4G or any other system component when using the OTA which might arise from a mass replacement of the /system.
Click to expand...
Click to collapse
YES, exactly what I want.... I mean, it is great to have a full ROM, but why not an option to patch just some things without rewriting ALL the system files?????
dchamero said:
YES, exactly what I want.... I mean, it is great to have a full ROM, but why not an option to patch just some things without rewriting ALL the system files?????
Click to expand...
Click to collapse
appreciate the support! in helping out some other users i discovered the PC36IMG.zip has all /system/app files deodex and the patch assumes users are running the release of software .1 which has many odex files.
i know a deodex system of software .6 is around the corner.
all the /system/app and /system/framework might have to be replaced to deal with the deodex/odex difference between PC36IMG.zip and release build, but that is still a lot less than replacing all 900+ system files.
this project keeps taking twists and turns so i'll keep the thread updated as i make progress!
joeykrim said:
OTA contains a total of 56 files which are all system patch files, radio and recovery updates, while flipz ROM 1.31.651.6 contains 978 files with a separate radio update.zip and does not update the recovery with the one from the OTA.
no offense to any of the developers. flipz 1.31.651.6 copies over the whole system directory (978 files) while the OTA only patches 56 specific system files which need to be patched leaving the rest of the system untouched including permissions.
the OTA also updates the radio and recovery while patching the 56 system files all in one clean boot using the stock recovery.
there shouldn't be any issues with 4G or any other system component when using the OTA which might arise from a mass replacement of the /system.
Click to expand...
Click to collapse
Thanks for the explanation. I'm looking forward to following your progress.
Here is the best I've been able to come up with and appreciate any other feedback or help!
The PC36IMG.zip has all files in /system/app and /system/framework already deodex but they are software version .1 software.
The OTA to .6 software and .05 radio update does three things:
1. updates files in /system to software version .6
2. updates radio to .05 version
3. updates recovery.img
1. The OTA .6 software update portion updates about 50+ files, to .6 software. All the 50+ files it updates except 5 of them are in /system/app and /system/framework but it applies to the odex version of these files. PC36IMG.zip only has the deodex version of these files. I can either manually pull these 50 files after after the OTA .6 is applied to the stock .01 software or use a Deodex version of these already updated .6 files?
2. radio update should be easy to duplicate with an update.zip
3. we aren't able to manually apply this recovery.img from the OTA because we don't have write access to recovery in our PC36IMG.zip. not sure there are any major updates to this anyway?
my goal is to update the PC36IMG.zip by making the bare minimum updates which come with OTA, not modifying or touching any other files outside of the OTA update! what does everybody think?
joeykrim said:
my goal is to update the PC36IMG.zip by making the bare minimum updates which come with OTA, not modifying or touching any other files outside of the OTA update! what does everybody think?
Click to expand...
Click to collapse
I LOVE IT, and I hope you can do it, especially for future OTA updates.... I don't want to flash a new rom every time there is a little update to some system files
Me too!
I only want to fix my SD problems. Not switch to a new ROM.

[Q] Stock Camera apk

Hi,
Im looking for original stock Camera apk. Im on sense 2.1, 2.3.3. I tired downloading different ROMs and extracting their camera apk to see if its the same but they are not. I also tried getting the RUU, extracting the ROM and using unyaffs to open the system.img but its not working for me. If anyone can provide me with the Camera apk I would appreciate it.
Thanks
EDIT: Never-mind I fixed the problem

Need a stock 4.0.4 audio_effects.conf

Hi I'm unable to apply the OTA update from 4.0.4 to 4.1.1 due to a status 7 error on /etc/audio_effects.conf.
I've installed beats audio which seems to be causing the problem, ideally I'd like to remove it and revert the audio to stock but I cant find any information on how to do that, can anybody shed some light on whether its possible to revert beats, if not could somebody provide me with a copy of their audio_effects.conf file from a stock ICS build.
Regards
Burgershot
burgershot said:
Hi I'm unable to apply the OTA update from 4.0.4 to 4.1.1 due to a status 7 error on /etc/audio_effects.conf.
I've installed beats audio which seems to be causing the problem, ideally I'd like to remove it and revert the audio to stock but I cant find any information on how to do that, can anybody shed some light on whether its possible to revert beats, if not could somebody provide me with a copy of their audio_effects.conf file from a stock ICS build.
Regards
Burgershot
Click to expand...
Click to collapse
attached
Thanks a million Ironia.
That got me past that file, now I need /system/lib/libSR_AudioIn.so do you have that as well?
I'm still unable to find a list of stock files that beats modifies so if, after reverting this file, I still have others to find I'll concentrate my efforts on extracting the contents of a stock ICS image. Right now the unyaffs.exe crashes when I try.
Thanks again
Your best bet is to fastboot flash system.img and boot.img from Google's factory images.
i quote rasengan82 , but anyway attached
up to you

[Q] (Stock Deodexing) -- boot.img failure on update.zip flash? Fix, Replace? Re-Zip?

I have a ZTE990 avail.
Currently I'm rooted with no other roms installed, simply stock, and odexed.
I've tried to manually de-odex using baksmali, Xultimate, etc. All were a pain, all wouldn't work properly.
I found someone and downloaded someone who just simply uploaded a Stock_Deodex.zip rom. Sounded perfect.
So I boot into CWM, try to update and...
assert failed: write_raw_image("/tmp/boot.img","boot" android
Click to expand...
Click to collapse
Since I have stock.. and am just trying to De-Odex.
Can I just unzip the Stock_Deodex.zip, delete the current (apparently faulty) boot.img, and replace it with one of the ones created with the cwm recovery, re-zip and attempt to update as usual?
Or since (if my understanding is correct), the only thing necessary for a system to become deodex is the files in /system/app and /system/restore.
Obviously when I un-zip stock_deodex.zip I have access to them. Could I possibly just replace the two folders (somehow?) and be properly de-odexed?
Any other options that I could use that'd be best?
Much appreciated to anyone who helps, thanks!

[Q] Add Stock ServiceMenu.apk (*#*# 7378423#*#*) to CM?

Hi Guys,
I was wondering if anyone had figured how to bring Sony's stock ServiceMenu.apk to work in CM or other custom ROMs that don't have it?
ServiceMenu (*#*# 7378423#*#* from dialer on stock ROM) is very handy for battery test, GPS test, Compass test and calibration, all the Sony device-specific hardware tests.
I tried to make a recovery-flashable zip by extracting ServiceMenu.apk from stock ROM but it doesn't install. I did more searching to find it also depends on files in /system/etc/permissions and /system/framework so I also added those to the zip, but still fails to install.
Can anyone with better experience chime in? I think a flashable Sony ServiceMenu.apk zip would be useful for every custom ROM on Sony devices.
So far I'll attach my zip which puts all the files where they should be, but App does not install. Signing problem? Odex problem? Please any ideas

Categories

Resources