[Android Software/Hacking General [Developers Only]] Desmanto:
Can you also upload the original lib before patch? Just wanna run a diff check between original vs patched. Thanks

I read ur post above, and think if stagefright lib doesn't affect much on the media playing, why don't just remove all of them altogether? So I check mine, there are

libstagefright.so

libstagefright_amrnb_common.so

libstagefright_avc_common.so

libstagefright_chromium_http.so

libstagefright_enc_common.so

libstagefright_foundation.so

libstagefright_memutil.so

libstagefright_omx.so

libstagefright_soft_aacdec.so

libstagefright_soft_aacenc.so

libstagefright_soft_amrdec.so

libstagefright_soft_amrnbenc.so

libstagefright_soft_amrwbenc.so

libstagefright_soft_flacenc.so

libstagefright_soft_g711dec.so

libstagefright_soft_h264dec.so

libstagefright_soft_h264enc.so

libstagefright_soft_mp3dec.so

libstagefright_soft_mpeg4dec.so

libstagefright_soft_mpeg4enc.so

libstagefright_soft_rawdec.so

libstagefright_soft_vorbisdec.so

libstagefright_soft_vpxdec.so

libstagefright_wfd.so

libstagefright_yuv.so

libstagefrighthw.so

FYI, my phone is ZTE N986, JB 4.2 using MT6589, 2 years old already. So there is no hope of patch from the vendor anymore. Need to think of our own solution.

I haven't try the build.prop method yet, directly jump to my own method. Using the Root Explorer, selecting each of the lib was too long for me (:) I'm lazy tapping each of them). So I just go to Es File Explorer, using the interval selection method which I discovered early this month, move all of the libstagefright* file to new folder /system/lib/stagefright/. Then I tried play video using MX player, seems fine. So no problem.

Proceed to reboot the phone to see if there is any problem. After pressing reboot, phone just go dark, no vibration to indicate successful shutdown. Wait for 2 minutes still no starting. So I just hold down power button for 10 seconds to force restart it. Now it is booting to the first boot logo. Then at the second logo, the phone just went dark, but it is on (the backlight is still on). OK, try again, still went dark.

So, I just learn that these lib may not removed from the /system/lib folder. Maybe they are used in the booting process to play the boot animation (my phone second logo is animation). No problem, I can always boot to TWRP, use the file manager and move the lib back to the original folder. I also have TWRP backup just last night, so anything gone wrong, I still have the safety button to press. There u go, power + vol up 8 seconds. 1st logo fine, second logo still went dark :eek: Try again for 3 times, still same result. So it seems the TWRP (or maybe another custom recovery) also use these lib. No recovery option, My phone is gone?

Not yet, i still have another original ROM backup at my PC. :) Fortunately, I always do triple to quadruple backup before doing anything stupid. Proceed to flash the phone using SPFT, only flashing the /system partition. After done, i still need to restore the /system from TWRP to my previous night backup. (since I have made a lot of modification to the /system). The phone then boots normally again.

Lesson Learned : Do not delete or remove the libstagefright* file from the /system/lib/

Removing the permission might be a bad idea as well, since we don't know if the system need the file while booting as well. Maybe this is why the stagefright exploit is too difficult to patch, since it affects a lot of things.

Now, I will just try the build.prop solution, while waiting for a working lib patching solution.