(Discontinued) Prime 6.5/6.6/7.4.2 OEM V12/V17 flashed Twrp recovery (Discontinued)

[vampirefo]

i am try to get 4g lte band in india
by changing the baseband
kindly help me to fix this

I don't know anything about that, this thread is just installing roms via twrp?

Sent from my R1 HD using Tapatalk

 

[ramesh1686]

I don't know anything about that, this thread is just installing roms via twrp?

Sent from my R1 HD using Tapatalk

ok thanks for reply

 

[anbaude]

Please forgive my ignorance, but what does this rom do that Colton's original stock guide doesn't? I'm newish to android and rooting, and I'm genuinely curious.

 

[vampirefo]

Please forgive my ignorance, but what does this rom do that Colton's original stock guide doesn't? I'm newish to android and rooting, and I'm genuinely curious.

This is a twrp method, meaning you install via recovery, rather than via splashtool.

Twrp is both cord and cordless, splashtool requires cord and computer everytime twrp doesn't.

Use what ever method you like.
Sent from my R1 HD using Tapatalk

 

[ColtonDRG]

This is a twrp method, meaning you install via recovery, rather than via splashtool.

Twrp is both cord and cordless, splashtool requires cord and computer everytime twrp doesn't.

Use what ever method you like.
Sent from my R1 HD using Tapatalk

Please forgive my ignorance, but what does this rom do that Colton's original stock guide doesn't? I'm newish to android and rooting, and I'm genuinely curious.

My method does also restore stock recovery so that you can take OTAs. I don't know if the TWRP method does, but I imagine it doesn't since it seems rather pointless to me to flash TWRP so that you can subsequently flash a ROM that removes TWRP.

 

[vampirefo]

My method does also restore stock recovery so that you can take OTAs. I don't know if the TWRP method does, but I imagine it doesn't since it seems rather pointless to me to flash TWRP so that you can subsequently flash a ROM that removes TWRP.

Correct, I don't include stock recovery, if needed it can be flashed directly through twrp.

Place stock recovery.img on sdcard boot into twrp select install, switch from zip to img and select recovery.img then select recovery.

Twrp flashes three img, recovery.img boot.img system.img

Sent from my R1 HD using Tapatalk

 

[kal250]

So it appears we have a new 6.6 prime OTA

http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip

Aug security and "minor" fixes, has anyone applied yet? Anything broken? Don't want to loose bootloader unlock

 

[RainofOranges]

So it appears we have a new 6.6 prime OTA

http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip

Aug security and "minor" fixes, has anyone applied yet? Anything broken? Don't want to loose bootloader unlock

Applying it now. Will update later, or if not later then in the morning.

Edit: Alright so the OTA softbricked me, but it was from my own stupidity. I installed it, but it seems to re-lock the bootloader? It's definitely able to be unlocked still, but I had to reinstall the ROM to get there.

 

[vampirefo]

So it appears we have a new 6.6 prime OTA

http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip

Aug security and "minor" fixes, has anyone applied yet? Anything broken? Don't want to loose bootloader unlock

I downloaded it, and looked at the OTA, while small in size, it's a big update, bootloader, and preloader are both updated.

I won't apply until, I have more time, I will flash stock 6.5 before installing update.

Sent from my R1 HD using Tapatalk

 

[vampirefo]

It's definitely able to be unlocked still, but I had to reinstall the ROM to get there.

What does this mean? You installed 6.5 rom?

Sent from my R1 HD using Tapatalk

 

[RainofOranges]

What does this mean? You installed 6.5 rom?

Yes I had to boot TWRP and installed the 6.5 stock ROM.

 

[ariesgodofwar]

Applying it now. Will update later, or if not later then in the morning.

Edit: Alright so the OTA softbricked me, but it was from my own stupidity. I installed it, but it seems to re-lock the bootloader? It's definitely able to be unlocked still, but I had to reinstall the ROM to get there.

So on a clean 6.5 Prime install (I assume from the above you left bootloader unlocked), attempting to take 6.6 OTA soft-bricked you? Just want to make sure I understand what you are saying.

 

[RainofOranges]

So on a clean 6.5 Prime install (I assume from the above you left bootloader unlocked), attempting to take 6.6 OTA soft-bricked you? Just want to make sure I understand what you are saying.

I used the SPFT to flash the stock 6.1 ROM, then used the built-in OTA tool to download and install the 6.6 OTA. My phone went into a boot loop that I fixed by booting to fastboot mode, flashing TWRP, reformatting the data partition, and flashing the 6.5 TWRP ROM. After that, I flashed the stock recovery back since I had flashed TWRP before. From there I updated to 6.6 with no other issues.

 

[kal250]

I used the SPFT to flash the stock 6.1 ROM, then used the built-in OTA tool to download and install the 6.6 OTA. My phone went into a boot loop that I fixed by booting to fastboot mode, flashing TWRP, reformatting the data partition, and flashing the 6.5 TWRP ROM. After that, I flashed the stock recovery back since I had flashed TWRP before. From there I updated to 6.6 with no other issues.

Just confirming, after 6.6 OTA applied, you were able to re-unlock bootloader via fastboot??

 

[RainofOranges]

Just confirming, after 6.6 OTA applied, you were able to re-unlock bootloader via fastboot??

Yes I was.

 

[kal250]

Yes I was.

I'm debating if I want to give this a shot, see if it resolves any of the funky adopted storage issues I have been facing, that don't seem to appear in non prime, or just go back to non prime and wait to see of BLU releases OTA --- at this point, im not sure if Amazon is giving us monthly security updates, or if they are desperately sending out "fixes" aimed to close the debloat methods, and using security fixes as a front to push the OTAs -- lol, paranoid me :silly:

 

[RainofOranges]

I'm debating if I want to give this a shot, see if it resolves any of the funky adopted storage issues I have been facing, that don't seem to appear in non prime, or just go back to non prime and wait to see of BLU releases OTA --- at this point, im not sure if Amazon is giving us monthly security updates, or if they are desperately sending out "fixes" aimed to close the debloat methods, and using security fixes as a front to push the OTAs -- lol, paranoid me :silly:

I don't think any OTAs have affected any debloat methods that involve root. There's another thread on here that has a TWRP flashable .zip file that debloats the Prime ROM amazingly (and doesn't require root). I highly recommend that over manually removing everything with root and Titanium Backup. Even though I bought the non-Prime version, I run the Prime ROM because of the security updates.

 

[vampirefo]

I'm debating if I want to give this a shot, see if it resolves any of the funky adopted storage issues I have been facing, that don't seem to appear in non prime, or just go back to non prime and wait to see of BLU releases OTA --- at this point, im not sure if Amazon is giving us monthly security updates, or if they are desperately sending out "fixes" aimed to close the debloat methods, and using security fixes as a front to push the OTAs -- lol, paranoid me :silly:

You can open an OTA and see exactly what it is doing, this has nothing to due with amazon, Blu is updating the phone and applying security patches as they said.

Sent from my R1 HD using Tapatalk

 

[KazuDante]

so 6.6 is just security patches and nothing more?

 

[vampirefo]

I used the SPFT to flash the stock 6.1 ROM, then used the built-in OTA tool to download and install the 6.6 OTA. My phone went into a boot loop that I fixed by booting to fastboot mode, flashing TWRP, reformatting the data partition, and flashing the 6.5 TWRP ROM. After that, I flashed the stock recovery back since I had flashed TWRP before. From there I updated to 6.6 with no other issues.

Ok this makes sense, flashing all the way back to 6.1 and flashing this update would cause problems, as the patch is from 6.5 to 6.6.

Meaning you need to be using 6.5 to install this OTA.

Sent from my R1 HD using Tapatalk