[FIRMWARE] <I535VRUCML1> (MODEM/RPM/TZ/SBL) Verizon SGS3 (SCH-I535)
No, I do not have a full I535VRUCML1 firmware package for you.
Yes, I somewhat lied in the title of this thread. But I did it for a good reason: to get your attention.
Mods - I'm sure you'll understand.
You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well. Even if you manage to flash an ENTIRE old bootchain over VRUCML1, you'll brick because they trip a qfuse that prevents it from working. More info about qfuse by djrbliss here: http://t.co/myb0LIrN6e
Just stick with VRUBMF1, trust me.
These firmware updates have, up until now, consisted of several partitions that we update:
- tz (trustzone)
- rpm (resource/power management)
- sbl[1,2,3] (secure bootloaders)
- NON-HLOS (modem/baseband)
Due to the way Samsung and Verizon have chosen to proceed with future updates (following what they do for the Galaxy S4) we cannot flash all these partitions anymore (see above) and retain our unlocked bootloader. We CAN
, however, update the baseband as it's not signed.
My recommendation: if you aren't already on MF1 firmware (below), flash that. Then update your baseband with this: http://invisiblek.org/sch-i535/modem..._ML1_modem.zip
Latest firmware (aka AIO) linked here: http://invisiblek.org/d2firmware.html
Find all firmware (aka AIO) packages here: http://invisiblek.org/sch-i535/firmware/
#verizons3 | #sgs4 | #cm-htc @ freenode