Metro PCS Samsung Galaxy S3 Official Android 4.1.2 Jelly Bean Update Rolls Out R530MVQAMB2

Samsung has just started pushing the official Android 4.1.2 Jelly Bean update for Metro PCS Samsung Galaxy S3 variants SCH-R530M. The latest 4.1.2 software build version is JZO54K.R530MVQAMB2 or with a new baseband of R530MVQAMB2. The 4.1.2 brings additional enhancement “camera 1.5” which makes a huge differences to the picture details and quality, all other stuff is for you to discover since changelog is not available. This update is push via OTA (over the air) and might also made available thru Kies, since we have been spotted this R530MVQAMB2 4.1.2 stock firmware in Samsung Kies server a few days ago. To check it out via OTA,just hit your device Settings>>About>>Check for Update.

R530MVQAMB2 4.1.2 Firmware
Official Android 4.1.2 Jelly Bean update software build R530MVQAMB2 on Metro PCS Samsung Galaxy S III SCH-R530M – screenshot

If you already updated your Metro PCS Galaxy S3 devices to this Android 4.1.2 Jelly Bean, just do share to us how this update performs.

2 comments

  1. It’s almost impossible to root 4.1.2 without voiding the phone’s warranty or jeopardizing future OTA updates.

    The DebugFS exploit rooting method no longer works after the 4.1.2 update. Now you have to use ODIN to flash in root, which increments the flash counter and changes the device status from “normal” to “modified” or “custom”. A changed device status prevents the phone from receiving future OTA updates.

    I used CF-Auto-Root via ODIN to root 4.1.2, (which is currently the only rooting method that does not flash in a custom recovery like CWM or TWRP; all other working rooting method flashes in a custom recovery that overrides the stock recovery.) Then I Triangle Away to reset the flash counter to 0. Unfortunately, the Device Status in the Settings menu is “Modified”. I have to constantly run Triangle Away with the “Tracker” feature on to change and keep the device status to “Normal”. Whenever I turn off the Tracker, the Device Status changes back to “Modified”.

    It is frustrating.

  2. I think using Verizon S3 rooting technique can be also applied for MPCS S3’s, on which the process includes installing 4.0.4 bootchain>>install CWM>>applied SuperSU kernel and then restore the 4.1.2 bootchain. The process is bit tricky but some few devs might come up something an easy rooting method soon.

Comments are closed.