[N910F][COH4/POI4][KNOX 0x0] Unofficial, re-packed Lollipop firmwares (multi CSC OXA)

_alexndr

Senior Member
Mar 1, 2013
2,784
17,408
203
I have decided to create this thread due to extraordinary success of my unofficial builds that I recently put in this thread :cool:

Main properties:

- PC Odin flashable (*.tar.md5 file)
- pure stock, NOT rooted, the only change is replaced CSC pack (unbranded multi CSC OXA package instead of original)
- contains CSC: BTU, CPW, DBT, ITV, KOR, XEF, XEO
- can be flashed on ANY N910F without a pit file
- it will NOT trip KNOX if you still have 0x0 :D


Downloads:

>> N910FXXU1COH4_N910FOXA1BOC3_alexndr.7z << (Android 5.1.1)

>> N910FXXU1POI4_N910FOXA1BOC3_alexndr.7z << (Android 5.0.1)

>> Recent unofficial builds for SM-N910F <<


Important notes:

- I do not have much time to expand this thread, so only multi CSC OXA builds will be available here
- I am not able to fix any bugs as all builds contains only ORIGINAL, unmodified partition images (to let you keep KNOX 0x0)
- Unofficial builds means => no OTA updates available (to restore OTA updates you just need to fash OFFICIAL firmware from Sammobile)
- In theory it is not possible to brick your phone or trip KNOX using these builds, but I have to write it (just in case) - I am not responsible for anything that will happen to your phone
 
Last edited:

alessandro_xda

Senior Member
Feb 8, 2007
440
84
58
Bologna
I have decided to create separate thread due to the extraordinary success of my unofficial compilation that I recently put in this thread :cool:

Main properties:

- PC Odin flashable (*.tar.md5 file)
- pure stock, NOT rooted, the only change is replaced multi CSC pack (putted multi CSC OXA package instead of original)
- contains CSC: BTU, CPW, DBT, ITV, KOR, XEF, XEO
- can be flashed on ANY N910F without a pit file
- it will NOT trip KNOX if you still have 0x0 :D


Downloads:

>> Recent unofficial builds for SM-N910F <<


Important notes:

- I do not have too much time to expand this thread, so only multi CSC OXA builds will be available here
- I am not able to fix any bug as all builds contains only ORIGINAL, unmodified partition images (to let you keep KNOX 0x0)
- Unofficial builds means => no OTA updates available (to restore OTA updates you just need to fash OFFICIAL firmware from Sammobile)
- In theory it is not possible to brick your phone or trip KNOX using these builds, but I have to write it (just in case) - I am not responsible for anything that will happen to your phone
thanks! it works perfectly
 
  • Like
Reactions: _alexndr

nikc0069

Senior Member
Jul 6, 2006
930
82
0
Brighton & Hove
How does a person go about a repack? As I still don't know if the EE BOD2 build includes wifi calling. If it does, then I'll be needing to flash it, but it won't be repacked as it isn't Multi-CSC - but won't flash on my phone due to the large /preload partition.
 

RandyKaoss

Senior Member
Apr 5, 2009
220
34
0
Oxford
Flashing now. Interested to see if this firmware fixes the problems with the BBC Media Player. Samsung have fixed it on the S5 and S6, according to the Play store page.
 

RandyKaoss

Senior Member
Apr 5, 2009
220
34
0
Oxford
Didn't work for me despite B0C7 appearing to be earlier than B0D2.
Yeah, just tried iPlayer on BOD2 - still broken :( Serious PITA not having access to BBC content on the move. Even radio streaming is glitchy.

Was trying to listen to the football at the weekend, and even with full 4G+ signal the sound kept breaking up. Switched to TuneIn Radio Pro - flawless! Crazy.
 

StevePritchard

Senior Member
Dec 27, 2005
2,113
522
183
Frodsham, Cheshire, UK
Yeah, just tried iPlayer on BOD2 - still broken :( Serious PITA not having access to BBC content on the move. Even radio streaming is glitchy.

Was trying to listen to the football at the weekend, and even with full 4G+ signal the sound kept breaking up. Switched to TuneIn Radio Pro - flawless! Crazy.
I'm struggling to see how it can be Samsung's fault when all the other players seem to work just fine.
 

RandyKaoss

Senior Member
Apr 5, 2009
220
34
0
Oxford
I'm struggling to see how it can be Samsung's fault when all the other players seem to work just fine.
That was also my view (i.e. the BBC are at fault) but if you read the info on the Google Play store for the BBC Media Player, it says:

"Users of Samsung Galaxy devices - especially the S5 and Note 4 - may be unable to play content after the upgrade to Android Lollipop (5.x), and may find that the BBC Media Player app crashes after a few seconds. This was due to a bug in the Samsung firmware which has now been fixed. Please ensure you update to the latest version of firmware (G900FXXU1BOC7) for your device."

G900FXXU1BOC7 is a Galaxy S5 firmware though. I wonder what version of the Note 4 firmware will have the same fix?
 

StevePritchard

Senior Member
Dec 27, 2005
2,113
522
183
Frodsham, Cheshire, UK
That was also my view (i.e. the BBC are at fault) but if you read the info on the Google Play store for the BBC Media Player, it says:

"Users of Samsung Galaxy devices - especially the S5 and Note 4 - may be unable to play content after the upgrade to Android Lollipop (5.x), and may find that the BBC Media Player app crashes after a few seconds. This was due to a bug in the Samsung firmware which has now been fixed. Please ensure you update to the latest version of firmware (G900FXXU1BOC7) for your device."

G900FXXU1BOC7 is a Galaxy S5 firmware though. I wonder what version of the Note 4 firmware will have the same fix?
Yeah, I had read that, but it does make you wonder how every other media player managed to avoid the "Samsung bug", but the BBC fell foul of it.
 

RandyKaoss

Senior Member
Apr 5, 2009
220
34
0
Oxford
Yeah, I had read that, but it does make you wonder how every other media player managed to avoid the "Samsung bug", but the BBC fell foul of it.
Indeed! I mean even Sky Go still works! ;)

I just emailed the Media Player dev team and suprisingly got an almost immediate response from the Product Manager:

"We've been trying to get an estimate for a fix from Samsung for some time, and contacted them again yesterday. We'll keep pushing – I'm sorry it's taking so long for this to get fixed. We're also looking into whether we might be able to create a workaround to resolve the issue. In the long-term, of course, the goal is to remove the need for the separate Media Player app entirely; we hope to have achieved this in the native BBC iPlayer app within a few months."

<Apologies to the OP for veering off topic!!>
 
  • Like
Reactions: StevePritchard