Quote:
|
Originally Posted by luv2chill
Quote:
|
Originally Posted by bujd
Quote:
|
Originally Posted by helmi_c
guys... please be ware... the new update hv new Bootloader in it... thats makes old rom unusable... just dont upgrade it yet...
I've already make a new Kitchen from this base mix with high storage capacity for OEM stuff like my new core rom... but it still not for user yet.. please wait a few more days and you'll hv the kitchen from this base for user...
|
Not sure I understand. Are you saying that, even after removing the files Luv identified ( bl_g3.nbf and bl_g4.nbf ) we'll still lose our ability to flash other ROMs? |
No at this point the easiest/best way to flash this rom is to open it up with winrar, extract out the nk.nbf, and use an older version of the apache flashing app to install it. Use the NoID app if you get the country code ID (or if you know how, use the HTC64 tool to decode and re-encode the ROM with the correct Carrier ID string for your device... then you can use the regular apache flashing app).
Doing that will allow you to use the new rom without any danger to your bootloader. |
Thanks. I have rare freezing issues with the R4 ROM (I actually think its from running Claunch, not the ROM) and want to see if an "official" ROM experiences the same issues.
I don't know how to re-encode the ROM with the correct carrier ID string. Is that just a matter of changing the carrier ID in the HTC64 tool to SPCS_001? Or is there something more to it?